Feature Overview (aka. Goal Summary)  

oc-mirror v2 can fail fast by checking registry credentials, DNS name, and SSL certificates are valid before populating the cache for disk2mirror.

Goals (aka. expected user outcomes)

Currently, oc-mirror directly starts from populating the cache (could take ~1 hour according to the reports from the NAPS front) and then starts the mirroring, and only to figure the access to the mirror registry failed (e.g., perhaps users forgot to add pull secrets or a typo in the registry hostname, etc).  

User fixed that error and restarted the session, and it took another hour to repopulate the cache (as described in the RFE)

With this behavior change, oc-mirror will fail quickly by checking if the mirror registry is accessible before the caching starts to help users address the underlying issues before going too far.

Requirements (aka. Acceptance Criteria):

oc-mirror v2 can fail quickly by verifying that registry credentials, DNS name, and SSL certificates are valid before populating the cache for disk2mirror.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>