zVM Cloud Connector

stop a server right after deploy may lead to ssh key not inserted

Bug #1770065 reported by jichenjc
6
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

jichenjc (jichenjc)
Changed in python-zvm-sdk:
assignee: nobody → nafeiyang (nafeiy)
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
nafeiyang (nafeiy) wrote :

I think this is caused by IP conflict issue?

Revision history for this message
jichenjc (jichenjc) wrote :

no, the root cause is cloud-init startup process seems have some either code bug or configuration issue , in any case the described step can reproduce this error in mass test (our CI ,for example)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.