Description of problem:
While installing, the node fails to start with the Could not find an allocated subnet for node: error. The we after creating the hostsubnet manually (https://access.redhat.com/solutions/2087721), the re-run of installer works but then again fails while registering other node as it seems the master is not allocating the subnet to the node, thereby node registration fails and node service fails to start.
Version-Release number of selected component (if applicable):
Openshift Enterprise 3.2
Only at customer end
Steps to Reproduce:
1.Mentioned in the description
1. We made the installation success by adding the host subnet manually and then
re-running the installer.
2. Then we removed the hostsubnet and then again tried to restart the node which again failed.
When node starts the master shall allocate the subnet to it
When node starts the master doesn't seem to have allocated the subnet to the node.
I'm moving this back to assigned. Please move it back to Modified when the pull requests have merged. Then once we have merged the code from origin to OSE I will move this to QE.
PRs have merged to origin.
This has been merged and is in OSE v126.96.36.199 or newer.
Test on latest openshift env, no this issue, verify this bug.
[root@ip-172-18-0-56 ~]# openshift version
setup a cluster env, then check all node is ready and no errors in node log 'Could not find an allocated subnet for node'
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.