#theforeman

looks like a good suggestion

ikonia: thanks, i don't know how familiar you are with the code inside foreman, but that would allow a whole lot of simplification to the codebase and likely less bugs around these areas

jsherrill: after I upgraded to katello 3.8 the problem went away

although when the upgrade script was running, there where some errors reported

and I was asked to re-run the upgrade script

the errors persisted but the katello interface is working and I was able to import the repos

so, I'm not sure exactly what failed

kwame: good to know it went away

you can always re-run the installer with --upgrade

to see the failures again

jsherrill: well, before the upgrade script, I ran a yum -y update as the documentation says

and there was an rpm conflict

pulp-consumer-client was conflicting with katello-agent-3.3.5-1.el7.noarch

ah

so, I removed it, ran the yum -y update and it ran without any issues

that works :)

the, after the yum update was finished, I tried to install the pulp-consumer-client but had the same problem

conflict

so, I just went ahead and executed the upgrade script

jsherrill: this is the error --> https://pastebin.com/3YCT1WLG

tbrisker: some parts of it I know out of need, very little though and I've never looked at the orgs stuff as it's just "worked" and never caused a problem

kwame: is your /tmp directory mounted as noexec ?

Hi guys, is there a way to find out which of my hosts are adrift (time wise)? I know that Foreman suggests this in the reports but can I filter / search on this?

you could do it in a puppet module

put an error messig if drift great then X

then all the hosts in foreman that show red you know are out of clock sync

or even better, just fix it by rolling out an ntpdate command and then configuring ntpd

(or chrony whatever)

With foreman/katello is there a way to search for hosts which failed to apply a specific resource on the last puppet run? My intent is to find hosts which had errors installing a certain yum package.

jsherrill: let me check

jsherrill: yes it is

should it not?

kwame: seems like that causes a problem with puppet? https://github.com/puppetlabs/puppetserver/blob...

jsherrill: and about the other issue? the rpm conflict of the pulp-consumer-client package?

is that package needed in katello 3.8?

its not

that might have been fixed by enabling the 3.7 client repo?

but i'm not super concerned about it

ok, so I modified the /tmp mount point

rebooted the server because I also disabled selinux :)

let's see

kwame, dont disable selinux :(

jsherrill: well, I just re-ran the upgrade script and all worked as a charm

Importing Subscriptions

foreman-rake katello:import_subscriptions finished successfully!

Upgrade completed!

great!