[Katello 2.2RC3] minor Issues with old katello-agent & subscription-manager

Hi all,

below some issues which I faced with Katello 2.2RC3, maybe it will help
others as well…

Issue1:
It seems for me that systems installed with previous katello-agent "2.1.4"
are no longer supported on Katello 2.2RC3, see below Error:
[WARNING][pulp.agent.48b7dcbc-a6ce-460d-bc64-16b72c1af57d] gofer.messaging.
model:88 - Invalid version 2.0/0.5

Workaround:
I had to update all my servers manually with the new katello-agent "2.2.0"
via yum or via puppet

Issue2:
Server-A with CentOS7 was installed in March with katello-agent 2.1.4 and
via activation key which was holding only centos7/epel7 packages. After
some weeks I added some new products (e.g. 1x HP-PRODUCT for EPEL6, 1x HP-PRODUCT
for EPEL7) to Katello and synced it to the Content View together with the
correct "Override Option" in the Activation Keys. Today (after UPG to 2.2RC3
) Server-A was powered up, it changed after a few minutes automatically the
YUM Repolist, now I was able to see also Products for "HP-EPEL6 & HP-EPEL7"
on my CentOS7 System, which is not so nice…

Workaround:
I re-registered the Server-A with the existing "activation-key" in force
mode, afterwards yum repolist was fine, the "HP-EPEL6" for my CentOS-7
Server disappeared

Any idea why this happens and is there a way to overcome this situation…

best regards,
Christian

> Hi all,
>
> below some issues which I faced with Katello 2.2RC3, maybe it will help
> others as well…
>
> Issue1:
> It seems for me that systems installed with previous katello-agent "2.1.4"
> are no longer supported on Katello 2.2RC3, see below Error:
> [WARNING][pulp.agent.48b7dcbc-a6ce-460d-bc64-16b72c1af57d] gofer.messaging
> .model:88 - Invalid version 2.0/0.5
>
> Workaround:
> I had to update all my servers manually with the new katello-agent "2.2.0"
> via yum or via puppet
>
>
Between 2.1 and 2.2 katello-agent was updated for gofer 2.4 which it sounds
like what you hit with the older version. The gofer error message you saw
– was that on the server or the client?

> Issue2:
> Server-A with CentOS7 was installed in March with katello-agent 2.1.4 and
> via activation key which was holding only centos7/epel7 packages. After
> some weeks I added some new products (e.g. 1x HP-PRODUCT for EPEL6, 1x HP-PRODUCT
> for EPEL7) to Katello and synced it to the Content View together with the
> correct "Override Option" in the Activation Keys. Today (after UPG to
> 2.2RC3) Server-A was powered up, it changed after a few minutes
> automatically the YUM Repolist, now I was able to see also Products for "HP-EPEL6
> & HP-EPEL7" on my CentOS7 System, which is not so nice…
>
> Workaround:
> I re-registered the Server-A with the existing "activation-key" in force
> mode, afterwards yum repolist was fine, the "HP-EPEL6" for my CentOS-7
> Server disappeared
>
> Any idea why this happens and is there a way to overcome this situation…
>

After you added the '1x HP-PRODUCT for EPEL6' to the content view, did you
run yum repolist and see the issue? Or did you only run yum repolist after
both adding the new repository and upgrading to RC3? Can you clarify what
override options you set?

Eric

··· On Wed, Apr 8, 2015 at 2:15 AM, wrote:

best regards,
Christian


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 foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

>
>
>
> Hi all,
>
> below some issues which I faced with Katello 2.2RC3, maybe it will
> help others as well…
>
> >
> Issue1:
> Itseems forme that systems installed withprevious katello-agent
> "2.1.4"are nolonger supported on Katello2.2RC3,see below Error:
> [WARNING][pulp.agent.48b7dcbc-a6ce-460d-bc64-16b72c1af57d]gofer.messaging.model:88-Invalidversion
> 2.0/0.5
>
> Workaround:
> I had to update all myservers manually withthe newkatello-agent
> "2.2.0"via yum orvia puppet
> >
>
>
> Between 2.1 and 2.2 katello-agent was updated for gofer 2.4 which it
> sounds like what you hit with the older version. The gofer error
> message you saw – was that on the server or the client?

Currently we piggyback on the remote execution technology in pulp. We've
found that technology to consistently break across upgrades of pulp and
the client (i.e. new versions of pulp require new versions of the
client). We are currently working on a new foreman feature to better
handle remote executions and handling clients across server upgrades is
a priority. We are in the design phase currently and should have more
to share soon.

-Justin

··· On 04/08/2015 11:00 AM, Eric D Helms wrote: > On Wed, Apr 8, 2015 at 2:15 AM, > wrote:
>
Issue2:
Server-A withCentOS7was installed inMarchwithkatello-agent
2.1.4andvia activation key which was holding only centos7/epel7
packages.Aftersome weeks I added some newproducts
(e.g.1xHP-PRODUCT forEPEL6,1xHP-PRODUCT forEPEL7)to
Katelloandsynced it to the ContentViewtogether withthe correct
"Override Option"inthe ActivationKeys.Today(after UPG to
2.2RC3)Server-A was powered up,it changed after a few minutes
automatically the YUM Repolist,now I was able to see also
Productsfor"HP-EPEL6 & HP-EPEL7"on myCentOS7System,which isnotso
nice...

Workaround:
I re-registered the Server-A withthe existing
"activation-key"inforce mode,afterwards yum repolist was fine,the
"HP-EPEL6"formyCentOS-7Serverdisappeared
>

Any idea why this happens and is there a way to overcome this
situation...

After you added the ‘1x HP-PRODUCT for EPEL6’ to the content view, did
you run yum repolist and see the issue? Or did you only run yum
repolist after both adding the new repository and upgrading to RC3?
Can you clarify what override options you set?

Eric

best regards,
Christian
-- 
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 foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users+unsubscribe@googlegroups.com>.
To post to this group, send email to
foreman-users@googlegroups.com
<mailto:foreman-users@googlegroups.com>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


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 foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Hi Justin & Eric,

below the Infos for the "first" issue, for me its not a big issue, but I
would recommend to add it maybe into some upgrade notes to make sure that
katello-agent needs to be upgraded on client side as well before trying a
package push after an Upgrade from 2.1 to 2.2

Step1: uninstall Package "xxx" via Katello GUI or Hammer CLI (Client

has "katello-agent-2.1.4-1.el7.noarc" installed)
Result: Process on Katello is hanging at 50% forever, Error in messages File
on Client Side (see below)
Client Log: goferd: [WARNING][pulp.agent.db0cd7ee-1463-4d7c-8c8c-
26ac208cee2a] gofer.messaging.model:88 - Invalid version 2.0/0.5
Katello Dynflow: 3: Actions::Pulp::Consumer::ContentUninstall (suspended) [
373.54s / 6.38s ]

Step2: perform "yum update katello-agent"

Result: ok

C### Step3: uninstall Package "xxx" via Katello GUI or Hammer CLI (Client
has "katello-agent-2.2.0-2.el7.noarch" installed)
Result: Error due to previous task, Could not remove packages:
Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.
Required lock: read
Conflicts with tasks:

Step4: try step3 again

Result: Package has been removed successfully

Client Logs:
Apr 8 19:13:29 centos-7-vmware goferd: [INFO][worker-0] gofer.messaging.
adapter.proton.connection:100 - connecting: URL: amqps://katello.cesystems.at:5647|SSL:
ca: /etc/rhsm/ca/katello-server-ca.pem|key: None|certificate:
/etc/pki/consumer/bundle.pem|host-validation: None
Apr 8 19:13:29 centos-7-vmware goferd: [INFO][worker-0] root:473 -
connecting to katello.cesystems.at:5647
Apr 8 19:13:30 centos-7-vmware goferd: [INFO][worker-0] gofer.messaging.
adapter.proton.connection:103 - connected: amqps://katello.cesystems.at:5647
Apr 8 19:13:30 centos-7-vmware goferd: [INFO][worker-0] root:493 -
connected to katello.cesystems.at:5647
Apr 8 19:13:31 centos-7-vmware goferd: [INFO][worker-0] gofer.rmi.
dispatcher:610 - call: Content.uninstall() sn=89482e9b-7b5d-4020-80d4-
7a0a0647d7c8 data={u'task_id': u'4e53d165-b7f4-4776-9f39-ce1e14c6bf53', u
'consumer_id': u'db0cd7ee-1463-4d7c-8c8c-26ac208cee2a'}
Apr 8 19:13:51 centos-7-vmware goferd: [INFO][worker-0] gofer.agent.rmi:161

  • sn=89482e9b-7b5d-4020-80d4-7a0a0647d7c8 processed in: 22.088 (seconds)

Thanks,
Christian

Hi Justin & Eric,

I´m trying it to explain the "second" issue, but its not easy, I will do my
best…(see also the Logs Attachment)

Anyway its also not a big issue for me, because re-registering all clients
will solve the issue.
This time its on my labsystem, but same issue with "Puppet EL6" Repo on an
CentOS-7 Client…

MY SETUP:
Activation-Keys => Product Content

  • for Key "centos-6-test" (EL6=Yes / EL7=Override to No)
  • for Key "centos-7-test" (EL6=Override to No / EL7=Yes)

MY ACTIONS:
15.03: Client Install via Katello 2.1
15.03: Upgrade from 2.1 to 2.2RC1
29.03: Product and Content added for Puppet YUM (EL6 & EL7)
03.04: Upgrade from 2.2RC1 to RC2
04.04: Product and Content Update for all YUM (EL6 & EL7)
07.04: Upgrade from 2.2RC2 to RC3
08.04: Powerup previous registered Client (was registered with activation-
key) "centos-7-vmware" from Release 2.1

Immediate Login after Boot of Client:

!CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7_-_Base_RPMs_x86_64

!CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7_-_Extras_RPMs_x86_64

!CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7_-_Updates_RPMs_x86_64

!CESYSTEMS_Extra_Packages_for_Enterprise_Linux_EPEL_7_-_Base_RPMs_x86_64

!CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7_-_Katello_Agent_RPMs_x86_64

!CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7_-_Subscription_Manager_RPMs_x86_64

!epel/x86_64

repolist: 17,768

After 1 Minute on Client the "EPEL6-Puppet" from 29.03 is now on enabled"

why I have no idea !!!
CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7_-Base_RPMs_x86_64
CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7
-Extras_RPMs_x86_64
CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7
-Updates_RPMs_x86_64
CESYSTEMS_Extra_Packages_for_Enterprise_Linux_EPEL_7
-Base_RPMs_x86_64
CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_6
-
Puppet_Dependencies_RPMs_x86_64
CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_6
-
Puppet_Products_RPMs_x86_64
CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7
-
Katello_Agent_RPMs_x86_64
CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7
-
Puppet_Dependencies_RPMs_x86_64
CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7
-
Puppet_Products_RPMs_x86_64
CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7
-
_Subscription_Manager_RPMs_x86_64
epel/x86_64
repolist: 21,626

Workaround: run the command "subscription-manager register

–org="CESYSTEMS" --activationkey="centos-7-test" --force", afterwards yum
repolist is back ok without "EPEL_6"
CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7_-_Base_RPMs_x86_64

CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7_-_Extras_RPMs_x86_64

CESYSTEMS_CentOS_Enterprise_Linux_Server_CentOS_7_-_Updates_RPMs_x86_64

CESYSTEMS_Extra_Packages_for_Enterprise_Linux_EPEL_7_-_Base_RPMs_x86_64

CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7_-_Katello_Agent_RPMs_x86_64

CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7_-_Puppet_Dependencies_RPMs_x86_64

CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7_-_Puppet_Products_RPMs_x86_64

CESYSTEMS_Other_Packages_for_Enterprise_Linux_EPEL_7_-_Subscription_Manager_RPMs_x86_64

epel/x86_64

repolist: 21,052

Thanks,
Christian

Hi Eric & Justin,

I think the "second" issue is a concept problem, whenever you add a repo
and and changing the "Repository Enablement" under a Activation Key you
need re-register the clients in order to get the correct Repolist,
otherwise yum will see all new added Repos. I dont know if this is worked
as designed or if it can be fixed…

Procedure:

  1. add a repo to a product
  2. add the repo to a content view
  3. publish the content
  4. modify "Product Content" under the activation-key (see screenshot
    activation-ley)
    • Override is set to "No"

Result:
5. check the "Product Content" under Content Host (see screenshot Content
Host)
- new Product is added, but with "Yes" instead of "Override to No"

br,
Christian

Activation keys are only applied at registration time, modifying them later will not update or modify previously registered content hosts. After adding a new product to a content view, the existing hosts in that view will need to have their override settings modified individually.

I believe there are redmine issues in this area to update content hosts via CLI and bulk in the UI, though my searching is not finding them right now. An RFE to allow the default setting to be set at the subscription level (so all existing registered content hosts would get that override value) would be worthwhile.

··· ----- Original Message ----- > Hi Eric & Justin, > > I think the "second" issue is a concept problem, whenever you add a repo > and and changing the "Repository Enablement" under a Activation Key you > need re-register the clients in order to get the correct Repolist, > otherwise yum will see all new added Repos. I dont know if this is worked > as designed or if it can be fixed... > > Procedure: > 1. add a repo to a product > 2. add the repo to a content view > 3. publish the content > 4. modify "Product Content" under the activation-key (see screenshot > activation-ley) > - Override is set to "No" > > Result: > 5. check the "Product Content" under Content Host (see screenshot Content > Host) > - new Product is added, but with "Yes" instead of "Override to No" > > br, > Christian >