Bug 1579898 - changes introduced by bz 1416639 not working for registry on NFS
Summary: changes introduced by bz 1416639 not working for registry on NFS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.z
Assignee: Michael Gugino
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-18 15:10 UTC by daniel
Modified: 2018-06-06 15:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-06 15:46:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
hosts file to set up 37 cluster (2.75 KB, text/plain)
2018-05-18 15:10 UTC, daniel
no flags Details
hosts file for upgrade to 3.9 (2.82 KB, text/plain)
2018-05-18 15:11 UTC, daniel
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1796 0 None None None 2018-06-06 15:46:42 UTC

Description daniel 2018-05-18 15:10:05 UTC
Description of problem:

With https://bugzilla.redhat.com/show_bug.cgi?id=1416639 (3.10) and https://github.com/openshift/openshift-ansible/pull/7920 (backport to 3.9.1)
we introduce blocking installation or upgrading of metrics, logging, registy,....  if located on NFS unless openshift_enable_unsupported_configurations=True is set in the hosts file.

Testing this is in lab showed that metrics and logging indeed stop and end with a warning but to my understanding it should actually even not be possible to upgrade at all because of the registry on NFS, which was not the case.

Version-Release number of selected component (if applicable):

oc v3.9.27
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://openshift.internal.example.com:443
openshift v3.9.27
kubernetes v1.9.1+a0ce1bc657


openshift-ansible-playbooks-3.9.27-1.git.0.52e35b5.el7.noarch
ansible-2.4.4.0-1.el7ae.noarch
openshift-ansible-roles-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-docs-3.9.27-1.git.0.52e35b5.el7.noarch

How reproducible:

Steps to Reproduce:
1. Install latest version of OCP 3.7 with registry, metrics, logging and asb on NFS
2. One the installation is working, follow docs to update to lastest, i.e. 3.9.1 OCP 
3. According to my understanding of bz 1416639 that should fail with a warning for registry on NFS and a hint that I would need to set openshift_enable_unsupported_configurations=True, which is not the case
4. However, updating metrics or logging shows the warning and installation fails

Actual results:
- OCP 3.9.1 installs without a warning for registry on NFS

Expected results:
- Fails with warning because of NFS for registry

Additional info:
- updating metrics logging shows:

$ ansible-playbook -i hosts_39 /usr/share/ansible/openshift-ansible/playbooks/openshift-logging/config.yml

[...]
TASK [Run variable sanity checks] ************************************************************************************************************************************************************
fatal: [10.10.10.22]: FAILED! => {"failed": true, "msg": "last_checked_host: 10.10.10.22, last_checked_var: openshift_hosted_registry_storage_kind;nfs is an unsupported type for openshift_
hosted_registry_storage_kind. openshift_enable_unsupported_configurations=True mustbe specified to continue with this configuration."}

NO MORE HOSTS LEFT ***************************************************************************************************************************************************************************
....

$ ansible-playbook -i hosts_39 /usr/share/ansible/openshift-ansible/playbooks/openshift-metrics/config.yml
[...]
TASK [Run variable sanity checks] ************************************************************************************************************************************************************
fatal: [10.10.10.22]: FAILED! => {"failed": true, "msg": "last_checked_host: 10.10.10.22, last_checked_var: openshift_hosted_registry_storage_kind;nfs is an unsupported type for openshift_hosted_registry_storage_kind. openshift_enable_unsupported_configurations=True mustbe specified to continue with this configuration."}



Description of problem:

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 daniel 2018-05-18 15:10:57 UTC
Created attachment 1438711 [details]
hosts file to set up 37 cluster

Comment 2 daniel 2018-05-18 15:11:34 UTC
Created attachment 1438712 [details]
hosts file for upgrade to 3.9

Comment 3 daniel 2018-05-18 15:12:32 UTC
please find attached the host files I have used 
- hosts_37 for the initial install 
- hosts_39 for the upgrade

Comment 5 Michael Gugino 2018-05-18 17:51:06 UTC
We are not currently running sanity checks during upgrades.

PR Created for master: https://github.com/openshift/openshift-ansible/pull/8445

Comment 7 Junqi Zhao 2018-06-04 04:41:05 UTC
openshift-ansible-3.9.30-1.git.7.46f8678.el7.noarch

# openshift version
openshift v3.9.30
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

Set registry or logging/metrics using nfs storage in ansible inventory

openshift_hosted_registry_storage_kind=nfs 
and there is not
openshift_enable_unsupported_configurations=true
in inventory file

the installer will fail in variable sanity check.

TASK [Run variable sanity checks] **********************************************
fatal: [host-8-249-107.host.centralci.eng.rdu2.redhat.com]: FAILED! => {"failed": true, "msg": "last_checked_host: host-8-249-107.host.centralci.eng.rdu2.redhat.com, last_checked_var: openshift_hosted_registry_storage_kind;nfs is an unsupported type for openshift_hosted_registry_storage_kind. openshift_enable_unsupported_configurations=True mustbe specified to continue with this configuration."}

Comment 9 errata-xmlrpc 2018-06-06 15:46:21 UTC
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/RHBA-2018:1796


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