Bug 618578 - ip resource should have netmask field
ip resource should have netmask field
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Jan Pokorný
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2010-07-27 06:07 EDT by Fabio Massimo Di Nitto
Modified: 2016-04-26 09:46 EDT (History)
4 users (show)

See Also:
Fixed In Version: luci-0.22.2-13.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 17:12:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fabio Massimo Di Nitto 2010-07-27 06:07:06 EDT
For both ipv4 and ipv6, it is possible to specify the netmask in ip.sh or

3ffe::1/64 for ipv6

In the UI it´s possible to cheat adding the netmask after the IP address, but it would be nice to either a separate field or at least explain in the field name that´s optionally possible to add the netmask.
Comment 1 Lon Hohberger 2010-07-28 10:06:10 EDT
IP address: [             ]   Netmask bits: [  ]

Comment 3 Lon Hohberger 2010-08-03 18:07:20 EDT
Adding a new IP address to an existing service (whether or not netmask was specified) caused an error 'No IP address specified'.

Adding or editing a global IP address resource works fine.
Comment 4 Lon Hohberger 2010-08-03 18:13:25 EDT
Also, attaching the global IP resource to a service does not work.
Comment 5 Ryan McCabe 2010-08-03 18:50:41 EDT
Fixed the remaining issues. Complete fix in luci-0.22.2-13.el6
Comment 7 Brian Brock 2010-08-26 16:09:18 EDT

IP address creation dialog has a working "netmask" field that is appended properly to the ip address in cluster.conf.  Additionally, the ip address can include the netmask.  Both styles of netmask are supported (i.e. /24 and /
Comment 8 releng-rhel@redhat.com 2010-11-10 17:12:25 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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