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.

For both ipv4 and ipv6, it is possible to specify the netmask in ip.sh

1.2.3.4/24 or 1.2.3.4/255.255.255.0

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.

IP address: [             ]   Netmask bits: [  ]

?

This should be fixed in http://git.fedorahosted.org/git/?p=luci.git;a=commit;h=be5bc438392f460820183cc937679e54f160fa12

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.

Also, attaching the global IP resource to a service does not work.

Fixed the remaining issues. Complete fix in luci-0.22.2-13.el6

verfied

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 /255.255.255.0

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.