Bug 1469336 - [3.6] registry dns value should be same with the exsiting masters for the added master
Summary: [3.6] registry dns value should be same with the exsiting masters for the add...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 3.6.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-11 02:06 UTC by Anping Li
Modified: 2018-10-08 10:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: any masters which are later added via the scaleup playbooks are setting a value for OPENSHIFT_DEFAULT_REGISTRY Consequence: New masters are added with configuration that is inconsistent with the already configured masters Fix: OPENSHIFT_DEFAULT_REGISTRY value is saved from oo_first_master Result: The saved OPENSHIFT_DEFAULT_REGISTRY value is used instead of the default for 3.6, which is to use a hard-coded registry value of 'docker-registry.default.svc:5000'
Clone Of:
Environment:
Last Closed: 2018-10-08 10:35:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
The scaleup logs (221.41 KB, application/x-gzip)
2017-07-11 02:07 UTC, Anping Li
no flags Details
scaleup logs (159.99 KB, application/zip)
2017-08-31 13:17 UTC, Anping Li
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-ansible pull 5952 0 None None None 2017-11-01 14:37:10 UTC

Description Anping Li 2017-07-11 02:06:06 UTC
Description of problem:
when the OCP v3.6 was upgraded from v3.5 ,the registry dns wasn't enabled by default.  But if we scale up master against this OCP 3.6 env, the registry dns was enabled on the added master. The new added master  configuration should use same with the existing master.

Version-Release number of the following components:
openshift-ansible-3.6.140

How reproducible:
always

Steps to Reproduce:
1. install HA OCP v3.5
2. upgrade to OCP 3.6
   anible-playbook /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_6/upgrade.yml
3. Add a new master.
   ansible-playbook --private-key /root/configdir/libra.pem -i /root/workdir/hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-master/scaleup.yml -v
4. check the registry dns configuration
   cat /etc/sysconfig/atomic-openshift-master-api


Actual results:
4. There is OPENSHIFT_DEFAULT_REGISTRY=docker-registry.default.svc:5000 for the added master [4]. These aren't OPENSHIFT_DEFAULT_REGISTRY for the upgraded masters [1][2][3].


[1]openshift-221.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-221.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
IMAGE_VERSION=v3.6.126.8

# Proxy configuration
# See https://docs.openshift.com/enterprise/latest/install_config/install/advanced_install.html#configuring-global-proxy

[2]openshift-182.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-182.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
IMAGE_VERSION=v3.6.126.8

# Proxy configuration
# See https://docs.openshift.com/enterprise/latest/install_config/install/advanced_install.html#configuring-global-proxy

[3]openshift-181.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-181.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
IMAGE_VERSION=v3.6.126.8

# Proxy configuration
# See https://docs.openshift.com/enterprise/latest/install_config/install/advanced_install.html#configuring-global-proxy

[4]openshift-210.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-210.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
OPENSHIFT_DEFAULT_REGISTRY=docker-registry.default.svc:5000
IMAGE_VERSION=v3.6.126.8

# Proxy configuration
# See https://docs.openshift.com/enterprise/latest/install_config/install/advanced_install.html#configuring-global-proxy
NO_PROXY=,172.30.0.0/16,10.128.0.0/14

Expected results:
The new added master has same configuration as the existing masters

Additional info:

Comment 1 Anping Li 2017-07-11 02:07:19 UTC
Created attachment 1296020 [details]
The scaleup logs

Comment 2 Tim Bielawa 2017-07-24 16:42:54 UTC
Successfully reproduced this error

Comment 3 Tim Bielawa 2017-07-27 12:58:13 UTC
PR for this is open here https://github.com/openshift/openshift-ansible/pull/4894

Need to clean out some debugging trash and squash the commits down.

Comment 4 Tim Bielawa 2017-07-27 15:30:03 UTC
Doing a last batch of testing. Attempting to reproduce the original bug. If I can not reproduce the bug then I'll switch the github portion of this over to requesting reviews so we can get the fix merged.

Comment 6 Anping Li 2017-08-31 13:09:19 UTC
With openshift3/ose-ansible:v3.6.173.0.27, the scale master is still include  OPENSHIFT_DEFAULT_REGISTRY.
[root@anli host3ha]# sshremote masters 'cat /etc/sysconfig/atomic-openshift-master-api |grep -v "#"' 
openshift-182.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-182.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
openshift-181.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-181.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
openshift-221.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-221.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
openshift-210.lab.eng.nay.redhat.com | SUCCESS | rc=0 >>
OPTIONS=--loglevel=2 --listen=https://0.0.0.0:8443 --master=https://openshift-210.lab.eng.nay.redhat.com:8443
CONFIG_FILE=/etc/origin/master/master-config.yaml
OPENSHIFT_DEFAULT_REGISTRY=docker-registry.default.svc:5000

Comment 7 Anping Li 2017-08-31 13:17:11 UTC
Created attachment 1320589 [details]
scaleup logs

Comment 10 Tim Bielawa 2017-10-31 17:39:22 UTC
I filed a 3.6 backport for this fix here

https://github.com/openshift/openshift-ansible/pull/5952

Comment 12 Scott Dodson 2018-01-25 15:51:19 UTC
should now be fixed based on comment 10

Comment 13 Gan Huang 2018-02-05 11:50:22 UTC
Verified in openshift-ansible-3.6.173.0.101-1.git.0.7c6b77f.el7.noarch.rpm

OPENSHIFT_DEFAULT_REGISTRY not set as the fist master after scaling up masters.


Note You need to log in before you can comment on or make changes to this bug.