After selecting the "Use Foreman Hosts Providers" option in the "New host" dialog and then deselecting it. The "Address" field to enter an fqdn/ip address is disabled/greyed out. It's now impossible to add a new node unless you cancel and try again
Hey, When "Use foreman hosts providers" is on the user picks one of the providers and select "Discovered Hosts" or "Provisioned Hosts". in that phase all enabled. when you pick an host, the address field gets filled by the IP address returned from foreman (foreman's dhcp signs the ip for the discovered or provisioned host). when removing the "Use foreman hosts providers" check, you can change the address again The FQDN depends on the "Name" you give to the host (which is configurable in the AddNewHost view). it will be the "[chosen name].[domain name]" after the provision ends. the domain specified on the Host group you pick and configured (you can see the details when choosing the hostgroup from the list). for example: if you declared domain "usersys.redhat.com" and you hostname is fedora20host. your FQDN will be - fedora20host.usersys.redhat.com. foreman takes care of that.. Oved, something different than what you expect?
(In reply to Yaniv Bronhaim from comment #1) > Hey, > When "Use foreman hosts providers" is on the user picks one of the providers > and select "Discovered Hosts" or "Provisioned Hosts". in that phase all > enabled. when you pick an host, the address field gets filled by the IP > address returned from foreman (foreman's dhcp signs the ip for the > discovered or provisioned host). > > when removing the "Use foreman hosts providers" check, you can change the > address again > > The FQDN depends on the "Name" you give to the host (which is configurable > in the AddNewHost view). it will be the "[chosen name].[domain name]" after > the provision ends. the domain specified on the Host group you pick and > configured (you can see the details when choosing the hostgroup from the > list). > for example: if you declared domain "usersys.redhat.com" and you hostname is > fedora20host. your FQDN will be - fedora20host.usersys.redhat.com. > foreman takes care of that.. > > Oved, something different than what you expect? Seems good to me. One question, though, if the domain defined in the hostgroup is example.com, and I set the name in the oVirt UI to oved.example.com, will it be set correctly by Foreman? I guess so... just making sure. Regardless of that, the bug refers to the FQDN being disabled after enabling the use of foreman host provider, and disabling that. Make sure it is enabled even if you set everything up with foreman, and then you regret and disable the use of a host provider, and want to add the host manually.
Apparently the latter is fixed by http://gerrit.ovirt.org/#/c/31102/. about setting name to full FQDN and assume that foreman will remove part of it is way too ambitious :) I almost sure it will be oved.example.com.example.com, but will check that if we want to handle such case we need to not allow setting the name with dotes or remove all after the dote.. something like that
(In reply to Yaniv Bronhaim from comment #3) > Apparently the latter is fixed by http://gerrit.ovirt.org/#/c/31102/. about > setting name to full FQDN and assume that foreman will remove part of it is > way too ambitious :) I almost sure it will be oved.example.com.example.com, > but will check that > > if we want to handle such case we need to not allow setting the name with > dotes or remove all after the dote.. something like that Let's first understand how it behaves. If needed, open a bug on that. As for this bug, move it to modified once the patch is merged on ovirt-engine-3.5.
Fixed
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA