You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Yusei Nishioka (JIRA)" <ji...@apache.org> on 2018/01/28 07:49:00 UTC
[jira] [Created] (CLOUDSTACK-10256) When using ConfigDrive, Cannot
deploy vm after rebooting the management server.
Yusei Nishioka created CLOUDSTACK-10256:
-------------------------------------------
Summary: When using ConfigDrive, Cannot deploy vm after rebooting the management server.
Key: CLOUDSTACK-10256
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10256
Project: CloudStack
Issue Type: Bug
Affects Versions: 4.11.0.0
Environment: CentOS7 Management server, vSphere5.5, NFS as primary and secondary storages.
Reporter: Yusei Nishioka
Attachments: management-server.log
I'm testing ConfigDrive behavior with CloudStack 4.11RC2.
At first test, ConfigDrive worked.
Then, I rebooted management server and I've deploy new VM.
However that vm didn't deploy with below message.
Unable to start a VM due to unavailable resources
I attached management-server.log at that time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)