Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-33098

Provide user a way to determine if the error happens during a mirroring is actually an error or a flake

XMLWordPrintable

    • Important
    • No
    • CLID Sprint 253
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, with oc-mirror plugin v2 (Technology Preview), mirroring errors were only displayed in the console output, making it difficult for users to analyze and troubleshoot other issues. For instance, an unstable network might just require a rerun, while a manifest unknown error might need further analysis to skip an image or operator. With this update, a file is generated that contains all errors in the workspace's `working-dir/logs` folder. And all the errors that occur during the mirroring process are now logged in `mirroring_errors_YYYYMMdd.txt`.
      (link:https://issues.redhat.com/browse/OCPBUGS-33098[*OCPBUGS-33098*])
      Show
      Previously, with oc-mirror plugin v2 (Technology Preview), mirroring errors were only displayed in the console output, making it difficult for users to analyze and troubleshoot other issues. For instance, an unstable network might just require a rerun, while a manifest unknown error might need further analysis to skip an image or operator. With this update, a file is generated that contains all errors in the workspace's `working-dir/logs` folder. And all the errors that occur during the mirroring process are now logged in `mirroring_errors_YYYYMMdd.txt`. (link: https://issues.redhat.com/browse/OCPBUGS-33098 [* OCPBUGS-33098 *])
    • Bug Fix
    • Done

      Description of problem:

      Currently in oc-mirror v2 user have no way of determining if the error occurs during a mirror is an actual mirror or a flake. We need to provide a way for the user to determine such errors easily which will make the product/user experience better.

      Version-Release number of selected component (if applicable):

          [knarra@knarra-thinkpadx1carbon7th openshift-tests-private]$ oc-mirror version
WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.16.0-202404221110.p0.g0e2235f.assembly.stream.el9-0e2235f", GitCommit:"0e2235f4a51ce0a2d51cfc87227b1c76bc7220ea", GitTreeState:"clean", BuildDate:"2024-04-22T16:05:56Z", GoVersion:"go1.21.9 (Red Hat 1.21.9-1.el9_4) X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}

      How reproducible:

           Always

      Steps to Reproduce:

          1.  Install latest oc-mirror v2
    2.  Run mirror2disk via command `oc-mirror -c <config.yaml> file://out --v2`
    3.  Now run disk2mirror via command `oc-mirror -c <config.yaml> --from file://out docker:<localhost:5000>/mirror

      Actual results:

          sometimes mirror fails with error 
 2024/04/24 13:15:38  [ERROR]  : [Worker] err: copying image 3/3 from manifest list: reading blob sha256:418a8fe842682e4eadab6f16a6ac8d30550665a2510090aa9a29c607d5063e67: fetching blob: unauthorized: Access to the requested resource is not authorized

      Expected results:

           There should be a way for user to determine whether the error happened was an actual error or kind of a race. Above error is not  intutive

      Additional info:

          Discussed here https://redhat-internal.slack.com/archives/C050P27C71S/p1714025295014549

              rh-ee-aguidi Alex Guidi
              knarra@redhat.com Rama Kasturi Narra
              Rama Kasturi Narra Rama Kasturi Narra
              Subhashini T K Subhashini T K
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: