bootdisk seems to only support static networking
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1120762
Description of problem:
This is probably more wide spread than just bootdisk, but the following template:
seems to only support static networking.
<% static = @host.token.nil? ? '?static=yes' : '&static=yes' -%>
seems to indicate that static networking would be used in all cases. In my case I did not have a subnet defined so the request to the kickstart attempted to use static networking and failed with 'undefined method mask for nil'.
Steps to Reproduce:
1. Create a host and do not specify a subnet (because its not needed)
2. Attempt to provision a system with bootdisk
Removing the static information seems to make it work just fine.
#2 Updated by Dominic Cleal about 7 years ago
This is by design for the host-specific disk, but I guess less so for the generic disk. Once Foreman has a way to specify static/dynamic config per host then it'll be easier to fix this without introducing an additional type of disk, or breaking it for other users.
#3 Updated by Marek Hulán over 6 years ago
I think this works as expected, when I tried to generate host-specific image I got an Foreman exception that subnet is not specified, for generic image it seems to work just fine. The user experience is not ideal since they don't see nice error explaining why it does not work, but that's a different story. Dominic, could you please confirm? This is my first bootdisk bug :-) Maybe the output of this issue would be to improve documentation?