API is not adding default IP adress for new Jails
When creating a new jail via the freenas WebGUI without any data than the jail name, the new jail will get a default IPv4 adress and subnetmask assigned.
When creating a new jail via the API, it won't get this default IP assigned.
I don't know if this is expected behaviour or a bug. I assumed creation of a new jail via API would behave same as in the WebGUI.
fix(api): set ipv4 or dhcp when creating jail
(cherry picked from commit 29c5bb97d17b826239df5529acead24c4f9d00a4)
#3 Updated by Suraj Ravichandran about 3 years ago
- Status changed from Screened to Unscreened
- Assignee changed from Suraj Ravichandran to Anonymous
Over to Neha, to work on, she asked for tickets on slack
@Neha please slack pm me if you have any questions as to how to go about making default jail ip assignment behaviour dhcp and as well as clean up the manual ip setting routines in jail gui code.
#8 Updated by Suraj Ravichandran almost 3 years ago
- Target version changed from 9.10.1-U1 to 9.10.1-U2
@Neha proposed a solution wherein we default to DHCP for all newly created jails henceforth with the option of letting the user manually specify the ip and everything.
This solution would have also satisfied the above ticket however, she discussed with some of us and we all found it ok. I still wanted John's opinion on it since he is primary on Jails & Plugins, and John has some issues with the fix which we are yet to discuss and resolve, so I do not know if we can get this in by U1, thus, moving target to 9.10.1-U2 for now will get it back in U1 if we are done earlier.
#13 Updated by Suraj Ravichandran over 2 years ago
- Status changed from Needs Developer Review to Reviewed
- Assignee changed from Suraj Ravichandran to William Grzybowski
My only suggestion here is to add ipv6 autoconfigure to the API hydrate routine (but discussed this with william and we both went "meh")
Other than that this is pretty straightforward so marking as reviewed.