본문 바로가기
Tech/Openstack

TripleO에서 deployment가 실패 했을 때 리셋하기

by 타이호 2017. 12. 22.
반응형

overcloud stack을 삭제해도 provision state가 꼬였는지 failed로 나오는 경우가 있다

[stack@manager templates]$ openstack baremetal node list
+--------------------------------------+-------------+--------------------------------------+-------------+--------------------+-------------+
| UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+-------------+--------------------------------------+-------------+--------------------+-------------+
| f3096509-1e5b-46e3-8c69-9d6018c30af8 | controller1 | d38378e5-de86-42ca-9377-5b8884f6fc3e | power off | deploy failed | False |
| 1719a73c-d60c-460d-a3d4-b33a72daa428 | compute1 | ae3ecb82-54d7-4a14-b8e3-256a591039c4 | power off | deploy failed | False |
+--------------------------------------+-------------+--------------------------------------+-------------+--------------------+-------------+

이럴때는 해당 instance uuid를 unset 하고 해당 상태를 다시 undeploy 상태로 변경한다

openstack baremetal node unset --instance-uuid f3096509-1e5b-46e3-8c69-9d6018c30af8
openstack baremetal node unset --instance-uuid 1719a73c-d60c-460d-a3d4-b33a72daa428

openstack baremetal node undeploy 1719a73c-d60c-460d-a3d4-b33a72daa428
openstack baremetal node undeploy f3096509-1e5b-46e3-8c69-9d6018c30af8
openstack baremetal node list

+--------------------------------------+-------------+---------------+-------------+--------------------+-------------+
| UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+-------------+---------------+-------------+--------------------+-------------+
| f3096509-1e5b-46e3-8c69-9d6018c30af8 | controller1 | None | power off | available | False |
| 1719a73c-d60c-460d-a3d4-b33a72daa428 | compute1 | None | power off | available | False |
+--------------------------------------+-------------+---------------+-------------+--------------------+-------------+

반응형

댓글0