Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-190

COO-Prometeheus candidate for 0.3.0 is not building due to cachito issues

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 0.3.0
    • 0.3.0
    • None
    • None
    • MON Sprint 255
    • Critical
    • No

      After the latest bump to obo-prometheus, which  is needed by the latest release. prometheus builds have started having issues with cachito related to npm dependencies.

      Overall, there seems to be two issues. The first one is related to two missing keys in package-lock.json missing two keys (resolved and integrity). This looks related to this npm issue. https://github.com/npm/cli/issues/4263

      [2024-06-18 10:33:37,461 cachito.workers.nexus INFO nexus.execute_script] Executing the Nexus script js_cleanup
      e[39570157-1b8e-4ed5-b8c9-0232ce5cb07a] raised unexpected: InvalidRepoStructure("@forevolve/bootstrap-dark@file:react-app/node_modules/@forevolve/bootstrap-dark is a 'file:' dependency. File dependencies are allowed if: a) the dependency is declared as a workspace in package.json or b) the dependency is present in the server-side allowlist.")
      Traceback (most recent call last):
        File "/usr/local/lib/python3.11/site-packages/celery/app/trace.py", line 477, in trace_task
          R = retval = fun(*args, **kwargs)
                       ^^^^^^^^^^^^^^^^^^^^
        File "/usr/local/lib/python3.11/site-packages/celery/app/trace.py", line 760, in __protected_call__
          return self.run(*args, **kwargs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^
      

       

      In order to overcome this, the same solution doesn't seem to work as Prometheus uses workspaces for the reactg-app, which was making the outcome fail as it would require also such keys for the workspace dependencies, nonexistent on the initial, upstream file.

      tmadore provided us with some build that he mentioned worked but after testing it with the build we're getting also another issue with cachito

      2024-06-18 11:58:14,104 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! code E404
      2024-06-18 11:58:14,104 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! 404 Remote Manually Blocked - GET https://cachito-nexus.engineering.redhat.com/repository/cachito-npm-1471393/nise/-/nise-5.1.9.tgz
      2024-06-18 11:58:14,104 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! 404
      2024-06-18 11:58:14,104 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! 404  'nise@https://cachito-nexus.engineering.redhat.com/repository/cachito-npm-1471393/nise/-/nise-5.1.9.tgz' is not in this registry.
      2024-06-18 11:58:14,104 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! 404
      2024-06-18 11:58:14,104 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! 404 Note that you can also install from a
      2024-06-18 11:58:14,155 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! 404 tarball, folder, http url, or git url.
      2024-06-18 11:58:15,407 - atomic_reactor.tasks.binary_container_build - INFO - 
      2024-06-18 11:58:15,407 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR! A complete log of this run can be found in:
      2024-06-18 11:58:15,409 - atomic_reactor.tasks.binary_container_build - INFO - npm ERR!     /root/.npm/_logs/2024-06-18T11_57_24_064Z-debug-0.log
      

       

       

              dmellado1@redhat.com Daniel Mellado Area
              dmellado1@redhat.com Daniel Mellado Area
              Mario Fernandez Herrero
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: