Bug 2265480
Summary: | Missing ActivationKey related changes when display_fqdn_for_hosts is disabled | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Matěj Mudra <mmudra> |
Component: | Activation Keys | Assignee: | Matěj Mudra <mmudra> |
Status: | CLOSED MIGRATED | QA Contact: | amolpati |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.15.0 | CC: | ahumbe, chrobert, gtalreja, iballou, rlavi |
Target Milestone: | stream | Keywords: | MigratedToJIRA, Regression, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://projects.theforeman.org/issues/37201 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-06 17:04:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matěj Mudra
2024-02-22 09:30:03 UTC
Verified. Tested on: Satellite stream Snap 50 Steps followed: 1) Enabled repositories -> sync repositories -> provision the host 2) Disable the setting in General -> display_fqdn_for_hosts in Satellite 3) Navigate to Content > Lifecycle > Activation Keys > Create/Select any AK 4) Move to Associations tab -> Content Hosts Additional info: after disabled "display_fqdn_for_hosts", as per the above steps it is displaying short-name w/o domain name Exp. - "phil-tyrrell" after enabled "display_fqdn_for_hosts", as per the above steps it is displaying full-name with domain name Exp. - "phil-tyrrell.vrdsgirtnb.foo" Observation: It is working as expected. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |