Description of problem: Director deployed OCP 3.11: openshift_master_cluster_hostname and openshift_master_cluster_public_hostname always get set to IP addresses. I am unable to set them to hostnames. Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-9.0.1-0.20181013060891.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy openshift overcloud with: parameter_defaults: CloudName: public.openshift.localdomain PublicVirtualFixedIPs: [{'ip_address':'10.0.0.200'}] CloudNameInternal: internal.openshift.localdomain InternalApiVirtualFixedIPs: [{'ip_address':'172.17.1.200'}] CloudDomain: openshift.localdomain OpenShiftGlobalVariables: openshift_master_cluster_hostname: internal.openshift.localdomain openshift_master_cluster_public_hostname: public.openshift.localdomain openshift_master_default_subdomain: apps.openshift.localdomain Actual results: [root@undercloud-0 stack]# grep openshift_master_cluster_hostname /var/lib/mistral/openshift/openshift/global_vars.yml openshift_master_cluster_hostname: 172.17.1.200 [root@undercloud-0 stack]# grep openshift_master_cluster_public_hostname /var/lib/mistral/openshift/openshift/global_vars.yml openshift_master_cluster_public_hostname: 10.0.0.200 Expected results: openshift_master_cluster_hostname: internal.openshift.localdomain openshift_master_cluster_public_hostname: public.openshift.localdomain Additional info:
Hey Luis, Marius patch was addressing https://bugzilla.redhat.com/show_bug.cgi?id=1655123. Marking this issue as NEW since no one has looked at it yet.
Thanks Martin! I mixed them!
Found the issue, we need to revert the combine on https://github.com/openstack/tripleo-heat-templates/blob/d295cd9/extraconfig/services/openshift-master.yaml#L292. I'll propose a patch a bit later.
Proposed upstream fix at https://review.openstack.org/#/c/622455/, please test.
(In reply to Martin André from comment #4) > Proposed upstream fix at https://review.openstack.org/#/c/622455/, please > test. Worked in my test, thanks Martin!
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-2019:0045