[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

Marking Ubuntu neutron task Fix Released (as pike shipped with Artful and in the Pike Ubuntu Cloud Archive) ** Changed in: neutron (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

Reviewed: https://review.openstack.org/424247 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cb6eae20fae1f5e46cb2af4f0b0dc5368074580b Submitter: Jenkins Branch:master commit cb6eae20fae1f5e46cb2af4f0b0dc5368074580b Author: Sam Betts Date: Mon

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

** Changed in: neutron (Ubuntu) Status: New => Triaged ** Changed in: neutron (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

** Changed in: ironic (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect notification to nova about ironic baremetall port (for

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

** Changed in: neutron Importance: Undecided => Low ** Changed in: neutron Milestone: None => pike-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect notification to

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

** Tags added: mitaka-backport-potential -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

** Changed in: ironic (Ubuntu) Status: New => Triaged ** Changed in: ironic (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

Reviewed: https://review.openstack.org/424248 Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=cbdf5076d37df61d2e9c46a0a73c7ad65652b866 Submitter: Jenkins Branch:master commit cbdf5076d37df61d2e9c46a0a73c7ad65652b866 Author: Sam Betts Date: Mon

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

Fix proposed to branch: master Review: https://review.openstack.org/424247 ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => Sam Betts (sambetts) ** Changed in: ironic Status: New => In Progress ** Changed in: ironic

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

This "fix" was done to support this bug: https://bugs.launchpad.net/neutron/+bug/1606229 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656010 Title: Incorrect notification to nova about ironic

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

When a Nova instance is deleted, it is fully removed from nova when the node enters the cleaning state.From that point onwards the node has no ties to a nova instance. As part of cleaning Ironic needs to create a neutron port to attach the node to the cleaning network, for this Ironic talks

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

I asked a colleague who works on Ironic about this, and I'm left wondering the same as Boden. My coworker did mention however that "the instance is deleted immediately when Ironic is set to clean." If I'm understanding him right, it's possible that Nova takes a bit to actually delete the instance,

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

Thanks for the comment. This area of the code is new to me, so I'm waiting for some neutron folks to come on-line that can help me triage this. Based on what I do know, I'm a little confused. How is neutron supposed to change the port.device_id in the clean node case so that it no longer has the

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

Problem is that 'ironic node uuid' is not the same as 'nova instance uuid'. When instance (created by ironic provision) boots, this is proper (?) behavior. But when ironic cleans node, there is no instance in nova. (Actually, in my stand, at that moment there is no nova instances at all, only

[Bug 1656010] Re: Incorrect notification to nova about ironic baremetall port (for nodes in 'cleaning' state)

Still looking into this... Based on the code I see, the port.device_id is used as the server_uuid in the notification which corresponds to the logs provided above. It's not yet clear to me why/how this should be different for this ironic case. -- You received this bug notification because you