Bug 1298198
| Summary: | Connectivity checks are broken for IPv6 deployments | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Jiri Stransky <jstransk> |
| Status: | CLOSED ERRATA | QA Contact: | yeylon <yeylon> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.0 (Kilo) | CC: | adarazs, dmacpher, dprince, jslagle, mandreou, mburns, rhel-osp-director-maint, shardy, srevivo |
| Target Milestone: | y3 | Keywords: | Regression |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-99.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
The validation script for deployment testing node availability only supported IPv4. This caused connectivity checks for an IPv6-based Overcloud to fail. This mix modifies the validation script to detect whether the IP address is v4 or v6 and run the respective connectivity check commands. Now connectivity checks succeed for IPv6-based Overclouds.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-18 16:49:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marius Cornea
2016-01-13 13:11:28 UTC
Yeah. I'm pretty sure the ./validation-scripts/all-nodes.sh script only supports IPv4 at the moment. We will need to look into adding that support upstream.
In the meantime you could simply disable the validation check like this:
diff --git a/all-nodes-validation.yaml b/all-nodes-validation.yaml
index a738337..a69042d 100644
--- a/all-nodes-validation.yaml
+++ b/all-nodes-validation.yaml
@@ -19,7 +19,9 @@ resources:
inputs:
- name: ping_test_ips
default: {get_param: PingTestIps}
- config: {get_file: ./validation-scripts/all-nodes.sh}
+ config: |
+ #!/bin/sh
+ exit 0
----
Alternately, you could modify the resource registry so that the validation nested stack is set to a Noop resource:
OS::TripleO::AllNodes::Validation: OS::Heat::None
I'm not sure if the OS::Heat::None resource is in the product yet but if it is available it is arguably cleaner then patching out the all-nodes-validation.yaml above.
Note that OS::Heat::None is new for liberty/OSP8, so if this is OSP7 (kilo), a different resource_registry mapping will be needed, e.g:
cp /usr/share/openstack-tripleo-heat-templates/all-nodes-validation.yaml disable_validation.yaml
Edit the template to disable the script, or point to another script which does nothing, e.g:
--- a/all-nodes-validation.yaml
+++ b/all-nodes-validation.yaml
@@ -19,7 +19,7 @@ resources:
inputs:
- name: ping_test_ips
default: {get_param: PingTestIps}
- config: {get_file: ./validation-scripts/all-nodes.sh}
+ config: |
+ #!/bin/sh
+ echo "validation disabled"
Then have an environment file like:
resource_registry:
OS::TripleO::AllNodes::Validation: disable_validation.yaml
proposed fixup: upstream: https://review.openstack.org/268103 Adds basic v6 capabilitiy to the deploy validation test (pings) https://bugs.launchpad.net/tripleo/+bug/1534578 The deploytime connectivity (ping) tests are failing in an ipv6 based deploy downstream: https://code.engineering.redhat.com/gerrit/65649 Adds v6 capability to the deploy validation test (pings) proposed fixup: upstream: https://review.openstack.org/268103 Adds basic v6 capabilitiy to the deploy validation test (pings) https://bugs.launchpad.net/tripleo/+bug/1534578 The deploytime connectivity (ping) tests are failing in an ipv6 based deploy downstream: https://code.engineering.redhat.com/gerrit/65649 Adds v6 capability to the deploy validation test (pings) apologies, downstream review updated, is now at https://code.engineering.redhat.com/gerrit/#/c/65658/ *** Bug 1299242 has been marked as a duplicate of this bug. *** openstack-tripleo-heat-templates-0.8.6-106.el7ost.noarch
[root@overcloud-compute-0 heat-admin]# journalctl -l -u os-collect-config | grep 'Trying to ping'
Jan 19 05:26:31 overcloud-compute-0.localdomain os-collect-config[8383]: + echo -n 'Trying to ping default gateway 192.0.2.1...'
Jan 19 05:26:31 overcloud-compute-0.localdomain os-collect-config[8383]: Trying to ping default gateway 192.0.2.1...+ local COUNT=0
Jan 19 05:28:45 overcloud-compute-0.localdomain os-collect-config[8383]: [2016-01-19 05:28:45,175] (heat-config) [INFO] {"deploy_stdout": "Trying to ping fd00:fd00:fd00:2000:f816:3eff:feeb:3100 for local network fd00:fd00:fd00:2000::/64...SUCCESS\nTrying to ping fd00:fd00:fd00:3000:f816:3eff:feca:b10a for local network fd00:fd00:fd00:3000::/64...SUCCESS\nTrying to ping fd00:fd00:fd00:5000:f816:3eff:fe71:8edd for local network fd00:fd00:fd00:5000::/64...SUCCESS\n", "deploy_stderr": "", "deploy_status_code": 0}
Jan 19 05:28:45 overcloud-compute-0.localdomain os-collect-config[8383]: [2016-01-19 05:28:45,171] (heat-config) [INFO] Trying to ping fd00:fd00:fd00:2000:f816:3eff:feeb:3100 for local network fd00:fd00:fd00:2000::/64...SUCCESS
Jan 19 05:28:45 overcloud-compute-0.localdomain os-collect-config[8383]: Trying to ping fd00:fd00:fd00:3000:f816:3eff:feca:b10a for local network fd00:fd00:fd00:3000::/64...SUCCESS
Jan 19 05:28:45 overcloud-compute-0.localdomain os-collect-config[8383]: Trying to ping fd00:fd00:fd00:5000:f816:3eff:fe71:8edd for local network fd00:fd00:fd00:5000::/64...SUCCESS
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://rhn.redhat.com/errata/RHBA-2016-0264.html |