Red Hat Bugzilla – Bug 1477120
Openstack Ocata3 fails due to timeout error because of Nova-Scheduler EXIT code 1 (failure of this service start).
Last modified: 2017-08-04 10:23:09 EDT
Created attachment 1307474 [details]
Description of problem:
Openstack Ocata-3 install fails on Centos 7.3, RedHat 7.3, Scientific Linux 7.3.
Version-Release number of selected component (if applicable):
Install OS (minimal install)
Follow this manual: https://www.rdoproject.org/install/packstack/
Steps to Reproduce:
1. Stop + delete all mentioned services in manual.
2. Run 'sudo packstack --allinone'
3. Check 'sudo journalctl -xe' and open install log to see the errors:
Got many errors:
Journalctl -xe: Failed to Start Nova Scheduler server
packstack output: ERROR: Error appeared during puppet run: 192.168.88.246_controller.pp
Error: /Stage[main]/Nova::Db::Sync/Exec[Nova-db-sync]: Failed to call refresh: Command exceeded timeout
log file output: Failed to apply catalog: Command 'openstack ["flavor", "list", "--quiet", "--format", "csv", ["--long", "--all"]]' has been running for more than 40 seconds (tried 4 for total of 170 seconds"
Install of Openstack without timeout error.
Used Hyper-V with 4 cores CPU, 8 Gb of RAM, 1 ext NIC.
Tried many times with different variants of package installation (minimal install, server with gui) on Centos, RadHat with Developers subscription, amd Scientific Linux. All the time i am facinf with such an error. Have not managed to find workaround.
1. Update from 2.7 python to 3.6 version.
2. Delete iptables, selinux with postfix.
3. Delete all listening sockets and programs which could interrupt Openstack installation.
Still no luck.
Ocata Version: centos-release-openstack-ocata-1-2.el7.noarch
I have already installed Openstack Ocata according to the following guide: https://www.rdoproject.org/install/packstack/ with VmWare Player 12.5.7 ver.
Installation has been passed without any issues from the first attempt.
So, looks like issue is only reproducible when use Hyper-V with Centos/RedHat/Scientific Linux as guest OS. Probably some additional configuration is needed for Hyper-V, e.g. like it is in VmWare player there is virtualization options but in Hyper-V there is no any.