Bug 1450251
Summary: | Replace references to 192.0.2.0/24 with 192.168.24.0/24 in templates | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Andreas Karis <akaris> |
Component: | openstack-tripleo-heat-templates | Assignee: | Emilien Macchi <emacchi> |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 11.0 (Ocata) | CC: | ahrechan, aschultz, jschluet, jslagle, mburns, rhel-osp-director-maint |
Target Milestone: | Upstream M2 | Keywords: | Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-7.0.0-0.20170609153210.2f5f8fc.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 21:27:05 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
Andreas Karis
2017-05-12 02:06:21 UTC
Please be careful with this type of change. If folks are using these defaults in the templates, changing them could cause issues with updates/upgrades. But if we keep them, then we are inconsistent with the new setup. What can we do about it? Verified openstack-tripleo-heat-templates-7.0.3-0.20171024200823.el7ost.noarch 192.0.2 is still use for update from 192_0_2-subnet.yaml which is correct (undercloud) [stack@undercloud-0 ~]$ grep 192.0.2 /usr/share/openstack-tripleo-heat-templates/* -R /usr/share/openstack-tripleo-heat-templates/environments/updates/update-from-192_0_2-subnet.yaml: ControlPlaneDefaultRoute: 192.0.2.1 /usr/share/openstack-tripleo-heat-templates/environments/updates/update-from-192_0_2-subnet.yaml: EC2MetadataIp: 192.0.2.1 (undercloud) [stack@undercloud-0 ~]$ grep 192.168.24 /usr/share/openstack-tripleo-heat-templates/* -R /usr/share/openstack-tripleo-heat-templates/deployed-server/README.rst: EC2MetadataIp: "192.168.24.1" /usr/share/openstack-tripleo-heat-templates/deployed-server/README.rst:192.168.24.1. /usr/share/openstack-tripleo-heat-templates/deployed-server/deployed-server-environment-output.yaml: default: 192.168.24.1 /usr/share/openstack-tripleo-heat-templates/environments/services/keystone_domain_specific_ldap_backend.yaml: url: ldap://192.168.24.251 /usr/share/openstack-tripleo-heat-templates/environments/contrail/contrail-net-storage-mgmt.yaml: ControlPlaneDefaultRoute: 192.168.24.254 /usr/share/openstack-tripleo-heat-templates/environments/contrail/contrail-net-storage-mgmt.yaml: EC2MetadataIp: 192.168.24.1 # Generally the IP of the Undercloud /usr/share/openstack-tripleo-heat-templates/environments/contrail/contrail-net.yaml: ControlPlaneDefaultRoute: 192.168.24.254 /usr/share/openstack-tripleo-heat-templates/environments/contrail/contrail-net.yaml: EC2MetadataIp: 192.168.24.1 # Generally the IP of the Undercloud /usr/share/openstack-tripleo-heat-templates/environments/contrail/contrail-services.yaml: ContrailRepo: http://192.168.24.1/contrail /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip-v6.yaml: ControlFixedIPs: [{'ip_address':'192.168.24.251'}] /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip.yaml: ControlFixedIPs: [{'ip_address':'192.168.24.251'}] /usr/share/openstack-tripleo-heat-templates/environments/fixed-ip-vips-v6.yaml: ControlFixedIPs: [{'ip_address':'192.168.24.240'}] /usr/share/openstack-tripleo-heat-templates/environments/neutron-ml2-cisco-n1kv.yaml: N1000vVSMIP: '192.168.24.50' /usr/share/openstack-tripleo-heat-templates/environments/neutron-ml2-cisco-n1kv.yaml: N1000vMgmtGatewayIP: '192.168.24.1' /usr/share/openstack-tripleo-heat-templates/environments/fixed-ip-vips.yaml: ControlFixedIPs: [{'ip_address':'192.168.24.240'}] /usr/share/openstack-tripleo-heat-templates/environments/network-environment-v6.yaml: ControlPlaneDefaultRoute: 192.168.24.254 /usr/share/openstack-tripleo-heat-templates/environments/network-environment-v6.yaml: EC2MetadataIp: 192.168.24.1 # Generally the IP of the Undercloud /usr/share/openstack-tripleo-heat-templates/environments/logging-environment.yaml:# - host: 192.168.24.11 /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml: ControlPlaneDefaultRoute: 192.168.24.254 /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml: EC2MetadataIp: 192.168.24.1 # Generally the IP of the Undercloud /usr/share/openstack-tripleo-heat-templates/environments/undercloud.yaml: IronicInspectorIpRange: '192.168.24.100,192.168.24.200' /usr/share/openstack-tripleo-heat-templates/extraconfig/post_deploy/undercloud_post.yaml: default: '192.168.24.5' /usr/share/openstack-tripleo-heat-templates/extraconfig/post_deploy/undercloud_post.yaml: default: '192.168.24.24' /usr/share/openstack-tripleo-heat-templates/extraconfig/post_deploy/undercloud_post.yaml: default: '192.168.24.0/24' /usr/share/openstack-tripleo-heat-templates/extraconfig/post_deploy/undercloud_post.yaml: default: '192.168.24.1' /usr/share/openstack-tripleo-heat-templates/net-config-linux-bridge.yaml: default: 192.168.24.1 /usr/share/openstack-tripleo-heat-templates/network_data.yaml:# ip_subnet: IP/CIDR, e.g. '192.168.24.0/24' or '2001:db8:fd00:1000::/64' /usr/share/openstack-tripleo-heat-templates/puppet/extraconfig/pre_deploy/controller/neutron-ml2-cisco-n1kv.yaml: default: '192.168.24.50' /usr/share/openstack-tripleo-heat-templates/puppet/extraconfig/pre_deploy/controller/neutron-ml2-cisco-n1kv.yaml: default: '192.168.24.1' /usr/share/openstack-tripleo-heat-templates/puppet/services/network/contrail-dpdk.yaml: default: '192.168.24.1' /usr/share/openstack-tripleo-heat-templates/puppet/services/network/contrail-tsn.yaml: default: '192.168.24.1' /usr/share/openstack-tripleo-heat-templates/puppet/services/network/contrail-vrouter.yaml: default: '192.168.24.1' 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/RHEA-2017:3462 |