RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1032673 - [RFE]“Repo-override” should inform user when adding an override for a non-existing Repo
Summary: [RFE]“Repo-override” should inform user when adding an override for a non-exi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michael Stead
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2013-11-20 14:57 UTC by spandey
Modified: 2015-04-23 23:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:58:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description spandey 2013-11-20 14:57:17 UTC 
Description of problem:


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


How reproducible:
5/5

Prerequisites:
Rhel7 with following subscription-manager rpm 
subscription-manager-gui-1.10.7-1.git.0.15d737b.el7.x86_64
subscription-manager-firstboot-1.10.7-1.git.0.15d737b.el7.x86_64
subscription-manager-migration-1.10.7-1.git.0.15d737b.el7.x86_64
subscription-manager-migration-data-2.0.5-1.git.0.3be2ad4.el7.noarch
subscription-manager-1.10.7-1.git.0.15d737b.el7.x86_64


Steps to Repro :
Register client to candlepin and subscribe instance based subscription 
Override non existing repo using following command 
[root@localhost ~]# subscription-manager repo-override --repo=tesssssssssss –add=test1:123

Expected Result : 
Message should display like 
invalid repoid , --repo=tesssssssssss
invalid Parameters  –add=test1:123

Actual result : 
command successfully executed , No message displayed on console 
[root@localhost yum.repos.d]# subscription-manager repo-override --repo=tesssssssssss --add=test1:123
[root@localhost yum.repos.d]# echo $?
0
[root@localhost yum.repos.d]#
Comment 2 John Sefler 2013-11-20 17:28:50 UTC 
In my opinion, adding a repo override to a currently non-existant repo is acceptable and will persist the life of the consumer applying to subscriptions as they are attached and removed.  I believe this is the behavior we want.

However, it can also be misleading to a user that has inadvertantly mistyped a repo name.  I would suggest adding an informative feedback similar to the following mock-up...

# subscription-manager repo-override --repo=foo --repo=bar --add=test1:123
Repository 'foo' does not currently exist, but the override has been added.  
Repository 'bar' does not currently exist, but the override has been added. 
# echo $?
0
Comment 3 Michael Stead 2013-11-21 16:30:21 UTC 
I like this idea. I'll work on a fix for this.
Comment 4 Michael Stead 2013-11-28 13:22:44 UTC 
https://github.com/candlepin/subscription-manager/pull/828
Comment 6 John Sefler 2013-12-06 17:59:44 UTC 
Verifying Version...
[root@jsefler-7 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: Unknown
subscription-manager: 1.10.8-1.el7
python-rhsm: 1.10.8-1.el7

[root@jsefler-7 ~]# subscription-manager register --serverurl=jsefler-f14-candlepin.usersys.redhat.com:8443/candlepin
Username: testuser1
Password: 
Organization: admin
The system has been registered with ID: 56a31342-9ab1-4185-8917-a641cf7b31c0 
[root@jsefler-7 ~]# subscription-manager repo-override --repo=tesssssssssss --add=test1:123
Repository 'tesssssssssss' does not currently exist, but the override has been added.
[root@jsefler-7 ~]# subscription-manager repo-override --list
Repository: tesssssssssss
  test1: 123

[root@jsefler-7 ~]# 


VERIFIED: When adding a repo-override to a currently non existent repo, the user is informed that the repo does not exist, yet the addition succeeds for future repos.
Comment 7 Ludek Smid 2014-06-13 12:58:48 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.