Yes

On May 4, 2016 7:05 AM, "Ignacio Bravo" <ibravo@ltgfederal.com> wrote:
Did you try doing an ironic node-delete and recreating the node again?

IB

On May 4, 2016, at 6:59 AM, Mohammed Arafa <mohammed.arafa@gmail.com> wrote:

oh and ironic node-show $id indicates that there are no reservations on these nodes but it still says locked!

On Wed, May 4, 2016 at 6:50 AM, Mohammed Arafa <mohammed.arafa@gmail.com> wrote:
so late last night i had this problem and searched google and found myself asking the same question after 4 months.

it appears there is a way (still untested by me but hopefully someone here can verify) to remove the lock
https://bugs.launchpad.net/ironic/+bug/1250348 states to run
   ironic node-update ba28de78-f300-4adb-b3e9-eb2ff137f8d7 replace reservation=fake

i am kind of leery of setting it to fake tho


On Tue, Jan 26, 2016 at 11:46 AM, Mohammed Arafa <mohammed.arafa@gmail.com> wrote:

I did an ironic node delete * and did everything over again. No lock. I did not change my hosts file.
Strange behaviour though

On Jan 26, 2016 10:22 AM, "Ignacio Bravo" <ibravo@ltgfederal.com> wrote:

This is what I have in my undercloud VM /etc/hosts file:

 

127.0.0.1   undercloud.mydomain undercloud localhost localhost.localdomain localhost4 localhost4.localdomain4

::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

 

 

--

Ignacio Bravo

LTG Federal

ibravo@ltgfederal.com

 

From: rdo-list-bounces@redhat.com [mailto:rdo-list-bounces@redhat.com] On Behalf Of Mohammed Arafa
Sent: Tuesday, January 26, 2016 7:52 AM
To: rdo-list@redhat.com
Subject: [Rdo-list] [rdo-manager] node locked by localhost.localdomain

 

hi

i am attempting introspection (for the umpteenth time) and i keep getting the error that says node is locked by localhost.localdomain.

it is extremely puzzling because i have a line in /etc/hosts just for my undercloud.

(hmm.. does my 127.0.0.1 undercloud.hostname need to be on its own line or with the 127.0.0.1 locahost.localdomain line?)

i found an rhosp bug since last year with no activity (1232997)  that  indicate the node may be a duplicate. however i am performing an ironic node-delete uuid before beginning introspection.


anybody got any any ideas?




--



--