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 1271041 - [s390x]Failed to reload virt-who after re-register system
Summary: [s390x]Failed to reload virt-who after re-register system
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: Eko
URL:
Whiteboard:
Depends On: 1291737
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-13 02:41 UTC by Liushihui
Modified: 2016-12-01 00:36 UTC (History)
4 users (show)

Fixed In Version: virt-who-0.17-1.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2016-11-04 05:06:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
rhsm_s390x.log (20.53 KB, text/plain)
2015-10-13 02:42 UTC, Liushihui 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2387 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2016-11-03 13:53:39 UTC

Description Liushihui 2015-10-13 02:41:42 UTC 
Description of problem:
Unregister RHEL system, then re-register it to SAM, it can't reload virt-who service.

Version-Release number of selected component (if applicable):
virt-who-0.14-9.el7.noarch
subscription-manager-1.15.9-14.el7.s390x
python-rhsm-1.15.4-5.el7.s390x

How reproducible:
Always

Steps to Reproduce:
1. Register system to SAM, configure virt-who run at libvirt mode, then restart virt-who service. virt-who send h/g mapping to SAM.
[root@ibm-z10-56 ~]# subscription-manager  identity
system identity: d0d8e087-91b6-47cf-a450-079b691d90c5
name: ibm-z10-56.rhts.eng.bos.redhat.com
org name: ACME_Corporation
org ID: ACME_Corporation
[root@ibm-z10-56 ~]# systemctl restart virt-who
[root@ibm-z10-56 ~]# ps -ef|grep virt-who
root     31051     1  4 22:09 ?        00:00:00 /usr/bin/python /usr/share/virt-who/virtwho.py
root     31056 31051  0 22:09 ?        00:00:00 /usr/bin/python /usr/share/virt-who/virtwho.py
root     31060 10633  0 22:09 pts/0    00:00:00 grep --color=auto virt-who

2. Unregister system, then check virt-who's thread, it is correct to show one virt-who thread.
[root@ibm-z10-56 ~]# subscription-manager  unregister
System has been unregistered.
[root@ibm-z10-56 ~]# ps -ef|grep virt-who
root     31051     1  0 22:09 ?        00:00:00 /usr/bin/python /usr/share/virt-who/virtwho.py
root     31070 10633  0 22:10 pts/0    00:00:00 grep --color=auto virt-who

3. Re-register system to SAM, then check virt-who's thread and virt-who's log
[root@ibm-z10-56 ~]# subscription-manager  register --username=admin --password=admin
Registering to: samserv.redhat.com:443/sam/api
The system has been registered with ID: 9748fd28-2e89-4c83-80ac-46a99a991248 
[root@ibm-z10-56 ~]# ps -ef|grep virt-who
root     31051     1  0 22:09 ?        00:00:00 /usr/bin/python /usr/share/virt-who/virtwho.py
[root@ibm-z10-56 ~]# ps -ef|grep virt-who
root     31051     1  0 22:09 ?        00:00:00 /usr/bin/python /usr/share/virt-who/virtwho.py
[root@ibm-z10-56 ~]# systemctl status virt-who
● virt-who.service - Daemon for reporting virtual guest IDs to subscription-manager
   Loaded: loaded (/usr/lib/systemd/system/virt-who.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2015-10-12 22:09:35 EDT; 9min ago
 Main PID: 31051 (python)
   CGroup: /system.slice/virt-who.service
           └─31051 /usr/bin/python /usr/share/virt-who/virtwho.py

Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: self._sendGuestList(report)
Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: File "/usr/share/virt-who/virtwho.py", line 196, in _sendGuestList
Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: manager.sendVirtGuests(report.guests)
Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: File "/usr/share/virt-who/manager/subscriptionmanager/subscripti...uests
Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: self._connect()
Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: File "/usr/share/virt-who/manager/subscriptionmanager/subscripti...nnect
Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: "Unable to read certificate, system is not registered or you are...oot")
Oct 12 22:09:59 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: SubscriptionManagerUnregisteredError: Unable to read certificate... root
Oct 12 22:10:37 ibm-z10-56.rhts.eng.bos.redhat.com python[31051]: virt-who reload
Oct 12 22:10:37 ibm-z10-56.rhts.eng.bos.redhat.com virt-who[31051]: 2015-10-12 22:10:37,503 WARNING: virt-who reload
Hint: Some lines were ellipsized, use -l to show in full.

Actual results:
1 Although system has registered to SAM, virt-who failed to send h/g mapping to server. please see the log in attachment.
2 Failed to re-load virt-who service , it only show one virt-who thread after re-register system.

Expected results:
After system re-register to SAM, virt-who should send h/g mapping to server successfully. Meanwhile, virt-who should re-load successfully, it should show two virt-who threads.

Additional info:
It hasn't this problem on x86_64 and ppc64
Comment 1 Liushihui 2015-10-13 02:42:48 UTC 
Created attachment 1082209 [details]
rhsm_s390x.log
Comment 2 Radek Novacek 2015-10-13 13:15:45 UTC 
Should be fixed in the upstream repository.
Comment 4 Radek Novacek 2016-05-17 13:03:30 UTC 
Fixed in virt-who-0.17-1.el7.
Comment 6 Liushihui 2016-06-03 02:40:41 UTC 
Verified it on virt-who-0.17-2.el7.noarch since virt-who work normally after re-register to Satellite/SAM.
Comment 9 errata-xmlrpc 2016-11-04 05:06:13 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2387.html
Note You need to log in before you can comment on or make changes to this bug.