Bug 1368913
Summary: | Openshift master major version info messed up | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Xia Zhao <xiazhao> |
Component: | oc | Assignee: | Clayton Coleman <ccoleman> |
Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.3.0 | CC: | aos-bugs, jokerman, mmccomas, tdawson |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
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: | 2016-09-27 09:45:23 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
Xia Zhao
2016-08-22 05:37:34 UTC
Closing this as not a bug. See conversation in this thread: https://github.com/openshift/origin/pull/10602#issuecomment-241857909 > Closing this as not a bug. See conversation in this thread: > https://github.com/openshift/origin/pull/10602#issuecomment-241857909 The reason why "dirty" shows up in version information is because the openshift build is leaving the working directory in a dirty state. Re-assigning to mkargaki to get his thoughts on this before closing. https://github.com/openshift/origin/pull/10602#issuecomment-241857909 https://github.com/openshift/origin/pull/10602#issuecomment-241858026 should be addressed. I am not sure who is responsible for the build process of the repo. Probably Clayton? This was an OSE bug, not openshift origin. It has been fixed in OSE v3.3.0.28 or newer. We have also pushed the fix upstream in this pull request. https://github.com/openshift/origin/pull/10666 But marking this onto QE so that the OSE issue can be verified and closed. 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-2016:1933 |