Difference between revisions of "Node1 issues"

From wiki
Jump to: navigation, search
(Created page with "=Red Hat Subscription issues= At some point in March 2016, node1 was not conencting to the repositories properly. the command subscription-manager identity After this, I go...")
 
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=Red Hat Subscription issues=
 
=Red Hat Subscription issues=
 +
 +
== Background==
  
 
At some point in March 2016, node1 was not conencting to the repositories properly. the command
 
At some point in March 2016, node1 was not conencting to the repositories properly. the command
 
  subscription-manager identity
 
  subscription-manager identity
  
 +
Was just showing RHN Classic, nothing more. Face with this, I wasn't able to do any updating on it.
 +
 +
I also ran into the pool ID concept which was mysterious.
 +
 +
 +
== Measures ==
 +
 +
However, it showed the system was registered. And when I ran
 +
 +
subscription-manager unregister
 +
 +
It would say it wasn't registered. However, despite complaints, it would let you register it again with
 +
subscription-manager register
 +
 +
and I then
 +
subscription-manager attach --auto
 +
 
After this, I got:
 
After this, I got:
  
Line 12: Line 31:
 
  org name: 6281253
 
  org name: 6281253
 
  org ID: 6281253
 
  org ID: 6281253
 +
 +
So this is much better, although the other nodes do not give out the server type (pity!), and do not seem to be "RHN Classic".
 +
 +
However, the redhat.repo file was wiped. Nothing in it. The I tried:
 +
 +
subscription-manager list --available
 +
 +
This gave me
 +
 +
+-------------------------------------------+
 +
    Available Subscriptions
 +
+-------------------------------------------+
 +
Subscription Name:  Red Hat Enterprise Linux Academic Server, Self-support (16 sockets) (Up to 1 guest) with Smart Management
 +
Provides:            Red Hat Beta
 +
                      Oracle Java (for RHEL Server)
 +
                      Red Hat Enterprise Linux Server
 +
                      Red Hat Software Collections Beta (for RHEL Server)
 +
SKU:                RH0156864RN
 +
Contract:            10754446
 +
Pool ID:            8a85f9814f02ff15014f0332a5200b04
 +
Provides Management: Yes
 +
Available:          1
 +
Suggested:          1
 +
Service Level:      Self-Support
 +
Service Type:        L1-L3
 +
Subscription Type:  Standard
 +
Ends:                16/08/16
 +
System Type:        Physical
 +
 +
Subscription Name:  Scalable File System
 +
Provides:            Red Hat Enterprise Linux Scalable File System (for RHEL Server)
 +
                      Red Hat Enterprise Linux Scalable File System (for RHEL Workstation)
 +
SKU:                RH00027RN
 +
Contract:            10877730
 +
Pool ID:            8a85f98152b0bc180152b0df6a8e2b2e
 +
Provides Management: No
 +
Available:          2
 +
Suggested:          2
 +
Service Level:      Layered
 +
Service Type:        L1-L3
 +
Subscription Type:  Instance Based
 +
Ends:                20/02/17
 +
System Type:        Physical
 +
 +
Subscription Name:  Red Hat Enterprise Linux Server, Standard (Physical or Virtual Nodes)
 +
Provides:            Red Hat Beta
 +
                      Red Hat Container Images Beta
 +
                      Red Hat Software Collections (for RHEL Server)
 +
                      Red Hat Enterprise Linux Atomic Host Beta
 +
                      Oracle Java (for RHEL Server)
 +
                      Red Hat Container Images
 +
                      Red Hat Enterprise Linux Server
 +
                      Red Hat Enterprise Linux Atomic Host
 +
                      Red Hat Software Collections Beta (for RHEL Server)
 +
                      Red Hat Developer Toolset (for RHEL Server)
 +
SKU:                RH00004F3
 +
Contract:            10308196
 +
Pool ID:            8a85f98441f5a5f20142045877c84bfb
 +
Provides Management: No
 +
Available:          4
 +
Suggested:          2
 +
Service Level:      Standard
 +
Service Type:        L1-L3
 +
Subscription Type:  Instance Based
 +
Ends:                29/10/16
 +
System Type:        Physical
 +
 +
This isn't very informative. Then I tried:
 +
 +
subscription-manager list --consumed
 +
 +
This gives something that is not too bad:
 +
 +
+-------------------------------------------+
 +
    Consumed Subscriptions
 +
+-------------------------------------------+
 +
Subscription Name:  Red Hat Enterprise Linux Server, Standard (Physical or Virtual Nodes)
 +
Provides:            Oracle Java (for RHEL Server)
 +
                      Red Hat Enterprise Linux Atomic Host
 +
                      Red Hat Enterprise Linux Server
 +
                      Red Hat Software Collections (for RHEL Server)
 +
                      Red Hat Beta
 +
                      dotNET on RHEL Beta (for RHEL Server)
 +
                      dotNET on RHEL (for RHEL Server)
 +
                      Red Hat Enterprise Linux Atomic Host Beta
 +
                      Red Hat Developer Toolset (for RHEL Server)
 +
                      Red Hat Software Collections Beta (for RHEL Server)
 +
                      Red Hat Container Images
 +
                      Red Hat Container Images Beta
 +
SKU:                RH00004F3
 +
Contract:            10308196
 +
Account:            1433699
 +
Serial:              3658604266442560863
 +
Pool ID:            8a85f98441f5a5f20142045877c84bfb
 +
Provides Management: No
 +
Active:              True
 +
Quantity Used:      2
 +
Service Level:      Standard
 +
Service Type:        L1-L3
 +
Status Details:      Subscription is current
 +
Subscription Type:  Instance Based
 +
Starts:              29/10/13
 +
Ends:                29/10/16
 +
System Type:        Physical
 +
 +
But it's still alarming how redhat.repo remains empty. And in fact this file still needs a bunch of information, especially the certificates. I did check inside /etc/rhsm/ca and node1 had two certificates, one with the name "candle" and this was the same as the other nodes. Finally I then used the "repos" subcommand like so:
 +
subscription-manager repos --list
 +
 +
On the face of it, this may just list out the content of the files in /etc/yum.repos.d, but in fact there was an effetc: it populated /etc/redhat.repo, quite a surprise. Finally it felt as if node1 was finally coming around to being normal.
 +
 +
==Conclusion==
 +
 +
Without reall knowing how, node1 has recovered, redhat.repo got populated and it has now been updated. The devtools sutie has not been installed yet however. This can be done later.

Latest revision as of 15:35, 20 November 2017

Red Hat Subscription issues

Background

At some point in March 2016, node1 was not conencting to the repositories properly. the command 

subscription-manager identity

Was just showing RHN Classic, nothing more. Face with this, I wasn't able to do any updating on it.

I also ran into the pool ID concept which was mysterious.


Measures

However, it showed the system was registered. And when I ran 

subscription-manager unregister

It would say it wasn't registered. However, despite complaints, it would let you register it again with 

subscription-manager register

and I then 

subscription-manager attach --auto

After this, I got: 

[root@node1 ~]# subscription-manager identity
server type: RHN Classic and Red Hat Subscription Management
system identity: fcd7331c-28fd-4b98-979c-be9f6066aa59
name: node1
org name: 6281253
org ID: 6281253

So this is much better, although the other nodes do not give out the server type (pity!), and do not seem to be "RHN Classic".

However, the redhat.repo file was wiped. Nothing in it. The I tried: 

subscription-manager list --available

This gave me 

+-------------------------------------------+
    Available Subscriptions
+-------------------------------------------+
Subscription Name:   Red Hat Enterprise Linux Academic Server, Self-support (16 sockets) (Up to 1 guest) with Smart Management
Provides:            Red Hat Beta
                     Oracle Java (for RHEL Server)
                     Red Hat Enterprise Linux Server
                     Red Hat Software Collections Beta (for RHEL Server)
SKU:                 RH0156864RN
Contract:            10754446
Pool ID:             8a85f9814f02ff15014f0332a5200b04
Provides Management: Yes
Available:           1
Suggested:           1
Service Level:       Self-Support
Service Type:        L1-L3
Subscription Type:   Standard
Ends:                16/08/16
System Type:         Physical

Subscription Name:   Scalable File System
Provides:            Red Hat Enterprise Linux Scalable File System (for RHEL Server)
                     Red Hat Enterprise Linux Scalable File System (for RHEL Workstation)
SKU:                 RH00027RN
Contract:            10877730
Pool ID:             8a85f98152b0bc180152b0df6a8e2b2e
Provides Management: No
Available:           2
Suggested:           2
Service Level:       Layered
Service Type:        L1-L3
Subscription Type:   Instance Based
Ends:                20/02/17
System Type:         Physical

Subscription Name:   Red Hat Enterprise Linux Server, Standard (Physical or Virtual Nodes)
Provides:            Red Hat Beta
                     Red Hat Container Images Beta
                     Red Hat Software Collections (for RHEL Server)
                     Red Hat Enterprise Linux Atomic Host Beta
                     Oracle Java (for RHEL Server)
                     Red Hat Container Images
                     Red Hat Enterprise Linux Server
                     Red Hat Enterprise Linux Atomic Host
                     Red Hat Software Collections Beta (for RHEL Server)
                     Red Hat Developer Toolset (for RHEL Server)
SKU:                 RH00004F3
Contract:            10308196
Pool ID:             8a85f98441f5a5f20142045877c84bfb
Provides Management: No
Available:           4
Suggested:           2
Service Level:       Standard
Service Type:        L1-L3
Subscription Type:   Instance Based
Ends:                29/10/16
System Type:         Physical

This isn't very informative. Then I tried: 

subscription-manager list --consumed

This gives something that is not too bad: 

+-------------------------------------------+
   Consumed Subscriptions
+-------------------------------------------+
Subscription Name:   Red Hat Enterprise Linux Server, Standard (Physical or Virtual Nodes)
Provides:            Oracle Java (for RHEL Server)
                     Red Hat Enterprise Linux Atomic Host
                     Red Hat Enterprise Linux Server
                     Red Hat Software Collections (for RHEL Server)
                     Red Hat Beta
                     dotNET on RHEL Beta (for RHEL Server)
                     dotNET on RHEL (for RHEL Server)
                     Red Hat Enterprise Linux Atomic Host Beta
                     Red Hat Developer Toolset (for RHEL Server)
                     Red Hat Software Collections Beta (for RHEL Server)
                     Red Hat Container Images
                     Red Hat Container Images Beta
SKU:                 RH00004F3
Contract:            10308196
Account:             1433699
Serial:              3658604266442560863
Pool ID:             8a85f98441f5a5f20142045877c84bfb
Provides Management: No
Active:              True
Quantity Used:       2
Service Level:       Standard
Service Type:        L1-L3
Status Details:      Subscription is current
Subscription Type:   Instance Based
Starts:              29/10/13
Ends:                29/10/16
System Type:         Physical

But it's still alarming how redhat.repo remains empty. And in fact this file still needs a bunch of information, especially the certificates. I did check inside /etc/rhsm/ca and node1 had two certificates, one with the name "candle" and this was the same as the other nodes. Finally I then used the "repos" subcommand like so: 

subscription-manager repos --list

On the face of it, this may just list out the content of the files in /etc/yum.repos.d, but in fact there was an effetc: it populated /etc/redhat.repo, quite a surprise. Finally it felt as if node1 was finally coming around to being normal.

Conclusion

Without reall knowing how, node1 has recovered, redhat.repo got populated and it has now been updated. The devtools sutie has not been installed yet however. This can be done later.

Retrieved from "http://stab.st-andrews.ac.uk/wiki/index.php?title=Node1_issues&oldid=1961"