[ovirt-users] Re: New install -- Error

Digging further into the logs... I can see that the engine VM is up. When I logged into the ovirt web ui, I saw the following logs : 1/2/198:18:05 PM Host host1.xxx.xxx became non responsive. Fence operation skipped as the system is still initializing and this is not a host where hosted engine was running on previously. Jan 2, 2019, 8:18:06 PM Fencing failed on Storage Pool Manager host1.xxx.xxx for Data Center dc1. Setting status to Non-Operational. After this in the setup logs, I can see. 2019-01-02 20:18:43,043+0530 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 ignored: [localhost]: FAILED! => {"changed": false, "deprecations": [{"msg": "The 'ovirt_vms' module is being renamed 'ovirt_vm'", "version": 2.8}], "msg": "Not possible to control VM, if it's in 'unknown' status"} Regards K Anand On 02-01-2019 15:04, K Anand wrote: > > Hi, > > I am trying to install a fresh hosted engine setup on FC. > > I have done a fresh install of Centos 7 minimal. > > Then I ran the hosted-engine --deploy....I got the following error : > > 2019-01-02 20:18:37,029+0530 INFO > otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:100 TASK [Check for the local bootstrap VM] > 2019-01-02 20:18:39,535+0530 INFO > otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:100 ok: [localhost] > 2019-01-02 20:18:40,838+0530 INFO > otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:100 TASK [Make the engine aware that > the external VM is stopped] > 2019-01-02 20:18:42,943+0530 DEBUG > otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:94 {u'_ansible_parsed': True, > u'deprecations': [{u'msg': u"The 'ovirt_vms' module is being renamed > 'ovirt_vm'", u'version': 2.8}], u'_ansible_no_log': False, > u'changed': False, u'invocation': {u'module_args': {u'comment': None, > u'affinity_label_mappings': [], u'soundcard_enabled': None, > u'cpu_pinning': None, u'force': False, u'cloud_init_nics': [], > u'placement_policy': None, u'boot_menu': None, u'xen': None, > u'custom_compatibility_version': None, u'template_version': None, > u'cluster': None, u'fetch_nested': False, u'io_threads': None, > u'timezone': None, u'watchdog': None, u'memory_max': None, u'id': > u'4906279b-9721-40e2-a6ac-7774ab6fd643', u'cpu_sockets': None, > u'high_availability': None, u'storage_domain': None, > u'domain_mappings': [], u'high_availability_priority': None, u'nics': > [], u'custom_properties': None, u'disk_format': u'cow', u'sysprep': > None, u'cpu_cores': None, u'ballooning_enabled': None, u'cpu_mode': > None, u'state': u'stopped', u'memory_guaranteed': None, u'vmware': > None, u'template': None, u'memory': None, u'cd_iso': None, > u'clone_permissions': False, u'type': None, u'initrd_path': None, > u'smartcard_enabled': None, u'lease': None, u'rng_device': None, > u'vnic_profile_mappings': [], u'stateless': None, u'lun_mappings': > [], u'clone': False, u'kvm': None, u'boot_devices': None, > u'nested_attributes': [], u'usb_support': None, u'reassign_bad_macs': > None, u'sso': None, u'role_mappings': [], u'serial_policy': None, > u'cpu_threads': None, u'quota_id': None, u'numa_nodes': [], > u'ticket': None, u'delete_protected': None, u'cloud_init_persist': > False, u'wait': True, u'use_latest_template_version': None, > u'affinity_group_mappings': [], u'operating_system': None, > u'serial_policy_value': None, u'name': None, u'kernel_path': None, > u'cloud_init': None, u'disks': [], u'poll_interval': 3, u'host': > None, u'numa_tune_mode': None, u'instance_type': None, > u'host_devices': None, u'graphical_console': None, u'timeout': 180, > u'description': None, u'cluster_mappings': [], u'kernel_params': > None, u'serial_console': None, u'allow_partial_import': None, > u'cpu_shares': None}}, u'msg': u"Not possible to control VM, if it's > in 'unknown' status"} > 2019-01-02 20:18:43,043+0530 DEBUG > otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:94 ignored: [localhost]: FAILED! => > {"changed": false, "deprecations": [{"msg": "The 'ovirt_vms' module > is being renamed 'ovirt_vm'", "version": 2.8}], "msg": "Not possible > to control VM, if it's in 'unknown' status"} > 2019-01-02 20:18:44,146+0530 DEBUG > otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:94 TASK [debug] > > Any clues ? > > -- > Regards > > K Anand > > ======================================== This Message has been scanned by SAIL CMO MAIL SECURITY ======================================== ======================================== This Message has been scanned by SAIL CMO MAIL SECURITY ======================================== _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/Q3YRRFO4W6O...