Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
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/
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.
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: