Project

General

Profile

Bug #24247

Repositories not updated after changing content view and lifecycle environment

Added by Martin Angermeier almost 4 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hello everybody,

we use Foreman 1.17.1 and Katello 3.6.0.

Recently we changed LE & CV of our servers but the repositories were not updated althoug we published / promoted after this change.
Following RedHat Solution https://access.redhat.com/solutions/1752493 we tried to update via hammer-cli with

# hammer host update --name client.example.com --lifecycle-environment "ENV_NAME" --content-view "CV_NAME" --organization-id <ORG_ID>

When we use the activation key "RTC-Artifactory_RHEL7" for a server, it gets the correct repositories. The non-working server got the activation key "Default-Test-RHEL7".

Is there any connection between activation key and content view that overrides host-specific settings ?

Regards,
Martin Angermeier

History

#1 Updated by Jonathon Turel almost 4 years ago

Have you tried performing a `subscription-manager refresh` on the machine? Before doing that you might check if the repo is already enabled due to the check-in process of the machine.

#2 Updated by Jonathon Turel almost 4 years ago

  • Status changed from New to Need more information

#3 Updated by Martin Angermeier almost 4 years ago

I've tried the refresh several times including cleaning the yum cache and even the yum.repos.d folder.

Where do I find the information whether the repo is already enabled?

Regards,
Martin Angermeier

#4 Updated by Andrew Kofink almost 4 years ago

You can find which repositories are enabled with `yum repolist --enabled`.

#5 Updated by Martin Angermeier almost 4 years ago

I already looked for the repos in yum, they got the wrong url. That's what I wanted to express initially.

For example...the correct url should look like .../pulp/.../RTC-Artifactory/... something like that.
But in the yum repolist I got something like .../pulp/.../Default_RHEL7/...

I tried the following :

1. yum clean all
2. rm -rf /var/cache/yum
3. subscription-manager refresh

No change.

Then I tried to delete *.repo and the steps above.

Everytime the machine got the repositories connected to the activation key "Default-Test-RHEL7".

#6 Updated by John Mitsch almost 4 years ago

  • Assignee set to Jonathon Turel

#7 Updated by Justin Sherrill almost 4 years ago

This may be a duplicate of https://projects.theforeman.org/issues/23837

Would you be able to upgrade to 3.7.0 and see if its resolved? Alternatively you could try applying this patch: https://patch-diff.githubusercontent.com/raw/Katello/katello/pull/7427.patch

#8 Updated by Martin Angermeier almost 4 years ago

Patch did not work unfortunately, update to version 3.7.0 is taking some time at the moment.

If it helps...
subscription-manager identity
show the wrong environment even after the hammer update script.

#9 Updated by Andrew Kofink almost 4 years ago

  • Status changed from Need more information to Needs design

#10 Updated by Jonathon Turel over 3 years ago

Martin Angermeier wrote:

Patch did not work unfortunately, update to version 3.7.0 is taking some time at the moment.

If it helps...
subscription-manager identity
show the wrong environment even after the hammer update script.

Sorry it didn't work. Can you please run the hammer command to update the environment once more and then provide the output of `hammer host info --name client.example.com` ?

Following that, run 'foreman-debug' on the Katello instance and attach the tarball to the issue and I can look into it.

#11 Updated by John Mitsch over 3 years ago

  • Status changed from Needs design to Need more information

#12 Updated by Justin Sherrill over 3 years ago

  • Target version set to Katello Recycle Bin

Moving to recycle bin, this will be closed after 7 more days of inactivity. Thanks!

#13 Updated by Martin Angermeier over 3 years ago

The tarball is over 70 MB but we got another punch of problems at the moment so we cannot provide it currently. Output of hammer info shows nothing suspicious:

Id: 2128
Name: XXX
Organization: XXX
Location: XXX
Cert name: XXX
Managed: no
Installed at:
Last report: 2018/09/01 03:24:43
Network:
IPv4 address: XXX
MAC: XXX
Domain: XXX
Network interfaces:
1) Id: 2777
Identifier: ens192
Type: interface (primary, provision)
MAC address: XXX
IPv4 address: XXX
FQDN: XXX
2) Id: 2778
Identifier: ens256
Type: interface
MAC address: XXX
IPv4 address: XXX
FQDN:
Operating system:
Architecture: x86_64
Operating System: RedHat 7.3
Build: no
Custom partition table:
Parameters:

All parameters:
XXXXXX
Additional info:
Owner: XXXX
Owner Type: User
Enabled: yes
Model: VMware Virtual Platform
Comment:
Content Information:
Content View:
ID: 30
Name: CORRECTCV
Lifecycle Environment:
ID: 32
Name: CORRECTLV
Content Source:
ID:
Name:
Kickstart Repository:
ID:
Name:
Applicable Packages: 0
Upgradable Packages: 0
Applicable Errata:
Enhancement: 0
Bug Fix: 0
Security: 0
Subscription Information:
UUID:
Last Checkin:
Service Level:
Release Version:
Autoheal:
Registered To:
Registered At:
Host Collections:

#14 Updated by Jonathon Turel over 3 years ago

Martin: Perhaps you can send me a dropbox link or something similar to my email address?

#15 Updated by Justin Sherrill over 3 years ago

  • Status changed from Need more information to Rejected

Closing due to inactivity. Feel free to reopen if you want to continue investigation. Thanks!

Also available in: Atom PDF