- Users - oVirt List Archives

ovirt node ng 4.3.0 rc1 and HCI single host problems
by Gianluca Cecchi 18 Jan '19

18 Jan '19

Let's start a new thread more focused on the subject I'm just testing deployment of HCI single host using oVirt Node NG CentOS 7 iso I was able to complete the gluster setup via cockpit with these modifications: 1) I wanted to check via ssh and found that files *key under /etc/ssh/ had too weak config so that ssh daemon didn't started after installation of node from iso changing to 600 and restarting the service was ok 2) I used a single disk configured as jbod, so I choose that option instead of the default proposed RAID6 But the playook failed with . . . PLAY [gluster_servers] ********************************************************* TASK [Create LVs with specified size for the VGs] ****************************** changed: [192.168.124.211] => (item={u'lv': u'gluster_thinpool_sdb', u'size': u'50GB', u'extent': u'100%FREE', u'vg': u'gluster_vg_sdb'}) PLAY RECAP ********************************************************************* 192.168.124.211 : ok=1 changed=1 unreachable=0 failed=0 Ignoring errors... Error: Section diskcount not found in the configuration file Reading inside the playbooks involved here: /usr/share/gdeploy/playbooks/auto_lvcreate_for_gluster.yml /usr/share/gdeploy/playbooks/vgcreate.yml and the snippet - name: Convert the logical volume lv: action=convert thinpool={{ item.vg }}/{{item.pool }} poolmetadata={{ item.vg }}/'metadata' poolmetadataspare=n vgname={{ item.vg }} disktype="{{disktype}}" diskcount="{{ diskcount }}" stripesize="{{stripesize}}" chunksize="{{ chunksize | default('') }}" snapshot_reserve="{{ snapshot_reserve }}" with_items: "{{ lvpools }}" ignore_errors: yes I simply edited the gdeploy.conf from the gui button adding this section under the [disktype] one " [diskcount] 1 " then clean lv/vg/pv and the gdeploy step completed successfully 3) at first stage of ansible deploy I have this failed command that seems not to prevent from completion but that I have not understood.. PLAY [gluster_servers] ********************************************************* TASK [Run a command in the shell] ********************************************** failed: [192.168.124.211] (item=vdsm-tool configure --force) => {"changed": true, "cmd": "vdsm-tool configure --force", "delta": "0:00:01.475528", "end": "2019-01-11 10:59:55.147601", "item": "vdsm-tool configure --force", "msg": "non-zero return code", "rc": 1, "start": "2019-01-11 10:59:53.672073", "stderr": "Traceback (most recent call last):\n File \"/usr/bin/vdsm-tool\", line 220, in main\n return tool_command[cmd][\"command\"](*args)\n File \"/usr/lib/python2.7/site-packages/vdsm/tool/__init__.py\", line 40, in wrapper\n func(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 143, in configure\n _configure(c)\n File \"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 90, in _configure\n getattr(module, 'configure', lambda: None)()\n File \"/usr/lib/python2.7/site-packages/vdsm/tool/configurators/bond_defaults.py\", line 39, in configure\n sysfs_options_mapper.dump_bonding_options()\n File \"/usr/lib/python2.7/site-packages/vdsm/network/link/bond/sysfs_options_mapper.py\", line 48, in dump_bonding_options\n with open(sysfs_options.BONDING_DEFAULTS, 'w') as f:\nIOError: [Errno 2] No such file or directory: '/var/run/vdsm/bonding-defaults.json'", "stderr_lines": ["Traceback (most recent call last):", " File \"/usr/bin/vdsm-tool\", line 220, in main", " return tool_command[cmd][\"command\"](*args)", " File \"/usr/lib/python2.7/site-packages/vdsm/tool/__init__.py\", line 40, in wrapper", " func(*args, **kwargs)", " File \"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 143, in configure", " _configure(c)", " File \"/usr/lib/python2.7/site-packages/vdsm/tool/configurator.py\", line 90, in _configure", " getattr(module, 'configure', lambda: None)()", " File \"/usr/lib/python2.7/site-packages/vdsm/tool/configurators/bond_defaults.py\", line 39, in configure", " sysfs_options_mapper.dump_bonding_options()", " File \"/usr/lib/python2.7/site-packages/vdsm/network/link/bond/sysfs_options_mapper.py\", line 48, in dump_bonding_options", " with open(sysfs_options.BONDING_DEFAULTS, 'w') as f:", "IOError: [Errno 2] No such file or directory: '/var/run/vdsm/bonding-defaults.json'"], "stdout": "\nChecking configuration status...\n\nabrt is already configured for vdsm\nlvm is configured for vdsm\nlibvirt is already configured for vdsm\nSUCCESS: ssl configured to true. No conflicts\nManual override for multipath.conf detected - preserving current configuration\nThis manual override for multipath.conf was based on downrevved template. You are strongly advised to contact your support representatives\n\nRunning configure...\nReconfiguration of abrt is done.\nReconfiguration of passwd is done.\nReconfiguration of libvirt is done.", "stdout_lines": ["", "Checking configuration status...", "", "abrt is already configured for vdsm", "lvm is configured for vdsm", "libvirt is already configured for vdsm", "SUCCESS: ssl configured to true. No conflicts", "Manual override for multipath.conf detected - preserving current configuration", "This manual override for multipath.conf was based on downrevved template. You are strongly advised to contact your support representatives", "", "Running configure...", "Reconfiguration of abrt is done.", "Reconfiguration of passwd is done.", "Reconfiguration of libvirt is done."]} to retry, use: --limit @/tmp/tmpQXe2el/shell_cmd.retry PLAY RECAP ********************************************************************* 192.168.124.211 : ok=0 changed=0 unreachable=0 failed=1 Would it be possible to save in some way the ansible playbook log even if it completes ok, without going directly to the "successful" page? Or is anyway stored in some location on disk of host? I then proceeded with Hosted Engine install/setup and 4) it fails here at final stages of the local vm engine setup during host activation: [ INFO ] TASK [oVirt.hosted-engine-setup : Set Engine public key as authorized key without validating the TLS/SSL certificates] [ INFO ] changed: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Ensure that the target datacenter is present] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Ensure that the target cluster is present in the target datacenter] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Enable GlusterFS at cluster level] [ INFO ] changed: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Set VLAN ID at datacenter level] [ INFO ] skipping: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Force host-deploy in offline mode] [ INFO ] changed: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Add host] [ INFO ] changed: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Wait for the host to be up] then after several minutes: [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": [{"address": "ov4301.localdomain.local", "affinity_labels": [], "auto_numa_status": "unknown", "certificate": {"organization": "localdomain.local", "subject": "O=localdomain.local,CN=ov4301.localdomain.local"}, "cluster": {"href": "/ovirt-engine/api/clusters/5e8fea14-158b-11e9-b2f0-00163e29b9f2", "id": "5e8fea14-158b-11e9-b2f0-00163e29b9f2"}, "comment": "", "cpu": {"speed": 0.0, "topology": {}}, "device_passthrough": {"enabled": false}, "devices": [], "external_network_provider_configurations": [], "external_status": "ok", "hardware_information": {"supported_rng_sources": []}, "hooks": [], "href": "/ovirt-engine/api/hosts/4202de75-75d3-4dcb-b128-2c4a1d257a15", "id": "4202de75-75d3-4dcb-b128-2c4a1d257a15", "katello_errata": [], "kdump_status": "unknown", "ksm": {"enabled": false}, "max_scheduling_memory": 0, "memory": 0, "name": "ov4301.localdomain.local", "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supported": false, "os": {"custom_kernel_cmdline": ""}, "permissions": [], "port": 54321, "power_management": {"automatic_pm_enabled": true, "enabled": false, "kdump_detection": true, "pm_proxies": []}, "protocol": "stomp", "se_linux": {}, "spm": {"priority": 5, "status": "none"}, "ssh": {"fingerprint": "SHA256:iqeQjdWCm15+xe74xEnswrgRJF7JBAWrvsjO/RaW8q8", "port": 22}, "statistics": [], "status": "install_failed", "storage_connection_extensions": [], "summary": {"total": 0}, "tags": [], "transparent_huge_pages": {"enabled": false}, "type": "ovirt_node", "unmanaged_networks": [], "update_available": false}]}, "attempts": 120, "changed": false} [ INFO ] TASK [oVirt.hosted-engine-setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : debug] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Set local_vm_disk_path] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Copy engine logs] [ INFO ] TASK [oVirt.hosted-engine-setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : debug] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} Going to see the log /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20190111113227-ov4301.localdomain.local-5d387e0d.log it seems the error is about ovirt-imageio-daemon 2019-01-11 11:32:26,893+0100 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 'ovirt-imageio-daemon.service'), rc=1 2019-01-11 11:32:26,894+0100 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 'ovirt-imageio-daemon.service') stdout: 2019-01-11 11:32:26,895+0100 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'ovirt-imageio-daemon.service') stderr: Job for ovirt-imageio-daemon.service failed because the control process exited with error code. See "systemctl status ovirt-imageio-daemon.service" and "journalctl -xe" for details. 2019-01-11 11:32:26,896+0100 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-PBFI2dyoDO/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-PBFI2dyoDO/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 175, in _start self.services.state('ovirt-imageio-daemon', True) File "/tmp/ovirt-PBFI2dyoDO/otopi-plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'ovirt-imageio-daemon' 2019-01-11 11:32:26,898+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed to start service 'ovirt-imageio-daemon' 2019-01-11 11:32:26,899+0100 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventEnd STAGE closeup METHOD otopi.plugins.ovirt_host_deploy.vdsm.packages.Plugin._start (odeploycons.packages.vdsm.started) The reason: [root@ov4301 ~]# systemctl status ovirt-imageio-daemon -l ● ovirt-imageio-daemon.service - oVirt ImageIO Daemon Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service; disabled; vendor preset: disabled) Active: failed (Result: start-limit) since Fri 2019-01-11 11:32:29 CET; 27min ago Process: 11625 ExecStart=/usr/bin/ovirt-imageio-daemon (code=exited, status=1/FAILURE) Main PID: 11625 (code=exited, status=1/FAILURE) Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: ovirt-imageio-daemon.service: main process exited, code=exited, status=1/FAILURE Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: Failed to start oVirt ImageIO Daemon. Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: Unit ovirt-imageio-daemon.service entered failed state. Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: ovirt-imageio-daemon.service failed. Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: ovirt-imageio-daemon.service holdoff time over, scheduling restart. Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: Stopped oVirt ImageIO Daemon. Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: start request repeated too quickly for ovirt-imageio-daemon.service Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: Failed to start oVirt ImageIO Daemon. Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: Unit ovirt-imageio-daemon.service entered failed state. Jan 11 11:32:29 ov4301.localdomain.local systemd[1]: ovirt-imageio-daemon.service failed. [root@ov4301 ~]# The file /var/log/ovirt-imageio-daemon/daemon.log contains 2019-01-11 10:28:30,191 INFO (MainThread) [server] Starting (pid=3702, version=1.4.6) 2019-01-11 10:28:30,229 ERROR (MainThread) [server] Service failed (remote_service=<ovirt_imageio_daemon.server.RemoteService object at 0x7fea9dc88050>, local_service=<ovirt_imageio_daemon.server.LocalService object at 0x7fea9ca24850>, control_service=None, running=True) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_imageio_daemon/server.py", line 58, in main start(config) File "/usr/lib/python2.7/site-packages/ovirt_imageio_daemon/server.py", line 99, in start control_service = ControlService(config) File "/usr/lib/python2.7/site-packages/ovirt_imageio_daemon/server.py", line 206, in __init__ config.tickets.socket, uhttp.UnixWSGIRequestHandler) File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__ self.server_bind() File "/usr/lib/python2.7/site-packages/ovirt_imageio_daemon/uhttp.py", line 79, in server_bind self.socket.bind(self.server_address) File "/usr/lib64/python2.7/socket.py", line 224, in meth return getattr(self._sock,name)(*args) error: [Errno 2] No such file or directory One potential problem I noticed is that on this host I setup eth0 with 192.168.122.x (for ovirtmgmt) and eth1 with 192.168.124.y (for gluster, even if only one host, but aiming at adding other 2 hosts in second step) and the libvirt network temporarily created for the local engine vm is also on 192.168.124.0 network..... 4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:b8:6b:3c brd ff:ff:ff:ff:ff:ff inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0 valid_lft forever preferred_lft forever 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:b8:6b:3c brd ff:ff:ff:ff:ff:ff I can change my gluster network of this env and re-test, but would it be possible to have the libvirt network configurable? It seems risky to have a fixed one... Can I go ahead from this failed hosted engine after understanding reason of ovirt-imageio-daemon failure or am I forced to scratch? Supposing I go to power down and then power on again this host, how can I retry without scratching? Gianluca

3 6

Problems uploading ISO
by jerry＠tom.com 18 Jan '19

18 Jan '19

I using ovirt-iso-uploader command to upload iso. but failed and giving me the following error.[root@ha ~]# engine-iso-uploader --verbose -i iso upload delta1.iso Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): DEBUG: API Vendor(None) API Version(4.2.0) DEBUG: id=029786a6-4686-44a1-a667-b948df945712 address=storage1 path=/iso Uploading, please wait... INFO: Start uploading delta1.iso ERROR: glfs_init failed: Success [root@ha ~]# ^C I've been looking for a possible solution but nothing works yet. Any guidance on this matter will be appreciate it. m1988m(a)tom.com

3 5

oVirt 4.3 hosted engine migration
by Maton, Brett 18 Jan '19

18 Jan '19

In the updated UI, it doesn't seem possible to migrate hosted engine from Compute -> Host -> Virtual Machines anymore, although there does appear to be a 'new' Cancel Migration button. It's handy to be able to migrate the hosted engine from this view, I normally manually migrate the hosted engine to another host before upgrading and it's nice to be able to do it all in the same area, rather than having to switch to the (all) virtual machines view and then back to hosts. Any chance this feature could be re-enabled? Regards, Brett

2 1

oVirt 4.3 RC2 test on single host HCI --> OK
by Gianluca Cecchi 18 Jan '19

18 Jan '19

Just tested what in subject on a vm (so it has been a nested env) configured with 2 disks: 1x60Gb for OS and 1x100Gb for gluster. Used node ng from ovirt-node-ng-installer-4.3.0-2019011608.el7.iso and almost all the problems had with RC1 here: https://www.mail-archive.com/users@ovirt.org/msg52870.html have gone solved. The hosted engine deploy completed successfully and I'm able to access engine web admin and see the VM and its storage domain and connect to console. The only persisting problem is that I choose JBOD in my disk config (because I have only one disk) and the deploy gives error about missing diskcount parameter in ansible playbook, so I have to edit the gdeploy conf file from the gui and add the section [diskcount] 1 after that all goes well. Good job guys! BTW: is it correct hat for data and vmstore I only have the volumes configured, while I have to manullay create storage domains? If I want to extend this initial configuration to 3 nodes, what would be the installation path to execute? Thanks, Gianluca

4 5

The admin portal ui should be more simplified
by flerxu＠hotmail.com 18 Jan '19

18 Jan '19

We have a rhv of 11 Datacerters, 11 clusters, 40 hosts and 300 vms. The 4 of us administrators are suffering from the new 4.2 UI lack of active area 。The manipulation logic also make us confused. A simple operation needs more clicks than before. Please just make the UI more simplified,

3 2

Use oVirt Node as virt-v2v server
by Vinícius Ferrão 17 Jan '19

17 Jan '19

Hello, I’m using virt-p2v tool to do some VM migrations from unsupported hypervisors and stumbled across the need of a virt-v2v dedicated server to handle conversions. My first action was: rpm -qa on oVirt Node and found virt-v2v already installed. So the natural ideia was to use oVirt Node as the conversion server, it already have everything needed: virt-v2v and the export domain. So why not? Well, it turns out it doesn’t work. After pointing to oVirt Node within virt-p2v tool, the conversion procedure hangs at the begging, requesting an username and password for libvirt that I’m unaware. And even if I was aware it is impossible to input the values since there’s no escape from the console to put the values nor any form on the GUI to do so. libguestfs: libvirt version = 4005000 (4.5.0) libguestfs: guest random name = guestfs-sf2i0jl3mmcxtwly libguestfs: connect to libvirt libguestfs: opening libvirt handle: URI = qemu:///system, auth = default+wrapper, flags = 0 libvirt needs authentication to connect to libvirt URI qemu:///system (see also: http://libvirt.org/auth.html http://libvirt.org/uri.html) Please enter your authentication name: Please enter your password: I eventually gave up and spun a VM with virt-v2v and the conversion is running. The question is: wasn’t a good ideia to use oVirt Node as the conversion server? Why it failed? I still have a lot of conversions to do, and if I can use the node installation it would be great. Thanks, Sent from my iPhone

1 0

V2V Proxmox to Ovirt
by Sebastian Antunez N. 17 Jan '19

17 Jan '19

Hello Guys Have 3 nodes with Proxmox and 23 Virtual Machines (Linux, Windows) and need migrate to Ovirt. I search information but ever show me is not supported. Any idea who I can migrate Proxmox to Ovirt? I can shutdown all VM of Proxmox. Regards Sebastian

4 3

Windows Virtual Machine
by Sebastian Antunez N. 17 Jan '19

17 Jan '19

Hello Guys When a VM Windows is created I install OVTools, drivers etc. and ever show me this messages. The latest guest agent needs to be installed and running on the guest. The version of Ovirt is 4.2. Any idea? Thanks Sebastian

2 1

VMs paused - unknown storage error - Stale file handle - distribute 2 - replica 3 volume with sharding
by Marco Lorenzo Crociani 17 Jan '19

17 Jan '19

Hi, I opened a bug on gluster because I have reading errors on files on a gluster volume: https://bugzilla.redhat.com/show_bug.cgi?id=1652548 The files are many of the VMs images of the oVirt DATA storage domain. oVirt pause the vms because unknown storage errors. It's impossibile to copy/clone, manage some snapshots of these vms. The errors on the low level are "stale file handle". Volume is distribute 2 replicate 3 with sharding. Should I open a bug also on oVirt? Gluster 3.12.15-1.el7 oVirt 4.2.6.4-1.el7 Regards, -- Marco Crociani

3 3

Re: Cannot Increase Hosted Engine VM Memory
by Douglas Duckworth 17 Jan '19

17 Jan '19

Sure, they're attached. In "first attempt" the error seems to be: 2019-01-17 07:49:24,795-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [680f82b3-7612-4d91-afdc-43937aa298a2] EVENT_ID: FAILED_HOT_SET_MEMORY_NOT_DIVIDABLE(2,048), Failed to hot plug memory to VM HostedEngine. Amount of added memory (4000MiB) is not dividable by 256MiB. Followed by: 2019-01-17 07:49:24,814-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-29) [26f5f3ed] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING 2019-01-17 07:49:24,815-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-29) [26f5f3ed] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. In "second attempt" I used values that are dividable by 256 MiB so that's no longer present. Though same error: 2019-01-17 07:56:59,795-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] START, SetAmountOfMemoryVDSCommand(HostName = ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu>, Params:{hostId='cdd5ffda-95c7-4ffa-ae40-be66f1d15c30', vmId='adf14389-1563-4b1a-9af6-4b40370a825b', memoryDevice='VmDevice:{id='VmDeviceId:{deviceId='7f7d97cc-c273-4033-af53-bc9033ea3abe', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='memory', type='MEMORY', specParams='[node=0, size=2048]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}', minAllocatedMem='6144'}), log id: 50873daa 2019-01-17 07:56:59,855-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] FINISH, SetAmountOfMemoryVDSCommand, log id: 50873daa 2019-01-17 07:56:59,862-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-22) [7059a48f] EVENT_ID: HOT_SET_MEMORY(2,039), Hotset memory: changed the amount of memory on VM HostedEngine from 4096 to 4096 2019-01-17 07:56:59,881-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-22) [28fd4c82] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING 2019-01-17 07:56:59,882-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-22) [28fd4c82] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. This message repeats throughout engine.log: 2019-01-17 07:55:43,270-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-89) [] EVENT_ID: VM_MEMORY_UNDER_GUARANTEED_VALUE(148), VM HostedEngine on host ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu> was guaranteed 8192 MB but currently has 4224 MB As you can see attached the host has plenty of memory. Thank you Simone! Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Thu, Jan 17, 2019 at 5:09 AM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com>> wrote: On Wed, Jan 16, 2019 at 8:22 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Sorry for accidental send. Anyway I try to increase physical memory however it won't go above 4096MB. The hypervisor has 64GB. Do I need to modify this value with Hosted Engine offline? No, it's not required. Can you please attach your engine.log for the relevant time frame? Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Wed, Jan 16, 2019 at 1:58 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Hello I am trying to increase Hosted Engine physical memory above 4GB Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_site_pri…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_communit…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGSXQVVPJJ2CR…<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archiv…>

1 0

Windows 10 VM Virtio Drivers
by Sebastian Antunez N. 17 Jan '19

17 Jan '19

Hello Guys In my enviroment Ovirt 4.2 when create a new VM with Windows 10, in the boot options menu, add the Floppy Disk for mount virtio driver but only show me sysprep. I check in my ISO Folder and show all vfd drivers for Windows and ISO but I can not add the drivers who floppy. This problem only is with Windows VM. Any idea because this is issue. Regards Sebastian

4 5

Cannot Increase Hosted Engine VM Memory
by Douglas Duckworth 17 Jan '19

17 Jan '19

Hello I am trying to increase Hosted Engine physical memory above 4GB Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690

2 2

migrate hosted-engine vm to another cluster?
by Douglas Duckworth 17 Jan '19

17 Jan '19

Hello I am trying to migrate my hosted-engine VM to another cluster in the same data center. Hosts in both clusters have the same logical networks and storage. Yet migrating the VM isn't an option. To get the hosted-engine VM on the other cluster I started the VM on host in that other cluster using "hosted-engine --vm-start." However HostedEngine still associated with old cluster as shown attached. So I cannot live migrate the VM. Does anyone know how to resolve? With other VMs one can shut them down then using the "Edit" option. Though that will not work for HostedEngine. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690

4 5

vGPU with NVIDIA M60 mdev_type not showing
by Josep Manel Andrés Moscardó 16 Jan '19

16 Jan '19

Hi all, I have a host with 2 M60 with the latest supported driver installed, and working as you can see: root@esxh-03 vdsm]# lsmod | grep vfio nvidia_vgpu_vfio 49475 0 nvidia 16633974 1 nvidia_vgpu_vfio vfio_mdev 12841 0 mdev 20336 2 vfio_mdev,nvidia_vgpu_vfio vfio_iommu_type1 22300 0 vfio 32656 3 vfio_mdev,nvidia_vgpu_vfio,vfio_iommu_type1 [root@esxh-03 vdsm]# nvidia-smi Mon Jan 14 17:39:30 2019 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 410.91 Driver Version: 410.91 CUDA Version: N/A | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 Tesla M60 Off | 00000000:05:00.0 Off | Off | | 16% 27C P0 41W / 120W | 14MiB / 8191MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 1 Tesla M60 Off | 00000000:06:00.0 Off | Off | | 17% 24C P0 39W / 120W | 14MiB / 8191MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 2 Tesla M60 Off | 00000000:84:00.0 Off | Off | | 15% 28C P0 41W / 120W | 14MiB / 8191MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 3 Tesla M60 Off | 00000000:85:00.0 Off | Off | | 16% 25C P0 40W / 120W | 14MiB / 8191MiB | 0% Default | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | No running processes found | +-----------------------------------------------------------------------------+ But the issue is that when I do : # vdsm-client Host hostdevListByCaps I don't see any "mdev" device. Also the directory /sys/class/mdev_bus is not existing. Am I missing something ? Cheers.

2 4

[ANN] oVirt 4.3.0 Second Release Candidate is now available for testing
by Sandro Bonazzola 16 Jan '19

16 Jan '19

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 4.3.0, as of January 16th, 2018 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first release candidate of the 4.3.0 version. This release brings more than 130 enhancements and more than 440 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * OVA export / import of Templates * Full support for live migration of High Performance VMs * Microsoft Failover clustering support (SCSI Persistent Reservation) for Direct LUN disks * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * Support of Neutron from RDO OpenStack 13 as external network provider * Support of using Skydive from RDO OpenStack 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 * New metrics support using rsyslog instead of fluentd This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for both CentOS 7 and Fedora 28 (tech preview). - oVirt Node NG is already available for both CentOS 7 and Fedora 28 (tech preview). Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Disk full
by suporte＠logicworks.pt 16 Jan '19

16 Jan '19

Hi, I have a all in one intallation with 2 glusters volumes. The disk of one VM filled up the brick, which is a partition. That partition has 0% free disk space. I moved the disk of that VM to the other gluster volume, the VM is working with the disk on the other gluster volume. When I move the disk, it didn't delete it from the brick, the engine keeps complaining that there is no more disk space on that volume. What can I do? Is there a way to prevent this in the future? Many thanks José -- Jose Ferradeira http://www.logicworks.pt

2 8

[Call for Testing] oVirt 4.3.0
by Sandro Bonazzola 15 Jan '19

15 Jan '19

Hi, we are planning to release a 4.3.0 RC2 tomorrow morning, January 16th 2019. We have a scheduled final release for oVirt 4.3.0 on January 29th: this is the time when testing is most effective to ensure the release will be as much stable as possible. Please join us testing the RC2 release this week and reporting issues to https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt Please remember this is still pre-release material, we recommend not installing it on production environments yet. Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Ansible and SHE deployment
by Vrgotic, Marko 15 Jan '19

15 Jan '19

Dear oVirt team, I would like to ask you help in get some general guidelines, do’s & don’ts in deploying complete oVirt environment using Ansible. The first Production deployment I made was done manual: 12 Hypervsiors – all exact same HW Brand and Specs 3/12 used for HA Env for SHE oVirt version 4.2.1 (now we are at 4.2.7) 4Gluster nodes, managed externally of oVirt This is environment I would like to convert into deployable by Ansible Atm, I am working on second Production env, for Eng/Dev department, and I want to go all way Ansible. I am aware of your playbooks, and location on github, but what I want to ask is an advice on how to approach using them: The second Env will have: 7Hypervisors different specs / all provisioned using Foreman oVirt version, latest 4.2.x at that point. 3/7 providing HA for SHE engine Storage used is to be NetApp. Please let me know how to proceed with modifying Ansible playbooks and what should be the recommended executing order, and what to look for? Also, If you need additional info, I will be happy to provide. Kind regards, Marko Vrgotic

2 2

Is it possible to migrate self hosted engine to bare metal?
by Abhishek Sahni 15 Jan '19

15 Jan '19

Hello Everyone, Do we have some steps where we can migrate self hosted engine to separate bare metal machine. I do have a recent backup of DB from the self hosted engine? -- ABHISHEK SAHNI Mob : +91-990-701-5143

3 2

Import existing storage domain into new server
by michael＠wanderingmad.com 15 Jan '19

15 Jan '19

I had original ovirt-engine that had stuck tasks and just had storage issues. I decided to load a new engine appliance and import existing servers and VMs into new engine. This actually worked perfect until I went to import the storage domain into new engine, which has failed. I was unable to move the domain to maintenance mode or anything from the old engine. Any way to force import? Error messages / logs: Failed to attach Storage Domains to Data Center Default. (User: admin@internal-authz) (in GUI log) engine.log: 2019-01-13 16:31:27,973-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler8) [176267b0] START, GlusterVolumesListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, GlusterVolumesListVDSParameters:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 2e7162ed 2019-01-13 16:31:28,204-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,205-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.14:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,206-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.12:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,208-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,209-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.14:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,221-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.12:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,232-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler8) [176267b0] FINISH, GlusterVolumesListVDSCommand, return: {7add3797-9b03-433c-aa1a-90ad7c5ac280=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@4205765f, fe0c3620-6a33-48fa-98b7-847ad76edaba=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@40fccb}, log id: 2e7162ed 2019-01-13 16:31:37,612-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterTasksListVDSCommand] (DefaultQuartzScheduler10) [2876ae97] START, GlusterTasksListVDSCommand(HostName = daedalus.redforest.wanderingmad.com, VdsIdVDSCommandParametersBase:{hostId='b79fe49c-761f-4710-adf4-8fa6d1143dae'}), log id: 30c3bd7c 2019-01-13 16:31:37,863-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterTasksListVDSCommand] (DefaultQuartzScheduler10) [2876ae97] FINISH, GlusterTasksListVDSCommand, return: [], log id: 30c3bd7c 2019-01-13 16:31:43,248-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] START, GlusterServersListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, VdsIdVDSCommandParametersBase:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 7f890a8 2019-01-13 16:31:43,705-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] FINISH, GlusterServersListVDSCommand, return: [10.100.50.12/24:CONNECTED, icarus.redforest.wanderingmad.com:CONNECTED, daedalus.redforest.wanderingmad.com:CONNECTED], log id: 7f890a8 2019-01-13 16:31:43,708-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] START, GlusterVolumesListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, GlusterVolumesListVDSParameters:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 50f59aca 2019-01-13 16:31:43,943-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,944-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.14:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,945-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.12:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,947-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,948-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.14:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,949-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.12:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,949-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] FINISH, GlusterVolumesListVDSCommand, return: {7add3797-9b03-433c-aa1a-90ad7c5ac280=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@4205765f, fe0c3620-6a33-48fa-98b7-847ad76edaba=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@40fccb}, log id: 50f59aca 2019-01-13 16:31:58,987-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] START, GlusterServersListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, VdsIdVDSCommandParametersBase:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 512ef5c0 2019-01-13 16:31:59,518-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] FINISH, GlusterServersListVDSCommand, return: [10.100.50.12/24:CONNECTED, icarus.redforest.wanderingmad.com:CONNECTED, daedalus.redforest.wanderingmad.com:CONNECTED], log id: 512ef5c0 2019-01-13 16:31:59,521-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] START, GlusterVolumesListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, GlusterVolumesListVDSParameters:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 2de38416 2019-01-13 16:31:59,773-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,774-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.14:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,775-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.12:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,776-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,777-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.14:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,778-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.12:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,778-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] FINISH, GlusterVolumesListVDSCommand, return: {7add3797-9b03-433c-aa1a-90ad7c5ac280=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@4205765f, fe0c3620-6a33-48fa-98b7-847ad76edaba=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@40fccb}, log id: 2de38416 and of course, none of the gluster hosts is set as the SPM

2 2

unable to create templates or upload files
by michael＠wanderingmad.com 15 Jan '19

15 Jan '19

ovirt stopped accepting new deployments or uploading ISOs, they just stay as locked disks. I checked ovirt-engine log and see constant errors like below: ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-2) [] OAuthException access_denied: Cannot authenticate user 'admin@N/A': No valid profile found in credentials.. I checked the ovn provider in the admin portal and it's set correctly to "admin@internal" for the ovn provider

2 1

External private ova / image repository
by Leo David 15 Jan '19

15 Jan '19

Hello Everyone, I am not sure what would it be the pieces needed to have an external repo that I can manage and use at the client site for downloading customized templates. ie: how an external docker repo works Any ideeas on this ? Thank you ! Have a nice day, Leo

1 1

oVirt Node install - kickstart postintall
by jeanbaptiste＠nfrance.com 14 Jan '19

14 Jan '19

Hello everybody, Since days, I'm trying to install oVirt (via Foreman) in network mode (TFTP net install). All is great, but I want to make some actions in postinstall (%post). Some actions are relatated to /etc/sysconfig/network-interfaces and another action is related to root authorized_keys. When I try to add pub-key to a created authorized_keys for root, I work (verified into anaconda. But after installation and anaconda reboot, I've noticed all my %post actions in /(root) are discared. After reboot, there is nothing in /root/.ssh for example. Whereas, in /etc, all my modications are preserved. I thought to a Selinux relative issue, but It is not relative to Selinux I miss something. Please can you help to understand how oVirt install / partition work ? thanks for all

2 1

Ovirt 4.3 / New Install / NFS (broken)
by Devin Acosta 14 Jan '19

14 Jan '19

I installed the latest 4.3 release candidate and tried to add an NFS mount to the Data Center, and it errors in the GUI with “Error while executing action New NFS Storage Domain: Invalid parameter”, then in the vdsm.log I see it is passing “block_size=None”. Does this regardless if NFS v3 or v4. InvalidParameterException: Invalid parameter: 'block_size=None' 2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] START createStorageDomain(storageType=1, sdUUID=u'b30c64c4-4b1f-4ebf-828b-e54c330ae84c', domainName=u'nfsdata', typeSpecificArg=u'192.168.19.155:/data/data', domClass=1, domVersion=u'4', block_size=None, max_hosts=2000, options=None) from=::ffff:192.168.19.178,51042, flow_id=67743df7, task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:48) 2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] FINISH createStorageDomain error=Invalid parameter: 'block_size=None' from=::ffff:192.168.19.178,51042, flow_id=67743df7, task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:52) 2019-01-12 20:37:58,241-0700 ERROR (jsonrpc/7) [storage.TaskManager.Task] (Task='ad82f581-9638-48f1-bcd9-669b9809b34a') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in createStorageDomain File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2583, in createStorageDomain alignment = clusterlock.alignment(block_size, max_hosts) File "/usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py", line 661, in alignment raise se.InvalidParameterException('block_size', block_size) InvalidParameterException: Invalid parameter: 'block_size=None' 2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [storage.TaskManager.Task] (Task='ad82f581-9638-48f1-bcd9-669b9809b34a') aborting: Task is aborted: u"Invalid parameter: 'block_size=None'" - code 100 (task:1181) 2019-01-12 20:37:58,242-0700 ERROR (jsonrpc/7) [storage.Dispatcher] FINISH createStorageDomain error=Invalid parameter: 'block_size=None' (dispatcher:81) 2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call StorageDomain.create failed (error 1000) in 0.00 seconds (__init__:312) 2019-01-12 20:37:58,541-0700 INFO (jsonrpc/1) [vdsm.api] START disconnectStorageServer(domType=1, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'tpgt': u'1', u'id': u'db7d16c8-7497-42db-8a75-81cb7f9d3350', u'connection': u'192.168.19.155:/data/data', u'iqn': u'', u'user': u'', u'ipv6_enabled': u'false', u'protocol_version': u'auto', u'password': '********', u'port': u''}], options=None) from=::ffff:192.168.19.178,51042, flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c, task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:48) 2019-01-12 20:37:58,542-0700 INFO (jsonrpc/1) [storage.Mount] unmounting /rhev/data-center/mnt/192.168.19.155:_data_data (mount:212) 2019-01-12 20:37:59,087-0700 INFO (jsonrpc/1) [vdsm.api] FINISH disconnectStorageServer return={'statuslist': [{'status': 0, 'id': u'db7d16c8-7497-42db-8a75-81cb7f9d3350'}]} from=::ffff:192.168.19.178,51042, flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c, task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:54) 2019-01-12 20:37:59,089-0700 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call StoragePool.disconnectStorageServer succeeded in 0.55 seconds (__init__:312) Devin Acosta

6 9

Trunk VLAN Ovirt 4.2
by Sebastian Antunez N. 14 Jan '19

14 Jan '19

Hello Guys Have a lab with 6 nodes Ovirt 4.2. All nodes have 4 nic 1GB and two nic are for Management and and I will assign two nic in bonding for VM traffic My problem is the following. The switch Cisco have 2 VLAN (56 and 57) and I need to be able to create a new network with the two vlan but I am not clear how to make it so that the vlan go through this created network. I have read that I must create a network with vlan 56 for example and assign it an IP, and then create the network with vlan 57 and assign it an IP and later assign it to bonding. Is what I indicate or should another process be correct? Thanks for the help. Sebastian

2 1