Project

General

Custom queries

Profile

Actions

Bug #24247

closed

Repositories not updated after changing content view and lifecycle environment

Added by Martin Angermeier almost 7 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

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

#2

Updated by Jonathon Turel almost 7 years ago

  • Status changed from New to Need more information
#6

Updated by John Mitsch almost 7 years ago

  • Assignee set to Jonathon Turel
#9

Updated by Andrew Kofink over 6 years ago

  • Status changed from Need more information to Needs design
#11

Updated by John Mitsch over 6 years ago

  • Status changed from Needs design to Need more information
#12

Updated by Justin Sherrill over 6 years ago

  • Target version set to Katello Recycle Bin
#15

Updated by Justin Sherrill over 6 years ago

  • Status changed from Need more information to Rejected
Actions

Also available in: Atom PDF