First of all a thumbs up to all devs for another fine release. An upgrade of a test instance of foreman-1.11.3 worked fine but then there was the announcement of a new katello that uses the new FM :-) Tried to upgrade a test instance of katello (I think 2.4 but could also be 3.0.2 but will check) but that went all wrong during the 'yum upgrade' step. Didn't spend to much time on it since the install didn't contain anything important, so did katello-remove, added back all the repos and did a reinstall of 3.1RC following the docs. Things went smooth this time and had access to the webui. One of the reasons to upgrade was that the foreman_setup plugin didn't generate the correct foreman-installer line when being used. To my surprise it didn't do that on 3.1RC too. I've foreman_setup-4.0 installed and looking at the code I think I have found why. There is a check if its running under katello or foreman and adjust the commandline accordingly BUT it doesn't take into account the fact that Katello switched to foreman-installer since 3.0? or 2.4.x? and thus generates the wrong commandline. It uses katello-installer --enable-capsule instead of foreman-installer --enable foreman-proxy.
@Lucas Should I file a bug in Redmine or use github issues of foreman_setup? If redmine which Category should I use? (Had trouble yesterday filing a request under the right one). Joop -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
