Hi Bill, On Tue, 2017-08-15 at 09:48 -0700, Bill Sirinek wrote: > Is there any update to this issue? I'm working on upgrading to 1.15.3 > and this problem still exists. I have about 20 DHCP servers with > smart proxies and many of them are multi-homed because we do a lot of > building on non-routable admin networks. > > I see Bug #1221 http://projects.theforeman.org/issues/1221 that was > "Ready For Testing" but got moved back to "New" (!)
I'm not sure you meant 1221, that bug appears to have been closed 5 years ago... > There is also http://projects.theforeman.org/issues/9169 that appears > related I think this is the bug you meant. To be clear, Ready For Testing means a patch has been written and can be reviewed. If the patch is not merged, or the approach needs to be changed, then the PR will be closed and the state reverted to New (or Assigned if someone is still owrking on it). In this case, as far as I can see, the person who proposed the change abandoned the patch before it got merged (see https://github.com/thefor eman/foreman/pull/3360#issuecomment-200659805), so it's correct that it was set back to New. I still think such a feature (a checkbox on the Subnet to not set next-server) is a welcome one, if anyone else wants to pick it up. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
