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)
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)