Problem: I have update my foreman+katello server from 3.12 to 3.15 and its broke my Puppet module, and i see Error: Minified React error #130 on the Puppet section on host. I see that this plugin have an update to 9.0 on gem, which i installed but Puppet still shows error. So can i downgrade fore…

[image] KirillZdanovsky: gem list | grep foreman_puppet foreman_puppet (9.0.0, 8.1.1) That does not seem right. If you have a state you can roll back to, I would highly recommend that and then try to install the nightly foreman_puppet packages using dnf and run the foreman-installer afterward…

Hi @KirillZdanovsky , have you run the foreman-installer after upgrading to foreman_puppet 9.0.0?

[image] KirillZdanovsky: rubygem-foreman_puppet-8.1.1-1.fm3_15.el9.noarch they are on 8.1.1 – I think we didn’t backport 9.0.0 to 3.15 yet?

Ah, okay, I just read through the top lines where he writes about foreman_puppet 9.0.0. About 3.15: Update ruby-foreman-puppet to 9.0.0 deb/3.15 ← ATIX-AG:deb_foreman_puppet_9.0.0_3.15 opened 09:07…

Same issue here, with fix i think: [image] Foreman 3.15 React Error when loading page Support Problem: When I select ‘Puppet’ tab in Foreman 3.15 for a host, I’m getting an error message and the page does not load Error: Minified React error #130; visit https://reactjs.…

Yes i use foreman-updater command after update version, i used step-by-step info for update from docs.theforeman.org What about version of foreman_puppet. I have on dnf only rubygem-foreman_puppet-8.1.1-1.fm3_15.el9.noarch from repository, also i see topic with simmilar problem where solution was n…

Thanks for answers, i restored my server on date before update and will try your recommendations. If it’ll not helps i’ll wait for 9.0.0 packet. Thanks again.

foreman_puppet 9.0.0 is now available for 3.15, so please try updating to it again.

Thanks, i have upgraded server to 3.15 with rubygem-foreman_puppet-9.0.0-1.fm3_15.el9.noarch. Tested Puppet and it works, thanks for release.

Error: Minified React error #130

Support

nem July 24, 2025, 10:07am 5

Same issue here, with fix i think: