stop a server right after deploy may lead to ssh key not inserted
Bug #1770065 reported by
jichenjc
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zVM Cloud Connector |
Confirmed
|
Low
|
nafeiyang |
Bug Description
This is a race condition and might not reproduced in manual stesp
if you create a server then right after it's ACTIVE, stop this server then you might get a server which doesn't change the hostname or ssh key not injected
this might be caused by punch or cloudinit or other unknow issue
Changed in python-zvm-sdk: | |
assignee: | nobody → nafeiyang (nafeiy) |
status: | New → Confirmed |
importance: | Undecided → Low |
To post a comment you must log in.
I think this is caused by IP conflict issue?