Bug 1752641 - Latest v3.11 installation failed on QE rpm-rhel7-s3_registry-aws-cloudprovider-elb-ha
Summary: Latest v3.11 installation failed on QE rpm-rhel7-s3_registry-aws-cloudprovide...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: Russell Teague
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-16 19:34 UTC by Weibin Liang
Modified: 2019-09-18 14:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-18 14:15:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Installation Console Log (4.06 MB, text/plain)
2019-09-16 19:34 UTC, Weibin Liang
no flags Details
Test Results Log (2.15 KB, text/plain)
2019-09-16 19:34 UTC, Weibin Liang
no flags Details

Description Weibin Liang 2019-09-16 19:34:01 UTC
Created attachment 1615623 [details]
Installation Console Log

Description of problem:
Using QE Flexy installation tool to install vars-ha/rpm-rhel7-s3_registry-aws-cloudprovider-elb-ha cluster, installing v3.11.43 passed, but installing latest v3.11 failed


How reproducible:
Always

Steps to Reproduce:
Using QE Flexy to install latest v3.11 in vars-ha/rpm-rhel7-s3_registry-aws-cloudprovider-elb-ha cluster


Actual results:
Installation failed
https://openshift-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Launch%20Environment%20Flexy/67706/console


Expected results:
Installation should pass

Additional info:
Installation log and test results attached

Comment 1 Weibin Liang 2019-09-16 19:34:34 UTC
Created attachment 1615624 [details]
Test Results Log

Comment 3 Yadan Pei 2019-09-18 07:42:43 UTC
Looks like this is an occasional failure, not always reproduced

Comment 4 zhaozhanqi 2019-09-18 07:51:39 UTC
the issue the that the control plane images for 3.11.146 is not exist, So the pod cannot be came up.

it's not a bug I guess.

Comment 5 Weibin Liang 2019-09-18 14:15:15 UTC
This morning, the installation passed with latest v3.11 code.

[root@ip-172-18-2-247 ec2-user]# oc version
oc v3.11.146
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://qe-preserve-masterapi-246045118.us-east-1.elb.amazonaws.com:443
openshift v3.11.146
kubernetes v1.11.0+d4cacc0
[root@ip-172-18-2-247 ec2-user]#


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