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:
# service fcoe restart
Stopping FCoE initiator service:                           [  OK  ]
Starting FCoE initiator service:                           [  OK  ]

# service fcoe status
/usr/sbin/fcoemon is running, pid=29187
No interfaces created.

# echo $?
2

Version-Release number of selected component (if applicable):
fcoe-utils-1.0.22-1.el6

How reproducible:
100%

Steps to Reproduce:
see description
  
Actual results:
status return 2
2:	program is dead and /var/lock lock file exists

Expected results:
status return 0

Additional info:
This is a regression as this bug cannot be reproduced with fcoe-utils-1.0.20-5.el6

Good catch.  This was changed intentionally upstream (d789267) but apparently isn't in line with our guidelines.

Any update?

Reproduced in fcoe-utils-1.0.22-1.el6.x86_64 and verified in fcoe-utils-1.0.22-2.el6.x86_64.

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/RHBA-2012-0851.html