Bug 1347432 - rhel-osp-director: 9.0 overcloud deployment with ipv6 fails with "Error: Could not start Service[nova-compute]: Execution of '/usr/bin/systemctl start openstack-nova-compute'"
Summary: rhel-osp-director: 9.0 overcloud deployment with ipv6 fails with "Error: Cou...
Keywords:
Status: CLOSED DUPLICATE of bug 1347802
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 9.0 (Mitaka)
Assignee: Alexander Chuzhoy
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-16 20:37 UTC by Alexander Chuzhoy
Modified: 2016-06-23 13:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 13:10:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alexander Chuzhoy 2016-06-16 20:37:47 UTC 
rhel-osp-director:  9.0 overcloud deployment with ipv6 fails with "Error: Could not start Service[nova-compute]: Execution of '/usr/bin/systemctl start openstack-nova-compute'"


Environment:
openstack-puppet-modules-8.1.1-1.el7ost.noarch
instack-undercloud-4.0.0-2.el7ost.noarch
openstack-tripleo-heat-templates-2.0.0-9.el7ost.noarch


Steps to reproduce:
Attempt to deploy overcloud 9 with:
openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --neutron-disable-tunneling --neutron-network-type vlan --neutron-network-vlan-ranges datacentre:118:143 --neutron-bridge-mappings datacentre:br-ex --ntp-server clock.redhat.com --timeout 90 -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation-v6.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans-v6.yaml -e network-environment.yaml --ceph-storage-scale 1


Result:
Deployment fails.
Debugging with heat shows:
Error: Could not start Service[nova-compute]: Execution of '/usr/bin/systemctl start openstack-nova-compute' returned 1: Job for openstack-nova-compute.service failed because the control process exited with error code. See \"systemctl status openstack-nova-compute.service\" and \"journalctl -xe\" for details.
Wrapped exception:
Execution of '/usr/bin/systemctl start openstack-nova-compute' returned 1: Job for openstack-nova-compute.service failed because the control process exited with error code. See \"systemctl status openstack-nova-compute.service\" and \"journalctl -xe\" for details.
Error: /Stage[main]/Nova::Compute/Nova::Generic_service[compute]/Service[nova-compute]/ensure: change from stopped to running failed: Could not start Service[nova-compute]: Execution of '/usr/bin/systemctl start openstack-nova-compute' returned 1: Job for openstack-nova-compute.service failed because the control process exited with error code. See \"systemctl status openstack-nova-compute.service\" and \"journalctl -xe\" for details.


workaround: rerun the deployment command.

Expected result:
Successful deployment.

Note:
Reproduced this bug, although it seems intermittent.
Comment 4 Jay Dobies 2016-06-21 13:21:28 UTC 
Assigning to QE to identify another environment to see if this can be reproduced.
Comment 5 Alexander Chuzhoy 2016-06-22 18:53:58 UTC 
Hi Jay,
Found  on another setup with (supposedly) enough resources.

I was able to deploy HA with ipv4, Removed it an attempted to deploy ipv6. Same issue.
Comment 7 Jay Dobies 2016-06-23 13:10:36 UTC 

*** This bug has been marked as a duplicate of bug 1347802 ***
Note You need to log in before you can comment on or make changes to this bug.