1255721 – RHEL 5 OS objects are named differently as RHEL6 and 7

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1255721 - RHEL 5 OS objects are named differently as RHEL6 and 7

Summary: RHEL 5 OS objects are named differently as RHEL6 and 7

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Provisioning
Sub Component:
Version:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	Unspecified
Assignee:	satellite6-bugs
QA Contact:	Katello QA List
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2015-08-21 11:52 UTC by Fred van Zwieten
Modified:	2017-01-12 15:13 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2017-01-12 15:13:01 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
Scrrenshot of issue (55.79 KB, image/png) 2015-08-21 11:52 UTC, Fred van Zwieten	no flags	Details
View All

Description Fred van Zwieten 2015-08-21 11:52:00 UTC

Created attachment 1065559 [details]
Scrrenshot of issue

Description of problem:
OS objects created from the syncing of a kickstart repo have a different format as OS objects created as a result from a client doing a yum update to a different minor version.

Version-Release number of selected component (if applicable):


How reproducible:
See description

Steps to Reproduce:
1.
2.
3.

Actual results:
See screenshot

Expected results:
consistent naming

Additional info:

Comment 1 Fred van Zwieten 2015-08-21 11:54:18 UTC

Actually, this is a different format for RHEL5 then for RHEL6 and 7.

Comment 2 Brad Buckingham 2015-11-19 14:57:00 UTC

Hi Fred,

I ran a test with Satellite 6.1.4 and I am not seeing the behavior described; therefore, wondering if perhaps it was either resolved during z-stream or if my test scenario may be different.

Scenario (all from UI):

- Content-> Red Hat Subscriptions : import a manifest
- Content -> Red Hat Repositories : enable Kickstart repos for Red Hat Enterprise Linux Server 5.9, 6.7 & 7.1
- Content -> Sync Status : select all 3 repos and initiate a sync
- Once the sync is finished : view the created Operating Systems at 'Hosts -> Operating systems'
- observe that the following were created:
  - RedHat 5.9
  - RedHat 6.7
  - RedHat 7.1

Is this similar to what you performed?
If not, can you highlight what may be different?

Also, would it be possible for you to try a test on the lastest (Satellite 6.1.4)?

Thanks!

Comment 3 Fred van Zwieten 2015-11-19 15:57:51 UTC

I am no longer on this site and I also was not there when they did this, so I am not entirely sure how they managed to do this. I just observed this when I visited. They were using a disconnected sat6 then (has been reinstalled as a connected since). So, it might be the issue is with the content iso's

Comment 4 Bryan Kearney 2016-07-26 19:11:26 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 5 Bryan Kearney 2017-01-12 15:13:01 UTC

This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.

Note You need to log in before you can comment on or make changes to this bug.