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.
Bug 856681 - Inappropriate use of "must" where "can" is OK
Summary: Inappropriate use of "must" where "can" is OK
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Cluster_Administration
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-12 14:54 UTC by Jan Pokorný [poki]
Modified: 2013-02-25 17:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-25 17:03:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Pokorný [poki] 2012-09-12 14:54:30 UTC
5.10. Adding a Cluster Service to the Cluster

To verify the existence of the IP service resource used in a cluster
service, you >>must<< use the /sbin/ip addr list command on a cluster
node.

This is not true as this information should be available, e.g., via
(admittedly obsolete) ifconfig command.  Hence, "can" is more
approriate here.

Comment 1 Jan Pokorný [poki] 2012-09-12 18:19:08 UTC
OK, ifconfig is not an option, but "hostname -I" is.

Comment 2 Jan Pokorný [poki] 2012-09-13 09:21:40 UTC
Re comment 1:

Maybe adding a parenthesised
--
obsoleted <code>ifconfig</code> is not capable of listing such IP
--
to the end of the referenced sentence would be suitable to prevent
confusion for people still using this instead of current "ip" tool.

References:
- http://arstechnica.com/civis/viewtopic.php?p=22890577#p22890577
- man ifconfig ("This program is obsolete!")
- own experience (with RHEL 6.3, IP configured within the cluster's
  service group will not show up, unlike with "ip addr")

Comment 3 Jan Pokorný [poki] 2012-09-13 09:29:47 UTC
Another point, please consider using canonical "ip addr show" instead
of "ip addr list".  Admittedly, both is treated equally by the tool.

References:
- man ip
- ip help, ip addr help

Comment 4 Jan Pokorný [poki] 2012-09-13 09:32:41 UTC
Please note there is another instance of using ip addr list,
3.10. Adding a Cluster Service to the Cluster.

Comment 5 Steven J. Levine 2012-09-26 20:41:23 UTC
In my current 6.4 draft, I have updated all 4 occurences of "ip addr list" to "ip addr show". I have also changed the word "must" to "can" in both places.

As to calling out the obsoleted ifconfig, I'm not sure about that yet. The manuals document the current state of the software, rather than what we used to support and what we may support in the future, so I'm cautious about calling out a no-longer-supported command. I'm guessing that whoever originally wrote this section used the word "must" to indicate that you use "ip addr" rather than "ifconfig", but even with changing that to "can" you still are using this section to indicate that this is the command you use to verify the existence of an IP service, which should address the issue.

So I'm considering what to do here.

Comment 6 Steven J. Levine 2012-09-26 20:42:32 UTC
Hmmm...

Maybe:

To verify the existence of the IP service resource used in a
cluster service, you can use the <command>/sbin/ip addr
show</command> command on a cluster node (rather than the obsoleted
<command>ifconfig</command>.

Would that address this?

Comment 7 Jan Pokorný [poki] 2012-09-27 18:45:42 UTC
Technical point is that ifconfig is capable to show only primary
IP address while ip addr shows all configured IP aliases.

My intention was to keep the idea not to use ifconfig (which was
why "must" was used, I guess), while making clear it is not the
only way to get other than primary IP address (e.g., mentioned
hostname command).

Being careful about marking something as obsolete is absolutely
correct approach, but looking into my RHCE book for RHEL 6
(dated 2011-07-29), at the end of section about IP aliases,
I read:

> Important
> Avoid using the obsolete ifconfig command. [...]

This probably makes it clear and proposal in [comment 6] is
completely right, then.

Comment 8 Steven J. Levine 2012-10-11 07:13:53 UTC
I have made the changes noted in comment 6 both places the sentence occurs in the document. I have checked this in to the svn repository and will move this to ON_QA at the next build.


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