Bug 622677 - [NetApp 6.0 bug] 'service iscsi status' doesn't display anything
[NetApp 6.0 bug] 'service iscsi status' doesn't display anything
Status: CLOSED DUPLICATE of bug 614035
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iscsi-initiator-utils (Show other bugs)
6.0
All Linux
medium Severity medium
: rc
: 6.0
Assigned To: Andy Grover
Red Hat Kernel QE team
: OtherQA, Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-10 02:49 EDT by Tanvi
Modified: 2012-06-26 12:27 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-10 12:21:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tanvi 2010-08-10 02:49:11 EDT
Description of problem:
If we try to know the status of iscsi service on RHEL6 box using "service iscsi status" or "/etc/init.d/iscsi status", it never returns anything.

Version-Release number of selected component (if applicable):
iscsi-initiator-utils-6.2.0.872-8.el6.x86_64

How reproducible:
Always
Comment 2 RHEL Product and Program Management 2010-08-10 03:18:31 EDT
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 3 Bill Nottingham 2010-08-10 12:21:21 EDT

*** This bug has been marked as a duplicate of bug 614035 ***
Comment 4 Andrius Benokraitis 2010-08-10 13:14:20 EDT
NEtApp: Please add yourselves to bug 614035 - it is proposed for Snapshot 11.
Comment 5 Tanvi 2010-08-25 07:21:59 EDT
Tested it on snap11. The issue is fixed.

Note You need to log in before you can comment on or make changes to this bug.