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

[03CE 007]

I cannot use the web UI due to network lock down. I have the
self-hosted-engine running using minimal centos 7.4.

But when I use the api to query new VM, i cannot see it 'reported_device'
under this either.

On 6 June 2018 at 11:33, Petr Horacek  wrote:

> Are they reported in oVirt UI?
>
> 2018-06-06 11:16 GMT+02:00 03CE 007 <03ce...@gmail.com>:
>
>> Thank you, I can see the interface/device for self-hosted-engine VM under
>> 'reported_devices' but when I spin up a new VM using cloud_init, i see
>> empty 'reported_devices' hence the task to wait for the ip address is
>> skipped.
>>
>>
>> On Wed, 6 Jun 2018, 10:13 am Petr Horacek,  wrote:
>>
>>> Hello,
>>>
>>> if you don't see IPs assigned to attached interfaces, you probably need
>>> to install ovirt-guest-agent on the VM. Or are you missing interfaces in
>>> general?
>>>
>>> Regards,
>>> Petr
>>>
>>> 2018-05-30 13:09 GMT+02:00 <03ce...@gmail.com>:
>>>
>>>> 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://www.ovirt.org/communit
>>>> y/about/community-guidelines/
>>>> List Archives: https://lists.ovirt.org/archiv
>>>> es/list/users@ovirt.org/message/NAJRZ62LOPIXGMWKOUM74NLQBIM6F33J/
>>>>
>>>
>>>
>
___
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://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RGKA5UTDQIKM777UDAT5Z6JS4Q7IBFWB/

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

[03CE 007]

Thank you, I can see the interface/device for self-hosted-engine VM under
'reported_devices' but when I spin up a new VM using cloud_init, i see
empty 'reported_devices' hence the task to wait for the ip address is
skipped.


On Wed, 6 Jun 2018, 10:13 am Petr Horacek,  wrote:

> Hello,
>
> if you don't see IPs assigned to attached interfaces, you probably need to
> install ovirt-guest-agent on the VM. Or are you missing interfaces in
> general?
>
> Regards,
> Petr
>
> 2018-05-30 13:09 GMT+02:00 <03ce...@gmail.com>:
>
>> 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://www.ovirt.org/community/about/community-
>> guidelines/
>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
>> message/NAJRZ62LOPIXGMWKOUM74NLQBIM6F33J/
>>
>
>
___
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://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/A7T4NJG3EIC4WNGUXVZXIXPOLWU7DSHA/

[ovirt-users] Re: VM status and issue with cloud_init

[03CE 007]

Hello Thomas,
Could j you please advise here?

On Thu, 31 May 2018, 9:09 am Arik Hadas,  wrote:

>
>
> On Thu, May 31, 2018 at 10:08 AM, 03CE 007 <03ce...@gmail.com> wrote:
>
>> Ok thanks, when you say guest agent, could you please provide the full
>> name and how to have it installed, and I am assuming it should be installed
>> on the the engineVM or the new VM I want to spin and boot up.
>>
>
> Generally speaking, we are transitioning from ovirt-guest-agent to
> qemu-guest-agent.
> I don't know what's the status of this transition with respect to centos
> as I typically use latest-fedora.
> Tomas, can you please advice what needs to be installed in centos 7.4?
>
> And it should be installed in the new VM.
>
>
>>
>> On Thu, 31 May 2018, 7:57 am Arik Hadas,  wrote:
>>
>>>
>>>
>>> On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:
>>>
>>>> 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 currently in "up" state.
>>>>
>>>>
>>>> - name: oVirt Self-Hosted-Engine - Manage VMs
>>>>   hosts: hypervisor_ovirt
>>>>   gather_facts: false
>>>>
>>>>   vars_files:
>>>> # Contains encrypted `engine_password` varibale using ansible-vault
>>>> - ovirt-secrets.yml
>>>>
>>>>   vars:
>>>> engine_url: https://engine-ovirt.dw/ovirt-engine/api
>>>> engine_user: admin@internal
>>>> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>>>>
>>>> mytest_vm:
>>>>   cluster: Default
>>>>   memory: 64GiB
>>>>   memory_guaranteed: 1GiB
>>>>   cores: 2
>>>>   nics:
>>>> - name: vnet0
>>>>   network: ovirtmgmt
>>>>   profile: ovirtmgmt
>>>>   interface: virtio
>>>>   wait: true
>>>>   domain: node.dev.dw
>>>>   os_type: rhel_7x64
>>>>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>>>>   root_password: super_password
>>>>   disks:
>>>> - size: 20GiB
>>>>   name: data
>>>>   storage_domain: hosted_storage
>>>>   interface: virtio
>>>>   bootable: true
>>>>   nics:
>>>> - name: vnet0
>>>>   network: ovirtmgmt
>>>>   profile: ovirtmgmt
>>>>   interface: virtio
>>>>
>>>> vms:
>>>>   - name: mytest_vm
>>>> tag: mytest_vm
>>>> profile: "{{ mytest_vm }}"
>>>> cloud_init:
>>>>   dns_servers:
>>>> - 10.90.x.1
>>>> - 10.90.x.1
>>>>   nic_boot_protocol: static
>>>>   nic_ip_address: 10.90.x.y
>>>>   nic_netmask: 255.255.255.0
>>>>   nic_gateway: 10.90.x.z
>>>>   nic_name: eth0
>>>>   nic_on_boot: true
>>>>   host_name: mytestvm.test.dw
>>>>   custom_script: |
>>>> write_files:
>>>>  - content: |
>>>>  Hello, world!
>>>>path: /tmp/greeting.txt
>>>>permissions: '0644'
>>>>   user_name: root
>>>>   root_password: super_password
>>>> cloud_init_persist: true
>>>>
>>>>   roles:
>>>> - oVirt.vm-infra
>>>>
>>>>
>>>> Above playbook runs fine, but when i see summary using ovirt4.py, i do
>>>> not see ipaddr for this test vm.
>>>>
>>>> - I do not see the ipaddr for this VM despite specifying it using
>>>> cloud_init
>>>>
>>>
>>> You need to install a guest agent in order to be provided with ip
>>> addresses.
>>>
>>>
>>>> - does the "up" status mean it has "booted" or I need to do something
>>>> else to boot it with centos 7.4 minimal
>>>>
>>>
>>> Without a guest agent installed we know nothing about the state of the
>>> guest so in this case the UP status only means that the VM process is
>>> running for more than 1 minute.
>>>
>>>
>>>>
>>>> Thank you in advance.
>>>> ___
>>>> 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://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>>>>
>>>
>>>
>
___
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://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DZO3GDPDQFMNS4MPBQUWHPGABIUM7PLP/

[ovirt-users] Re: VM status and issue with cloud_init

[03CE 007]

upon checking  yum install ovirt-guest-agent-common, I can get

Package ovirt-guest-agent-common-1.0.14-1.el7.noarch already installed and
latest version
Nothing to do

systemctl status ovirt-guest-agent.service shows that service is enabled
and has been running.

Is there something else I need to check/do ?


On 31 May 2018 at 07:57, Arik Hadas  wrote:

>
>
> On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:
>
>> 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 currently in "up" state.
>>
>>
>> - name: oVirt Self-Hosted-Engine - Manage VMs
>>   hosts: hypervisor_ovirt
>>   gather_facts: false
>>
>>   vars_files:
>> # Contains encrypted `engine_password` varibale using ansible-vault
>> - ovirt-secrets.yml
>>
>>   vars:
>> engine_url: https://engine-ovirt.dw/ovirt-engine/api
>> engine_user: admin@internal
>> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>>
>> mytest_vm:
>>   cluster: Default
>>   memory: 64GiB
>>   memory_guaranteed: 1GiB
>>   cores: 2
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>   wait: true
>>   domain: node.dev.dw
>>   os_type: rhel_7x64
>>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>>   root_password: super_password
>>   disks:
>> - size: 20GiB
>>   name: data
>>   storage_domain: hosted_storage
>>   interface: virtio
>>   bootable: true
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>
>> vms:
>>   - name: mytest_vm
>> tag: mytest_vm
>> profile: "{{ mytest_vm }}"
>> cloud_init:
>>   dns_servers:
>> - 10.90.x.1
>> - 10.90.x.1
>>   nic_boot_protocol: static
>>   nic_ip_address: 10.90.x.y
>>   nic_netmask: 255.255.255.0
>>   nic_gateway: 10.90.x.z
>>   nic_name: eth0
>>   nic_on_boot: true
>>   host_name: mytestvm.test.dw
>>   custom_script: |
>> write_files:
>>  - content: |
>>  Hello, world!
>>path: /tmp/greeting.txt
>>permissions: '0644'
>>   user_name: root
>>   root_password: super_password
>> cloud_init_persist: true
>>
>>   roles:
>> - oVirt.vm-infra
>>
>>
>> Above playbook runs fine, but when i see summary using ovirt4.py, i do
>> not see ipaddr for this test vm.
>>
>> - I do not see the ipaddr for this VM despite specifying it using
>> cloud_init
>>
>
> You need to install a guest agent in order to be provided with ip
> addresses.
>
>
>> - does the "up" status mean it has "booted" or I need to do something
>> else to boot it with centos 7.4 minimal
>>
>
> Without a guest agent installed we know nothing about the state of the
> guest so in this case the UP status only means that the VM process is
> running for more than 1 minute.
>
>
>>
>> Thank you in advance.
>> ___
>> 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://www.ovirt.org/communit
>> y/about/community-guidelines/
>> List Archives: https://lists.ovirt.org/archiv
>> es/list/users@ovirt.org/message/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>>
>
>
___
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://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EUG3IUI6QF6AMWG7XZRJHEGETHDVVZL3/

[ovirt-users] Re: VM status and issue with cloud_init

[03CE 007]

Ok thanks, when you say guest agent, could you please provide the full name
and how to have it installed, and I am assuming it should be installed on
the the engineVM or the new VM I want to spin and boot up.

On Thu, 31 May 2018, 7:57 am Arik Hadas,  wrote:

>
>
> On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:
>
>> 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 currently in "up" state.
>>
>>
>> - name: oVirt Self-Hosted-Engine - Manage VMs
>>   hosts: hypervisor_ovirt
>>   gather_facts: false
>>
>>   vars_files:
>> # Contains encrypted `engine_password` varibale using ansible-vault
>> - ovirt-secrets.yml
>>
>>   vars:
>> engine_url: https://engine-ovirt.dw/ovirt-engine/api
>> engine_user: admin@internal
>> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>>
>> mytest_vm:
>>   cluster: Default
>>   memory: 64GiB
>>   memory_guaranteed: 1GiB
>>   cores: 2
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>   wait: true
>>   domain: node.dev.dw
>>   os_type: rhel_7x64
>>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>>   root_password: super_password
>>   disks:
>> - size: 20GiB
>>   name: data
>>   storage_domain: hosted_storage
>>   interface: virtio
>>   bootable: true
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>
>> vms:
>>   - name: mytest_vm
>> tag: mytest_vm
>> profile: "{{ mytest_vm }}"
>> cloud_init:
>>   dns_servers:
>> - 10.90.x.1
>> - 10.90.x.1
>>   nic_boot_protocol: static
>>   nic_ip_address: 10.90.x.y
>>   nic_netmask: 255.255.255.0
>>   nic_gateway: 10.90.x.z
>>   nic_name: eth0
>>   nic_on_boot: true
>>   host_name: mytestvm.test.dw
>>   custom_script: |
>> write_files:
>>  - content: |
>>  Hello, world!
>>path: /tmp/greeting.txt
>>permissions: '0644'
>>   user_name: root
>>   root_password: super_password
>> cloud_init_persist: true
>>
>>   roles:
>> - oVirt.vm-infra
>>
>>
>> Above playbook runs fine, but when i see summary using ovirt4.py, i do
>> not see ipaddr for this test vm.
>>
>> - I do not see the ipaddr for this VM despite specifying it using
>> cloud_init
>>
>
> You need to install a guest agent in order to be provided with ip
> addresses.
>
>
>> - does the "up" status mean it has "booted" or I need to do something
>> else to boot it with centos 7.4 minimal
>>
>
> Without a guest agent installed we know nothing about the state of the
> guest so in this case the UP status only means that the VM process is
> running for more than 1 minute.
>
>
>>
>> Thank you in advance.
>> ___
>> 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://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>>
>
>
___
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://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JPKSV7NABF64XRQIESB6LHADERXAQPMO/

[ovirt-users] Re: SSH into guest VM

[03CE 007]

Thank you, I am using cloud-init module as suggested, but the VM that
starts on engineVM does not seem to have ip or nic assigned.

below is my ansible task -

- name: "Create VM {{ current_vm.name }}"
  ovirt_vms:
auth: "{{ ovirt_auth }}"
name: "{{ current_vm.name }}"
template: "{{ current_vm.profile.template | default(omit) }}"
cluster: "{{ current_vm.profile.cluster | default(omit) }}"
memory: "{{ current_vm.profile.memory | default(omit) }}"
high_availability: "{{ current_vm.profile.high_availability |
default(omit) }}"
cpu_cores: "{{ current_vm.profile.cores | default(omit) }}"
cpu_sockets: "{{ current_vm.profile.sockets | default(omit) }}"
storage_domain: "{{ current_vm.profile.storage_domain | default(omit)
}}"
timeout: "{{ vm_infra_create_single_timeout }}"
operating_system: rhel_7x64
memory_guaranteed: "{{ current_vm.profile.memory_guaranteed |
default(omit) }}"
cloud_init:
 * host_name: "{{ current_vm.name  }}.test.dw"*
  nic_boot_protocol: static
  nic_ip_address: 10.90.x.z
  nic_netmask: 255.255.255.0
  nic_gateway: 10.90.x.y
  nic_name: eth1
  nic_on_boot: true
  custom_script: |
write_files:
 - content: |
 Hello, world!
   path: /tmp/greeting.txt
   permissions: '0644'
  user_name: root
  root_password: super_password
cloud_init_persist: true
  changed_when: false
  async: "{{ vm_infra_create_single_timeout }}"
  poll: 0
  register: added_vm



I use ovirt4.py to check the vm overview, but I see below only (shouldn't
the devices dic be populated with above nic details?, nor I see the
hostname updated from h*ypervisor-ovirt.dw* to *mytest-vm.test.dw*

mytest-vm": {
"affinity_groups": [],
"affinity_labels": [],
"ansible_host": null,
"cluster": "Default",
"description": null,
   * "devices": {}*,
   * "fqdn": null,*
"host": "hypervisor-ovirt.dw",
"id": "0c1f6a11-0ca2-4d2e-b05f-0d3bdc70d4af",
"name": "mytest-vm",
"os_type": "rhel_7x64",
"statistics": {
  "cpu.current.guest": 0.72,
  "cpu.current.hypervisor": 0.33,
  "cpu.current.total": 1.1,
  "memory.buffered": 0.0,
  "memory.cached": 0.0,
  "memory.free": 0.0,
  "memory.installed": 68719476736.0,
  "memory.used": 0.0,
  "migration.progress": 0.0
},
"status": "up",
"tags": [],
"template": "Blank"
  }
}


is anything missing in my setup, I use rhel_7x64 as operating_system.

Thank you.



On 24 May 2018 at 13:43, Yaniv Kaul  wrote:

>
>
> On Wed, May 23, 2018 at 5:43 PM, <03ce...@gmail.com> wrote:
>
>> 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 other config/var i need to add in them so that I can ssh
>> into this new VM. Some example, tips, hints would be helpful.
>>
>
> I think that you'd want (via cloud-init) to set the SSH keys for the root
> user (or the password), etc.
> Y.
>
>
>>
>> Thank you.
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

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

[03CE 007]

Hello Ondra,
you're correct, there was much accept removing 'connection: local' line
from ovirt ansible roles.

however, the example playbook to deploy new vm fails at template option and
it complains that i don't have rhel7 template. Doesn't this come bundled
with hosted-engine and is available after deployment?

Do i need to create/install new template?



On 23 May 2018 at 06:50, Ondra Machacek  wrote:

> On 05/22/2018 06:44 PM, 03ce...@gmail.com wrote:
>
>> 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
>> control the vms using ansible from my macbook and run ansible playbooks
>> locally.
>>
>> so I have downloaded the ovirt.ini and ovirt4.py from server and tried
>> running it, but had no success.
>>
>> Is there something special needs setting up for
>> 'self-hosted-ovirt-engine' as oppose to vanilla ovirt-engine which will
>> allow me to control vms from my macbook?
>>
>
> You don't need to do anything special.
> What's the error you get?
>
>
>
>> thanks.
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

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

[03CE 007]

this has worked, many thanks for helping.

On 18 May 2018 at 09:47, Sumit Bharadia <03ce...@gmail.com> wrote:

> thanks, will give it a try and report back.
>
> On 18 May 2018 at 09:45, Simone Tiraboschi  wrote:
>
>>
>>
>> On Fri, May 18, 2018 at 10:30 AM, Sumit Bharadia <03ce...@gmail.com>
>> wrote:
>>
>>> I see, which one specific step during the hosted-engine-setup option, is
>>> it 1st or the 2nd question I need to set value for?
>>>
>>>
>>>1. Please provide a comma-separated list (max 3) of IP addresses of
>>>domain name servers for the engine VM
>>>2. Add lines for the appliance itself and for this host to
>>>/etc/hosts on the engine VM?
>>>
>>> Say yes to this one.
>>
>>
>>
>>> thank you.
>>>
>>>
>>> On 18 May 2018 at 09:20, Simone Tiraboschi  wrote:
>>>


 On Fri, May 18, 2018 at 10:09 AM, Sumit Bharadia <03ce...@gmail.com>
 wrote:

> attached, initial engine.log from engine VM
>

 OK, your issue is here:

 2018-05-18 09:05:27,756+01 ERROR 
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
 (EE-ManagedThreadFactory-engineScheduled-Thread-12) [294c1528]
 Exception during connection
 2018-05-18 09:05:27,763+01 ERROR 
 [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
 (EE-ManagedThreadFactory-engineScheduled-Thread-12) [294c1528] Unable
 to RefreshCapabilities: UnknownHostException: ovirt
 2018-05-18 09:05:27,766+01 ERROR [org.ovirt.engine.core.vdsbrok
 er.vdsbroker.GetCapabilitiesAsyncVDSCommand]
 (EE-ManagedThreadFactory-engineScheduled-Thread-12) [294c1528] Command
 'GetCapabilitiesAsyncVDSCommand(HostName = ovirt,
 VdsIdAndVdsVDSCommandParametersBase:{hostId='80fed076-1789-4e8e-bbd9-cfde1b0faea2',
 vds='Host[ovirt,80fed076-1789-4e8e-bbd9-cfde1b0faea2]'})' execution
 failed: java.net.UnknownHostException: ovirt
 2018-05-18 09:05:27,786+01 ERROR [org.ovirt.engine.core.dal.dbb
 roker.auditloghandling.AuditLogDirector] 
 (EE-ManagedThreadFactory-engineScheduled-Thread-14)
 [294c1528] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt
 command GetCapabilitiesAsyncVDS failed: Connection issue ovirt
 2018-05-18 09:05:27,786+01 ERROR 
 [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
 (EE-ManagedThreadFactory-engineScheduled-Thread-14) [294c1528] Unable
 to RefreshCapabilities: VDSNetworkException: VDSGenericException:
 VDSNetworkException: Connection issue ovirt


 When the engine VM restarts from the shared storage your engine VM
 could not resolve 'ovirt' address and so the host becomes unresponsive at
 engine eyes.
 Is your DNS properly working? if not, please take care that
 hosted-engine-setup has an option for injecting a value into /etc/hosts on
 the engine VM for you.


>
> thank you.
>
> On 18 May 2018 at 08:35, Simone Tiraboschi 
> wrote:
>
>> Here engine.log got already rotated, we need the initial engine.log;
>> can you please look for that?
>>
>>
>> On Fri, May 18, 2018 at 9:34 AM, Sumit Bharadia <03ce...@gmail.com>
>> wrote:
>>
>>> attached engine.log from engine VM
>>>
>>> thank you.
>>>
>>> On 18 May 2018 at 08:10, Simone Tiraboschi 
>>> wrote:
>>>
 Hi,
 can you please attach the whole engine.log file?

 On Fri, May 18, 2018 at 8:43 AM, <03ce...@gmail.com> wrote:

> 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-status
> shows the engine status as up and is in good health, but I cannot 
> interact
> with host installed on engine VM.
>
> The host within engine VM shows it is in non-responsive state, not
> clear why and what caused it. I can ssh into the local engine VM and 
> the
> engine.log has below entries -
>
> 2018-05-17 11:03:57,739+01 ERROR [org.ovirt.engine.core.vdsbrok
> er.monitoring.VmDevicesMonitoring] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-78)
> [6768004b] Exception:: 
> org.springframework.dao.DataIntegrityViolationException:
> CallableStatementCallback; SQL [{call insertvmdevice(?, ?, ?, ?, ?, 
> ?, ?,
> ?, ?, ?, ?, ?, ?, ?)}]; ERROR: insert or update on table "vm_device"
> violates foreign key constraint "fk_vm_device_vm_static"
>   Detail: Key (vm_id)=(114581bb-7fef-4b08-8e3c-85dd5a9e680b) is
> not present in table "vm_static".
> ...
> ...