Hi Marcos,
The dnsmasq service running on the KVM host manages the IP assignment during the first
deployment phase.
How did you deploy your KVM host? Which configurations have you done on it before
running
the hosted-engine --deploy?
Also, what is your full hosted-engine deployment command?
I deployed the KVM hosts using the guide at:
https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_eng...
(section 4.2 Installing Enterprise Linux Hosts)
and
https://www.ovirt.org/download/install_on_rhel.html
Most of the ovirt packages were installed from the installation of the
ovirt-engine-appliance. The KVM hosts are using EL 9.3. I've tried on two different EL
hosts: one with the standard ovirt-45 repos, and the other had the nightly builds enabled.
I observed the same issues on both. I haven't changed any specific settings, such as
networking or storage.
The full command to deploy the engine VM was done via:
hosted-engine --deploy --4
I have just setup glusterfs just as a temporary storage option now (yet to run the deploy
again), though I'm not sure how to get ovirt to use it. As mentioned I don't know
whether this or the networking is causing it to fail.
In case it is important, I notice that virtnetworkd.socket systemd unit gets killed during
the deployment, and has to be restarted otherwise the deployment fails prematurely. It
also masks all the libvirtd systemd units as part of the cleanup, and these have to
manually unmasked and several need manually restarting (virtnetword.socket,
virtqemud.socket and virtstoraged.sock) before the deployment is run again or the deploy
will fail on trying to communicate with these.
Thanks very much for the help, let me know if any further information needed.
Cam
>
> -----Original Message-----
> From:
iucounu(a)gmail.com <iucounu(a)gmail.com>
> Sent: Tuesday, January 23, 2024 12:49 PM
> To:
users(a)ovirt.org
> Subject: [ovirt-users] Re: [External] : Re: can hosted engine deploy use local
repository
> mirrors instead of internet ones?
>
> Thanks very for the reply Marcos. I tried another deployment, just to see if
"wait
> for the host to be up" would time out, and I saw a couple of errors in the log:
>
> From the ovirt-hosted-engine-setup-ansible-final_clean log, it mentions that the VM
IP is
> undefined:
>
> 2024-01-23 12:50:19,554+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 {'msg': "The task includes an option
with
> an undefined variable. The error was: 'local_vm_ip' is undefined.
> 'local_vm_ip' is undefined\n\nThe error appears to be in
>
'/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_machine.yml':
> line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax
> problem.\n\nThe offending line appears to be:\n\n---\n- name: Set the name for
add_host\n
> ^ here\n", '_ansible_no_log': False}
>
> In the ovirt-hosted-engine-setuplog, it mentions not being able to get the storage
pool:
>
>
> 2024-01-23 12:50:35,787+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 {'changed': True, 'stdout':
'',
> 'stderr': "error: failed to get pool 'localvmvy8whst5'\nerror:
> Storage pool not found: no storage pool with matching name
> 'localvmvy8whst5'", 'rc': 1, 'cmd': ['virsh',
> '-c',
'qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf',
> 'pool-destroy', 'localvmvy8whst5'], 'start': '2024-01-23
> 12:50:35.558666', 'end': '2024-01-23 12:50:35.611808',
> 'delta': '0:00:00.053142', 'msg': 'non-zero return
code',
> 'invocation': {'module_args': {'_raw_params': 'virsh -c
> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf pool-destroy
> localvmvy8whst5', '_uses_shell': False, 'stdin_add_newline':
True,
> 'strip_empty_ends': True, 'argv': None, 'chdir': None,
> 'executable': None, 'creates': None, 'removes': None,
> 'stdin': None}}, 'stdout_lines': [], 'stderr_lines':
["error:
> failed to get pool 'localvmvy8whst5'", "error: Storage pool not
fou
> nd: no storage pool with matching name 'localvmvy8whst5'"],
> '_ansible_no_log': None}
>
> I set the IP to the one I have assigned in DNS, but when I attach to the console of
the VM
> (which is still running, though the disk image has been deleted) via virsh, it shows
me a
> completely different IP: In hosted-engine --deploy, I set a 10.0.0.x address,
however, it
> shows a 192.168.1.x address on the VM. Do I need to set this somewhere else, e.g.,
with
> '--ansible-extra-vars=he_ipv4_subnet_prefix='?
>
> As for the storage pool, is that for later VM deployment? The deploy script did not
ask me
> for a storage location. If I need to specify this, where do I do this?
>
> Thanks again for any help,
>
> Kind regards,
>
> Cam
>
> PS: is there a simple way to have the answers saved so I don't have to keep
running
> through all the questions every time I try a deployment
> _______________________________________________
> Users mailing list --
users(a)ovirt.org
> To unsubscribe send an email to
users-leave(a)ovirt.org Privacy Statement:
>
https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!...
> oVirt Code of Conduct:
>
https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi...
> List Archives:
>
https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...