[2.1.5] node marked broken then fixed retains auto assigned IP in ready state
Bug #1678231 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned |
Bug Description
I have a node that failed deployment, with an auto assigned IP. I marked it as broken and powered it off. The node still has the auto assigned IP.
Even after I mark it as fixed and it goes back to Ready, it still has the auto assigned IP. I have to deploy and then release the node to get it to release the auto assigned IP.
tags: | added: oil oil-2.0 |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in maas: | |
milestone: | 2.2.0 → 2.2.x |
Changed in maas: | |
milestone: | 2.2.x → 2.3.0 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
To post a comment you must log in.
The question is, what happens if the node actually holds the IP address? for example, failed deployment failed after the machine was configured to use /e/n/i that IP address, you mark it broken, and then you turn it on manually to investigate
The machine holds the IP, and when you turn it on, it conflicts with another machine MAAS has... that would be bad....
I dont think we can safely assume that because the machine is broken (when set from failed deployment/ deployment) , it wont hold the IP for it.