Bug 1431077
Summary: | fatal excluder error when upgrade atomic OCP | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
Component: | Cluster Version Operator | Assignee: | Jan Chaloupka <jchaloup> |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.0 | CC: | anli, aos-bugs, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: the upgrade plays are upgrading excluders on AH
Consequence: the plays fail as excluders on AH are not supported
Fix: skip excluders on AH
Result: excluders are skip on AH, the plays no longer fail
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-12 19:03:45 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
Anping Li
2017-03-10 10:19:08 UTC
Anping Li, can you provide steps to reproduce and the entire ansible tasks log? I am not able to reproduce it with the latest commit in master branch with [1] applied. I will run another installation and upgrade scenario later on again once [1] and its dependent PR [2] are merged. [1] https://github.com/openshift/openshift-ansible/pull/3620 [2] https://github.com/openshift/openshift-ansible/pull/3610 Can you check your repositories if the excluders are available at all? Just before you run the upgrade, can you run: # yum update atomic-openshift-docker-excluder atomic-openshift-excluder without -y option? Just to verify the excluders can be updated to 3.5. Upstream PR: https://github.com/openshift/openshift-ansible/pull/3631 Excluders are not supported on AH yet. Verified and pass with openshift-ansible-3.5.32 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-2017:0903 |