Bug 1677214
Summary: | Email field should be an optional on Create Image Pull Secret page | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> |
Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | aos-bugs, jhadvig, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Email field on Create Image Pull Secret page is required, even though email is not a required credential for any registry config.
Consequence: User has to provide email on Create Image Pull Secret page even though it's not necessary.
Fix: Removing the requirement to provide email when creating Image Pull Secret.
Result: It's not necessary for the user to provide email when creating Image Pull Secret.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:44:00 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
XiaochuanWang
2019-02-14 09:58:49 UTC
The email field now is an optional. Created Image Pull secret successfully as below: {"auths":{"docker.io":{"username":"xiaocwan","password":"bla","auth":"eGlhb2N3YW46Vml2aWFuLTEyMw==","email":""}}} Verified on 4.0.0-0.nightly-2019-02-26-125216 Image: registry.svc.ci.openshift.org/ocp/release@sha256:ad591cc0d5654a14e3b722d0c7e538889900ea2c99f800597b9afb66c0be4ba0 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-2019:0758 |