undertaker worker failing to destroy storage because of bad cloud credentials

Bug #1830216 reported by Junien Fridrick on 2019-05-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


Running juju 2.5.4, I have a model that's stuck in status "destroying" because of the following :

2019-05-23 13:15:56 ERROR juju.worker.dependency engine.go:636 "undertaker" manifold worker returned unexpected error: destroying storage: listing volumes:
Please subscribe to the requested Amazon service.
You are currently not authorized to use it.
New Amazon accounts might take some time to be activated while
your details are being verified.: You are not authorized to perform this operation. (UnauthorizedOperation)

As a result, the undertaker worker is being constantly restarted.

Note : bug 1827988 is related.


Changed in juju:
status: New → Triaged
importance: Undecided → High
Ian Booth (wallyworld) on 2019-05-23
Changed in juju:
milestone: none → 2.6.3
assignee: nobody → Anastasia (anastasia-macmood)
Changed in juju:
status: Triaged → In Progress
milestone: 2.6.3 → none
Anastasia (anastasia-macmood) wrote :

PR for develop (heading for 2.7): https://github.com/juju/juju/pull/10259

Anastasia (anastasia-macmood) wrote :

2.6.3 is going through Solutions QA , so re-targeting 2.6 work for 2.6.4

Changed in juju:
status: In Progress → Fix Committed
milestone: none → 2.7-beta1
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers