Rubygem-Staypuft: Nova deployment gets paused with error on installing the compute nodes. Get the following in the report: change from absent to present failed: Execution of '/usr/bin/nova-manage floating create 10.8.30.100/31' returned 1: Command failed Environment: rhel-osp-installer-0.1.6-5.el6ost.noarch openstack-puppet-modules-2014.1-19.9.el6ost.noarch openstack-foreman-installer-2.0.16-1.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch Steps to reproduce: 1. install rhel-osp-installer. 2. Configure/run a nova deployment with Tenant Network Type "Flat with DHCP" a. Floating IP range for external network: 10.8.30.100/31 b. Private IP range for tenant networks: 192.168.32.0/24 Result: The deployment gets paused with error upon installing the compute nodes - 60%. Expected result: A successful deployment.
Sasha, can you see what is in the nova-manage log and attach it? Also, do you get the same fail if you run that command by hand?
Also, the controller's yaml would make it easier for me to attempt to reproduce
Based on the input values, I think this is exactly the same error as https://bugzilla.redhat.com/show_bug.cgi?id=1126072. If you have nova-manage.log from the compute, that would verify, I suspect you will see the same error I did with /31.
Yes - It's probably the same issue. We should in QE use /24 (and not /31) . Example: external network: 10.8.30.100/24 private IP range for tenant networks: 192.168.100.0/24
Based on comments, this is due to bad configuration and is a valid failure. Closing as notabug. Please reopen if you disagree
I reproduced this bug using 10.8.30.100/30. Seems like this is related to the fact that both compute nodes (have 2 compute nodes in the same deployment) tried that at the same time. running puppet agent on the host with the error and resuming the deployment resulted in successful deployment.
Ok, having a deployment with 1 compute succeedes. So, the investigation should focus on why 2 computes fail - probably run the network create command simultaneously.
deployed successfully with 2 compute nodes using this ip subnets External network: 10.XX.XX.100/21 private IP range for tenant networks: 192.168.100.0/22
based on comment 10, closing as this works as expected