Nexus not populated with Labs NPM Resources - No Error - Jenkins Fails

[tmichett]

Jenkins exercise will fail with strange issues. Typically because it can't find certain artifacts. For example ...

npm ERR! 404 Repository not found - GET http://nexus:8081/repository/labs-npm/zone.js/-/zone.js-0.11.4.tgz
npm ERR! 404 
npm ERR! 404  'zone.js@http://nexus:8081/repository/labs-npm/zone.js/-/zone.js-0.11.4.tgz' is not in this registry.
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

This is related to the Nexus build and deployment from earlier. Nexus reports back fine with ArgoCD and OpenShift and Nexus appears to be working. However, when looking at Nexus, all the repositories haven't been loaded.

Jenkins build fails ...

[tmichett]

@springdo @oybed @eformat

This has happened a few times during multiple deliveries.

Solution ...

Delete Nexus Setup Job from ArgoCD and OCP

Resync job and Rebuild

@springdo did this for our group in the TL500 Raleigh July 2022 delivery. Please add additional context and description.

Need to notify users in best case on failure so can re-deploy, but we also need this added for facilitators/instructors for troubleshooting and quick resolutions.

[eformat]

OK .. we are using an old version of the chart. Newer version has some fixes to make this more robust in failure scenarios, specifically:

redhat-cop/helm-charts@2057947

I have just updated the exercises for this 1.1.6

rht-labs/tech-exercise@490866a

lets see how that goes. You should see a failure when installing the nexus chart if the repos fail to install.

Also, we made the red-hat repos optional in public - as Nexus is very slow on first request if there are multiple repos with the same dep and all of our deps are either in mvn central or npm. So we install them, but do not use them in tl500.

We can keep this open and monitor how it goes ?

For completeness i was checking the nightly test suite from yesterday where this has been working OK, so pretty sure the above chart fix should work for us.

[tmichett]

Thanks @eformat - this is wonderful to hear, but yes, keeping this open for tracking would be a great idea.