MAAS

[2.1.5] node marked broken then fixed retains auto assigned IP in ready state

Bug #1678231 reported by Jason Hobbs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned
MAAS 2.3.x

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.

See original description
Tags: oil oil-2.0
Jason Hobbs (jason-hobbs)
tags: added: oil oil-2.0
description: updated
description: updated
description: updated
Revision history for this message
Andres Rodriguez (andreserl) wrote :

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.

Changed in maas:
status: New → Incomplete
milestone: none → 2.2.0
status: Incomplete → Opinion
Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

Ok, changed the title of the bug. It definitely shouldn't have the IP when it's back in ready state.

summary: - [2.1.5] broken node retains auto assigned IP
+ [2.1.5] node marked broken then fixed retains auto assigned IP in ready
+ state
Changed in maas:
status: Opinion → New
Jason Hobbs (jason-hobbs)
description: updated
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.2.0 → 2.2.x
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.2.x → 2.3.0
importance: Undecided → High
status: New → Triaged
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.3.0 → 2.3.x
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release.
Due to the original date of the bug report, we are currently marking it
as Invalid. If you believe this bug report still valid against the
latest release of MAAS, or if you are still interested in this, please
re-open this bug report.

Thanks

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

Other bug subscribers

Remote bug watches

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