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 1308828 - RHEL 6.7 VM created from On-Demmand Image is showing "not registered" when running "yum update"
Summary: RHEL 6.7 VM created from On-Demmand Image is showing "not registered" when ru...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.7
Hardware: other
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-16 08:59 UTC by mingzhan
Modified: 2016-02-18 22:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1308820
Environment:
Last Closed: 2016-02-18 22:01:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description mingzhan 2016-02-16 08:59:56 UTC
+++ This bug was initially created as a clone of Bug #1308820 +++

Description of problem:

RHEL 6.7 VM created from On-Demmand Image is showing "not registered" when running "yum update"

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

How reproducible:
100%

Steps to Reproduce:
1.Login Azure portal through portal.azure.com
2.Create a RHEL 6.7 VM
3.Login the VM through SSH
4.Run "sudo yum update"

Actual results:
[azureuser@scotttestrhel67 ~]$ sudo yum update

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for azureuser:
Loaded plugins: langpacks, product-id, rhui-lb, search-disabled-repos,
              : subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
No packages marked for update

Actually, below will be always showing up when running yum related command:

This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

Expected results:
-the output should be indicating this is an registered RHEL.

Additional info:
The "not registered" message could be ignored given the "yum update" actually worked well, but the message provided the bad user experience.

Comment 2 Barnaby Court 2016-02-18 22:01:54 UTC
Subscription manager appears to be working exactly the it was designed. If no subscription is attached to the system then no updates will be provided. 

Please open a support case with Red Hat from the Azure Portal for support of on-demand images.


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