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:
When I add IPv4 server with ipvsadm for a IPv4 service I do not have to specify the port. When I switch to IPv6 the port is mandatory. This could be confusing when someone wants to migrate from IPv4 to IPv6.
IPv4:
# ipvsadm -A -t 1.2.3.4:80 -s rr
# ipvsadm -a -t 1.2.3.4:80 -r 5.6.7.8 -g
# ipvsadm
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 1.2.3.4:http rr
-> 5.6.7.8:http Route 1 0 0
IPv6:
# ipvsadm -A -t [fe01::5]:80 -s rr
# ipvsadm -a -t [fe01::5]:80 -r [fe01::20] -g
illegal real server address[:port] specified
# ipvsadm
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP [fe01::5]:http rr
# ipvsadm -a -t [fe01::5]:80 -r [fe01::20]:80 -g
# ipvsadm
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP [fe01::5]:http rr
-> [fe01::20]:http Route 1 0 0
Version-Release number of selected component (if applicable):
ipvsadm-1.27-7.el7.x86_64
How reproducible:
100%
Steps to Reproduce: see description
Actual results: port is mandatory when adding real server
Expected results: port should not be mandatory
(In reply to Ryan O'Hara from comment #1)
> To be clear, it is the port on the real server that is required for IPv6?
Yes.
In the command:
ipvsadm -a -t [fe01::5]:80 -r [fe01::20] -g
it is the part '-r [fe01::20]'
Currently you have to specify the port otherwise you get an error.
I see the problem. When parsing an IPv6 address, the parse_service function never returns SERVICE_ADDR. I'll make some minor code changes and do some testing before sending this upstream. Would like to get any patch reviewed upstream before applying to RHEL packages.
Comment 5RHEL Program Management
2020-12-15 07:40:59 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.