Bug 1560820
Summary: | OCP `oc cluster up` uses origin image for some processes and returns origin version info | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> | ||||||
Component: | Master | Assignee: | Michal Fojtik <mfojtik> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Wang Haoran <haowang> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 3.10.0 | CC: | aos-bugs, jokerman, mmccomas, spadgett, wewang, wzheng, xiuwang, xxia | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 3.10.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-07-30 19:11:31 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: | |||||||||
Attachments: |
|
Description
Xingxing Xia
2018-03-27 03:15:07 UTC
OCP oc v3.10.0-0.15.0 meets same issue. Can you locate the `openshift.local.clusterup/logs/install-router-001.*` and attach them to this BZ? So we can see the error output from the command. I can't reproduce this on OSX or on linux. Hmm, today met several other errors to answer the needinfo. Will continue check next day :) I can reproduce the same issue like comment #4, attaching log in attachment now. Created attachment 1419695 [details]
Get this log when set Loglevel=5
Created attachment 1426452 [details]
oc_cluster_up_error
The error has changed with oc v3.10.0-0.28.0 kubernetes v1.10.0+b81c8f8 In the button of the error log, prompt no 'write-flags' option for cmd ' openshift start node', but the 'openshift start node' v3.10 and v3.9 has included this option. 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:1816 |