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.
Previously, due to a race condition, an exception error would sometimes occur in forceIScsiScan when attempting to put a host containing the host storage manager into maintenance mode and deactivating the attached storage domains. This caused the deactivation to fail and also caused problems when attempting to reactivate the domain. The race issue has been corrected to prevent exception errors when forceIScsiScan is used.
Created attachment 630944[details]
logs
Description of problem:
we get Error in forceIScsiScan when we put hsm host in maintenance and deactivating storage domains.
event logs will show first:
Failed to deactivate Storage Domain Dafna_New2 (Data Center iSCSI). (User: admin@internal)
and then we will deactivate the domains since it is not visible by the host:
Storage Domain Dafna_New2 (Data Center iSCSI) was deactivated by system because it's not visible by any of the hosts.
Version-Release number of selected component (if applicable):
si21.1
How reproducible:
30%
Steps to Reproduce:
1. have at least two hosts with a lot of iscsi domains.
2. start putting domains in maintenance + put the hsm hosts in maintenance.
3.
Actual results:
we get Error in forceIScsiScan
domains was disconnected and will be deactivated since the host cannot connect to it
Expected results:
we should be able to put the hsm in maintenance and deactivate domains with no issues.
Additional info:logs
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.
http://rhn.redhat.com/errata/RHSA-2012-1508.html
Created attachment 630944 [details] logs Description of problem: we get Error in forceIScsiScan when we put hsm host in maintenance and deactivating storage domains. event logs will show first: Failed to deactivate Storage Domain Dafna_New2 (Data Center iSCSI). (User: admin@internal) and then we will deactivate the domains since it is not visible by the host: Storage Domain Dafna_New2 (Data Center iSCSI) was deactivated by system because it's not visible by any of the hosts. Version-Release number of selected component (if applicable): si21.1 How reproducible: 30% Steps to Reproduce: 1. have at least two hosts with a lot of iscsi domains. 2. start putting domains in maintenance + put the hsm hosts in maintenance. 3. Actual results: we get Error in forceIScsiScan domains was disconnected and will be deactivated since the host cannot connect to it Expected results: we should be able to put the hsm in maintenance and deactivate domains with no issues. Additional info:logs