hextht opened a new issue #3866: New installation of v 4.13 on Centos 7 completes successfully, but the svms end up in a non-healthy state. URL: https://github.com/apache/cloudstack/issues/3866 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Other ##### COMPONENT NAME <!-- --> ~~~ svm deployment ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> Basic networking. I am configuring cloudstack with the configuration wizard. ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> Centos 7 I am using mysql-connector-java-5.1.25-3.el7 instead of the last version, because the installation fails with mysql-java-connector v.8.0.19-1. ##### SUMMARY <!-- Explain the problem/feature briefly --> I am following the instructions for quick installation of v 4.13 on Centos 7 (http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html) The installation completes successfully, the configuration wizard also completes with no error, but then both svms - console and secondary storage seems to be incomplete. Here are the symptoms that i noticed: - They do not have IP addresses assigned, altough the in the control panel there are IPs listed. - Inside the VMs i looked for the check-health script, but the /usr/local/cloud directory is empty. - The cloud agent inside the svms is not running and when i try to start it, it fails. - In the /var/log/cloud.log there are such entries: No suitable VirtIO port was found in /dev/virtio-ports - The templates listed in the UI are actually not present - they do not appear when i try to create a VM, but considering that the svms are not accessible i guess it is to be expected - After manually restarting the VMs, they do restart, but the control panel sees tham in "starting" state and remains like that forever. alert: Console proxy creation failure. zone: B5, error details: We cannot stop VM[ConsoleProxy\|v- 1-VM] when it is in state Starting -- - There are alerts related to both svms : - Console proxy creation failure. zone: B5, error details: null - Secondary Storage Vm creation failure. zone: B5, error details: null -- I have repeated the installation several times on different server, and every time the installations ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> <!-- Paste example playbooks or commands between quotes below --> ~~~ Install Centos 7.5 minimal with one NIC and follow the instructions for quick installation: http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html ~~~ <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ After the initial configuration wizard completes successfully, the svms should be in a healthy state. ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ The configuration wizard completes with no error, but the svms are not complete or not in a healthy state - resulting in an overall non-functional Cloudstack installation ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
