attempting to delete locked maas node results in juju marking valid cloud credentials as invalid
Bug #1952792 reported by
Steven Parker
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Replicate with MAAS node that has been locked.
Remove node with:
juju remove-machine and/or --force
juju status will yield
foundations-maas maas_cloud 2.9.18 unsupported 22:01:30Z suspended since cloud credential is not valid
Workaround:
juju update-credentials maas_cloud maas_cloud_
and/or
juju set-credential -m lma maas_cloud maas_cloud_
NOTE: Loss of cloud credentials can lead to actions such as add-machine, remove-machine failing to complete or error out. These actions simply hang. In fact remove-machine --force will also fail.
Changed in juju: | |
milestone: | 2.9.23 → 2.9.24 |
Changed in juju: | |
milestone: | 2.9.24 → 2.9.25 |
Changed in juju: | |
milestone: | 2.9.25 → 2.9.26 |
Changed in juju: | |
milestone: | 2.9.26 → 2.9.27 |
Changed in juju: | |
milestone: | 2.9.27 → 2.9.28 |
Changed in juju: | |
milestone: | 2.9.28 → 2.9.29 |
Changed in juju: | |
milestone: | 2.9.29 → 2.9.30 |
Changed in juju: | |
milestone: | 2.9.30 → 2.9-next |
description: | updated |
description: | updated |
tags: | added: canonical-is |
Changed in juju: | |
milestone: | 2.9-next → none |
To post a comment you must log in.
If Juju makes an cloud (MAAS in this case) API call, if the cloud responses with codes 401, 403 etc then Juju will deem the credential to be invalid as the api call was rejected as unauthorised.
It seems that here MAAS might be responding to attempt to delete a locked node with 403, thus triggering the juju to deem the credential as invalid. We need to audit what return codes MAAS uses and see what's appropriate to use to trigger the invalid credential behaviour in juju.