| Summary: | [RFE]: Add possibility to test connection when creating a custom Registry | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Peter Ondrejka <pondrejk> |
| Component: | Container Management | Assignee: | Daniel Lobato Garcia <dlobatog> |
| Status: | CLOSED ERRATA | QA Contact: | Sebastian Gräßl <sgraessl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2.0 | CC: | bbuckingham, jcallaha, sgraessl, tomckay |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/14181 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-21 16:51:07 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: | |
|
Description
Peter Ondrejka
2016-09-05 13:12:43 UTC
Connecting redmine issue http://projects.theforeman.org/issues/14181 from this bug Peter, This changed - Maybe it's not on 6.2 but for 6.3 at least, when the user tries to add a registry, we not only check the URL is available, but we also: * check the URL is actually for a containers registry * attempt to log in using the user credentials / check if anonymous access is allowed I believe this fixes the bug as it introduces the check you asked for and more. It's not exactly the "test connection" button but you definitely cannot save the registry unless it's a containers registry and you have the credentials. I've linked the commit in the upstream with this issue so it's cp-ed to 6.2.z. Closing tentatively now - let me know if there is something else I'm missing 1405401 Verified on Satellite-6.3 Snap 12. The registry gets checked on submitting it and presents an error in case it is not available or unable to login. 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:0336
|