I am trying to upgrade from 1.20.2 to 1.21.0-1 but yum keeps failing with dependency errors. I attempted this with Katello 3.9 but have since upgraded to Katello-3.10 but th esame problem keeps occurring.
Error:
--> Processing Dependency: foreman-webpack-vendor-js(8f1a560ed7b654fe8dba) for package: tfm-rubygem-katello-3.10.0-1.el7.noarch
---> Package tfm-rubygem-xmlrpc.noarch 0:0.3.0-1.el7 will be installed
--> Finished Dependency Resolution
Error: Package: tfm-rubygem-katello-3.10.0-1.el7.noarch (@katello)
Requires: foreman-webpack-vendor-js(8f1a560ed7b654fe8dba)
Removing: foreman-1.20.2-1.el7.noarch (@foreman)
foreman-webpack-vendor-js(8f1a560ed7b654fe8dba)
Updated By: foreman-1.21.0-1.el7.noarch (foreman)
Not found
rubygem-katello-3.10.0-1.el7.noarch was installed as part of the Katello upgrade and has a dependancy for foreman-webpack-vendor-js(8f1a560ed7b654fe8dba):
Hello,
Katello 3.10 is not compatible with Foreman 1.21.
Katello 3.11 should be out soon and will be compatible - @Jonathon_Turel can give us an updated estimate of when we can expect its release.
Hello another noob user here.
Is Foreman 1.21 compatible with Katello 3.11 RC2?
From my usage so far IMHO it would seem that using Foreman with the Katello plug-in would be the most popular use case. Is it on the roadmap for these projects that going forward both latest releases of Katello & Foreman would be tested to make sure that they actually work together before releasing? I’ve read thru the release notes for each’s latest releases and I don’t see it stated in either that they are not compatible. Thankfully, you stated this above but you get the idea.
Hi,
Usually Katello is released in coordination with Foreman releases. In this case there was a significant bug (Bug #25515: Subscription detail page is empty - Katello - Foreman) that delayed the Katello release by a bit, but we are hoping to get the final 3.11.0 version packaged and released this week. 3.11 RC2 may work with 1.21, but keep in mind that it still contains a few bugs that were fixed for the final 3.11 release.
You are correct that there is no mention in the documentation of which Foreman version is compatible with which Katello version - PRs welcome! The Katello manual source can be found here: https://github.com/theforeman/theforeman.org/tree/gh-pages/plugins/katello/
There’s also been some discussions led by @rabajaj and @lzap regarding redesigning the manual completely. If you want to help in that effort I’m sure they’ll be happy
Thanks for the info. Actually as I learn more with this I’d be happy to help w/documentation around some of the things that I’ve been stumbling with (like this issue). The product that you all have built along w/all of the plugins is really awesome!
thanks,
Greg
Finally got around to building a new instance of Foreman/Katello using versions 1.21.0 and 3.11. The install worked flawlessly so thanks and excellent job.
For some reason, it didn’t show the default login creds nor do I see them in /var/log/foreman-installer/katello.log… Am I looking in the wrong place?
To install an additional Foreman proxy on separate machine continue by running:
foreman-proxy-certs-generate --foreman-proxy-fqdn “$FOREMAN_PROXY” --certs-tar “/root/$FOREMAN_PROXY-certs.tar”
The full log is at /var/log/foreman-installer/katello.log
yum install -y -q rh-mongodb34-syspaths finished successfully!
The Katello installer only outputs the credentials on the first run, after that it places a .installed file. Perhaps that already existed which is why it wasn’t shown? You could remove it, rerun the installer to verify this.
You can also pass --foreman-initial-admin-password mypassword to explicitly set it on fresh installs.
This was a fresh install on a newly built VM (CentOS-7-x86_64-Minimal-1810) so there was nothing preexisting. In any event that was the only snag. I’ll be building 2 more over the next week so I’ll try your suggestion if one of those exhibits the same problem.
