[ovirt-users] Setting up new VM

I have self-hosted-engine (4.2) running on centos (7.4), the engine is running fine so I am trying to deploy a test vm to check ssh connectivity. however, the vm-infra role runs without any issues and I can see the new VM is in "up" state but it does not have any IP assigned eventhough I have d

[ovirt-users] VM status and issue with cloud_init

Some what new to the VM and Ovirt world here and need some help understanding terminologies and get the VM to work as per requirement. I have a self-hosted-engine (4.2) running on centos (7.4). The engine is in good health and I have deployed a test VM using below playbook successfully. It is

[ovirt-users] Re: Cannot see ipaddr of new VM

the vm does come up, but I do not see any ipaddr, fqdn or dns. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://w

[ovirt-users] Cannot see ipaddr of new VM

I have got a self-hosted-engine (4.2) running on centos (7.4). I am trying to create new vanilla vm with static ip using cloud-init to test ssh connectivity. I have below playbook - - name: Add vanilla vm ovirt_vms: auth: "{{ ovirt_auth }}" name: test01 cluster: Default

[ovirt-users] SSH into guest VM

I have self-hosted-engine (4.2) deployed successfully on cento (7.4) server. The physical server has 'ovirt' as hostname and the self-hosted engineVM deployed and running on it has 'engine.ovirt' as fdqn. I can successfully create new VM using the oVirt.vm-infra example playbook. But what othe

[ovirt-users] Second host deployment fails on self-hosted-engine

I have self-hosted-engine (4.2) deployed successfully on cento (7.4) server. The physical server has 'ovirt' as hostname and the self-hosted engineVM deployed and running on it has 'engine.ovirt' as fdqn. I want to deploy another host on engineVM and I am using pre-baked oVirt.Infra role examp

[ovirt-users] Obtain dynamic inventory onto local machine using ovirt4.py for self-hosted engine

I have successfully deployed self-hosted-engine (4.2) on centos (7.4) server. the server address is ovirt where the self-hosted engine running on it has fdqn as engine.ovirt. I have ovirt,ini configured on server acan run the ovirt4.py from the server to obtain the vms in groups. But I want to

[ovirt-users] Use local ansible to talk to engineVM and other vm

I have a self-hosted-engine (4.2) running on a centos 7.4 server. I have downloaded ovirt ansible roles from ansible-galaxy and can run them from the server where the engineVM is running and able to deploy new vms, clusters, dc, etc. I have seen the use of ovirt4.py file to target and group ho

[ovirt-users] First host within Self-Hosted engine stays in non-responsive state

I am trying to setup self-hosted-engine (4.2) on a single machine running centos 7.4. I ran hosted-engine deploy script and it ran all the way through but failed on last task (at "Wait for the local bootstrap VM to be down at engine eyes") while creating the local engine VM. However, the --vm-s

[ovirt-users] Self-Hosted engine deploy fails but hosted-engine --vm-status shows engine in good health

I am setting up self-hosted engine (4.2) on centos 7.4. The setup runs all the way through and creates the local VM, but fails on task "Wait for the local bootstrap VM to be down at engine eyes". But if I then run hosted-engine --vm-start, it comes back up and shows it is in good health, but

[ovirt-users] Ovirt host becomes non_operational

I am setting up self-hosted-ovirt-engine (4.2) on centos7.4. While running hosted-engine --deploy script, it fails at "Check host status" with 'host has been set in non_operational status' error. logs on engine vm at /var/log/ovirt-engine/host-deploy shows ansible tasl for "add host" ran succes

[ovirt-users] Ovirt Self Hosted engine deploy fails

I am trying to setup self hosted ovirt engine (4.2) on centos 7.4, but the setup fails after 'Add host' task on 'wait for the host to be up'. The log doesn't seem to give clear indication where the issue might be. But I got below when ssh manually into ovirt appliance where the engine-deploy run