[ovirt-users] How can I set up a newly created virtual machine to use the qcow2 format disk by default?

[mask . zan]

How can I set up a newly created virtual machine to use the qcow2 format disk 
by default?
My storage configuration is glusterfs non-ovirt managed
___
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/AIB5DOJD3IWUXVXUHVJOTZVKDIXEUA4B/

[ovirt-users] Re: Storage Domain Ovirt 4.3 RC EPYC

[Darin Schmidt]

Seems the system is version locked? Looks like ovirt-engine 4.3.0.4 is
available and I have 4.3.0.2 installed. Should I disable the version lock?

[root@ovirt ~]# yum versionlock status
Loaded plugins: enabled_repos_upload, fastestmirror, langpacks,
package_upload, product-id, search-disabled-repos,
  : subscription-manager, vdsmupgrade, versionlock
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Loading mirror speeds from cached hostfile
 * base: mirror.cisp.com
 * epel: epel.mirror.constant.com
 * extras: repo1.ash.innoscale.net
 * ovirt-4.3: mirrors.ibiblio.org
 * ovirt-4.3-epel: epel.mirror.constant.com
 * updates: mirror.cisp.com
0:ovirt-engine-webadmin-portal-4.3.0.4-1.el7.*
0:ovirt-engine-tools-backup-4.3.0.4-1.el7.*
0:ovirt-engine-restapi-4.3.0.4-1.el7.*
0:ovirt-engine-dbscripts-4.3.0.4-1.el7.*
0:ovirt-engine-4.3.0.4-1.el7.*
0:ovirt-engine-backend-4.3.0.4-1.el7.*
0:ovirt-engine-tools-4.3.0.4-1.el7.*
versionlock status done
Uploading Enabled Repositories Report
Loaded plugins: fastestmirror, langpacks, product-id, subscription-manager,
  : versionlock
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Cannot upload enabled repos report, is this client registered?


On Thu, Jan 31, 2019 at 7:38 PM Darin Schmidt 
wrote:

> Same issue
>
> [root@ovirt ~]# rpm -qa|grep ovirt-engine-appliance
> ovirt-engine-appliance-4.3-20190131.1.el7.x86_64
>
> Error while executing action New Local Storage Domain: Storage format is
> unsupported
>
>
>
> On Thu, Jan 31, 2019 at 5:06 PM Greg Sheremeta 
> wrote:
>
>> Hi,
>>
>> On Thu, Jan 31, 2019 at 4:19 PM Darin Schmidt 
>> wrote:
>>
>>>
>>>
>>> Uncaught exception occurred. Please try reloading the page. Details:
>>> (TypeError) : Cannot read property 'Vg' of null
>>> Please have your administrator check the UI logs
>>>
>>
>> please attach ui.log
>>
>>
>>>
>>> Im trying to setup Ovirt 4.3 RC because its the only one that supports
>>> AMD EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB
>>> SSDs using mdadm and mounted it at /VM. I put the Host into maintenance,
>>> select Configure Local Storage, and it fails telling me:
>>> New Local Storage Domain: Storage format is unsupported
>>>
>>
>> We fixed this one this morning -- update your appliance to
>> ovirt-engine-appliance-4.3-20190131.1.el7.x86_64
>> Then redeploy and it should work.
>> https://bugzilla.redhat.com/show_bug.cgi?id=1669606
>>
>> Best wishes,
>> Greg
>>
>>
>>>
>>> I formatted the array to ext4. This is a self hosted system.  Anyone
>>> have any ideas?
>>>
>>> [root@ovirt VM]# uname -r
>>> 3.10.0-957.1.3.el7.x86_64
>>> [root@ovirt VM]# cat /etc/centos-release
>>> CentOS Linux release 7.6.1810 (Core)
>>>
>>> [root@ovirt VM]# rpm -qa|grep ovirt
>>> ovirt-engine-backend-4.3.0.2-1.el7.noarch
>>> ovirt-imageio-common-1.4.6-1.el7.x86_64
>>> ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch
>>> ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
>>> ovirt-ansible-infra-1.1.11-1.el7.noarch
>>> ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch
>>> libgovirt-0.3.4-1.el7.x86_64
>>> ovirt-hosted-engine-setup-2.3.3-1.el7.noarch
>>> ovirt-iso-uploader-4.3.0-1.el7.noarch
>>> ovirt-engine-4.3.0.2-1.el7.noarch
>>> python2-ovirt-host-deploy-1.8.0-1.el7.noarch
>>> ovirt-ansible-repositories-1.1.4-1.el7.noarch
>>> python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64
>>> ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch
>>> ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
>>> ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
>>> ovirt-ansible-image-template-1.1.9-1.el7.noarch
>>> ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
>>> ovirt-engine-dwh-4.3.0-1.el7.noarch
>>> ovirt-ansible-roles-1.1.6-1.el7.noarch
>>> ovirt-host-deploy-common-1.8.0-1.el7.noarch
>>> ovirt-engine-api-explorer-0.0.3-1.el7.noarch
>>> ovirt-engine-setup-base-4.3.0.4-1.el7.noarch
>>> ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch
>>> cockpit-ovirt-dashboard-0.12.1-1.el7.noarch
>>> ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch
>>> ovirt-engine-restapi-4.3.0.2-1.el7.noarch
>>> ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch
>>> ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch
>>> ovirt-hosted-engine-ha-2.3.1-1.el7.noarch
>>> ovirt-ansible-cluster-upgrade-1.1.11-1.el7.noarch
>>> ovirt-cockpit-sso-0.1.1-1.el7.noarch
>>> ovirt-engine-ui-extensions-1.0.2-1.el7.noarch
>>> ovirt-engine-setup-4.3.0.4-1.el7.noarch
>>> ovirt-imageio-daemon-1.4.6-1.el7.noarch
>>> ovirt-host-4.3.0-2.el7.x86_64
>>> ovirt-vmconsole-1.0.6-2.el7.noarch
>>> ovirt-imageio-proxy-1.4.6-1.el7.noarch
>>> ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch
>>> ovirt-web-ui-1.5.0-1.el7.noarch
>>> ovirt-provider-ovn-1.2.19-1.el7.noarch
>>> ovirt-engine-dbscripts-4.3.0.2-1.el7.noarch
>>> ovirt-ansible-engine-setup-1.1.7-1.el7.noarch
>>> ovirt-engine-setup-plugin-ovirt-engine-4.3.0.4-1.el7.noarch
>>> 

[ovirt-users] Re: Storage Domain Ovirt 4.3 RC EPYC

[Darin Schmidt]

Same issue

[root@ovirt ~]# rpm -qa|grep ovirt-engine-appliance
ovirt-engine-appliance-4.3-20190131.1.el7.x86_64

Error while executing action New Local Storage Domain: Storage format is
unsupported



On Thu, Jan 31, 2019 at 5:06 PM Greg Sheremeta  wrote:

> Hi,
>
> On Thu, Jan 31, 2019 at 4:19 PM Darin Schmidt 
> wrote:
>
>>
>>
>> Uncaught exception occurred. Please try reloading the page. Details:
>> (TypeError) : Cannot read property 'Vg' of null
>> Please have your administrator check the UI logs
>>
>
> please attach ui.log
>
>
>>
>> Im trying to setup Ovirt 4.3 RC because its the only one that supports
>> AMD EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB
>> SSDs using mdadm and mounted it at /VM. I put the Host into maintenance,
>> select Configure Local Storage, and it fails telling me:
>> New Local Storage Domain: Storage format is unsupported
>>
>
> We fixed this one this morning -- update your appliance to
> ovirt-engine-appliance-4.3-20190131.1.el7.x86_64
> Then redeploy and it should work.
> https://bugzilla.redhat.com/show_bug.cgi?id=1669606
>
> Best wishes,
> Greg
>
>
>>
>> I formatted the array to ext4. This is a self hosted system.  Anyone have
>> any ideas?
>>
>> [root@ovirt VM]# uname -r
>> 3.10.0-957.1.3.el7.x86_64
>> [root@ovirt VM]# cat /etc/centos-release
>> CentOS Linux release 7.6.1810 (Core)
>>
>> [root@ovirt VM]# rpm -qa|grep ovirt
>> ovirt-engine-backend-4.3.0.2-1.el7.noarch
>> ovirt-imageio-common-1.4.6-1.el7.x86_64
>> ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch
>> ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
>> ovirt-ansible-infra-1.1.11-1.el7.noarch
>> ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch
>> libgovirt-0.3.4-1.el7.x86_64
>> ovirt-hosted-engine-setup-2.3.3-1.el7.noarch
>> ovirt-iso-uploader-4.3.0-1.el7.noarch
>> ovirt-engine-4.3.0.2-1.el7.noarch
>> python2-ovirt-host-deploy-1.8.0-1.el7.noarch
>> ovirt-ansible-repositories-1.1.4-1.el7.noarch
>> python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64
>> ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch
>> ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
>> ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
>> ovirt-ansible-image-template-1.1.9-1.el7.noarch
>> ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
>> ovirt-engine-dwh-4.3.0-1.el7.noarch
>> ovirt-ansible-roles-1.1.6-1.el7.noarch
>> ovirt-host-deploy-common-1.8.0-1.el7.noarch
>> ovirt-engine-api-explorer-0.0.3-1.el7.noarch
>> ovirt-engine-setup-base-4.3.0.4-1.el7.noarch
>> ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch
>> cockpit-ovirt-dashboard-0.12.1-1.el7.noarch
>> ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch
>> ovirt-engine-restapi-4.3.0.2-1.el7.noarch
>> ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch
>> ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch
>> ovirt-hosted-engine-ha-2.3.1-1.el7.noarch
>> ovirt-ansible-cluster-upgrade-1.1.11-1.el7.noarch
>> ovirt-cockpit-sso-0.1.1-1.el7.noarch
>> ovirt-engine-ui-extensions-1.0.2-1.el7.noarch
>> ovirt-engine-setup-4.3.0.4-1.el7.noarch
>> ovirt-imageio-daemon-1.4.6-1.el7.noarch
>> ovirt-host-4.3.0-2.el7.x86_64
>> ovirt-vmconsole-1.0.6-2.el7.noarch
>> ovirt-imageio-proxy-1.4.6-1.el7.noarch
>> ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch
>> ovirt-web-ui-1.5.0-1.el7.noarch
>> ovirt-provider-ovn-1.2.19-1.el7.noarch
>> ovirt-engine-dbscripts-4.3.0.2-1.el7.noarch
>> ovirt-ansible-engine-setup-1.1.7-1.el7.noarch
>> ovirt-engine-setup-plugin-ovirt-engine-4.3.0.4-1.el7.noarch
>> ovirt-provider-ovn-driver-1.2.19-1.el7.noarch
>> ovirt-engine-extension-aaa-jdbc-1.1.8-1.el7.noarch
>> python2-ovirt-setup-lib-1.2.0-1.el7.noarch
>> ovirt-host-deploy-java-1.8.0-1.el7.noarch
>> ovirt-engine-tools-4.3.0.2-1.el7.noarch
>> cockpit-machines-ovirt-176-4.el7.centos.noarch
>> ovirt-engine-metrics-1.2.0.3-1.el7.noarch
>> ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch
>> ovirt-vmconsole-host-1.0.6-2.el7.noarch
>> ovirt-ansible-manageiq-1.1.13-1.el7.noarch
>> ovirt-engine-wildfly-14.0.1-3.el7.x86_64
>> ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
>> ovirt-host-dependencies-4.3.0-2.el7.x86_64
>> ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch
>> ovirt-engine-dwh-setup-4.3.0-1.el7.noarch
>> ovirt-ansible-v2v-conversion-host-1.9.1-1.el7.noarch
>> python2-ovirt-engine-lib-4.3.0.4-1.el7.noarch
>> ovirt-release43-pre-4.3.0-0.7.rc4.el7.noarch
>>
>> ___
>> 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/3ASMB4IW74TXD576KKIIZBKYCQTTISJI/
>>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
>


ui.log

[ovirt-users] Re: Suggestions on adding 1000 or more networks to an engine/hosts

[Dominik Holler]

On Wed, 30 Jan 2019 02:37:00 -
"Brian Wilson"  wrote:

> 
> > Would external OVN networks fit for your scenario?
> 
> We steered away from them when we couldn't figure out how to add a
> VLAN Id on them without having to turn around and attach them to an
> "outside network" anyway we would essentially end up with double the
> networks with them in order to allow VMs to interface with Physical
> Hardware on the Same Vlan IDs
> 

If you would be interested in using Open vSwitch, which is still in
technology preview in oVirt and limited
https://ovirt.org/develop/release-management/features/network/openvswitch/native-openvswitch.html#limitations
, there would be a way to connect OVN networks to physical VLANs:

1. Create a new cluster with switchtype OVS and ovirt-provider-ovn as
default network provider.

2. At least one host is added, in best case a new installed one, to the
new cluster.

3. Create a new network in oVirt, e.g. called 'trunk_net', and attach
this to the network interface on the hosts, which should transport the
data.

4. Create the OVN networks with port-security disabled, 
provider:network_type vlan, provider:physical_network trunk_net and
the desired VLAN tag as provider:segmentation_id.
For me worked the following script utilizing the python
module 'openstack':

#!/bin/env python
from __future__ import print_function
import openstack
cloud = openstack.connect(cloud='ovirt')
provider = {
'network_type': 'vlan',
'segmentation_id': 2,
'physical_network': 'trunk_net'
}
print(cloud.create_network('ovn_vlan_2', port_security_enabled=False, 
provider=provider))

The configuration of the python module 'openstack' is documented in
https://docs.openstack.org/python-openstackclient/pike/configuration/index.html
e.g. a file clouds.yaml in the working directory with content
similar to:
clouds:
  ovirt:
auth:
  auth_url: https://localhost:35357/v2.0
  password: '123456'
  username: admin@internal
verify: false
should do the trick.
Alternatively the configuration could be provided by the environment
variables: OS_USERNAME, OS_PASSWORD, OS_AUTH_URL and OS_CACERT.

In default configuration, the networks will be imported automatically
into oVirt and ready to be attached to VMs.

> 
> 
> > If possible, would you be able to share the relevant part of
> > engine.log? 
> I can try to kick off the playbook again and gather the logs
> 
> 
> > From my point of view, it is a good idea to label the host interface
> > after creating the networks, if many networks are created rapidly.
> 
> That could be a workable solution to an extent if we were to propop
> them and then do the label assignment at the end, this specific use
> case was adding to an existing label where there may be VMs using
> networks on the label already
> 
> 
> > Is this cluster of switchtype OVS or linux bridge?
> Linux Bridge
> 
> 
> ___
> 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/VPGE7SZH46TYAEKY2CP5II2LRCYYSIVZ/
___
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/64I5FSBGBZSKDVUQICJ7SWP5VHEE3E2X/

[ovirt-users] Re: Storage Domain Ovirt 4.3 RC EPYC

[Greg Sheremeta]

Hi,

On Thu, Jan 31, 2019 at 4:19 PM Darin Schmidt 
wrote:

>
>
> Uncaught exception occurred. Please try reloading the page. Details:
> (TypeError) : Cannot read property 'Vg' of null
> Please have your administrator check the UI logs
>

please attach ui.log


>
> Im trying to setup Ovirt 4.3 RC because its the only one that supports AMD
> EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB SSDs
> using mdadm and mounted it at /VM. I put the Host into maintenance, select
> Configure Local Storage, and it fails telling me:
> New Local Storage Domain: Storage format is unsupported
>

We fixed this one this morning -- update your appliance to
ovirt-engine-appliance-4.3-20190131.1.el7.x86_64
Then redeploy and it should work.
https://bugzilla.redhat.com/show_bug.cgi?id=1669606

Best wishes,
Greg


>
> I formatted the array to ext4. This is a self hosted system.  Anyone have
> any ideas?
>
> [root@ovirt VM]# uname -r
> 3.10.0-957.1.3.el7.x86_64
> [root@ovirt VM]# cat /etc/centos-release
> CentOS Linux release 7.6.1810 (Core)
>
> [root@ovirt VM]# rpm -qa|grep ovirt
> ovirt-engine-backend-4.3.0.2-1.el7.noarch
> ovirt-imageio-common-1.4.6-1.el7.x86_64
> ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch
> ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
> ovirt-ansible-infra-1.1.11-1.el7.noarch
> ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch
> libgovirt-0.3.4-1.el7.x86_64
> ovirt-hosted-engine-setup-2.3.3-1.el7.noarch
> ovirt-iso-uploader-4.3.0-1.el7.noarch
> ovirt-engine-4.3.0.2-1.el7.noarch
> python2-ovirt-host-deploy-1.8.0-1.el7.noarch
> ovirt-ansible-repositories-1.1.4-1.el7.noarch
> python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64
> ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch
> ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
> ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
> ovirt-ansible-image-template-1.1.9-1.el7.noarch
> ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
> ovirt-engine-dwh-4.3.0-1.el7.noarch
> ovirt-ansible-roles-1.1.6-1.el7.noarch
> ovirt-host-deploy-common-1.8.0-1.el7.noarch
> ovirt-engine-api-explorer-0.0.3-1.el7.noarch
> ovirt-engine-setup-base-4.3.0.4-1.el7.noarch
> ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch
> cockpit-ovirt-dashboard-0.12.1-1.el7.noarch
> ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch
> ovirt-engine-restapi-4.3.0.2-1.el7.noarch
> ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch
> ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch
> ovirt-hosted-engine-ha-2.3.1-1.el7.noarch
> ovirt-ansible-cluster-upgrade-1.1.11-1.el7.noarch
> ovirt-cockpit-sso-0.1.1-1.el7.noarch
> ovirt-engine-ui-extensions-1.0.2-1.el7.noarch
> ovirt-engine-setup-4.3.0.4-1.el7.noarch
> ovirt-imageio-daemon-1.4.6-1.el7.noarch
> ovirt-host-4.3.0-2.el7.x86_64
> ovirt-vmconsole-1.0.6-2.el7.noarch
> ovirt-imageio-proxy-1.4.6-1.el7.noarch
> ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch
> ovirt-web-ui-1.5.0-1.el7.noarch
> ovirt-provider-ovn-1.2.19-1.el7.noarch
> ovirt-engine-dbscripts-4.3.0.2-1.el7.noarch
> ovirt-ansible-engine-setup-1.1.7-1.el7.noarch
> ovirt-engine-setup-plugin-ovirt-engine-4.3.0.4-1.el7.noarch
> ovirt-provider-ovn-driver-1.2.19-1.el7.noarch
> ovirt-engine-extension-aaa-jdbc-1.1.8-1.el7.noarch
> python2-ovirt-setup-lib-1.2.0-1.el7.noarch
> ovirt-host-deploy-java-1.8.0-1.el7.noarch
> ovirt-engine-tools-4.3.0.2-1.el7.noarch
> cockpit-machines-ovirt-176-4.el7.centos.noarch
> ovirt-engine-metrics-1.2.0.3-1.el7.noarch
> ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch
> ovirt-vmconsole-host-1.0.6-2.el7.noarch
> ovirt-ansible-manageiq-1.1.13-1.el7.noarch
> ovirt-engine-wildfly-14.0.1-3.el7.x86_64
> ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
> ovirt-host-dependencies-4.3.0-2.el7.x86_64
> ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch
> ovirt-engine-dwh-setup-4.3.0-1.el7.noarch
> ovirt-ansible-v2v-conversion-host-1.9.1-1.el7.noarch
> python2-ovirt-engine-lib-4.3.0.4-1.el7.noarch
> ovirt-release43-pre-4.3.0-0.7.rc4.el7.noarch
>
> ___
> 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/3ASMB4IW74TXD576KKIIZBKYCQTTISJI/
>


-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

___
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/O34FAS5SQDUVKHZRQIOX4AOESEHCL7BX/

[ovirt-users] Storage Domain Ovirt 4.3 RC EPYC

[Darin Schmidt]

Uncaught exception occurred. Please try reloading the page. Details: 
(TypeError) : Cannot read property 'Vg' of null
Please have your administrator check the UI logs

Im trying to setup Ovirt 4.3 RC because its the only one that supports AMD 
EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB SSDs 
using mdadm and mounted it at /VM. I put the Host into maintenance, select 
Configure Local Storage, and it fails telling me:
New Local Storage Domain: Storage format is unsupported

I formatted the array to ext4. This is a self hosted system.  Anyone have any 
ideas?

[root@ovirt VM]# uname -r
3.10.0-957.1.3.el7.x86_64
[root@ovirt VM]# cat /etc/centos-release
CentOS Linux release 7.6.1810 (Core)

[root@ovirt VM]# rpm -qa|grep ovirt
ovirt-engine-backend-4.3.0.2-1.el7.noarch
ovirt-imageio-common-1.4.6-1.el7.x86_64
ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch
ovirt-ansible-vm-infra-1.1.12-1.el7.noarch
ovirt-ansible-infra-1.1.11-1.el7.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch
libgovirt-0.3.4-1.el7.x86_64
ovirt-hosted-engine-setup-2.3.3-1.el7.noarch
ovirt-iso-uploader-4.3.0-1.el7.noarch
ovirt-engine-4.3.0.2-1.el7.noarch
python2-ovirt-host-deploy-1.8.0-1.el7.noarch
ovirt-ansible-repositories-1.1.4-1.el7.noarch
python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64
ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch
ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
ovirt-vmconsole-proxy-1.0.6-2.el7.noarch
ovirt-ansible-image-template-1.1.9-1.el7.noarch
ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
ovirt-engine-dwh-4.3.0-1.el7.noarch
ovirt-ansible-roles-1.1.6-1.el7.noarch
ovirt-host-deploy-common-1.8.0-1.el7.noarch
ovirt-engine-api-explorer-0.0.3-1.el7.noarch
ovirt-engine-setup-base-4.3.0.4-1.el7.noarch
ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch
cockpit-ovirt-dashboard-0.12.1-1.el7.noarch
ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch
ovirt-engine-restapi-4.3.0.2-1.el7.noarch
ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch
ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7.noarch
ovirt-ansible-cluster-upgrade-1.1.11-1.el7.noarch
ovirt-cockpit-sso-0.1.1-1.el7.noarch
ovirt-engine-ui-extensions-1.0.2-1.el7.noarch
ovirt-engine-setup-4.3.0.4-1.el7.noarch
ovirt-imageio-daemon-1.4.6-1.el7.noarch
ovirt-host-4.3.0-2.el7.x86_64
ovirt-vmconsole-1.0.6-2.el7.noarch
ovirt-imageio-proxy-1.4.6-1.el7.noarch
ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch
ovirt-web-ui-1.5.0-1.el7.noarch
ovirt-provider-ovn-1.2.19-1.el7.noarch
ovirt-engine-dbscripts-4.3.0.2-1.el7.noarch
ovirt-ansible-engine-setup-1.1.7-1.el7.noarch
ovirt-engine-setup-plugin-ovirt-engine-4.3.0.4-1.el7.noarch
ovirt-provider-ovn-driver-1.2.19-1.el7.noarch
ovirt-engine-extension-aaa-jdbc-1.1.8-1.el7.noarch
python2-ovirt-setup-lib-1.2.0-1.el7.noarch
ovirt-host-deploy-java-1.8.0-1.el7.noarch
ovirt-engine-tools-4.3.0.2-1.el7.noarch
cockpit-machines-ovirt-176-4.el7.centos.noarch
ovirt-engine-metrics-1.2.0.3-1.el7.noarch
ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch
ovirt-vmconsole-host-1.0.6-2.el7.noarch
ovirt-ansible-manageiq-1.1.13-1.el7.noarch
ovirt-engine-wildfly-14.0.1-3.el7.x86_64
ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch
ovirt-host-dependencies-4.3.0-2.el7.x86_64
ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch
ovirt-engine-dwh-setup-4.3.0-1.el7.noarch
ovirt-ansible-v2v-conversion-host-1.9.1-1.el7.noarch
python2-ovirt-engine-lib-4.3.0.4-1.el7.noarch
ovirt-release43-pre-4.3.0-0.7.rc4.el7.noarch

___
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/3ASMB4IW74TXD576KKIIZBKYCQTTISJI/

[ovirt-users] Re: Mounting ISO in subfolder

[Sandro Bonazzola]

Il giorno mer 30 gen 2019 alle ore 10:02 Giulio Casella 
ha scritto:

> Hi,
> I noticed that if I create a directory in root of ISO domain and put an
> image in it, you can see it in admin portal image list (listed as
> "foo/bar.iso"), but mounting that iso in a VM ("change CD") fails
>
> "Error while executing action Change CD: Drive image file could not be
> found"
>
> I can easily reproduce this behaviour in ovirt 4.2.8 and rhv 4.2.7.
>
> Is it a bug?
>

As far as I can tell, there are no tools that creates subdirectories within
storage domains.
Did you manually upload the iso into the nfs mount creating a subdirectory
there?
I think this layout is not supported at all.




>
> Cheers,
> gc
> ___
> 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/WRVLT542RUQPE76MA6YO5KGZIMKVDS6I/
>


-- 

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com

___
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/B37TSIZKGETLMSFMWWU65FQ32RR73NC6/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[Simone Tiraboschi]

On Thu, Jan 31, 2019 at 4:20 PM Douglas Duckworth 
wrote:

> Hi Simone
>
> Thanks again for your help!
>
> Do you have some ideas on what I can try to resolve this issue?
>

Honestly I'm not able to reproduce this issue.
I can only suggest to try upgrading to 4.2.8 if still not there, and if
still not working open a bug on bugzilla attaching engine.log.


>
>
> Thanks,
>
> Douglas Duckworth, MSc, LFCS
> HPC System Administrator
> Scientific Computing Unit 
> Weill Cornell Medicine
> 1300 York Avenue
> New York, NY 10065
> E: d...@med.cornell.edu
> O: 212-746-6305
> F: 212-746-8690
>
>
> On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth 
> wrote:
>
>> Yes, I do.  Gold crown indeed.
>>
>> It's the "HostedEngine" as seen attached!
>>
>>
>> Thanks,
>>
>> Douglas Duckworth, MSc, LFCS
>> HPC System Administrator
>> Scientific Computing Unit 
>> Weill Cornell Medicine
>> 1300 York Avenue
>> New York, NY 10065
>> E: d...@med.cornell.edu
>> O: 212-746-6305
>> F: 212-746-8690
>>
>>
>> On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi 
>> wrote:
>>
>>>
>>>
>>> On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth <
>>> dod2...@med.cornell.edu> wrote:
>>>
 Hi Simone

 Can I get help with this issue?  Still cannot increase memory for
 Hosted Engine.

>>>
>>> From the logs it seams that the engine is trying to hotplug memory to
>>> the engine VM which is something it should not happen.
>>> The engine should simply update engine VM configuration in the OVF_STORE
>>> and require a reboot of the engine VM.
>>> Quick question, in the VM panel do you see a gold crown symbol on the
>>> Engine VM?
>>>
>>>

 Thanks,

 Douglas Duckworth, MSc, LFCS
 HPC System Administrator
 Scientific Computing Unit 
 Weill Cornell Medicine
 1300 York Avenue
 New York, NY 10065
 E: d...@med.cornell.edu
 O: 212-746-6305
 F: 212-746-8690


 On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth <
 dod2...@med.cornell.edu> wrote:

> 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,
> 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
> 

[ovirt-users] Re: Sanlock volume corrupted on deployment

[Simone Tiraboschi]

On Thu, Jan 31, 2019 at 2:48 PM Nir Soffer  wrote:

> On Thu, Jan 31, 2019 at 2:52 PM Strahil Nikolov 
> wrote:
>
>> Dear Nir,
>>
>> the issue with the 'The method does not exist or is not available:
>> {'method': u'GlusterHost.list'}, code = -32601' is not related to the
>> sanlock. I don't know why the 'vdsm-gluster' package was not installed as a
>> dependency.
>>
>
> Please file a bug about this.
>
> > Can you share your sanlock log?
>> >
>> I'm attaching the contents of /var/log , but here is a short snippet:
>>
>> About the sanlock issue - it reappeared with errors like :
>> 2019-01-31 13:33:10 27551 [17279]: leader1 delta_acquire_begin error -223
>> lockspace hosted-engine host_id 1
>>
>
> As I said, the error is not -233, but -223, which make sense - this error
> means sanlock did not
> find the magic number for a delta lease area, which means the area was not
> formatted, or
> corrupted.
>
>
>> 2019-01-31 13:33:10 27551 [17279]: leader2 path
>> /var/run/vdsm/storage/808423f9-8a5c-40cd-bc9f-2568c85b8c74/2c74697a-8bd9-4472-8a98-bf624f3462d5/411b6cee-5b01-47ca-8c28-bb1fed8ac83b
>> offset 0
>> 2019-01-31 13:33:10 27551 [17279]: leader3 m 0 v 30003 ss 512 nh 0 mh 1
>> oi 0 og 0 lv 0
>> 2019-01-31 13:33:10 27551 [17279]: leader4 sn hosted-engine rn  ts 0 cs
>> 60346c59
>> 2019-01-31 13:33:11 27551 [21482]: s6 add_lockspace fail result -223
>> 2019-01-31 13:33:16 27556 [21482]: s7 lockspace
>> hosted-engine:1:/var/run/vdsm/storage/808423f9-8a5c-40cd-bc9f-2568c85b8c74/2c74697a-8bd9-4472-8a98-bf624f3462d5/411b6cee-5b01-47ca-8c28-bb1fe
>> d8ac83b:0
>>
>>
>> I have managed to fix it by running the following immediately after the
>> ha services were started by ansible:
>>
>> cd
>> /rhev/data-center/mnt/glusterSD/ovirt1.localdomain\:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/ha_agent/
>>
>
> This is not a path managed by vdsm, so I guess the issue is with hosted
> enigne
> specific lockspace that is managed by hosted engine, not by vdsm.
>
>
>> sanlock direct init -s hosted-engine:0:hosted-engine.lockspace:0
>>
>
> This formats the lockspace, and is expected to fix this issue.
>
>
>
>> systemctl stop ovirt-ha-agent ovirt-ha-broker
>> systemctl status vdsmd
>> systemctl start ovirt-ha-broker ovirt-ha-agent
>>
>> Once the VM started - ansible managed to finish the deployment without
>> any issues.
>> I hope someone can check the sanlock init stuff , as it is really
>> frustrating.
>>
>
I'd suggest to avoid directly playing with the managed in the middle of the
deployment to avoid further issues.


>
> If I understand the flow correctly, you create a new environment from
> scratch, so this is
> an issue with hosted engine deploymnet, not initializing the lockspace.
>
> I think filing a bug with the info in this thread is the first step.
>
> Simone, can you take a look at this?
>

On our CI env everything is working as expected and the lockspace volume
got initialised as expected.
In the attached logs a log of steps got skipped since a lot of things were
already up and running so they are not really useful.
Strahil, can you please retry on a really clean environment and eventually
attach the relevant logs if you are able to reproduce the issue?
___
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/ZQWO6H5JRKIJI6ZDRTP2PTK7SX6XILQH/

[ovirt-users] Re: Changing DNS servers

[Chris Adams]

Once upon a time, Luca 'remix_tj' Lorenzetto  said:
> did you checked under the network configuration of ovirtmgmt on each
> host? Here there are directives for setting ip, dns and gateway.
> Since you're reporting a file from vdsm, that configuration can be
> changed through the manager ui.

On a 4.2 cluster, I see a tab for DNS configuration, but on this 4.1
cluster, I don't see any DNS config in the web UI.
-- 
Chris Adams 
___
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/WPVDF2MMJF5F6SDJG3FH7M7K3MV3VOAA/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[Douglas Duckworth]

Hi Simone

Thanks again for your help!

Do you have some ideas on what I can try to resolve this issue?


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Yes, I do.  Gold crown indeed.

It's the "HostedEngine" as seen attached!


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi 
mailto:stira...@redhat.com>> wrote:


On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Hi Simone

Can I get help with this issue?  Still cannot increase memory for Hosted Engine.

From the logs it seams that the engine is trying to hotplug memory to the 
engine VM which is something it should not happen.
The engine should simply update engine VM configuration in the OVF_STORE and 
require a reboot of the engine VM.
Quick question, in the VM panel do you see a gold crown symbol on the Engine VM?


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
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, 
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 

[ovirt-users] [ANN] oVirt 4.3.0 Fifth Release Candidate is now available for testing

[Sandro Bonazzola]

The oVirt Project is pleased to announce the availability of the Fifth
Release Candidate of oVirt 4.3.0, as of January 31th, 2019

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 450 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 CentOS 7

- oVirt Appliance for Fedora 28 (tech preview) is being delayed due to
build issues with the build system.

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 RHV

Red Hat EMEA 

sbona...@redhat.com

___
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/ANS3JNVLVKDTPB3WMEQWBCCBCGLLTWNC/

[ovirt-users] Re: host NonResponsive after trying to update network MTUs

[Edward Berger]

 I've ended up resetting engine's MTU and reverting the MTU on ovirtmgmt to
1500 and resyncing all the host nodes.
The underlying NIC MTU was still 9000 for other VLANs.
Afterwards, the host is available again and was able to install with engine
deploy enabled.

Maybe the network switch|router is misconfigured?
I don't have the direct access to examine it.
The symptom was that ssh host to engine, or the other way, would connect
but hang before completing negotiations.
This caused the "unresponsive" host problems.

On Wed, Jan 30, 2019 at 5:02 AM Sahina Bose  wrote:

> On Tue, Jan 29, 2019 at 10:05 PM Edward Berger 
> wrote:
> >
> > Done. It still won't let me remove the host.
> > clicked maintenance, checked ignore gluster... box.
> > clicked remove.  got popup " track00.yard.psc.edu:
> >
> > Cannot remove Host. Server having Gluster volume."
>
> If the server has bricks, the only option to remove the host is to
> replace/remove the bricks.
> Can you try reinstall of host instead?
>
> >
> >
> > On Tue, Jan 29, 2019 at 4:24 AM Sahina Bose  wrote:
> >>
> >> On Mon, Jan 28, 2019 at 7:31 AM Edward Berger 
> wrote:
> >> >
> >> > I have a problem host which also is the one I deployed a
> hyperconverged oVirt node-ng cluster from with the cockpit's hyperconverged
> installation wizard.
> >> >
> >> > When I realized after deploying that I hadn't set the MTUs correctly
> for the engine-mgmt, associated vlan and eno.2 device and also for my
> infiniband interface ib0, I went in and tried to set them to new values
> 9000 and 65520 it got into some kind of hung state.
> >> >
> >> > The engine task window shows a task in "executing" and a never ending
> spinning widget
> >> > "Handing non responsive Host track00..."
> >> >
> >> > I can tried updating the hosts /etc/sysconfig/network-scripts by hand.
> >> > I've tried every combination of the engines set host in maintenance
> mode , "sync networks" "refresh host capabilities" activating and
> rebooting, but I'm still stuck with an unresponsive host.
> >> >
> >> > I had another host that also failed but it allowed me to put it into
> maintenance mode and then remove it from the cluster and "add new" it back
> and it was happy.
> >> >
> >> > This one won't let me remove it because its serving the gluster
> volume mount point, even though I did give the mount options for the 2nd
> and 3rd backup volume servers.
> >> >
> >> > I'd appreciate any help restoring it to proper working order.
> >>
> >> Can you try removing the host after checking the "Ignore quorum loss
> ..." box?
> >>
> >> >
> >> > I'm attaching the gzip'd engine log.
> >> > ___
> >> > 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/HT2G345VWDWSIQDAYLFI55S6VE6HGGCA/
>
___
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/OCHCMI74EJFPGZ4NNHQIMI5TLCDBOA7B/

[ovirt-users] Re: Changing DNS servers

[Luca 'remix_tj' Lorenzetto]

Hello,

did you checked under the network configuration of ovirtmgmt on each
host? Here there are directives for setting ip, dns and gateway.
Since you're reporting a file from vdsm, that configuration can be
changed through the manager ui.

Luca


On Thu, Jan 31, 2019 at 3:25 PM Chris Adams  wrote:
>
> I am trying to change the DNS servers on the hosts on a 4.1 cluster.  It
> appears that oVirt has "learned" them somewhere.  They are in
> /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt (and of course
> /etc/resolv.conf), but that file gets rewritten on a reboot (so if I
> change it they just change back).  I can't find anything in the web UI
> to set/change DNS, but obviously they're stored somewhere.
>
> I see /var/lib/vdsm/persistence/netconf./nets/ovirtmgmt has
> the config; is it safe to directly edit that file?
>
> --
> Chris Adams 
> ___
> 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/3XV6UP6EIHBP25DXVY2Y4MLB2LG2VOMT/



-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
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/UXTYEKIR52I2NIPZBAM54GLZ7VVU6AKK/

[ovirt-users] Re: Issues adding iscsi storage domain

[Leo David]

Thank you Benny,

from engine:

2019-01-31 14:22:36,884Z INFO
[org.ovirt.engine.core.bll.storage.connection.ConnectStorageToVdsCommand]
(default task-6344) [d8697f85-8822-4588-8d7c-1ed6a5b1d9ca] Running command:
ConnectStorageToVdsCommand internal: false. Entities affected :  ID:
aaa0----123456789aaa Type: SystemAction group
CREATE_STORAGE_DOMAIN with role type ADMIN
2019-01-31 14:22:36,892Z INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(default task-6344) [d8697f85-8822-4588-8d7c-1ed6a5b1d9ca] START,
ConnectStorageServerVDSCommand(HostName = hp-1.test.lab,
StorageServerConnectionManagementVDSParameters:{hostId='e45920ea-572d-4d52-917d-207d82c1d305',
storagePoolId='----', storageType='ISCSI',
connectionList='[StorageServerConnections:{id='null',
connection='10.10.8.13',
iqn='iqn.2004-04.com.qnap:ts-ec1280u-rp:iscsi.test.f35296', vfsType='null',
mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null',
iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'}),
log id: 347096b2
2019-01-31 14:22:38,112Z INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(default task-6344) [d8697f85-8822-4588-8d7c-1ed6a5b1d9ca] FINISH,
ConnectStorageServerVDSCommand, return:
{----=0}, log id: 347096b2
2019-01-31 14:22:38,437Z INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand]
(default task-6344) [0ef49cb3-8b81-4f65-8a9d-aa5d57ca6575] START,
GetDeviceListVDSCommand(HostName = hp-1.test.lab,
GetDeviceListVDSCommandParameters:{hostId='e45920ea-572d-4d52-917d-207d82c1d305',
storageType='ISCSI', checkStatus='false', lunIds='null'}), log id: 2fdc334a
2019-01-31 14:22:39,694Z INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand]
(default task-6344) [0ef49cb3-8b81-4f65-8a9d-aa5d57ca6575] FINISH,
GetDeviceListVDSCommand, return: [], log id: 2fdc334a

In vdsm I can't find something related to this operation...
It feels like is not getting the luns from the target,  although from a
different client ( windows machine) i can successfully connect and map the
lun.



On Thu, Jan 31, 2019 at 4:10 PM Benny Zlotnik  wrote:

> Can you attach engine and vdsm logs?
>
> On Thu, Jan 31, 2019 at 4:04 PM Leo David  wrote:
>
>> Hello everyone,
>> Trying to setup an iscsi target as a storage domain,  and it seems not to
>> be possible.
>> Discovered the hosts,  the targets are displayed.
>> Selected one target, clicked the "Login" arrow, spinner runs a bit ,  and
>> the arrow gets grayed out.
>> But no LUNs are displayed, to select from.
>> From this step,  I can't go further,  if I hit "OK" nothing happends.
>> Just as a thoughtssh into the ovirt node used as initiator, and lsblk
>> command shows the block device as present.
>> So i have to cancel the "New Domain" windows without being able to add
>> the domain,  but that iscsi block device still remains present on the hosts.
>>
>> Using 4.2.8
>>
>> Any thoughts ?
>>
>> Thank you very much !
>>
>> Leo
>>
>> --
>> Best regards, Leo David
>> ___
>> 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/RRMR5TMWBKQQ3IKFDD2VQ5YELJGX4TCI/
>>
>

-- 
Best regards, Leo David
___
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/RSMEE7I7GGENDGNAHEFCDNZNDP5AUKTR/

[ovirt-users] Changing DNS servers

[Chris Adams]

I am trying to change the DNS servers on the hosts on a 4.1 cluster.  It
appears that oVirt has "learned" them somewhere.  They are in
/etc/sysconfig/network-scripts/ifcfg-ovirtmgmt (and of course
/etc/resolv.conf), but that file gets rewritten on a reboot (so if I
change it they just change back).  I can't find anything in the web UI
to set/change DNS, but obviously they're stored somewhere.

I see /var/lib/vdsm/persistence/netconf./nets/ovirtmgmt has
the config; is it safe to directly edit that file?

-- 
Chris Adams 
___
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/3XV6UP6EIHBP25DXVY2Y4MLB2LG2VOMT/

[ovirt-users] Re: Issues adding iscsi storage domain

[Benny Zlotnik]

Can you attach engine and vdsm logs?

On Thu, Jan 31, 2019 at 4:04 PM Leo David  wrote:

> Hello everyone,
> Trying to setup an iscsi target as a storage domain,  and it seems not to
> be possible.
> Discovered the hosts,  the targets are displayed.
> Selected one target, clicked the "Login" arrow, spinner runs a bit ,  and
> the arrow gets grayed out.
> But no LUNs are displayed, to select from.
> From this step,  I can't go further,  if I hit "OK" nothing happends.
> Just as a thoughtssh into the ovirt node used as initiator, and lsblk
> command shows the block device as present.
> So i have to cancel the "New Domain" windows without being able to add the
> domain,  but that iscsi block device still remains present on the hosts.
>
> Using 4.2.8
>
> Any thoughts ?
>
> Thank you very much !
>
> Leo
>
> --
> Best regards, Leo David
> ___
> 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/RRMR5TMWBKQQ3IKFDD2VQ5YELJGX4TCI/
>
___
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/BV6FMZROFM3OAWBOMPBPAXFLAUFL6DJJ/

[ovirt-users] Issues adding iscsi storage domain

[Leo David]

Hello everyone,
Trying to setup an iscsi target as a storage domain,  and it seems not to
be possible.
Discovered the hosts,  the targets are displayed.
Selected one target, clicked the "Login" arrow, spinner runs a bit ,  and
the arrow gets grayed out.
But no LUNs are displayed, to select from.
>From this step,  I can't go further,  if I hit "OK" nothing happends.
Just as a thoughtssh into the ovirt node used as initiator, and lsblk
command shows the block device as present.
So i have to cancel the "New Domain" windows without being able to add the
domain,  but that iscsi block device still remains present on the hosts.

Using 4.2.8

Any thoughts ?

Thank you very much !

Leo

-- 
Best regards, Leo David
___
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/RRMR5TMWBKQQ3IKFDD2VQ5YELJGX4TCI/

[ovirt-users] Re: Sanlock volume corrupted on deployment

[Nir Soffer]

On Tue, Jan 29, 2019 at 2:00 PM Strahil  wrote:

> Dear Nir,
>
> According to redhat solution 1179163 'add_lockspace fail result -233'
> indicates corrupted ids lockspace.
>

Good work finding the solution!

Note that the page mention error -223, not -233:

2014-08-27 14:26:42+ 2244 [14497]: s30 add_lockspace fail result
-223  #<-- corrupted ids lockspace



>
> During the install, the VM fails to get up.
> In order to fix it, I stop:
> ovirt-ha-agent, ovirt-ha-broker, vdsmd, supervdsmd, sanlock
> Then reinitialize the lockspace via 'sanlock direct init -s' (used
> bugreport 1116469 as guidance).
> Once the init is successful and all the services are up - the VM is
> started but the deployment was long over and the setup needs additional
> cleaning up.
>
> I will rebuild the gluster cluster and then will repeat the deployment.
>
> Can you guide me what information will be needed , as I'm quite new in
> ovirt/RHV ?
>
> Best Regards,
> Strahil Nikolov
>
> On Jan 28, 2019 20:34, Nir Soffer  wrote:
>
> On Sat, Jan 26, 2019 at 6:13 PM Strahil  wrote:
>
> Hey guys,
>
> I have noticed that with 4.2.8 the sanlock issue (during deployment) is
> still not fixed.
> Am I the only one with bad luck or there is something broken there ?
>
> The sanlock service reports code 's7 add_lockspace fail result -233'
> 'leader1 delta_acquire_begin error -233 lockspace hosted-engine host_id
> 1'.
>
>
> Sanlock does not have such error code - are you sure this is -233?
>
> Here sanlock return values:
> https://pagure.io/sanlock/blob/master/f/src/sanlock_rv.h
>
> Can you share your sanlock log?
>
>
>
>
> Best Regards,
> Strahil Nikolov
> ___
> 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/SZMF5KKHSXOUTLGX3LR2NBN7E6QGS6G3/
>
>
>
___
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/FMAWDZO5UO2HAGMHXT7AKGEKKXTIJS5S/

[ovirt-users] Re: Sanlock volume corrupted on deployment

[Nir Soffer]

On Thu, Jan 31, 2019 at 2:52 PM Strahil Nikolov 
wrote:

> Dear Nir,
>
> the issue with the 'The method does not exist or is not available:
> {'method': u'GlusterHost.list'}, code = -32601' is not related to the
> sanlock. I don't know why the 'vdsm-gluster' package was not installed as a
> dependency.
>

Please file a bug about this.

> Can you share your sanlock log?
> >
> I'm attaching the contents of /var/log , but here is a short snippet:
>
> About the sanlock issue - it reappeared with errors like :
> 2019-01-31 13:33:10 27551 [17279]: leader1 delta_acquire_begin error -223
> lockspace hosted-engine host_id 1
>

As I said, the error is not -233, but -223, which make sense - this error
means sanlock did not
find the magic number for a delta lease area, which means the area was not
formatted, or
corrupted.


> 2019-01-31 13:33:10 27551 [17279]: leader2 path
> /var/run/vdsm/storage/808423f9-8a5c-40cd-bc9f-2568c85b8c74/2c74697a-8bd9-4472-8a98-bf624f3462d5/411b6cee-5b01-47ca-8c28-bb1fed8ac83b
> offset 0
> 2019-01-31 13:33:10 27551 [17279]: leader3 m 0 v 30003 ss 512 nh 0 mh 1 oi
> 0 og 0 lv 0
> 2019-01-31 13:33:10 27551 [17279]: leader4 sn hosted-engine rn  ts 0 cs
> 60346c59
> 2019-01-31 13:33:11 27551 [21482]: s6 add_lockspace fail result -223
> 2019-01-31 13:33:16 27556 [21482]: s7 lockspace
> hosted-engine:1:/var/run/vdsm/storage/808423f9-8a5c-40cd-bc9f-2568c85b8c74/2c74697a-8bd9-4472-8a98-bf624f3462d5/411b6cee-5b01-47ca-8c28-bb1fe
> d8ac83b:0
>
>
> I have managed to fix it by running the following immediately after the ha
> services were started by ansible:
>
> cd
> /rhev/data-center/mnt/glusterSD/ovirt1.localdomain\:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/ha_agent/
>

This is not a path managed by vdsm, so I guess the issue is with hosted
enigne
specific lockspace that is managed by hosted engine, not by vdsm.


> sanlock direct init -s hosted-engine:0:hosted-engine.lockspace:0
>

This formats the lockspace, and is expected to fix this issue.



> systemctl stop ovirt-ha-agent ovirt-ha-broker
> systemctl status vdsmd
> systemctl start ovirt-ha-broker ovirt-ha-agent
>
> Once the VM started - ansible managed to finish the deployment without any
> issues.
> I hope someone can check the sanlock init stuff , as it is really
> frustrating.
>

If I understand the flow correctly, you create a new environment from
scratch, so this is
an issue with hosted engine deploymnet, not initializing the lockspace.

I think filing a bug with the info in this thread is the first step.

Simone, can you take a look at this?
___
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/JWFLLOQS7AWN6P4XZS3HC4PTUWU2G5SP/

[ovirt-users] Re: Failed to configure management network on host Local due to setup networks failure.

[Sandro Bonazzola]

Il giorno gio 17 gen 2019, 20:57  ha scritto:

> Friends,
>
> I have install oVirt but appears failed.
>
> And interfaces stay not available (LLPD) and not sync.
>
> I try install on CentOS and Scientific Linux same problems
>


Hi, can you please share exact errors you are seeing and log collector or
SOS reports from affected hosts?




___
> 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/3F2K3P727X7OYEKRPR5S7JWTWUO62TVK/
>
___
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/JTLZHI5PBLK5HGRJZ3ZBTFDLXLGEK5X2/

[ovirt-users] Changing CPU type in oVirt Cluster 4.2

[Juhani Rautiainen]

Hi!

I made two node oVirt cluster with self hosted engine. It's running top of
oVirt Node 4.2. Hardware is built on AMD Epyc processors. I just noticed
that "Clusters"-view warns that I have AMD Opteron G3 as CPU type and it
will not supported in the future. Didn't check this during installation so
it probably came automatically. But question is how can I change this? I
get warning 'Error while executing action: Cannot change Cluster CPU to
higher CPU type when there are active Hosts with lower CPU type.'. I saw
old thread from 2016 where it was suggested that you change value straight
to db. Put that seems bit dangerous. Is there any other way to solve this
problem?

Thanks,
Juhani
-- 
Juhani Rautiainen   jra...@iki.fi
___
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/RDHS6WDZZKDVDDMFICPYJYN3BI454RWR/

[ovirt-users] Re: ovirt-sdk_external network add

[ada per]

Perfect! Thanks!!! 


On Thu, 31 Jan 2019, 11:37 Dominik Holler  On Thu, 31 Jan 2019 10:52:21 +0200
> ada per  wrote:
>
> > Thank you for your reply,
> >
> > Unfortunately i check all documentation and i  cant seem to find the
> > cloud name that is generated by default from ovirt for openstack
> > instances. I tried the hostname i used,  the provider name etc but
> > nothing seems to work
> >
>
> The configuration if the python module 'openstack' is documented in
>
> https://docs.openstack.org/python-openstackclient/pike/configuration/index.html
> e.g. a file clouds.yaml in the working directory with content
> similar to:
> clouds:
>   ovirt:
> auth:
>   auth_url: https://0.0.0.0:35357/v2.0
>   password: '123456'
>   username: admin@internal
> verify: false
>
> should do the trick.
> Alternatively the configuration could be provided by the envoronment
> variables: OS_USERNAME, OS_PASSWORD, OS_AUTH_URL
> and OS_CACERT.
>
> > On Wed, Jan 30, 2019 at 4:34 PM Dominik Holler 
> > wrote:
> >
> > > On Wed, 30 Jan 2019 16:25:02 +0200
> > > ada per  wrote:
> > >
> > > > Just something i noticed with the removal of external logical
> > > > networks script:
> > > >
> > > > > > network_service = networks_service.network_service(network.id)
> > > > > > network_service.remove()
> > > >
> > > > it only removes the network from the network list , it does not
> > > > remove it from the external provider.
> > >
> > >
> > > Sorry, I did not mention this.
> > > The network has to removed on the external provider manually, e.g.:
> > > import openstack
> > > cloud = openstack.connect(cloud='ovirt')
> > > cloud.delete_network('ext_net')
> > >
> > >
> > >
> > > > And for that reason when im trying to recreate an external network
> > > > with the *same
> > > > name* as the previously removed one it comes up with error:
> > > > ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail
> > > > is "[Failed to communicate with the external provider, see log for
> > > > additional details.]". HTTP response code is 400
> > > >
> > > > Is it a bug? How can it be resolved?
> > > >
> > > > On Tue, Jan 29, 2019 at 1:59 PM Dominik Holler
> > > >  wrote:
> > > >
> > > > > On Tue, 29 Jan 2019 13:08:06 +0200
> > > > > ada per  wrote:
> > > > >
> > > > > > thank you!!
> > > > > >
> > > > > > Is there any other method to use the network name instead of
> > > > > > id? if not its fine, i ll  use the list networks first and
> > > > > > then match the ids with the names and delete accordingly
> > > > > >
> > > > >
> > > > > I am not aware.
> > > > > If you want to have more luxury, I recommend to use the ovirt_*
> > > > > ansible roles.
> > > > >
> > > > > > On Tue, Jan 29, 2019 at 12:46 PM Dominik Holler
> > > > > >  wrote:
> > > > > >
> > > > > > > On Tue, 29 Jan 2019 12:23:32 +0200
> > > > > > > ada per  wrote:
> > > > > > >
> > > > > > > > Hello again,
> > > > > > > >
> > > > > > > > And how about to delete a logical network?
> > > > > > > > as remove option is not available in:
> > > > > > > > system_service().networks_service()
> > > > > > > >
> > > > > > >
> > > > > > > network_service =
> > > > > > > networks_service.network_service(network.id)
> > > > > > > network_service.remove()
> > > > > > >
> > > > > > > > On Mon, Jan 28, 2019 at 7:01 PM Dominik Holler
> > > > > > > >  wrote:
> > > > > > > >
> > > > > > > > > On Mon, 28 Jan 2019 16:34:30 -
> > > > > > > > > "ada per"  wrote:
> > > > > > > > >
> > > > > > > > > > Hello everyone,
> > > > > > > > > > I  have the following script,
> > > > > > > > > > i ve been looking in ovirt-sdk but i cannot seem to
> > > > > > > > > > find the proper way of adding an external provider
> > > > > > > > > > network under ovirt-ovn I manage to add logical
> > > > > > > > > > networks and vlans but no luck in external provider.
> > > > > > > > > >
> > > > > > > > > > Any advice is appreciated
> > > > > > > > > >
> > > > > > > > > > network = networks_service.add(
> > > > > > > > > > network=types.Network(
> > > > > > > > > > name='ext_net',
> > > > > > > > > > description='Testing network',
> > > > > > > > > > data_center=types.DataCenter(
> > > > > > > > > > name='Default'
> > > > > > > > > > ),
> > > > > > > > > >  usages=[types.NetworkUsage.VM],
> > > > > > > > > >  external_provider='ovirt-provider-ovn',
> > > > > > > > > > -->i know this part is wrong what is it supposed to be
> > > > > > > > > > called? ),
> > > > > > > > >
> > > > > > > > > external_provider=types.OpenStackNetworkProvider(
> > > > > > > > > id=provider.id
> > > > > > > > > )
> > > > > > > > >
> > > > > > > > > please find a full example script in
> > > > > > > > >
> > > > >
> https://gist.github.com/dominikholler/be7286931c0ea26b14965a5f91783cd4
> > > > > > > > >
> > > > > > > > > > ___
> > > > > > > > > > Users mailing list -- users@ovirt.org
> > > > > > > > 

[ovirt-users] Re: engine-iso-uploader very slow

[Tommaso M]

Hi Sandro, and thank you, my sos report : https://bit.ly/2MJleA0

bye
___
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/UI6TL4JYILYMGK4YSZYO6M46OFFRPRDJ/

[ovirt-users] Re: ovirt-sdk_external network add

[Dominik Holler]

On Thu, 31 Jan 2019 10:52:21 +0200
ada per  wrote:

> Thank you for your reply,
> 
> Unfortunately i check all documentation and i  cant seem to find the
> cloud name that is generated by default from ovirt for openstack
> instances. I tried the hostname i used,  the provider name etc but
> nothing seems to work
> 

The configuration if the python module 'openstack' is documented in
https://docs.openstack.org/python-openstackclient/pike/configuration/index.html
e.g. a file clouds.yaml in the working directory with content
similar to:
clouds:
  ovirt:
auth:
  auth_url: https://0.0.0.0:35357/v2.0
  password: '123456'
  username: admin@internal
verify: false

should do the trick.
Alternatively the configuration could be provided by the envoronment
variables: OS_USERNAME, OS_PASSWORD, OS_AUTH_URL
and OS_CACERT.

> On Wed, Jan 30, 2019 at 4:34 PM Dominik Holler 
> wrote:
> 
> > On Wed, 30 Jan 2019 16:25:02 +0200
> > ada per  wrote:
> >
> > > Just something i noticed with the removal of external logical
> > > networks script:
> > >
> > > > > network_service = networks_service.network_service(network.id)
> > > > > network_service.remove()
> > >
> > > it only removes the network from the network list , it does not
> > > remove it from the external provider.
> >
> >
> > Sorry, I did not mention this.
> > The network has to removed on the external provider manually, e.g.:
> > import openstack
> > cloud = openstack.connect(cloud='ovirt')
> > cloud.delete_network('ext_net')
> >
> >
> >
> > > And for that reason when im trying to recreate an external network
> > > with the *same
> > > name* as the previously removed one it comes up with error:
> > > ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail
> > > is "[Failed to communicate with the external provider, see log for
> > > additional details.]". HTTP response code is 400
> > >
> > > Is it a bug? How can it be resolved?
> > >
> > > On Tue, Jan 29, 2019 at 1:59 PM Dominik Holler
> > >  wrote:
> > >
> > > > On Tue, 29 Jan 2019 13:08:06 +0200
> > > > ada per  wrote:
> > > >
> > > > > thank you!!
> > > > >
> > > > > Is there any other method to use the network name instead of
> > > > > id? if not its fine, i ll  use the list networks first and
> > > > > then match the ids with the names and delete accordingly
> > > > >
> > > >
> > > > I am not aware.
> > > > If you want to have more luxury, I recommend to use the ovirt_*
> > > > ansible roles.
> > > >
> > > > > On Tue, Jan 29, 2019 at 12:46 PM Dominik Holler
> > > > >  wrote:
> > > > >
> > > > > > On Tue, 29 Jan 2019 12:23:32 +0200
> > > > > > ada per  wrote:
> > > > > >
> > > > > > > Hello again,
> > > > > > >
> > > > > > > And how about to delete a logical network?
> > > > > > > as remove option is not available in:
> > > > > > > system_service().networks_service()
> > > > > > >
> > > > > >
> > > > > > network_service =
> > > > > > networks_service.network_service(network.id)
> > > > > > network_service.remove()
> > > > > >
> > > > > > > On Mon, Jan 28, 2019 at 7:01 PM Dominik Holler
> > > > > > >  wrote:
> > > > > > >
> > > > > > > > On Mon, 28 Jan 2019 16:34:30 -
> > > > > > > > "ada per"  wrote:
> > > > > > > >
> > > > > > > > > Hello everyone,
> > > > > > > > > I  have the following script,
> > > > > > > > > i ve been looking in ovirt-sdk but i cannot seem to
> > > > > > > > > find the proper way of adding an external provider
> > > > > > > > > network under ovirt-ovn I manage to add logical
> > > > > > > > > networks and vlans but no luck in external provider.
> > > > > > > > >
> > > > > > > > > Any advice is appreciated
> > > > > > > > >
> > > > > > > > > network = networks_service.add(
> > > > > > > > > network=types.Network(
> > > > > > > > > name='ext_net',
> > > > > > > > > description='Testing network',
> > > > > > > > > data_center=types.DataCenter(
> > > > > > > > > name='Default'
> > > > > > > > > ),
> > > > > > > > >  usages=[types.NetworkUsage.VM],
> > > > > > > > >  external_provider='ovirt-provider-ovn',
> > > > > > > > > -->i know this part is wrong what is it supposed to be
> > > > > > > > > called? ),
> > > > > > > >
> > > > > > > > external_provider=types.OpenStackNetworkProvider(
> > > > > > > > id=provider.id
> > > > > > > > )
> > > > > > > >
> > > > > > > > please find a full example script in
> > > > > > > >
> > > > https://gist.github.com/dominikholler/be7286931c0ea26b14965a5f91783cd4
> > > > > > > >
> > > > > > > > > ___
> > > > > > > > > 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:
> > > > > > > > >

[ovirt-users] Re: ovirt-sdk_external network add

[ada per]

Thank you for your reply,

Unfortunately i check all documentation and i  cant seem to find the cloud
name that is generated by default from ovirt for openstack instances.
I tried the hostname i used,  the provider name etc but nothing seems to
work

On Wed, Jan 30, 2019 at 4:34 PM Dominik Holler  wrote:

> On Wed, 30 Jan 2019 16:25:02 +0200
> ada per  wrote:
>
> > Just something i noticed with the removal of external logical networks
> > script:
> >
> > > > network_service = networks_service.network_service(network.id)
> > > > network_service.remove()
> >
> > it only removes the network from the network list , it does not
> > remove it from the external provider.
>
>
> Sorry, I did not mention this.
> The network has to removed on the external provider manually, e.g.:
> import openstack
> cloud = openstack.connect(cloud='ovirt')
> cloud.delete_network('ext_net')
>
>
>
> > And for that reason when im trying to recreate an external network
> > with the *same
> > name* as the previously removed one it comes up with error:
> > ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is
> > "[Failed to communicate with the external provider, see log for
> > additional details.]". HTTP response code is 400
> >
> > Is it a bug? How can it be resolved?
> >
> > On Tue, Jan 29, 2019 at 1:59 PM Dominik Holler 
> > wrote:
> >
> > > On Tue, 29 Jan 2019 13:08:06 +0200
> > > ada per  wrote:
> > >
> > > > thank you!!
> > > >
> > > > Is there any other method to use the network name instead of id?
> > > > if not its fine, i ll  use the list networks first and then match
> > > > the ids with the names and delete accordingly
> > > >
> > >
> > > I am not aware.
> > > If you want to have more luxury, I recommend to use the ovirt_*
> > > ansible roles.
> > >
> > > > On Tue, Jan 29, 2019 at 12:46 PM Dominik Holler
> > > >  wrote:
> > > >
> > > > > On Tue, 29 Jan 2019 12:23:32 +0200
> > > > > ada per  wrote:
> > > > >
> > > > > > Hello again,
> > > > > >
> > > > > > And how about to delete a logical network?
> > > > > > as remove option is not available in:
> > > > > > system_service().networks_service()
> > > > > >
> > > > >
> > > > > network_service = networks_service.network_service(network.id)
> > > > > network_service.remove()
> > > > >
> > > > > > On Mon, Jan 28, 2019 at 7:01 PM Dominik Holler
> > > > > >  wrote:
> > > > > >
> > > > > > > On Mon, 28 Jan 2019 16:34:30 -
> > > > > > > "ada per"  wrote:
> > > > > > >
> > > > > > > > Hello everyone,
> > > > > > > > I  have the following script,
> > > > > > > > i ve been looking in ovirt-sdk but i cannot seem to find
> > > > > > > > the proper way of adding an external provider network
> > > > > > > > under ovirt-ovn I manage to add logical networks and
> > > > > > > > vlans but no luck in external provider.
> > > > > > > >
> > > > > > > > Any advice is appreciated
> > > > > > > >
> > > > > > > > network = networks_service.add(
> > > > > > > > network=types.Network(
> > > > > > > > name='ext_net',
> > > > > > > > description='Testing network',
> > > > > > > > data_center=types.DataCenter(
> > > > > > > > name='Default'
> > > > > > > > ),
> > > > > > > >  usages=[types.NetworkUsage.VM],
> > > > > > > >  external_provider='ovirt-provider-ovn',  -->i
> > > > > > > > know this part is wrong what is it supposed to be
> > > > > > > > called? ),
> > > > > > >
> > > > > > > external_provider=types.OpenStackNetworkProvider(
> > > > > > > id=provider.id
> > > > > > > )
> > > > > > >
> > > > > > > please find a full example script in
> > > > > > >
> > > https://gist.github.com/dominikholler/be7286931c0ea26b14965a5f91783cd4
> > > > > > >
> > > > > > > > ___
> > > > > > > > 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/LGGF7HZTMWDMCLNUATLHIXRYP7666TE4/
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
>
>
___
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/65P4CYKLOCTJ5VN7UG3GKCWWE62F7ZQH/