Red Hat Bugzilla – Bug 1262995
osp-d deployment fails on network validation scripts when network-isolation is not enabled.
Last modified: 2016-04-18 03:12:54 EDT
Description of problem: osp-d deployment fails on network validation scripts when network-isolation is not enabled. build: http://ayanami.boston.devel.redhat.com/poodles/rhos-devel-ci/7.0-director/2015-09-14.1/ Deployment command: source /home/stack/stackrc; openstack overcloud deploy --debug --log-file overcloud_deployment_34.log --templates --libvirt-type=qemu --neutron-network-type gre --neutron-tunnel-types gre --ntp-server 10.5.26.10 --control-scale 1 --compute-scale 1 --ceph-storage-scale 1 --block-storage-scale 0 --swift-storage-scale 0 --control-flavor baremetal --compute-flavor baremetal --ceph-storage-flavor baremetal --block-storage-flavor baremetal --swift-storage-flavor baremetal -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yam 01:38:21.162 stdout: 01:38:21.162 { 01:38:21.162 "status": "FAILED", 01:38:21.162 "server_id": "c1eb5f3c-5583-4100-9978-b7a5cd077271", 01:38:21.162 "config_id": "67d933b6-bf66-4824-84ab-995ac836c0a7", 01:38:21.162 "output_values": { 01:38:21.162 "deploy_stdout": "Trying to ping 192.0.2.10 for local network 192.0.2.0/24...SUCCESS\nTrying to ping 192.0.2.12 for local network 192.0.2.0/24...FAILURE\n", 01:38:21.162 "deploy_stderr": "192.0.2.12 is not pingable. Local Network: 192.0.2.0/24\n", 01:38:21.162 "deploy_status_code": 1 01:38:21.162 }, 01:38:21.162 "creation_time": "2015-09-14T14:44:05Z", 01:38:21.162 "updated_time": "2015-09-14T14:44:44Z", 01:38:21.162 "input_values": {}, 01:38:21.162 "action": "CREATE", 01:38:21.162 "status_reason": "deploy_status_code : Deployment exited with non-zero status code: 1", 01:38:21.162 "id": "0d34a9cf-a0e1-416b-8d94-c83b70eee392" 01:38:21.162 } 01:38:21.162 { 01:38:21.162 "status": "FAILED", 01:38:21.162 "server_id": "83b19634-e0a0-4e0b-9049-86849f73f67c", 01:38:21.162 "config_id": "df40b25a-6ab0-4e06-8beb-e95dbd0f2ebb", 01:38:21.162 "output_values": { 01:38:21.162 "deploy_stdout": "Trying to ping 192.0.2.10 for local network 192.0.2.0/24...SUCCESS\nTrying to ping 192.0.2.12 for local network 192.0.2.0/24...FAILURE\n", 01:38:21.162 "deploy_stderr": "192.0.2.12 is not pingable. Local Network: 192.0.2.0/24\n", 01:38:21.162 "deploy_status_code": 1 01:38:21.162 }, 01:38:21.162 "creation_time": "2015-09-14T14:44:11Z", 01:38:21.162 "updated_time": "2015-09-14T14:44:49Z", 01:38:21.162 "input_values": {}, 01:38:21.162 "action": "CREATE", 01:38:21.162 "status_reason": "deploy_status_code : Deployment exited with non-zero status code: 1", 01:38:21.162 "id": "e27cc8fc-47ae-4d0a-8486-eda63580dafa" 01:38:21.162 } 01:38:21.162 { 01:38:21.162 "status": "FAILED", 01:38:21.162 "server_id": "dc04d5e9-6219-4ae5-a336-93436b15d396", 01:38:21.162 "config_id": "d5ef7e9a-d068-4b83-b26b-d34281c42803", 01:38:21.162 "output_values": { 01:38:21.162 "deploy_stdout": "Trying to ping 192.0.2.10 for local network 192.0.2.0/24...SUCCESS\nTrying to ping 192.0.2.12 for local network 192.0.2.0/24...FAILURE\n", 01:38:21.162 "deploy_stderr": "192.0.2.12 is not pingable. Local Network: 192.0.2.0/24\n", 01:38:21.162 "deploy_status_code": 1 01:38:21.162 }, 01:38:21.162 "creation_time": "2015-09-14T14:44:23Z", 01:38:21.162 "updated_time": "2015-09-14T14:45:10Z", 01:38:21.162 "input_values": {}, 01:38:21.162 "action": "CREATE", 01:38:21.162 "status_reason": "deploy_status_code : Deployment exited with non-zero status code: 1", 01:38:21.162 "id": "c3d7195b-e400-43f4-83d7-1bd8ee891ab3" 01:38:21.162 } 01:38:13.566 | attributes | {} | 01:38:13.566 | description | | 01:38:13.566 | links | http://192.0.2.1:8004/v1/c87c47ee60ec40cd9ed6c4a1bbc0320a/stacks/overcloud/f0f19dd8-2f61-4726-98e4-2789f1c8b861/resources/ControllerNodesPostDeployment (self) | 01:38:13.566 | | http://192.0.2.1:8004/v1/c87c47ee60ec40cd9ed6c4a1bbc0320a/stacks/overcloud/f0f19dd8-2f61-4726-98e4-2789f1c8b861 (stack) | 01:38:13.566 | | http://192.0.2.1:8004/v1/c87c47ee60ec40cd9ed6c4a1bbc0320a/stacks/overcloud-ControllerNodesPostDeployment-m44vgqkjfx3j/322de447-39a1-48a4-9def-4d9deda6fd90 (nested) | 01:38:13.566 | logical_resource_id | ControllerNodesPostDeployment | 01:38:13.566 | physical_resource_id | 322de447-39a1-48a4-9def-4d9deda6fd90 | 01:38:13.566 | required_by | BlockStorageNodesPostDeployment | 01:38:13.566 | | CephStorageNodesPostDeployment | 01:38:13.566 | resource_name | ControllerNodesPostDeployment | 01:38:13.566 | resource_status | CREATE_FAILED | 01:38:13.566 | resource_status_reason | CREATE aborted | 01:38:13.566 | resource_type | OS::TripleO::ControllerPostDeployment | 01:38:13.566 | updated_time | 2015-09-14T14:37:30Z
Question should the network validation scripts be executed on environments where network isolation is not enabled?
We spoke about this on IRC today. I'm not seeing the same sorts of failures in upstream TripleO at the moment. We think the issue may be resolved if we backport this: https://review.openstack.org/#/c/205206/
I successfully deployed using python-rdomanager-oscplugin-0.0.10-5.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1862