Bug 1400788

Summary: It will show "Interrupted system call" when unregister system
Product: Red Hat Enterprise Linux 7 Reporter: Liushihui <shihliu>
Component: virt-whoAssignee: candlepin-bugs
Status: CLOSED CURRENTRELEASE QA Contact: Eko <hsun>
Severity: low Docs Contact:
Priority: medium    
Version: 7.5CC: hsun, jhnidek, jsefler, redakkan, sgao, wpoteat, yuefliu
Target Milestone: pre-dev-freezeKeywords: Reopened, Triaged
Target Release: 7.7   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-11 11:18:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
rhsm.log none

Description Liushihui 2016-12-02 05:39:46 UTC
Description of problem:
When virt-who run at xen mode, unregister system will show "ConnectionError: ('Connection aborted.', error(4, 'Interrupted system call'))" in rhsm log.

Version-Release number of selected component (if applicable):
virt-who-0.18-1.el6.noarch
subscription-manager-1.18.5-1.el6.x86_64
python-rhsm-1.18.5-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Register system to stage candlepin
[root@dell-t320-01 ~]# subscription-manager  register --username=stage_ci_test --password=redhat
Registering to: subscription.rhsm.stage.redhat.com:443/subscription
The system has been registered with ID: a864bf25-ce37-4d6b-a42b-eb9db72a0840 

2. Configure virt-who at xen mode and restart virt-who service, virt-who start successfully.
[root@dell-t320-01 ~]# cat /etc/sysconfig/virt-who  | grep -v ^# | grep -v ^$
VIRTWHO_DEBUG=1
VIRTWHO_XEN=1
VIRTWHO_XEN_OWNER=7970632
VIRTWHO_XEN_ENV=7970632
VIRTWHO_XEN_SERVER=10.73.131.133
VIRTWHO_XEN_USERNAME=root
[root@dell-t320-01 ~]# service virt-who restart

3. Unregister system and check virt-who's log.
[root@dell-t320-01 ~]# subscription-manager unregister
System has been unregistered.

Actual results:
When unregister system, virt-who communicate with xen server firstly(it will show "interrupt system call" in the log). then it will communicate with subscription-manager to check out"system is not registered or you are not root".please see detail log in attachment.

Expected results:
When unregister system, Virt-who should communicate with subscription-manager to check system has been unregistered firstly, if system has been unregistered, virt-who needn't communicate with xen server.

Additional info:

Comment 3 Liushihui 2016-12-06 02:16:22 UTC
Created attachment 1228247 [details]
rhsm.log

Comment 6 Jan Kurik 2017-12-06 12:11:32 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/

Comment 7 William Poteat 2018-04-06 18:46:09 UTC
This is a correct response because the system has not been configured with credentials when the cert is absent. The above condition can be corrected by reregistering.

The best solution here is to enhance the message so the user knows how to correct.

Moving to RHEL 7.6 as this will not qualify as a blocker in RHEL 6.

Comment 9 William Poteat 2019-05-15 20:47:14 UTC
Please re-evaluate based on the change of configuration files. The config listed here is no longer valid.

Comment 11 Rehana 2020-12-11 11:18:03 UTC
Old bug clean up :
================

Closing the bug with Current release ,the bug was verified by QE during a RHEL release cycle but was not closed.