Unable to register content host to Katello 4.2.0.1 RC3

Problem:
When trying various ways to register a content host to Katello, it fails with message “HTTP error (400 - Bad Request): Problem creating unit class ConsumerDTO”.
Expected outcome:
When using subscription-manager command with an activation key it would register as normal.
Foreman and Proxy versions:
foreman-3.0.0-1.el8.noarch
foreman-proxy-3.0.0-1.el8.noarch
Foreman and Proxy plugin versions:
foreman-tasks 5.1.0
foreman_ansible 6.4.1
foreman_leapp 0.1.7
foreman_puppet 1.0.3
foreman_remote_execution 4.7.0
katello 4.2.0.1.rc3
Distribution and version:
Alma Linux 8.4
Other relevant data:
In addition to the registration issue, Apache won’t start after latest general updates.

Apache error message " httpd: Configuration error: More than one MPM loaded"

I worked around it by commenting all LoadModule lines in /etc/httpd/conf.modules.d/00-mpm.conf. Once I did that it still would not start because multiple configuration files were trying to use port 443. This port is defined in both /etc/httpd/conf.d/05-foreman-ssl.conf and /etc/httpd/conf.d/ssl.conf. To work around the port issue, I simply removed /etc/httpd/conf.d/ssl.conf. Once those items were complete all services started without issue.

Still my last item that isn’t working is registering content hosts.

Output from log /var/log/foreman/production.log during a registration attempt.

RestClient::BadRequest: Katello::Resources::Candlepin::Consumer: 400 Bad Request {“displayMessage”:"Problem creating unit class ConsumerDTO

I have able to get back to working status. I first downgraded the packages that were updated on 10/12 then ran ‘foreman-installer -v’ to reset the configuration. Once done, I was able to successfully register a system and update the packages. I see that the final release for Katello 4.2.0.1 so I’m half tempted to update all the packages again then re-run the foreman-installer to see if any issues comeback.

Here are the packages that were downgraded.

Picture1

I went ahead and updated the Katello server to the all latest packages then ran the foreman-installer again to reset the configuration. I have done a little validation like registering a new system and all appears to working as expected.

1 Like