-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
1. Proposed title of this feature request
Verify the registry credentials, registry hostname, and SSL certificates before populating the cache registry during disk to mirror operations
2. What is the nature and description of the request?
Reorder or add preflight checks so customers avoid waiting for the cache registry to be populated before finding out they made a mistake with their CLI options during disk to mirror operations.
3. Why does the customer need this? (List the business requirements here)
Currently oc-mirror v2 will populate the cache registry during disk to mirror operations before validating that the registry credentials, DNS name, and SSL certificates are valid. For large mirror operations, populating the cache registry can take over an hour. This means that if a customer does something like, forgets to add the pull secret CLI flag, mistypes the registry hostname or port, or the SSL certificate are not working, they must wait over an hour for an error. Once the customer resolves the issue, the cache registry will be repopulated, even if the directory was never removed, which will again take over an hour. The result is that simple problems with the auth, cert, or DNS options can take hours to fix if the user makes 1 or more mistakes.
4. List any affected packages or components.
- is triggering
-
OCPSTRAT-2255 oc-mirror v2: Verify creds, hostname, and certs before populating the cache during disk2mirror
-
- Release Pending
-