Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1624657

Summary: upgrade failed at TASK [openshift_web_console : Ensure openshift-web-console project exists]
Product: OpenShift Container Platform Reporter: Weihua Meng <wmeng>
Component: Cluster Version OperatorAssignee: Scott Dodson <sdodson>
Status: CLOSED DUPLICATE QA Contact: Weihua Meng <wmeng>
Severity: high Docs Contact:
Priority: high    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: 3.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-03 02:22:03 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 Weihua Meng 2018-09-02 23:13:47 UTC
Description of problem:
upgrade failed at TASK [openshift_web_console : Ensure openshift-web-console project exists]


    "msg": {
        "cmd": "/usr/bin/oc adm new-project openshift-web-console --admin-role=admin --node-selector=", 
        "results": {}, 
        "returncode": 1, 
        "stderr": "The connection to the server preserve-wmeng1ug310-master-etcd-1:8443 was refused - did you specify the right host or port?\n", 
        "stdout": ""
    }

When I tried this command after a while, got the correct response.
I think we need to verify the api server is ready before doing this task

Version-Release number of the following components:
openshift-ansible-3.11.0-0.25.0.git.0.7497e69.el7.noarch

How reproducible:
30%

Steps to Reproduce:
1. upgrade OCP v3.10 cluster to v3.11


Actual results:
upgrade failed

Expected results:
upgrade succeeds

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

Comment 2 Weihua Meng 2018-09-03 02:22:03 UTC

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