I attempted to hard-reboot it, and it went into an error state. The
initial error in the server status was
{'message': 'Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainCreateWithFlags)', 'code': 500, 'created': '2019-07-25T07:25:25Z'}
After a short period, I tried again and got a different error state
{'message': "internal error: process exited while connecting to monitor: lc=,keyid=masterKey0,iv=jHURYcYDkXqGBu4pC24bew==,format=base64 -drive 'file=rbd:volumes/volume-41553c15-6b12-4137-a318-7caf6a9eb44c:id=cinder:auth_supported=cephx\\;none:mon_host=172.24.0.56\\:6789", 'code': 500, 'created': '2019-07-25T07:27:21Z'}
I don't know if this is a setting or a bug. Better to report and close than not say anything I guess.
It would appear Nova is revealing information that may be sensitive in error messages
http:// lists.openstack .org/pipermail/ openstack- infra/2019- July/006426. html
I attempted to hard-reboot it, and it went into an error state. The
initial error in the server status was
{'message': 'Timed out during operation: cannot acquire state change lock (held by monitor= remoteDispatchD omainCreateWith Flags)' , 'code': 500, 'created': '2019-07- 25T07:25: 25Z'}
After a short period, I tried again and got a different error state
{'message': "internal error: process exited while connecting to monitor: lc=,keyid= masterKey0, iv=jHURYcYDkXqG Bu4pC24bew= =,format= base64 -drive 'file=rbd: volumes/ volume- 41553c15- 6b12-4137- a318-7caf6a9eb4 4c:id=cinder: auth_supported= cephx\\ ;none:mon_ host=172. 24.0.56\ \:6789" , 'code': 500, 'created': '2019-07- 25T07:27: 21Z'}
I don't know if this is a setting or a bug. Better to report and close than not say anything I guess.