Can't deploy due to "Next IP address to allocate from XXX has been observed previously""
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Undecided
|
Unassigned |
Bug Description
We occasionally will see issues failing to deploy machines (a vm named 'crdvm3' in this case) due to not being able to assign an IP address. The logs look like:
021-10-
2021-10-
2021-10-
2021-10-
2021-10-
2021-10-
2021-10-
Two things were observed here:
* The IP '192.168.102.155' was not seen in the subnet web UI page for "192.168.102.0/24". If it was "observed", shouldn't it show up in the used list as such?
* Why does it only try one IP address then give up?
After restarting maas, we can deploy crdvm3 again (although with a different IP now).
Version: 2.9.3~beta2 (9199-g.6e6ee4dcd) from the snap
The message about the IP should just be a warning.
What's interesting there is this message:
2021-10- 21T16:03: 19.771120+ 00:00 common maas.node: [info] crdvm3: Aborting DEPLOYING and reverted to ALLOCATED. Unable to power control the node. Please check power credentials.
which seems to point to invalid BMC credentials.
Could you please confirm that the machine can be powered on/off with the current configuration?