Problem:
undefined mthod content_view when trying to allocate host a different lifecycle but same content view Expected outcome:
the above works, no errors Foreman and Proxy versions:
3.6 /4.8
Other relevant data:
New setup of Foreman 3.6 with katello 4.8 on EL8. Created the same products, content views and lifecycle environments as our previous Foreman 3.2 setup. Migrated some dev hosts across to this new setup using activation key which puts them into library. Go to the content hosts page and choose the host i want to change to the dev lifecycle environment and once applied, it gives me the below error
ah thats really good to know. I am curently on katello 4.8.1. Can I update katello to 4.8.2 or will i need to update both foreman/katello to 3.7 / 4.9 per Upgrading and Updating Foreman ?
If you still get this error, it seems like the upgrade didnât happen yet. Not sure what happened.
As a workaround, there are a few other places you can change a hostâs content view and lifecycle environment:
From the content host details page;
From the new host details page: Hosts > All Hosts > (select your host) > Content view details > (vertical ellipsis) > Edit content view assignment
From the âChange Content Sourceâ page for the host: Hosts > All Hosts > (select your host) > (vertical ellipsis) > Change content source (if the content source didnât actually change, you donât have to run the job invocation script on the host.)
thanks yeah im aware of the other methods, but my preferred method (which fails) is good because more than 1 content host can selected and changed in bulk
The katello package definitely updated, but perhaps something else is needed to pull it in
Or I could try upgrading to latest version of Foreman/Katello
intersting. The katello-4.8.2-1 update on the proxies also pulled in newer rubgem-katello, but on the master, it did not
I have updated rubygem on the master, then run foreman-installer, but now I receive an error towards the end of thisâŚ
2023-07-07 08:31:05 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[sv-prod-foreman01.splat.bt.com]: Could not evaluate: Error making GET request to Foreman at https://sv-prod-foreman01.splat.bt.com/api/v2/smart_proxies: Response: 500 Internal Server Error: Check /var/log/foreman/production.log on sv-prod-foreman01.splat.bt.com for detailed information
2023-07-07 08:31:05 [NOTICE] [configure] 1500 configuration steps out of 1502 steps complete.
2023-07-07 08:31:07 [NOTICE] [configure] System configuration has finished.
There were errors detected during install.
Please address the errors and re-run the installer to ensure the system is properly configured.
thanks, yeah tried that and managed to get the installer happy again after a few attempts.
also tested the lifecycle change and all good
is there a need to also update katello-debug and katello-repos to 4.8.2.1 or can leave as is?
Will likely perform a full update to 3.7 / 4.9 in the next month or so anyway