Bug 1589941 - Upgrade fails - Configmap for node-config-master must be present
Summary: Upgrade fails - Configmap for node-config-master must be present
Keywords:
Status: CLOSED DUPLICATE of bug 1569476
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.10.0
Assignee: Vadim Rutkovsky
QA Contact: Vikas Laad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-11 17:21 UTC by Vikas Laad
Modified: 2018-06-13 12:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-13 12:26:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ansible log with -vvv (423.29 KB, text/plain)
2018-06-11 17:25 UTC, Vikas Laad
no flags Details

Description Vikas Laad 2018-06-11 17:21:39 UTC
Description of problem:

I am trying to upgrade from 3.9 cluster to 3.10 cluster and getting following error.

TASK [openshift_node_group : fail] **********************************************************************************************************
task path: /root/openshift-ansible/roles/openshift_node_group/tasks/check_for_config.yml:5
fatal: [ec2-34-220-187-111.us-west-2.compute.amazonaws.com]: FAILED! => {
    "changed": false, 
    "failed": true, 
    "msg": "Configmap for node-config-master must be present"
}

3.9 cluster has
1 lb
3 masters
3 etcd (separate)
1 infra
2 computes


Version-Release number of the following components:
openshift-ansible - 0626581810b7577e64ba2ba0d7d8aba7ae7b91f2

rpm -q ansible
ansible-2.4.4.0-1.el7ae.noarch

ansible --version
ansible 2.4.4.0
  config file = /root/openshift-ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, May  4 2018, 09:38:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-34)]

Steps to Reproduce:
1. create 3.9 cluster (version openshift v3.9.27)
2. run 3.10 upgrade playbook openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_10/upgrade.yml

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

Expected results:
Upgrade should complete.

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

Comment 2 Vikas Laad 2018-06-11 17:25:05 UTC
Created attachment 1450158 [details]
ansible log with -vvv

Comment 3 Russell Teague 2018-06-11 17:52:29 UTC
I also saw this error on a 3.10 to 3.10 upgrade.  It appears the API was not responding for an unknown reason.  A second run of the upgrade passed this task.

Comment 4 Scott Dodson 2018-06-11 18:39:19 UTC
This is a lack of documentation issue. We're forcing people to create configmaps during the upgrade process.

Can you please take a look at https://github.com/openshift/openshift-ansible/pull/8710

and see if that helps to explain the situation? Formal documentation is coming soon.

Comment 5 liujia 2018-06-12 06:19:21 UTC
Hit it on both openshift-ansible-3.10.0-0.65 and openshift-ansible-3.10.0-0.66

Comment 6 liujia 2018-06-12 06:41:26 UTC
Block all upgrade tests.

Comment 7 Vadim Rutkovsky 2018-06-12 10:38:27 UTC
This seems to be happening anytime 3.9 is updated to 3.10. Created https://github.com/openshift/openshift-ansible/pull/8727 to fix it.

Comment 8 Vikas Laad 2018-06-12 14:45:20 UTC
running playbooks/openshift-master/openshift_node_config.yml creates config maps. Install continues without any errors.

Scott, Is there a doc bug ? or can we use this as doc bug ?

Comment 10 Scott Dodson 2018-06-13 12:26:53 UTC

*** This bug has been marked as a duplicate of bug 1569476 ***


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