On Tue, Feb 8, 2022 at 4:05 PM Charles Stellen <[email protected]> wrote: > > Dear Ovirt Hackers, > > sorry: incidently send to [email protected] > > we are dealing with hosted engine deployment issue on a fresh AMD EPYC > servers: > > and we are ready to donate hardware to Ovirt community after we pass > this issue ( :-) ) > > 0/ base infra: > > - 3 identical physical servers (produced in 2021-4Q) > - fresh, clean and recent version of centos 8 stream installed > (@^minimal-environment) > - servers are interconnected with cisco switch, each other are network > visible, > all with nice internet access (NAT) > > > 1/ storage: > > - all 3 servers/nodes host nice and clean glusterfs (v9.5) and volume > "vol-images01" is ready for VM images > - ovirt hosted engine deployment procedure: > - easily accept mentioned glusterfs storage domain > - mount it during "hosted-engine --deploy" with no issue > - all permissions are set correctly at all glustrfs nodes ("chown > vdsm.kvm vol-images01") > - no issue with storage domain at all > > > 2/ ovirt - hosted engine deployment: > > - all 3 servers successfully deployed recent ovirt version with standart > procedure > (on top of minimal install of centos 8 stream): > > dnf -y install ovirt-host > virt-host-validate: PASS ALL > > - at first server we continue with: > > dnf -y install ovirt-engine-appliance > hosted-engine --deploy (pure commandline - so no cockpit is used) > > DEPLOYMENT ISSUE: > > - during "hosted-engine --deploy" procedure - hosted engine becomes > temporairly accessible at:https://server01:6900/ovirt-engine/ > - with request to manualy set "ovirtmgmt" virtual nic > - Hosts > server01 > Network Interfaces > [SETUP HOST NETWORKS] > "ovirtmgmt" dropped to eno1 - [OK] > - than All pass fine - and host "server01" becomes Active > - back to commandline to Continue with deployment "Pause execution until > /tmp/ansible.jksf4_n2_he_setup_lock is removed" > by removing the lock file > > - deployment than pass all steps_until_ "[ INFO ] TASK > [ovirt.ovirt.hosted_engine_setup : Check engine VM health]" > > ISSUE DETAILS: new VM becomes not accessible in the final stage - as it > should be reachable at its final IP:
Can you please try with qemu 6.0.0? See other threads here about broken 6.1. Sorry for that. Good luck and best regards, -- Didi _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/55EAJSAUCO47ZZ7PDYFSTRGGQZXFQPYP/
