Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 744285

Summary:	The names of repos is a bit odd to understand
Product:	Red Hat Satellite	Reporter:	Bryan Kearney <bkearney>
Component:	API	Assignee:	Ivan Necas <inecas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Garik Khachikyan <gkhachik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	gkhachik, inecas, mkoci
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-22 18:00:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	747354

Description Bryan Kearney 2011-10-07 18:36:26 UTC

If I go through the basic patch management and subscribe to a product I get a repo which is named:

1318012094512-base-Dev-TestOrg

I think this is

[random string]-[repo]-[env]-[org]

can we make it

[org]-[env]-[prod]-[repo]

Comment 1 Ivan Necas 2011-10-12 14:18:34 UTC

Fixed in commit ddac3cd92a275c3bb833c3c1d4a451239703bbf5

Comment 2 Mike McCune 2012-01-26 19:08:17 UTC

mass ON_QA move

Comment 4 Garik Khachikyan 2012-02-15 11:01:11 UTC

# REOPEN

I can confirm: there is changed that random number: but still the yum repo contains no info about the subscribed env.

format looks like:
[org]_[product]_[repo]

please confirm it this is ok - otherwise I would expect to have [env] also - as defined in comment#0

checked against:
---
katello-0.1.237-1.git.7.752d8de.el6.noarch
katello-cli-0.1.54-1.git.79.17c365f.el6.noarch
candlepin-0.5.17-1.el6.noarch
pulp-0.0.265-1.el6.noarch

Comment 6 Ivan Necas 2012-02-16 14:09:05 UTC

[env] can not be there, because this data is generated when creating a repository and can not be touched later when promoting. The presence of [env] has no impact on any other feature (in a sense that it would prevent collisions in uniq names). For RH content there can not be env either, because repo names are imported with the manifest.

Comment 7 Garik Khachikyan 2012-02-22 14:58:33 UTC

# VERIFIED

then:) verified.

checked against:
---
katello-0.1.243-1.git.0.a066880.el6.noarch
katello-cli-0.1.57-1.git.0.4e2dd9a.el6.noarch
pulp-0.0.266-1.el6.noarch
candlepin-0.5.20-1.el6.noarch
---

Comment 9 Mike McCune 2013-08-16 18:12:05 UTC

getting rid of 6.0.0 version since that doesn't exist