Fuel for OpenStack

  1. Bug #1664974
  2. Comment #3

Comment 3 for bug 1664974

Revision history for this message
Gregory Orange (gregoryo2017) wrote :

Further detail from this same environment, here is the error message from the Fuel Dashboard:

Error
All nodes are finished. Failed tasks: Task[openstack-network-networks/42] Stopping the deployment process!

This appears to match the node id, because "fuel2 node list -e $env" yields:
| 42 | Untitled (xx:xx) | error | ubuntu

Looking at node-42:/var/log/puppet.log :

2017-02-20 06:39:00 +0000 /Stage[main]/Openstack_tasks::Openstack_network::Plugins::Ml2/Service[neutron-server] (notice): Triggered 'refresh' from 1 events
2017-02-20 06:42:20 +0000 /Stage[main]/Openstack_tasks::Openstack_network::Plugins::Ml2/Exec[waiting-for-neutron-api]/returns (notice): <html><body><h1>503 Service Unavailable</h1>
2017-02-20 06:42:20 +0000 /Stage[main]/Openstack_tasks::Openstack_network::Plugins::Ml2/Exec[waiting-for-neutron-api]/returns (notice): No server is available to handle this request.
2017-02-20 06:42:20 +0000 /Stage[main]/Openstack_tasks::Openstack_network::Plugins::Ml2/Exec[waiting-for-neutron-api]/returns (notice): </body></html>
2017-02-20 06:42:20 +0000 /Stage[main]/Openstack_tasks::Openstack_network::Plugins::Ml2/Exec[waiting-for-neutron-api] (err): Failed to call refresh: neutron net-list --http-timeout=4 2>&1 > /dev/null returned 1 instead of one of [0]
2017-02-20 06:42:20 +0000 /Stage[main]/Openstack_tasks::Openstack_network::Plugins::Ml2/Exec[waiting-for-neutron-api] (err): neutron net-list --http-timeout=4 2>&1 > /dev/null returned 1 instead of one of [0]

Looking at node-42:/etc/puppet/modules/openstack_tasks/manifests/openstack_network/plugins/ml2.pp I see the 'waiting-for-neutron-api' exec subscribes to the neutron-server service, and retries 30 times at 4 seconds each - total of two minutes. That fits with the timing above.

Running the command manually on node-42 succeeds:

root@node-42:~# . openrc
root@node-42:~# neutron net-list --http-timeout=4 && echo yes || echo no

yes

So, it looks to me like the neutron-server service isn't running within two minutes of being started by the Puppet run. Now, I'll try to work out how to tweak Fuel to increase that time, to test.