Bug 1457379
| Summary: | [3.3] exclude list stays the same after atomic-openshift-docker-excluder pkg update | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Release | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.1 | CC: | adellape, aos-bugs, jiajliu, jokerman, jrosenta, mmccomas, tdawson, wsun, xtian |
| Target Milestone: | --- | ||
| Target Release: | 3.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The rpm scripts that run when upgrading atomic-openshift-docker-excluder were executed at the wrong times which may have led to incorrect docker versions being excluded. These scripts have been corrected and will not ensure that the proper versions are excluded when the package is updated.
|
Story Points: | --- |
| Clone Of: | 1430929 | Environment: | |
| Last Closed: | 2017-06-20 06:21:51 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: | |||
| Bug Depends On: | 1430929 | ||
| Bug Blocks: | 1426570 | ||
|
Comment 1
Scott Dodson
2017-06-09 03:18:41 UTC
Version: atomic-openshift-docker-excluder-3.3.1.38-1.git.0.5695b84.el7.noarch Steps: 1. prepare 3.2 repo and install atomic-openshift-docker-excluder 2. prepare 3.3 repo on the hosts 3. Update docker-excluder to 3.3 #yum update atomic-openshift-docker-excluder Result: ->before update exclude= docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* docker*1.13* docker*1.12* docker*1.11* ->after update exclude= docker*1.20* docker*1.19* docker*1.18* docker*1.17* docker*1.16* docker*1.15* docker*1.14* docker*1.13* docker*1.12* The issue has been fixed. 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:1492 |