Description of problem: Deploying multiple assisted installers where the user does not provide the VIP addresses with the same cluster name ends up with them competing for the same DHCP leased address and conflicting. Version: baremetal-runtimecfg 4.6 Steps to reproduce: 1. Deploy an assisted installer cluster without providing VIPs specifying clustername='reproducer' 2. Deploy another cluster on the same DHCP served network without providing VIP addresses and specifying the same clustername, i.e., 'reproducer' Actual results: Both the first and the second cluster ask DHCP for a lease with the same MAC address, thus the first cluster breaks as the address is taken by the second and the second fails to deploy. Expected results: Each cluster requests different addresses to DHCP so we keep allowing multiple clusters named the same
Yuval could you please provide more details about the problem? The description is not very clear. Thanks
*** Bug 1866348 has been marked as a duplicate of this bug. ***
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196