Bug 1618696
| Summary: | libuv.so.0.10 is in the wrong place of logging-auth-proxy image | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Logging | Assignee: | Rich Megginson <rmeggins> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.10.0 | CC: | ahaile, aos-bugs, bleanhar, rmeggins, tbielawa |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 3.10.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openshift3/logging-auth-proxy:v3.10.29-1 | Doc Type: | No Doc Update |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-22 04:55:14 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
Junqi Zhao
2018-08-17 11:06:59 UTC
I see when looking through our image build info that logging auth proxy is the only one using this suspiciously relevant looking content source > $ grep -r rhel-server-ose-OLD_NODE_JS-rpms groups/*/images/* > groups/openshift-3.10/images/logging-auth-proxy.yml:- rhel-server-ose-OLD_NODE_JS-rpms > groups/openshift-3.11/images/logging-auth-proxy.yml:- rhel-server-ose-OLD_NODE_JS-rpms > ... Which is mapped as such: > rhel-server-ose-OLD_NODE_JS-rpms: > conf: > baseurl: http://download.lab.bos.redhat.com/rcm-guest/puddles/RHAOS/AtomicOpenShift-signed/3.2/building/RH7-RHAOS-3.2/x86_64/os/ > content_set: > default: rhel-7-server-ose-3.2-rpms Pinging my team to see if they have any more insight. Not a TestBlocker for logging-auth-proxy:v3.10.34 No such issue in logging:v3.10.44 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:2660 |