Foreman DEB nightly pipeline failed:
https://ci.theforeman.org/job/foreman-nightly-deb-pipeline/1374/
foreman-pipeline-foreman-deb-nightly (failed) (remote job)
This seems to be fallout from the recent foreman-js release.
I pinged Maria on Matrix about this, but here is a brief version of my investigation.
With foreman-js (well, theforeman/builder/theforeman/vendor) 12.2.2, current nightly fails with errors in the console:
/webpack/foreman_puppet/foreman_puppet:global-b717f9fce8d9f45edda0.js: Uncaught TypeError: (0 , r.translate) is not a function
Also, the overall Puppet JS integration seems dead. As in: you go to a host detail page, and there is no “Puppet” tab. Opening the (known) link to the Puppet data just renders an empty content block (the rest of the UI is fine).
Rebuilding foreman_puppet seems to fix the first error (“not a function”) but now I see a ton of componentRegistry.js:58 Component name already taken: <some component> in the console and visiting https://foreman.example.com/new/hosts/foreman.example.com#/Puppet/reports gives an error:
foreman-vendor.bundle-v12.2.2-production-7763c14b92d0009d309d.js:277 TypeError: Cannot read properties of undefined (reading 'Puppet details')
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.