Bug 1542387
Summary: | Unable to retrieve image names from rhcc(stage) registry | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zhang Cheng <chezhang> |
Component: | Service Broker | Assignee: | Dylan Murray <dymurray> |
Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.9.0 | CC: | aos-bugs, dymurray, zitang |
Target Milestone: | --- | ||
Target Release: | 3.9.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-27 18:01:32 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: |
Comment 1
Zhang Cheng
2018-02-06 09:49:59 UTC
This appears to be a problem with the stage registry. curl -k https://registry.access.stage.redhat.com/v1/search?q=apb returns a 500. I am asking RCM folks to confirm whether there is an issue with the registry. (In reply to Zhang Cheng from comment #1) > RHCC(stage) registry is QE mainly downstream registry, this issue is > blocking our large number of testing and bug verification. Let me clarify this issue is blocking which testing and bug verification: 1. Blocking the testing relate with / focus on APB images(such as services will be shipped in ocp3.9 life cycle: provision, binding, deprevision, unbinding etc.). 2. Blocking the function test of ansible service broker relate with APB images. 3. Blocking the testing of apb-tools https://github.com/openshift/ansible-service-broker/pull/742 Added a PR to print out the server response for easier debugging. Stage registry is still busted. Zhang, Looks like the stage registry is fixed. Please confirm on your end. I double confirmed, stage registry came back and work well. Dylan, thanks for your tracing and filed IT ticket. 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/RHSA-2018:2013 |