Deploy host engine error: The task includes an option with an undefined variable
by Angel R. Gonzalez
Hi all!
I'm deploying a host engine in a host node with a 8x Intel(R) Xeon(R)
CPU E5410 @ 2.33GHz.
The deploy proccess show the next message
> [INFO]TASK [ovirt.hosted_engine_setup : Convert CPU model name]
> [ERROR]fatal: [localhost]: FAILED! => {"msg": "The task includes an
> option with an undefined variable. The error was: 'dict object' has no
> attribute ''\n\nThe error appears to be in
> '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml':
> line 105, column 15, but may\nbe elsewhere in the file depending on
> the exact syntax problem.\n\nThe offending line appears to be:\n\n -
> debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v'
> shorthand syntax and YAML in this task. Only one syntax may be used.\n"}
The ansible deploy script in his 105 line show:
> - name: Parse server CPU list
> set_fact:
> server_cpu_dict: "{{ server_cpu_dict |
> combine({item.split(':')[1]: item.split(':')[3]}) }}"
> with_items: >-
> {{
> server_cpu_list.json['values']['system_option_value'][0]['value'].split(';
> ')|list|difference(['']) }}
> - debug: var=server_cpu_dict
I don´t know ansible and i don't how to resolve this issue. Any idea?
Thanks in advance,
Ángel González.
3 years, 8 months
Unassigned hosts
by Nardus Geldenhuys
Hi oVirt land
Hope you are well. Got a bit of an issue, actually a big issue. We had some
sort of dip of some sort. All the VM's is still running, but some of the
hosts is show "Unassigned" or "NonResponsive". So all the hosts was showing
UP and was fine before our dip. So I did increase vdsHeartbeatInSecond to
240, no luck.
I still get a timeout on the engine lock even thou I can connect to that
host from the engine using nc to test to port 54321. I also did restart
vdsmd and also rebooted the host with no luck.
nc -v someserver 54321
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to 172.40.2.172:54321.
2020-08-05 20:20:34,256+02 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engineScheduled-Thread-70) [] EVENT_ID:
VDS_BROKER_COMMAND_FAILURE(10,802), VDSM someserver command Get Host
Capabilities failed: Message timeout which can be caused by communication
issues
Any troubleshoot ideas will be gladly appreciated.
Regards
Nar
3 years, 8 months
Re: [ovirt-devel] Error during deployment of self hosted engine oVirt 4.4
by Michal Skrivanek
> On 6 Aug 2020, at 00:41, i iordanov <iiordanov(a)gmail.com> wrote:
>
> Hi Michal,
>
> I dug down enough to see that I could alter the option that specifies the supported CPUs in the database. What would have helped me is a diff of what was removed. Ultimately, I didn't have enough time to dig for the diff, but if you know where it can be found it may be of use for other people that need to use a Penryn based server.
Hi,
the diff is right there, the option value for 4.2 cluster still has it. so you just need that piece (penryn definition) to copy&paste into the 4.4 entry(i think the numbers are then duplicated, but it shouldn’t really matter, cpu name is the "key”)
Thanks,
michal
>
> I was able to swap two systems at my place and get a Nehalem one to use with oVirt, but if I get a chance I may try to revert to the older one since it's a bit more convenient for me to use. I would certainly try updating the DB if I could get the diff where you guys removed the line from the DB seed files.
>
> Cheers and thanks!
> iordan
>
> On Tue, Aug 4, 2020 at 4:46 AM Michal Skrivanek <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> wrote:
>
>
>> On 4 Aug 2020, at 06:10, i iordanov <iiordanov(a)gmail.com <mailto:iiordanov@gmail.com>> wrote:
>>
>> It seems the issue stems from cpu type being empty.
>>
>> 'cpu': {'architecture': 'undefined', 'type': ''}
>>
>> 2020-08-03 23:31:39,888-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 cluster_facts: {'changed': False, 'ansible_facts': {'ovirt_clusters': [{'href': '/ovirt-engine/api/clusters/0eb77d38-d5fe-11ea-8808-00163e42a94a', 'comment': '', 'description': 'The default server cluster', 'id': '0eb77d38-d5fe-11ea-8808-00163e42a94a', 'name': 'Default', 'affinity_groups': [], 'ballooning_enabled': True, 'bios_type': 'cluster_default', 'cpu': {'architecture': 'undefined', 'type': ''}, 'cpu_profiles': [], 'data_center': {'href': '/ovirt-engine/api/datacenters/0ea3b60e-d5fe-11ea-a87c-00163e42a94a', 'id': '0ea3b60e-d5fe-11ea-a87c-00163e42a94a'}, 'enabled_features': [], 'error_handling': {'on_error': 'migrate'}, 'external_network_providers': [], 'fencing_policy': {'enabled': True, 'skip_if_connectivity_broken': {'enabled': False, 'threshold': 50}, 'skip_if_gluster_bricks_up': False, 'skip_if_gluster_quorum_not_met': False, 'skip_if_sd_active': {'enabled': False}}, 'firewall_type': 'firewalld', 'gluster_hooks': [], 'gluster_service': False, 'gluster_volumes': [], 'ha_reservation': False, 'ksm': {'enabled': True, 'merge_across_nodes': True}, 'log_max_memory_used_threshold': 95, 'log_max_memory_used_threshold_type': 'percentage', 'mac_pool': {'href': '/ovirt-engine/api/macpools/58ca604b-017d-0374-0220-00000000014e', 'id': '58ca604b-017d-0374-0220-00000000014e'}, 'memory_policy': {'over_commit': {'percent': 100}, 'transparent_huge_pages': {'enabled': True}}, 'migration': {'auto_converge': 'inherit', 'bandwidth': {'assignment_method': 'auto'}, 'compressed': 'inherit', 'encrypted': 'inherit', 'policy': {'id': '80554327-0569-496b-bdeb-fcbbf52b827b'}}, 'network_filters': [], 'networks': [], 'permissions': [], 'required_rng_sources': ['urandom'], 'scheduling_policy': {'href': '/ovirt-engine/api/schedulingpolicies/b4ed2332-a7ac-4d5f-9596-99a439cb2812', 'id': 'b4ed2332-a7ac-4d5f-9596-99a439cb2812'}, 'switch_type': 'legacy', 'threads_as_cores': False, 'trusted_service': False, 'tunnel_migration': False, 'version': {'major': 4, 'minor': 4}, 'virt_service': True, 'vnc_encryption': False}]}, 'deprecations': [{'msg': "The 'ovirt_cluster_facts' module has been renamed to 'ovirt_cluster_info', and the renamed one no longer returns ansible_facts", 'version': '2.13'}], 'failed': False}
>>
>> Perhaps this Penryn series CPU is too old for this oVirt installation...
>
> Yes, we dropped Penryn from supported CPU list i 4.3. You could probably stil make it run but it would need messing with engine’s db, adding back Nehalem entry to ServerCPUList(e.g. from 4.2 cluster version line) and resume the deployment somehow.
>
>>
>> iordan
>>
>> On Mon, Aug 3, 2020 at 11:54 PM i iordanov <iiordanov(a)gmail.com <mailto:iiordanov@gmail.com>> wrote:
>> Hi guys,
>>
>> I am trying to install oVirt 4.4 for testing of the aSPICE and Opaque Android clients and tried to follow this slightly outdated doc:
>>
>> https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_eng... <https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_eng...>
>>
>> to deploy an all-in-one self-hosted engine using the command-line.
>>
>> I started with a clean CentOS 8 installation, set up an NFS server and tested that mounts work from the local host and other hosts, opened all ports with firewalld to my LAN and localhost (but left firewalld enabled).
>>
>> During the run of
>> hosted-engine --deploy
>> I got the following error:
>>
>> 2020-08-03 23:31:51,426-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 TASK [ovirt.hosted_engine_setup : debug]
>> 2020-08-03 23:31:51,827-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 server_cpu_dict: {'Intel Nehalem Family': 'Nehalem', 'Secure Intel Nehalem Family': 'Nehalem,+sp
>> ec-ctrl,+ssbd,+md-clear', 'Intel Westmere Family': 'Westmere', 'Secure Intel Westmere Family': 'Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel SandyBridge Family': 'SandyBridge', 'Secure Intel SandyBridge Fa
>> mily': 'SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel IvyBridge Family': 'IvyBridge', 'Secure Intel IvyBridge Family': 'IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel Haswell Family': 'Haswell-noTSX
>> ', 'Secure Intel Haswell Family': 'Haswell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Broadwell Family': 'Broadwell-noTSX', 'Secure Intel Broadwell Family': 'Broadwell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Sk
>> ylake Client Family': 'Skylake-Client,-hle,-rtm', 'Secure Intel Skylake Client Family': 'Skylake-Client,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Skylake Server Family': 'Skylake-Server,-hle,-rtm', 'Secure I
>> ntel Skylake Server Family': 'Skylake-Server,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Cascadelake Server Family': 'Cascadelake-Server,-hle,-rtm,+arch-capabilities', 'Secure Intel Cascadelake Server Family':
>> 'Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities', 'AMD Opteron G4': 'Opteron_G4', 'AMD Opteron G5': 'Opteron_G5', 'AMD EPYC': 'EPYC', 'Secure AMD EPYC': 'EPYC,+ibpb,+virt-ssbd', 'IB
>> M POWER8': 'POWER8', 'IBM POWER9': 'POWER9', 'IBM z114, z196': 'z196-base', 'IBM zBC12, zEC12': 'zEC12-base', 'IBM z13s, z13': 'z13-base', 'IBM z14': 'z14-base'}
>> 2020-08-03 23:31:52,128-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Convert CPU model name]
>> 2020-08-03 23:31:52,530-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': "The task includes an option with an undefined variable. The error was: 'dict object' ha
>> s no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column 15, but may\nbe elsewhere in th
>> e file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task
>> . Only one syntax may be used.\n", '_ansible_no_log': False}
>> 2020-08-03 23:31:52,630-0400 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable.
>> The error was: 'dict object' has no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column
>> 15, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shortha
>> nd syntax and YAML in this task. Only one syntax may be used.\n"}
>> 2020-08-03 23:31:52,931-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 PLAY RECAP [localhost] : ok: 35 changed: 5 unreachable: 0 skipped: 5 failed: 1
>> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:215 ansible-playbook rc: 2
>> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:222 ansible-playbook stdout:
>> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:225 ansible-playbook stderr:
>> 2020-08-03 23:31:53,033-0400 DEBUG otopi.context context._executeMethod:145 method exception
>> Traceback (most recent call last):
>> File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod
>> method['method']()
>> File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/target_vm.py", line 238, in _closeup
>> r = ah.run()
>> File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 229, in run
>> raise RuntimeError(_('Failed executing ansible-playbook'))
>> RuntimeError: Failed executing ansible-playbook
>> 2020-08-03 23:31:53,034-0400 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook
>>
>> On line 105 of the Ansible config file indicated, there is the following task:
>> - debug: var=server_cpu_dict
>>
>> However, here is a bit more of the file:
>> - name: Parse server CPU list
>> set_fact:
>> server_cpu_dict: "{{ server_cpu_dict | combine({item.split(':')[1]: item.split(':')[3]}) }}"
>> with_items: >-
>> {{ server_cpu_list.json['values']['system_option_value'][0]['value'].split('; ')|list|difference(['']) }}
>> - debug: var=server_cpu_dict
>> - name: Convert CPU model name
>> set_fact:
>> cluster_cpu_model: "{{ server_cpu_dict[cluster_cpu.type] }}"
>> - debug: var=cluster_cpu_model
>> - name: Parse emulated_machine
>> set_fact:
>> emulated_machine:
>> emulated_machine_list.json['values']['system_option_value'][0]['value'].replace(
>> '[','').replace(']','').split(', ')|first
>>
>> Exact version of the package that contains the file in question:
>>
>> ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch
>>
>> Many thanks for your attention! Please cc me when you reply, as I may not be monitoring the mailing list actively. Happy to provide any other information.
>>
>> In case it's relevant, the CPU of the machine:
>>
>> # cat /proc/cpuinfo
>> processor : 0
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Xeon(R) CPU X5460 @ 3.16GHz
>> stepping : 6
>> microcode : 0x60f
>> cpu MHz : 2703.129
>> cache size : 6144 KB
>> physical id : 0
>> siblings : 4
>> core id : 0
>> cpu cores : 4
>> apicid : 0
>> initial apicid : 0
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 10
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm pti tpr_shadow vnmi flexpriority dtherm
>> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
>> bogomips : 6318.15
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 38 bits physical, 48 bits virtual
>> power management:
>>
>> Sincerely,
>> iordan
>>
>> --
>> The conscious mind has only one thread of execution.
>>
>>
>> --
>> The conscious mind has only one thread of execution.
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org <mailto:devel@ovirt.org>
>> To unsubscribe send an email to devel-leave(a)ovirt.org <mailto:devel-leave@ovirt.org>
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html>
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/>
>> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4CUXHTZTTAW... <https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4CUXHTZTTAW...>
>
>
> --
> The conscious mind has only one thread of execution.
3 years, 8 months
oVirt 4.4.1 HCI single server deployment failed nested-kvm
by wodel youchi
Hi,
I am using these versions for my test :
- ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm
- ovirt-node-ng-installer-4.4.1-2020072310.el8.iso
A single HCI server using nested KVM.
The gluster part works now without error, but when I click the
hosted-engine deployment button I get :
*System data could not be retrieved!*
*No valid network interface has been found *
* If you are using Bonds or VLANs Use the following naming conventions: *
- VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128,
enp3s0.50)
- Bond interfaces: bond*number* (for example, bond0, bond1)
- VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50,
bond1.128)
* Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad
* Networking teaming is not supported and will cause errors
From this log file I get :
cat ovirt-hosted-engine-setup-ansible-get_network_interfaces-xxxxxxxx.log
2020-07-29 15:27:09,246+0100 DEBUG var changed: host "localhost" var
"otopi_host_net" type "<class 'list'>" value: "[
"enp1s0",
"enp2s0"
]"
2020-07-29 15:27:09,246+0100 INFO ansible ok {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng
ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost',
'ansible_task': 'Filter unsupported interface types', 'task_duration
': 0}
2020-07-29 15:27:09,246+0100 DEBUG ansible on_any args
<ansible.executor.task_result.TaskResult object at 0x7fe804bc5940> kwargs
2020-07-29 15:27:09,514+0100 INFO ansible task start {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho
sted-engine-setup/ansible/trigger_role.yml', 'ansible_task':
'ovirt.hosted_engine_setup : debug'}
2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args TASK:
ovirt.hosted_engine_setup : debug kwargs is_conditional:False
2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args localhostTASK:
ovirt.hosted_engine_setup : debug kwargs
2020-07-29 15:27:09,792+0100 INFO ansible ok {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng
ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost',
'ansible_task': '', 'task_duration': 0}
2020-07-29 15:27:09,793+0100 DEBUG ansible on_any args
<ansible.executor.task_result.TaskResult object at 0x7fe804cb45f8> kwargs
2020-07-29 15:27:10,059+0100 INFO ansible task start {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho
sted-engine-setup/ansible/trigger_role.yml', 'ansible_task':
'ovirt.hosted_engine_setup : Failed if only teaming devices are availible
'}
2020-07-29 15:27:10,059+0100 DEBUG ansible on_any args TASK:
ovirt.hosted_engine_setup : Failed if only teaming devices are availible
kwargs is_conditional:False
2020-07-29 15:27:10,060+0100 DEBUG ansible on_any args localhostTASK:
ovirt.hosted_engine_setup : Failed if only teaming devices are a
vailible kwargs
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"ansible_play_hosts" type "<class 'list'>" value: "[]"
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"ansible_play_batch" type "<class 'list'>" value: "[]"
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"play_hosts" type "<class 'list'>" value: "[]"
2020-07-29 15:27:10,376+0100 ERROR ansible failed {
"ansible_host": "localhost",
"ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
"ansible_result": {
"_ansible_no_log": false,
"msg": "The conditional check
*'(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The
error was: error while evaluating conditional
((otopi_host_net.ansible_facts.otopi_host_net | length == 0)): 'list
object' has no attribute 'ansible_facts'\n\nThe error appears to be in
'/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml':
line 29, column 13, *
but may\nbe elsewhere in the file depending on the exact syntax
problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_ho
st_net\n ^ here\n\nThere appears to be both 'k=v' shorthand
syntax and YAML in this task. Only one syntax may be used.\n"
},
"ansible_task": "Failed if only teaming devices are availible",
"ansible_type": "task",
"status": "FAILED",
"task_duration": 0
}
2020-07-29 15:27:10,377+0100 DEBUG ansible on_any args
<ansible.executor.task_result.TaskResult object at 0x7fe804c175c0> kwargs
ignor
e_errors:None
2020-07-29 15:27:10,378+0100 INFO ansible stats {
"ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
"ansible_playbook_duration": "00:15 Minutes",
"ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 16,
'failures': 1, 'unreachable': 0, 'changed': 1, 'skipped': 2
, 'rescued': 0, 'ignored': 0}}",
"ansible_type": "finish",
"status": "FAILED"
}
2020-07-29 15:27:10,378+0100 INFO SUMMARY:
Duration Task Name
-------- --------
[ < 1 sec ] Execute just a specific set of steps
[ 00:02 ] Force facts gathering
[ 00:01 ] Get all active network interfaces
[ < 1 sec ] Filter bonds with bad naming
[ < 1 sec ] Generate output list
[ 00:01 ] Collect interface types
[ < 1 sec ] Get list of Team devices
[ < 1 sec ] Filter unsupported interface types
[ FAILED ] Failed if only teaming devices are availible
2020-07-29 15:27:10,378+0100 DEBUG ansible on_any args
<ansible.executor.stats.AggregateStats object at 0x7fe8074bce80> kwargs
Regards.
3 years, 8 months
Setting Up oVirt + NFS Storage Issues
by Arden Shackelford
Hello!
Been looking to get setup with oVirt for a few weeks and had a chance the past week or so to attempt getting it all setup. Ended up doing a bit of troubleshooting but finally got to the point where the Cockpit setup prompts for me setting up the storage piece, for which I've opted for NFS (path of least resistance for now). However, I constantly run into this issue (pulled from the administration portal events page):
VDSM asgard.shackfam.net command CreateStorageDomainVDS failed: Could not initialize cluster lock: ()
This specifically shows up in the following task for the Ansible piece:
[ovirt.hosted_engine_setup : Add NFS storage domain]
When I browse the NFS share, I do see a file structure being created, which kind of confuses me based on the error provide in the Administration portal.
Any suggestions on what would be best steps forward at this point?
For reference, here's my setup:
1x oVirt Node
1x NFS server (storage01: NFS shares mainly managed by ZFS)
3 years, 8 months
4.2.8 and yum update
by carl langlois
Hi all,
I am in the process of upgrading our cluster to 4.3. But first i need to
update everything to 4.2.8 and update the os to the latest 7.x. I was able
to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But
when i tried to update the host yum update got broken gluster packages.
The current host that i'm trying to update is on 7.5. If i look at the
release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
this.
Any suggestions?.
Carl
3 years, 8 months
Re: VDSM can't see StoragePool
by Nardus Geldenhuys
Hi
Hope you are well. Did you find a solution for this? Think we have the same
type of issue.
Regards
Nar
3 years, 8 months
useful workaround for catch-22 situation with nic drivers and Windows
by i iordanov
Hello,
I just wanted to post a nice workaround I came up with in case it helps
anybody.
The reason I needed it is that in oVirt 4.4, it appears I am unable to
change the nic1 type when creating VMs (maybe that's a bug?) and I
necessarily end up with the default nic1 type which needs a virtio driver
in Windows which is obviously not present on a clean install. Also, since
there is no networking, it can't be downloaded. I did think of mounting a
USB stick via remote-viewer, but something is wonky there too - the USB
device selection menu item is grayed out, and no, it's not permissions.
So what i did was to create an .iso file with spice-guest-tools-latest.exe
in it and copy the resulting iso file to the ISO domain. Then, I was easily
able to attach the ISO to the Windows machine in question and install
spice-guest-tools, which made the network adapter work.
Quick snippet of how I created the .iso:
$ find test
test
test/spice-guest-tools-latest.exe
$ mkisofs -o spice-tools.iso test
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 116
Path table size(bytes): 10
Max brk space used 0
5124 extents written (10 MB)
Hope it helps somebody :).
Cheers!
iordan
--
The conscious mind has only one thread of execution.
3 years, 8 months
Resize partition cause oVirt installation failed
by hkexdong＠yahoo.com.hk
I've 2 x 512GB SSD. Purely for oVirt 4.4.1 (CentOS 8.2) installation.
Using auto partitioning will assign 800+ GB to root partition. I think that's too much so manually reduce it to 80 GB.
As there are 2 disks. I want to form RAID too. So, I manually change all the partitions from "LVM thin provisioning" to "RAID" (with RAID 1).
Eventually, cause the installation failed with a message "There was an error running the kickstart script at line ....."
If I don't make any change to the partitions. The installation success.
Is this a known issue? oVirt not allow resize partition and using Linux software RAID?
3 years, 8 months
