* IPI (automated install with `openshift-install`. If you don't know, then it's IPI)
We have this bug before https://bugzilla.redhat.com/show_bug.cgi?id=1925291 that prevent us to deploy OCP with provision network addresses range smaller then /64 (e.g /118) This bug has been solved so we check the opposite case that we define provision network addresses range larger then /64 (e.g /48). this test has been failed in the automation.
What did you expect to happen?
We want to know if there is a reason to support range larger then /64 and if not we need to document this
How to reproduce it (as minimally and precisely as possible)?
Deploy OCP with provision network addresses range larger then /64 (e.g /48)
I reproduced this and the failure is in dnsmasq:
dnsmasq: prefix length must be at least 64 at line 10 of /etc/dnsmasq.conf
This seems to be a limitation of dnsmasq and ipv6, from the man page:
> For IPv6, the parameters are slightly different: instead of netmask and broadcast address, there is an optional prefix length which must
> be equal to or larger then the prefix length on the local interface. If not given, this defaults to 64. Unlike
> the IPv4 case, the prefix length is not automatically derived from the interface configuration. The minimum size of the prefix length is 64.
As far as I can tell there is no simple way to work around this limitation so I think it's best to document for now.
I read the description /lgtm
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.