Created attachment 1428388 [details] screenshot of UI Description of problem: While we were trying to create a host on libvirt compute resource, each time have to click on "suggest new" to fetch free IP. While in case of sat 6.3, free IP get assigned once subnet selected. Version-Release number of selected component (if applicable): # rpm -q satellite satellite-6.4.0-3.beta.el7sat.noarch How reproducible: always Steps to Reproduce: 1. Create hostgroup with required parameters 2. Try to create host on libvirt compute resource 3. Go to interfaces tab 3. Edit interface Actual results: IPv4 Address field will be blank though subnet is populated. (see attachment) Expected results: Free IP should be automatically populate. (No need to click on suggest new) Additional info:
Does the empty IP address actually prevent from provisioning or is the IP generated later?
No this will not prevent from provisioning and the IP get generated later.
Is this a regression?
Yes, this is regression...missed to add keyword!
I was able to reproduce the issue now: it happens only when `Deploy on` field is specified in the hostgroup, updated the subject of the BZ to narrow down the scope.
Created redmine issue https://projects.theforeman.org/issues/24072 from this bug
Upstream bug assigned to inecas
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24072 has been resolved.
QE Notes: When testing this BZ, also consider VM tab form which throws a error, when there is a compute resource in hostgroup and we use the hostgroup to create a host. "'penny-broadway' not found on 'rhv11 (RHV)' 'penny-broadway' could be deleted or 'rhv11 (RHV)' is not responding."
VERIFIED Version tested: Satellite 6.4 snap 13 Free IP get automatically populated and no need to click on suggest new. Also as per comment #22 I could not see the error on VM tab.
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. https://access.redhat.com/errata/RHSA-2018:2927