Bug 1775542
Summary: | payload 4.2.8 need the signature | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
Component: | Release | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED ERRATA | QA Contact: | Jian Zhang <jiazha> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.2.z | CC: | aos-bugs, bandrade, jdelft, jeff.li, jokerman, scolange, tbuskey |
Target Milestone: | --- | ||
Target Release: | 4.2.z | ||
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: | 2019-12-03 22:43:15 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
Jian Zhang
2019-11-22 08:53:41 UTC
I believe this has been resolved. Yes, it has been signed. Verify it. mac:~ jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.7 True False 106m Cluster version is 4.2.7 mac:~ jianzhang$ oc patch clusterversion/version --patch '{"spec":{"upstream":"https://openshift-release.svc.ci.openshift.org/graph"}}' --type=merge clusterversion.config.openshift.io/version patched mac:~ jianzhang$ oc adm upgrade Cluster version is 4.2.7 Updates: VERSION IMAGE 4.2.0-0.nightly-2019-11-19-194213 registry.svc.ci.openshift.org/ocp/release@sha256:c7f7edcb19bf05460e68a58e12cdb564c5c161e6a0204ae3ab4d79888663f6a6 4.2.8 registry.svc.ci.openshift.org/ocp/release@sha256:4bf307b98beba4d42da3316464013eac120c6e5a398646863ef92b0e2c621230 mac:~ jianzhang$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.7 True True 19s Working towards 4.2.8: 17% complete Can I ask how you resolved this error? 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-2019:3953 |