Can't deploy due to "Next IP address to allocate from XXX has been observed previously""

Bug #1948051 reported by Francis Ginther
6
This bug affects 1 person
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-21T16:03:18.225801+00:00 common maas.node: [info] crdvm3: Status transition from READY to ALLOCATED
2021-10-21T16:03:18.236797+00:00 common maas.node: [info] crdvm3: allocated to user jenkins
2021-10-21T16:03:18.903663+00:00 common maas.node: [info] crdvm3: Status transition from ALLOCATED to DEPLOYING
2021-10-21T16:03:19.441556+00:00 common maas.subnet: [warn] Next IP address to allocate from '192.168.102.0/24' has been observed previously: 192.168.102.155 was last claimed by b4:96:91:61:dd:30 via enp6s0f1 (physical) on common at 2021-06-10 20:09:24.108795.
2021-10-21T16:03:19.714449+00:00 common maas.subnet: [warn] Next IP address to allocate from '192.168.102.0/24' has been observed previously: 192.168.102.155 was last claimed by b4:96:91:61:dd:30 via enp6s0f1 (physical) on common at 2021-06-10 20:09:24.108795.
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.
2021-10-21T16:03:19.776280+00:00 common maas.node: [info] crdvm3: Status transition from DEPLOYING to ALLOCATED

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

Revision history for this message
Alberto Donato (ack) wrote :

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?

Changed in maas:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.