Re: [foreman-users] Errata and Content View issue

On 9 December 2017 at 07:38, Arsène Gschwind wrote: > Hi, > > I'm running Foreman 1.15.6 and Katello 3.4. > I did apply an Errata to a host what did generate a new Content View > version, so far s good. The new Content View includes the Errata but not > the package for

Re: [foreman-users] [foreman-announce] Katello 3.5.0 (a.k.a. Schwarzbier) is Here!

Thanks to all involved! Updates applied easier than ever before. Nice little speed bump in spots. Cheers L. -- "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared

Re: [foreman-users] Re: Foreman-Katello installation

On 24 November 2017 at 03:23, Ondrej Prazak wrote: > Hi, > I just went over the installation steps at [1]. I executed on a clean > CentOS 7: > > yum -y localinstall > http://fedorapeople.org/groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-repos-latest.rpm > yum -y

Re: [foreman-users] katello 3.3

On 18 October 2017 at 09:20, Edward Clay wrote: > I have some host that I attempted to apply applicable erratas to in a > large group of host. During that task some host failed and others > completed. I can't remember why they failed but I was able to manually >

[foreman-users] Re: How to remove a lifecycle environment from a content view?

On 5 October 2017 at 10:35, Lachlan Musicman <data...@gmail.com> wrote: > If a Lifecycle Environment is inadvertently promoted to the wrong Content > View, what is the process for removing it from that content view? > > To answer my own question - you use "remove&quo

[foreman-users] How to remove a lifecycle environment from a content view?

If a Lifecycle Environment is inadvertently promoted to the wrong Content View, what is the process for removing it from that content view? cheers L. -- "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should

Re: [foreman-users] Re: [Katello] Successfully imported CentOS errata into Katello

Hmm. I'm about to leave work, but it works for us with no major changes. We run Foreman 1.15.3 and Katello 3.4.5 L. -- "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared

[foreman-users] Re: How to add Content View to Lifecycle Environment?

@greggish https://twitter.com/greggish/status/873177525903609857 On 6 September 2017 at 08:12, Lachlan Musicman <data...@gmail.com> wrote: > We are using Foreman 1.15.3 and Katello 3.4.5 > > I haven't had to create a Lifecycle environment for a while. When my > colleague went t

[foreman-users] Re: Katello::Errors::PulpError: PLP0000: /path/to/thing exists, but should be a symlink. Cannot find published directory.

On 30 August 2017 at 09:30, Lachlan Musicman <data...@gmail.com> wrote: > Error per subject line, but no obvious method to resolve? > > Would be happy to stop task and delete that version - but even that is not > an option? > Argh! My bad - found a very subtle "Sk

[foreman-users] Katello::Errors::PulpError: PLP0000: /path/to/thing exists, but should be a symlink. Cannot find published directory.

Error per subject line, but no obvious method to resolve? Would be happy to stop task and delete that version - but even that is not an option? cheers L. -- "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor

Re: [foreman-users] Re: subscription expected behaviour?

On 18 August 2017 at 12:58, Andrew Schofield wrote: > Activation keys are good for the initial host registration only. If you > assign new products to a content view then you need to : > > a) Add these to the activation key (so newly provisioned servers get the > new repos)

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

On 30 May 2017 at 16:31, Evgeni Golov <evg...@redhat.com> wrote: > On Tue, May 30, 2017 at 11:50:40AM +1000, Lachlan Musicman wrote: > > On 30 May 2017 at 11:40, Lachlan Musicman <data...@gmail.com> wrote: > > > > > Great, thanks. > > > > > &g

Re: [foreman-users] Re: LCE or CV/CCV package differentials

.com/theforeman/rfcs/pull/17 > > I've written a script using both hammer and apipie to do comparisons I > could share. > > On Aug 3, 2017 7:35 PM, "Lachlan Musicman" <data...@gmail.com> wrote: > >> >> On 3 August 2017 at 22:42, Greg Sutcliffe <greg.sut

Re: [foreman-users] Re: LCE or CV/CCV package differentials

On 3 August 2017 at 22:42, Greg Sutcliffe <greg.sutcli...@gmail.com> wrote: > On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote: > > On the "I wish" pile. > > Maybe also add it to our "I wish" pile too? :) > > http://projects.the

Re: [foreman-users] Re: LCE or CV/CCV package differentials

ween two content view versions. > > We do this by grabbing all packages / puppet modules (as that's the two > bits we're interested in) in the two content view versions and diff'ing. > Its slow. Really slow - like 15 minutes or so slow. > > On Tuesday, August 1, 2017 at 12:59:02 AM

[foreman-users] Re: LCE or CV/CCV package differentials

On 1 August 2017 at 14:14, Lachlan Musicman <data...@gmail.com> wrote: > Hola, > > Is there an easy way to get a comprehensive list of package changes > between two CV versions or two Lifecycle Environment versions? > > I'm looking into the hammer help no

[foreman-users] LCE or CV/CCV package differentials

Hola, Is there an easy way to get a comprehensive list of package changes between two CV versions or two Lifecycle Environment versions? I'm looking into the hammer help now, and have found http://projects.theforeman.org/issues/20046 which suggests that a per CV package list is available. I

Re: [foreman-users]

ish/status/873177525903609857 On 17 July 2017 at 08:38, Lachlan Musicman <data...@gmail.com> wrote: > On 14 July 2017 at 21:33, Daniel Lobato Garcia <elobat...@gmail.com> > wrote: > >> > >> > I'm getting the error: >> > >> > RPM1015: Malformed repo

Re: [foreman-users]

On 14 July 2017 at 21:33, Daniel Lobato Garcia wrote: > > > > I'm getting the error: > > > > RPM1015: Malformed repository: metadata is missing for some packages > > in filelists.xml and in other.xml > > > > There are a lot of pulp bugs reported to this end, but none with a

[foreman-users]

With both http://yum.theforeman.org/releases/1.15/el7/x86_64/ and http://yum.theforeman.org/releases/latest/el7/x86_64/ I'm getting the error: RPM1015: Malformed repository: metadata is missing for some packages in filelists.xml and in other.xml There are a lot of pulp bugs reported to this

Re: [foreman-users] Hosts: One or more processes require restarting

so run "tracer -ea" on the client. > > On Wed, 5 Jul 2017 at 23:28, Lachlan Musicman <data...@gmail.com> wrote: > >> On 5 July 2017 at 23:38, Daniel Lobato Garcia <elobat...@gmail.com> >> wrote: >> >>> On 07/05, Lachlan Musicman wrote: >>

Re: [foreman-users] Hosts: One or more processes require restarting

On 5 July 2017 at 23:38, Daniel Lobato Garcia <elobat...@gmail.com> wrote: > On 07/05, Lachlan Musicman wrote: > > When I look in the "all hosts" page of Foreman gui, some hosts are marked > > as orange with the note "One or more processes require restarting&q

[foreman-users] Hosts: One or more processes require restarting

When I look in the "all hosts" page of Foreman gui, some hosts are marked as orange with the note "One or more processes require restarting": How do I find which process that is so I can restart it? cheers L. ​ -- "Mission Statement: To provide hope and inspiration for collective action,

Re: [foreman-users] Unable to add non-RHEL subscription to activation key

Make the Product into a Content View - then add that to the activation key, then add the subscriptions. Cheers L. -- "Mission Statement: To provide hope and inspiration for collective action, to build collective power, to achieve collective transformation, rooted in grief and rage but

[foreman-users] Re: Couldn't find User with 'id'=3 [WHERE (1=0)]

ement: To provide hope and inspiration for collective action, to build collective power, to achieve collective transformation, rooted in grief and rage but pointed towards vision and dreams." - Patrisse Cullors, *Black Lives Matter founder* On 19 June 2017 at 10:09, Lachlan Musicman <data...@gma

[foreman-users] Re: Listing all packages on all hosts?

ieve collective transformation, rooted in grief and rage but pointed towards vision and dreams." - Patrisse Cullors, *Black Lives Matter founder* On 9 June 2017 at 08:10, Lachlan Musicman <data...@gmail.com> wrote: > Is there a command line one liner that will list all packages install

[foreman-users] Listing all packages on all hosts?

Is there a command line one liner that will list all packages installed on hosts? cheers L. -- "Mission Statement: To provide hope and inspiration for collective action, to build collective power, to achieve collective transformation, rooted in grief and rage but pointed towards vision and

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

On 30 May 2017 at 11:40, Lachlan Musicman <data...@gmail.com> wrote: > Great, thanks. > > I am seeing another issue: > > - add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc) > to the Katello Content View (with or without removing pulp-3.3, > kat

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

ured for a typical installation. If you are importing all > the necessary repositories into Katello and using that yourself then I > wouldn't worry about it. > > Eric > > > On Mon, May 29, 2017 at 8:51 PM, Lachlan Musicman <data...@gmail.com> > wrote: > >> Thanks for all

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

Thanks for all the hard work. I'd like to ask a question about the upgrade instructions. In step 3, what does the line yum update -y foreman-release-scl do? The other two lines make sense. This one, I don't quite understand. We host Katello on katello, so there is some jiggery-pokery with

Re: [foreman-users] Katello 3.4 RC2 Available for Testing

Did Katello 3.4 get released yet - did I miss an announcement? I feel like there has been movement on the github (3.4.0 released 11 days ago, 3.4.0.1 released over the weekend?) Cheers L. -- "Mission Statement: To provide hope and inspiration for collective action, to build collective

[foreman-users] Foreman 1.14/Katello 3.3 upgrade make CCVs useless

Hi I upgraded Foreman/Katello successfully (ie, without warning or error) from 1.13/3.2 -> 1.14/3.3 Now, when I go to a Composite Content Views, their "List/Remove Content Views" has the right number of rows in the table, but there is no text nor any ability to update to a newer version. This

[foreman-users] Filesystem changes for repositories after update?

Hi, We recently (3 months ago?) updated from one version of Katello to the next (Foreman 1.12 to 1.13; Katello 3.1 to 3.2). During that process I also changed the structure of our Content Views and Composite Content Views to better reflect our structures. Last week we started to run out of room

[foreman-users] Updating Subscriptions in Activation Key

When I update the subscriptions in an Activation Key, how do I get that change pushed to the systems that are subscribed via that key? I've tried yum clean all and subscription-manager refresh, but neither works. The only way I've had success is to subscription-manager unregister and then

[foreman-users] Katello and Errata updates

Hola, When one ticks off an Errata, a minor version of the Content View is created (see att image). How are they stored on the filesystem? Is it ok to delete any of the versions an just keep the most recent? For eg, if I make version 3.0 and then over a month there are 4 errata updates, taking

Re: [foreman-users] CentOS foreman 1.12.4 puppet 3.7.x best Upgrade Procedure to puppet 4.x

The recommended steps in the docs are what I followed https://theforeman.org/plugins/katello/3.2/upgrade/puppet.html cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 2 March 2017 at 22:53, Karsten Horsmann

Re: [foreman-users] Katello 3.3 building CentOS 7 hosts

I don't know if there's an automagic way to do it, but I use ansible to change all files in /etc/yum.repos.d/ except "redhat.repo". In each file change any enabled =1 to enabled = 0. cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper

Re: [foreman-users] Re: Sync is stuck in pending

Break or break through. running foreman-installer --scenario katello --upgrade seems to have solved the issue. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 28 February 2017 at 11:39, Lachlan Musicman <data...@gma

Re: [foreman-users] Re: Sync is stuck in pending

s/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context' I've broken pulp, haven't I. L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 28 February 2017 at 09:29, Lachlan Musicman <dat

Re: [foreman-users] Re: Sync is stuck in pending

wrote: > Try foreman-rake katello:reimport > > foreman-rake katello:reindex Has been renamed recently. > > On Mon, 27 Feb 2017 at 00:49, Lachlan Musicman <data...@gmail.com> wrote: > >> Search turned up this potential solution: >> >> https://access.redhat.com/d

[foreman-users] Re: Sync is stuck in pending

problems. The problem seems to have persisted - where do I look next? cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 27 February 2017 at 09:39, Lachlan Musicman <data...@gmail.com> wrote: > CentOS 7.3, Katello

[foreman-users] Sync is stuck in pending

CentOS 7.3, Katello 3.2, Foreman 1.13.4 And it's cascading - there are four other sync's that haven't finished because one seems to be in a permanent pending state. I don't see any obvious cancel/resume function? The cancel link on the sync status page bounces when clicked but...nothing. The

[foreman-users] Composite Content Views have become disassociated from CVs

Hola, I seem to have a couple of CCVs that have become disassociated from their relevantAs Content Views. As can be seen in the screen shot, one CCV has completely unmoored and has no CVs associated with it any more. I have been aggressive in my cleaning up of old versions and views, but I've

Re: [foreman-users] Programmatic method for finding content views?

ptions. > > The API: > https:///apidoc/v2/content_views.html > > Nailgun: > https://github.com/SatelliteQE/nailgun > > Various projects here: > https://github.com/RedHatSatellite > > > > -- > *From: *"Lachlan Mu

[foreman-users] Programmatic method for finding content views?

I have become comfortable with the Foreman/Katello GUI, but sometimes I want an easy way to find a list of Composite Content Views, their versions, what Content View is in each version of said Composite Content View, and what that version is. eg: list CCVs CCV Worker Node v5.0: - base centos

[foreman-users] foreman-console throws rake error, fails to load console gems

Hi, While trying to debug my other issues, I found this potential solution https://access.redhat.com/solutions/1381053 after noticing that I had a "Package Profile Update" job in the planning state but not moving to pending or doing anything. Clicking on the job gave me *Oops, we're sorry but

[foreman-users] Pulp streamer is looking for non directory

Hola, I am seeing a lot of errors because one repository seems to be off kilter. The directory that it is publishing as being where the various rpms can be found doesn't exist on the file system. The symptoms I see on the content hosts are failures to update

[foreman-users] Promotion Errors: how to solve?

Hi, Using CentOS 7.3 Katello 3.2 and Foreman 1.13.4 I'm getting an error while promoting a LCE. It is stuck on Paused. I can skip the erroneous step, but then the repos are broken. I'm confused about how to cancel, kill and/or unwind the job once it gets into this state. I have been skipping,

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

44, Eric D Helms <eric.d.he...@gmail.com> wrote: > Could you please file a bug report with this information including your > fix or add it to an existing report so that we can look at getting this > fixed in the upcoming 3.3 release? > > Thanks > Eric > > > On Feb

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

bug solution after it, and all worked fine. cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 17 February 2017 at 14:54, Lachlan Musicman <data...@gmail.com> wrote: > Daniel, > > running the instructions

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

ote: > On 02/13, Lachlan Musicman wrote: > > Ok, I've found the itemized puppet upgrade instructions that are here: > > > > http://projects.theforeman.org/projects/foreman/wiki/ > > Upgrading_from_Puppet_3_to_4 > > > > and the place where the doc'd proc

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

Klaas, Thank you for this, much appreciated. We have decided to revert back to snapshot taken last week and try again - your notes will be very helpful. One thing in particular that has us confused is 18131 "foreman-installer --upgrade-puppet fails to set new paths for foreman-installer"

[foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

February 2017 at 12:56, Lachlan Musicman <data...@gmail.com> wrote: > Ok, I've found the itemized puppet upgrade instructions that are here: > > http://projects.theforeman.org/projects/foreman/wiki/Upgradi > ng_from_Puppet_3_to_4 > > and the place where the doc'd process fai

[foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

way." - Grace Hopper On 13 February 2017 at 11:28, Lachlan Musicman <data...@gmail.com> wrote: > I don't understand what I've done wrong - I am literally following the > rule book here, but it seems to trip at every step. > > I read the logs, and discovered that there we

[foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

--skip-copy-data" Anyway - I guess my question now is do I even need to run the --upgrade-puppet? Cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 13 February 2017 at 10:19, Lachlan Musicman <data...@gmail.com&

[foreman-users] Re: Errno 14 404 not found

This seems to have solved itself when I published a new version and promoted to that. cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 13 February 2017 at 09:40, Lachlan Musicman <data...@gmail.com> wrote: > H

[foreman-users] Puppet upgrade from 3.x to 4.x fails

Hi, Self hosted installation. The upgrade foreman-installer --upgrade-puppet fails because it can't find packages. Which would be because I've just turned off all services as asked to in the instructions found here https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html under "in

[foreman-users] Re: Errno 14 404 not found

this by hand, but that is less than ideal. How do I fix it more permanently? cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 13 February 2017 at 09:25, Lachlan Musicman <data...@gmail.com> wrote: > Hola, > > I

[foreman-users] Unused Product lines?

Last week Edgars sent through the very useful repo of Sat6/Katello scripts which I found excellent. How might I discover which Products are unused? By which I mean that no packages from them are installed on any content hosts. I have a sneaking suspicion that there are some repositories in our

Re: [foreman-users] Content View with status "Deletion from Library"

y would have helped had I said --upgrade. :-/ > > > > On Feb 9, 2017, at 10:20 PM, Lachlan Musicman <data...@gmail.com> wrote: > > oooh. Big new world. Sorry, I mostly use the Katello/Foreman web gui. I'm > just slowly coming to grips with the whole system. That's the com

Re: [foreman-users] Content View with status "Deletion from Library"

done it this way." - Grace Hopper On 10 February 2017 at 15:16, Lachlan Musicman <data...@gmail.com> wrote: > Great - one question, what is ? > > > -- > The most dangerous phrase in the language is, "We've always done it this > way." > > - Gra

Re: [foreman-users] Content View with status "Deletion from Library"

lp. Running foreman-installer flag> upgrade fixes weirdness for me sometimes as well. > > These are just shots in the dark. I haven't seen this particular issue. > > J > > > On Feb 9, 2017, at 10:04 PM, Lachlan Musicman <data...@gmail.com> wrote: > > Foreman 1

[foreman-users] Re: upgrading puppet

Ignore - I found the repo. The product it belonged to was added to the CV, but tt was not added to the CV. cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 10 February 2017 at 13:56, Lachlan Musicman <data...@gma

[foreman-users] upgrading puppet

Foreman 1.13, katello 3.2 We are self hosted. Following the instructions here: https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html When I did this it told me I didn't have the puppet 4 repos in place. I look at the repos, and I can't see puppet 4 anywhere. Here

Re: [foreman-users] CV publishing errors

sers < foreman-users@googlegroups.com> wrote: > That's set automagically during foreman-installer. :) > > J > > > On Feb 9, 2017, at 6:02 PM, Lachlan Musicman <data...@gmail.com> wrote: > > AH! No, I wasn't. Thank you - I don't remember setting that, but now I > k

Re: [foreman-users] CV publishing errors

7 at 09:42, Lachlan Musicman <data...@gmail.com> wrote: > That didn't work either :/ same error. > > > [root@vmpr-res-utils ~]# pulp-admin login -u admin -p admin > The specified user does not have permission to execute the given command > > > cheers > L. > > -

Re: [foreman-users] CV publishing errors

per On 10 February 2017 at 09:39, Tom McKay <thomasmc...@redhat.com> wrote: > Try including the -u admin -p admin on all the pulp-admin commands > > On Thu, Feb 9, 2017 at 5:30 PM, Lachlan Musicman <data...@gmail.com> > wrote: > >> CentOS 7.3.1611, foreman 1.13.4, k

Re: [foreman-users] Re: This thing itches me....

In the GUI, I would like to be able to group Content Views into Composite Views and Non Composite views. All of my servers are deployed using composite CVs. All non composite CVs are single purpose for flexibility within the Composite CVs. It would be handy to be able to visually separate them

Re: [foreman-users] Re: [Katello] Katello 3.1 to 3.2 upgrade error

FWIW, I had errors thrown while upgrading from 3.1 to 3.2 on a self hosted system. Each time I just re-ran the upgrade command and it got a little further. There were three errors thrown and the last time it "just worked". Now happily running 3.2 cheers L. -- The most dangerous phrase in

[foreman-users] Changing Content hosts' Life Cycle Envs/Content Views

Hi, I have decided that one of my Life Cycle Envs and Content Views is extraneous, and I want to move the Content Hosts associated with those LCEs into another. Those hosts were added to the LCEs via Activation Keys. I have followed the docs

Re: [foreman-users] This thing itches me....

Ability to add a new Lifecycle stage to the middle of a Lifecycle Path. eg: Old Library -> Dev -> Prod New Library -> Dev -> UAT -> Prod cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 8 December 2016 at 01:51, 'Jason B. Nance'

[foreman-users] Lifecycle Environments ordering

Hola, Is there any way to reorder Lifecycle Environments after they've been created? EG: I created "Cluster Dev" and then "Cluster Prod" Library - Cluster Dev - Cluster Prod Now I realise I want a "Cluster UAT" that would go after Dev but before Prod Library - Cluster Dev - Cluster UAT -

Re: [foreman-users] Re: Installing and updating Katello, Foreman

problems if katello-server has > epel-release and our custom epel-repo installed at the same time on the > system. So after removing epel-releae, we got our problem solved. > > > Am Dienstag, 6. Dezember 2016 04:29:52 UTC+1 schrieb Lachlan Musicman: >> >> Hi, >>

[foreman-users] Katello repositories

Hola, Investigating the Katello repos, I see there are 4 - pulp, client, candlepin and katello At the moment my understanding of what these are: katello - the foreman plugin, goes on the "foreman/katello server" (satellite server in RHEL speak) candlepin - used on the foreman/katello server,

[foreman-users] Installing and updating Katello, Foreman

Hi, We spent 3 months wrestling with Spacewalk before giving it up and moving to Katello/Foreman early this year. Centos 7.2 is our main OS. Everything is up to date (or at least as up to date as possible). Currently we have Foreman 1.12.4 w Katello 3.1.0, "self-registered". I think I would

[foreman-users] No such file or directory: yum_repo_metadata_file causes sync to fail

Hola, Centos 7, pulp-server 2.8.6, foreman 1.11.4, one of my repos wont syncronise with the error: PLP: [Errno 2] No such file or directory: '/var/lib/pulp/content/units/yum_repo_metadata_file/-appstream.xml.gz' Google search shows a couple of bug reports back when pulp-server was < 2.8.3

[foreman-users] Katello, applying errata: "issue with the backend service pulp: 500 Internal Server Error"

I'm having trouble applying some Errata - after hitting confirm on applying the Errata to the content hosts, I get an error message: There was an issue with the backend service pulp: 500 Internal Server Error Centos 7.2, Katello 3.0 9.el7, Foreman 1.11.4 hammer ping tells me the pulp;

[foreman-users] Should I upgrade regularly on Centos7?

We have an otherwise up to date Centos 7 vm running Katello/Foreman/"satellite 6". From the about page - foreman-installer-katello-3.0.2-1.el7.noarch - katello-3.0.0-9.el7.noarch - katello-agent-2.5.0-3.el7.noarch I notice that katello is up to 3.1 and 3.0.2 and Foreman is up to