Error: Minified React error #130

Support
,
1

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 foreman version or should i just wait to update ? moreover i had another server with 3.12 version which updated to 3.15 without any problem.

image
image1396×702 37.7 KB

Expected outcome:

Foreman and Proxy versions:

Foreman and Proxy plugin versions:
foreman_puppet 9.0.0
foreman_discovery 26.0.0
foreman-tasks 11.0.0
Distribution and version:

  • ansible-collection-pulp-pulp_installer-3.22.1-2.el9.noarch
  • ansible-collection-pulp-pulp_installer-doc-3.22.1-2.el9.noarch
  • ansible-collection-theforeman-foreman-5.3.0-1.el9.noarch
  • candlepin-4.4.20-1.el9.noarch
  • candlepin-selinux-4.4.20-1.el9.noarch
  • dynflow-utils-1.6.3-1.el9.x86_64
  • foreman-3.15.0-1.el9.noarch
  • foreman-cli-3.15.0-1.el9.noarch
  • foreman-dynflow-sidekiq-3.15.0-1.el9.noarch
  • foreman-installer-3.15.0-1.el9.noarch
  • foreman-installer-katello-3.15.0-1.el9.noarch
  • foreman-postgresql-3.15.0-1.el9.noarch
  • foreman-proxy-3.15.0-1.el9.noarch
  • foreman-redis-3.15.0-1.el9.noarch
  • foreman-release-3.15.0-1.el9.noarch
  • foreman-selinux-3.15.0-1.el9.noarch
  • foreman-service-3.15.0-1.el9.noarch
  • foreman-vmware-3.15.0-1.el9.noarch
  • katello-4.17.0-1.el9.noarch
  • katello-certs-tools-2.10.0-1.el9.noarch
  • katello-client-bootstrap-1.7.9-2.el9.noarch
  • katello-common-4.17.0-1.el9.noarch
  • katello-repos-4.17.0-1.el9.noarch
  • katello-selinux-5.2.0-1.el9.noarch
  • pulpcore-obsolete-packages-1.3.0-1.el9.noarch
  • pulpcore-selinux-2.0.1-2.el9.x86_64
  • python3.12-pulp-ansible-0.24.6-1.el9.noarch
  • python3.12-pulp-cli-0.32.3-1.el9.noarch
  • python3.12-pulp-container-2.24.2-2.el9.noarch
  • python3.12-pulp-deb-3.5.2-1.el9.noarch
  • python3.12-pulp-glue-0.32.3-1.el9.noarch
  • python3.12-pulp-python-3.13.5-1.el9.noarch
  • python3.12-pulp-rpm-3.29.4-1.el9.noarch
  • python3.12-pulpcore-3.73.12-1.el9.noarch
  • rubygem-dynflow-1.9.1-1.el9.noarch
  • rubygem-foreman-tasks-11.0.0-1.fm3_15.el9.noarch
  • rubygem-foreman_ansible-16.0.0-1.fm3_15.el9.noarch
  • rubygem-foreman_discovery-26.0.0-1.fm3_15.el9.noarch
  • rubygem-foreman_maintain-1.10.3-1.el9.noarch
  • rubygem-foreman_puppet-8.1.1-1.fm3_15.el9.noarch
  • rubygem-foreman_remote_execution-16.0.3-1.fm3_15.el9.noarch
  • rubygem-foreman_virt_who_configure-0.5.26-1.fm3_15.el9.noarch
  • rubygem-hammer_cli-3.15.0-1.el9.noarch
  • rubygem-hammer_cli_foreman-3.15.0-1.el9.noarch
  • rubygem-hammer_cli_foreman_puppet-0.1.1-1.fm3_15.el9.noarch
  • rubygem-hammer_cli_foreman_remote_execution-0.3.2-1.fm3_15.el9.noarch
  • rubygem-hammer_cli_foreman_tasks-0.0.22-1.fm3_15.el9.noarch
  • rubygem-hammer_cli_katello-1.17.0-0.1.pre.main.20250514082549git2c8c109.el9.noarch
  • rubygem-katello-4.17.0-1.el9.noarch
  • rubygem-pulp_ansible_client-0.24.6-1.el9.noarch
  • rubygem-pulp_certguard_client-3.73.9-1.el9.noarch
  • rubygem-pulp_container_client-2.24.2-2.el9.noarch
  • rubygem-pulp_deb_client-3.5.2-1.el9.noarch
  • rubygem-pulp_file_client-3.73.9-1.el9.noarch
  • rubygem-pulp_ostree_client-2.4.8-1.el9.noarch
  • rubygem-pulp_python_client-3.13.5-1.el9.noarch
  • rubygem-pulp_rpm_client-3.29.2-1.el9.noarch
  • rubygem-pulpcore_client-3.73.9-1.el9.noarch
  • rubygem-smart_proxy_dynflow-0.9.4-1.fm3_14.el9.noarch
  • rubygem-smart_proxy_pulp-3.4.0-1.fm3_13.el9.noarch
    Other relevant data:
2

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

3

they are on 8.1.1 – I think we didn’t backport 9.0.0 to 3.15 yet?

4

Ah, okay, I just read through the top lines where he writes about foreman_puppet 9.0.0.

About 3.15:

5

Same issue here, with fix i think:

6

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 new version on puppet

Fixes #37801 - Update to Patternfly 5 by MariaAga · Pull Request #426 · theforeman/foreman_puppet · GitHub

I install puppet with gem install foreman_puppet too and now i have 2 version on puppet

gem list | grep foreman_puppet
foreman_puppet (9.0.0, 8.1.1)

And in About information on my sever i see verion of puppet - 9.0.0

image
image856×354 33.2 KB

I tried to reinstall/delete dnf version 8.1.1 of puppet but it completely crushing my server,so i think that i don’t need to delete this.

7

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 afterwards. Or wait until the foreman_puppet 9.0.0 package will be available for 3.15 and update then.

I’ll have another look once the foreman_puppet 9.0.0 package is available for 3.15. Should be soonish :slight_smile:

8

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.

9

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

10

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.