[ovirt-users] Re: reinstallation information

[Sandro Bonazzola]

Il giorno mer 23 gen 2019 alle ore 21:49  ha scritto:

> Hi Sandro,
> thanks for your reply and your council.
> You suggest me to upgrade my ovirt infrastructure.
> Can I upgrade the engine first and after the hosts and then can I
> reinstall using ovirt node 4.2.8 without remove it from engine? Thats right?
>

Yes, you can start with the engine and then reinstall hosts one by one
using oVirt Node 4.2.8. Once finished you can change cluster compatibility
level to 4.2 for consuming new features included in 4.2.


> I thought I could reinstall the hosts still in version 4.1 and upgrade
> later but I will follow your advice.
>

You can reinstall 4.1 hosts but 4.1 is not compatible with CentOS >= 7.5 so
you'll miss all the security fixes from the past year including meltdown
and spectre fixes.
I would recommend to use 4.2.8.


>
> Thank you for you help.
>
> nikkognt
> ___
> 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/2KMGOESF3DUKBLMKADV4W6MU5DBU3HYY/
>


-- 

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/2JQKNBBSAVGIAJTE3D2L4WDBEQEFQRTE/

[ovirt-users] Re: reinstallation information

[nikkognt]

Hi Sandro,
thanks for your reply and your council.
You suggest me to upgrade my ovirt infrastructure.
Can I upgrade the engine first and after the hosts and then can I reinstall 
using ovirt node 4.2.8 without remove it from engine? Thats right?
I thought I could reinstall the hosts still in version 4.1 and upgrade later 
but I will follow your advice.

Thank you for you help.

nikkognt
___
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/2KMGOESF3DUKBLMKADV4W6MU5DBU3HYY/

[ovirt-users] Re: oVirt 4.2.8 CPU Compatibility

[Vinícius Ferrão]

There’s any way to just put the CPUs on a legacy mode to simply use the 
servers, even with a low performance? We have a machine with an Opteron 6380 
and it appears to be the same case as Uwe reported. Our plan was to add this 
machine to the Datacenter in an isolated Cluster.

Thanks,

> On 23 Jan 2019, at 13:49, Lucie Leistnerova  wrote:
> 
> Hello Uwe,
> 
> On 1/23/19 9:21 AM, Uwe Laverenz wrote:
>> Hi,
>> 
>> Am Dienstag, den 22.01.2019, 15:46 +0100 schrieb Lucie Leistnerova:
>> 
>>>  Yes, it should be supported also in 4.2.8. According to Release
>>> notes for 4.2.7 this warning is related to 4.3 version.
>>> 
>>> https://www.ovirt.org/release/4.2.7/
>>> 
>>> BZ 1623259 Mark clusters with deprecated CPU type
>>> In the current release, for compatibility versions 4.2 and 4.3, a
>>> warning in the Cluster screen indicates that the CPU types currently
>>> used are not supported in 4.3. The warning enables the user to change
>>> the cluster CPU type to a supported CPU type.
>> Does this mean that I would not be able to install OVirt 4.3 on
>> machines with Opteron 6174 cpu? Or would I just get a warning?
>> 
>> I was thinking of recycling our old DL385 machines for an OVirt/Gluster
>> testing lab. :)
> 
> As I understand it, you won't be able to add such host to cluster with 
> compatibility version 4.3.
> So after engine upgrade to 4.3, old cluster and hosts will still work. Until 
> you will need to update also cluster compatibility version to 4.3
> 
>> cu,
>> Uwe
>> 
>> ___
>> 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/H5OCE7Y53RZ2WEOCCU77PBV7DZTTHZTR/
> Best regards,
> 
> -- 
> Lucie Leistnerova
> Quality Engineer, QE Cloud, RHVM
> Red Hat EMEA
> 
> IRC: lleistne @ #rhev-qe
> ___
> 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/ZSLZRQGOAGN5TK4NZFQAA5YGINRBW23T/
___
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/F65QRWSOLRVPUO52XJCMLDILS7A3ZUM4/

[ovirt-users] Re: Q: Is it safe to execute on node "saslpasswd2 -a libvirt username" ?

[Darrell Budic]

I’ve done it with no ill effects. Can be useful for troubleshooting or clearing 
a stuck VM if the engine is down, but I don’t recommend doing much with it if 
your engine is up and running.


> On Jan 23, 2019, at 11:27 AM, Andrei Verovski  wrote:
> 
> Hi !
> 
> Is it safe to execute on oVirt node this command ?
> saslpasswd2 -a libvirt username
> 
> Its a production environment, screwing up anything is not an option.
> I have no idea how VDSM interacts with libvirt, so not sure about this.
> 
> Thanks in advance
> Andrei
> ___
> 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/YWQUXSQ7F2WOHX3ZUXBQVHOB4KRBFJAO/
___
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/VOLTTM5PNIQJRYHYGNG7XH6YCW6MR227/

[ovirt-users] Re: Host non-responsive after yum update CentOS7/Ovirt3.6

[Николаев Алексей]

oVirt 3.6 support and work well only on node with CentOS 7.3 or oVirt Node NG 4.1. I recommend using with oVirt 3.6 only CentOS 7.3 vault repo. http://vault.centos.org/7.3.1611/  23.01.2019, 19:29, "Sandro Bonazzola" :  Il giorno mar 1 gen 2019 alle ore 03:26  ha scritto:Hi, I working on a CentOS7 based Ovirt 3.6 system (ovirt-engine/db on one machine, two separate ovirt vm hosts) which has been running fine but mostly ignored for 2-3 of years.  Recently it was decided to update the OS as it was far behind on security updates, so one host was put into maintenance mode, yum update'd, rebooted, and then it was attempted to take out of maintenance mode but it's "non-responsive" now. Hi, please note oVirt 3.6 is no longer supported.While waiting for 4.3 I would recommend to replace the non-responsive node with an oVirt 4.2.8 + CentOS 7.6 or oVirt Node 4.2.8 and plan to upgrade the whole data center.If I look in /var/log/ovirt-engine/engine.log on the engine machine I see for this host (vmserver2):"ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-36) [2bc0978d] Command 'GetCapabilitiesVDSCommand(HostName = vmserver2, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='6725086f-42c0-40eb-91f1-0f2411ea9432', vds='Host[vmserver2,6725086f-42c0-40eb-91f1-0f2411ea9432]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed"  and thereafter more errors.  This keep repeating in the log.In the Ovirt GUI I see multiple occurrences of log entries for the problem host:"vmserver2...command failed: Vds timeout occurred""vmserver2...command failed: Heartbeat exceeded""vmserver2...command failed: internal error: Unknown CPU model Broadwell-noTSX-IBRS"Firewall rules look identical to the host which is working normally but has not been updated.Any thoughts about how to fix or further troubleshoot this?___Users mailing list -- users@ovirt.orgTo unsubscribe send an email to users-le...@ovirt.orgPrivacy 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/HVP2YCIYGSFN7OCDOYWIFX2CDN4LTJBR/  --SANDRO BONAZZOLAMANAGER, SOFTWARE ENGINEERING, EMEA R RHVRed Hat EMEAsbona...@redhat.com   ,___Users mailing list -- users@ovirt.orgTo unsubscribe send an email to users-le...@ovirt.orgPrivacy 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/HTSLJ4CZSUS5GTVZT22475V7URODR3KR/___
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/RZJVFLTKSZMVULFDMPB5CKXTQPX26LM7/

[ovirt-users] Q: Is it safe to execute on node "saslpasswd2 -a libvirt username" ?

[Andrei Verovski]

Hi !

Is it safe to execute on oVirt node this command ?
saslpasswd2 -a libvirt username

Its a production environment, screwing up anything is not an option.
I have no idea how VDSM interacts with libvirt, so not sure about this.

Thanks in advance
Andrei
___
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/YWQUXSQ7F2WOHX3ZUXBQVHOB4KRBFJAO/

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

[Simone Tiraboschi]

On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth 
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 
> 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 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 

[ovirt-users] Re: Hosted Engine VM and Storage not showing up

[Simone Tiraboschi]

On Wed, Jan 23, 2019 at 5:38 PM Vinícius Ferrão 
wrote:

>
>
> On 23 Jan 2019, at 14:33, Simone Tiraboschi  wrote:
>
>
>
> On Wed, Jan 23, 2019 at 5:27 PM Vinícius Ferrão 
> wrote:
>
>> Simone, may I up this thread.
>>
>> I will request the RFE on bugzilla. I just need some time to do this.
>>
>> But I have another question on this issue. In a case of an already
>> deployed oVirt installation with this bug. There’s a way to fix it?
>> Production VMs are running and I would like to know if this can be fixed
>> without interrupting the VMs.
>>
>> I was thinking on getting a backup of the bugged SHE VM with
>> hosted-engine command and then trying to restore it with
>> ovirt-hosted-engine-setup with the Ansible backend. But I’m not sure if
>> this will work.
>>
>
> Yes, it will.
> You can also use that tool to migrate from bare metal to hosted-engine and
> so on.
>
>
> Thank you Simone!!!
>
> So I will get the backup from the broken HE and then redeploy it using the
> backup with the Ansible backend. Rewriting just to be sure.
>

Yes, it sounds like a good plan.


>
>
>
>>
>> If not, there’s a way to at least keep the VMs running and redeploy the
>> engine from the ground without restoring the backup?
>>
>> Thanks!
>>
>> Sent from my iPhone
>>
>> On 8 Jan 2019, at 14:49, Simone Tiraboschi  wrote:
>>
>>
>>
>> On Tue, Jan 8, 2019 at 5:31 PM Vinícius Ferrão 
>> wrote:
>>
>>> Hello,
>>>
>>> On 8 Jan 2019, at 11:20, Simone Tiraboschi  wrote:
>>>
>>>
>>>
>>> On Mon, Jan 7, 2019 at 10:43 PM Vinícius Ferrão <
>>> fer...@versatushpc.com.br> wrote:
>>>
 Simone,

 I have additional findings: Ansible was failing because I was defined
 the option without-password on SSH root access. So it fails with an
 authentication failure error during the deployment.

 After allowing root access over SSH the hosted engine deployement with
 Ansible worked.

 Now I will check if everything else is working fine.

 Maybe I need to open a bug on Bugzilla on this issue?

>>>
>>> Ok, from the logs I see that you set without-password and you correctly
>>> entered a public ssh key when requested.
>>> But then ansible failed to authenticate to the engine VM, as root, with
>>> that password.
>>> So, if you are sure that the correspondent private key was available in
>>> the right place and with the right permissions, please open a bug.
>>>
>>>
>>> Hello Simone, just to be sure. The private key was always on my personal
>>> computer. It was never on the oVirt Node.
>>>
>>> For years I’ve deployed oVirt this way and it worked as expected.
>>>
>>> So if the new behaviour demands a private key on the hypervisor this
>>> makes the deployment different.
>>>
>>> The purpose of the key and enabling root ssh without-password is to
>>> enforce the security of the hosted engine, right? Not the security between
>>> the hypervisor and hosted engine during the deployment phase. So the
>>> setting without-password should be set at the end of hosted engine
>>> deployment.
>>>
>>> If this assumptions are correct I will proceed to the ticket on bugzilla.
>>>
>>
>> Now the whole flow, including engine-setup on the engine VM to create the
>> DB and so on, is executed with ansible and this requires ansible, executed
>> on the first host, to be able to authenticate to the engine VM over ssh.
>> Currently the setup is configuring the root password and/or the root ssh
>> pub key on the first boot with cloud-init and so this implicitly requires
>> the user to enable password authentication or to configure the host to be
>> able to access the engine VM with an ssh key.
>>
>> What you are proposing requires the setup to inject a temporary key
>> generated on the fly and remove it at the end or configure without-password
>> only after the deployment.
>> It makes sense to me but on my opinion it's more an RFE than a real bug.
>> Feel free to file it.
>>
>>
>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>>

 Thanks,

 On 7 Jan 2019, at 15:22, Vinícius Ferrão 
 wrote:

 Hello,

 On 7 Jan 2019, at 12:52, Simone Tiraboschi  wrote:



 On Mon, Jan 7, 2019 at 2:03 PM Vinícius Ferrão <
 fer...@versatushpc.com.br> wrote:

> Hello Simone,
>
> Sent from my iPhone
>
> On 7 Jan 2019, at 07:11, Simone Tiraboschi 
> wrote:
>
>
>
> On Sun, Jan 6, 2019 at 5:31 PM  wrote:
>
>> Hello,
>>
>> I’ve a new oVirt installation using oVirt 4.2.7.1 Node and after
>> deploying the hosted engine it does not show up on the interface even 
>> after
>> adding the first storage.
>>
>> The Datacenter is up but the engine VM and the engine storage does
>> not appear.
>>
>> I have the following message repeated constantly on /var/log/messages:
>>
>> Jan  4 20:17:30 ovirt1 journal: ovirt-ha-agent
>> ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR
>> Unable to identify the OVF_STORE 

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

[Douglas Duckworth]

Hi Simone

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

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

[ovirt-users] Re: Hosted Engine VM and Storage not showing up

[Vinícius Ferrão]

> On 23 Jan 2019, at 14:33, Simone Tiraboschi  wrote:
> 
> 
> 
> On Wed, Jan 23, 2019 at 5:27 PM Vinícius Ferrão  > wrote:
> Simone, may I up this thread.
> 
> I will request the RFE on bugzilla. I just need some time to do this.
> 
> But I have another question on this issue. In a case of an already deployed 
> oVirt installation with this bug. There’s a way to fix it? Production VMs are 
> running and I would like to know if this can be fixed without interrupting 
> the VMs.
> 
> I was thinking on getting a backup of the bugged SHE VM with hosted-engine 
> command and then trying to restore it with ovirt-hosted-engine-setup with the 
> Ansible backend. But I’m not sure if this will work.
> 
> Yes, it will.
> You can also use that tool to migrate from bare metal to hosted-engine and so 
> on.

Thank you Simone!!!

So I will get the backup from the broken HE and then redeploy it using the 
backup with the Ansible backend. Rewriting just to be sure.

>  
> 
> If not, there’s a way to at least keep the VMs running and redeploy the 
> engine from the ground without restoring the backup?
> 
> Thanks!
> 
> Sent from my iPhone
> 
> On 8 Jan 2019, at 14:49, Simone Tiraboschi  > wrote:
> 
>> 
>> 
>> On Tue, Jan 8, 2019 at 5:31 PM Vinícius Ferrão > > wrote:
>> Hello,
>> 
>>> On 8 Jan 2019, at 11:20, Simone Tiraboschi >> > wrote:
>>> 
>>> 
>>> 
>>> On Mon, Jan 7, 2019 at 10:43 PM Vinícius Ferrão >> > wrote:
>>> Simone,
>>> 
>>> I have additional findings: Ansible was failing because I was defined the 
>>> option without-password on SSH root access. So it fails with an 
>>> authentication failure error during the deployment.
>>> 
>>> After allowing root access over SSH the hosted engine deployement with 
>>> Ansible worked.
>>> 
>>> Now I will check if everything else is working fine.
>>> 
>>> Maybe I need to open a bug on Bugzilla on this issue?
>>> 
>>> Ok, from the logs I see that you set without-password and you correctly 
>>> entered a public ssh key when requested.
>>> But then ansible failed to authenticate to the engine VM, as root, with 
>>> that password.
>>> So, if you are sure that the correspondent private key was available in the 
>>> right place and with the right permissions, please open a bug.
>> 
>> Hello Simone, just to be sure. The private key was always on my personal 
>> computer. It was never on the oVirt Node.
>> 
>> For years I’ve deployed oVirt this way and it worked as expected.
>> 
>> So if the new behaviour demands a private key on the hypervisor this makes 
>> the deployment different. 
>> 
>> The purpose of the key and enabling root ssh without-password is to enforce 
>> the security of the hosted engine, right? Not the security between the 
>> hypervisor and hosted engine during the deployment phase. So the setting 
>> without-password should be set at the end of hosted engine deployment.
>> 
>> If this assumptions are correct I will proceed to the ticket on bugzilla.
>> 
>> Now the whole flow, including engine-setup on the engine VM to create the DB 
>> and so on, is executed with ansible and this requires ansible, executed on 
>> the first host, to be able to authenticate to the engine VM over ssh.
>> Currently the setup is configuring the root password and/or the root ssh pub 
>> key on the first boot with cloud-init and so this implicitly requires the 
>> user to enable password authentication or to configure the host to be able 
>> to access the engine VM with an ssh key.
>> 
>> What you are proposing requires the setup to inject a temporary key 
>> generated on the fly and remove it at the end or configure without-password 
>> only after the deployment.
>> It makes sense to me but on my opinion it's more an RFE than a real bug.
>> Feel free to file it.
>> 
>>  
>> 
>> Thanks, 
>> 
>>> 
>>>  
>>> 
>>> Thanks,
>>> 
 On 7 Jan 2019, at 15:22, Vinícius Ferrão >>> > wrote:
 
 Hello,
 
> On 7 Jan 2019, at 12:52, Simone Tiraboschi  > wrote:
> 
> 
> 
> On Mon, Jan 7, 2019 at 2:03 PM Vinícius Ferrão  > wrote:
> Hello Simone,
> 
> Sent from my iPhone
> 
> On 7 Jan 2019, at 07:11, Simone Tiraboschi  > wrote:
> 
>> 
>> 
>> On Sun, Jan 6, 2019 at 5:31 PM > > wrote:
>> Hello,
>> 
>> I’ve a new oVirt installation using oVirt 4.2.7.1 Node and after 
>> deploying the hosted engine it does not show up on the interface even 
>> after adding the first storage.
>> 
>> The Datacenter is up but the engine VM and the engine storage does not 
>> appear.
>> 
>> I have the following message repeated constantly on /var/log/messages:
>> 
>> Jan  4 20:17:30 ovirt1 

[ovirt-users] Migrating Hosted Engine environment from untagged to LACP bonded interfaces with tagged ovirtmgmt network

[Bernhard Dick]

Hi,

I have an oVirt 4.2 environment running with the engine in hosted engine 
state. We are now going to change our whole setup migrating to 
redundancy on switch side and using a different VLAN for the ovirt 
management traffic.


Currently all host and management-traffic is running untagged on one 
network interface on all of our hosts and we want to change this to be 
VLAN-tagged inside LACP-Bonds (each bond containing two network 
interfaces) on all hosts. While changing the configuration for the VM 
networks should be straight forward as I can shutdown all VMs during the 
migration I'm asking how to handle this for the hosted engine VM and 
configuration. Is there any information how to do such a change?


  Regards
Bernhard
___
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/IXE5PEZFSS3KBXJK55UUWGBWCM7BRHSG/

[ovirt-users] Re: Hosted Engine VM and Storage not showing up

[Simone Tiraboschi]

On Wed, Jan 23, 2019 at 5:27 PM Vinícius Ferrão 
wrote:

> Simone, may I up this thread.
>
> I will request the RFE on bugzilla. I just need some time to do this.
>
> But I have another question on this issue. In a case of an already
> deployed oVirt installation with this bug. There’s a way to fix it?
> Production VMs are running and I would like to know if this can be fixed
> without interrupting the VMs.
>
> I was thinking on getting a backup of the bugged SHE VM with hosted-engine
> command and then trying to restore it with ovirt-hosted-engine-setup with
> the Ansible backend. But I’m not sure if this will work.
>

Yes, it will.
You can also use that tool to migrate from bare metal to hosted-engine and
so on.


>
> If not, there’s a way to at least keep the VMs running and redeploy the
> engine from the ground without restoring the backup?
>
> Thanks!
>
> Sent from my iPhone
>
> On 8 Jan 2019, at 14:49, Simone Tiraboschi  wrote:
>
>
>
> On Tue, Jan 8, 2019 at 5:31 PM Vinícius Ferrão 
> wrote:
>
>> Hello,
>>
>> On 8 Jan 2019, at 11:20, Simone Tiraboschi  wrote:
>>
>>
>>
>> On Mon, Jan 7, 2019 at 10:43 PM Vinícius Ferrão <
>> fer...@versatushpc.com.br> wrote:
>>
>>> Simone,
>>>
>>> I have additional findings: Ansible was failing because I was defined
>>> the option without-password on SSH root access. So it fails with an
>>> authentication failure error during the deployment.
>>>
>>> After allowing root access over SSH the hosted engine deployement with
>>> Ansible worked.
>>>
>>> Now I will check if everything else is working fine.
>>>
>>> Maybe I need to open a bug on Bugzilla on this issue?
>>>
>>
>> Ok, from the logs I see that you set without-password and you correctly
>> entered a public ssh key when requested.
>> But then ansible failed to authenticate to the engine VM, as root, with
>> that password.
>> So, if you are sure that the correspondent private key was available in
>> the right place and with the right permissions, please open a bug.
>>
>>
>> Hello Simone, just to be sure. The private key was always on my personal
>> computer. It was never on the oVirt Node.
>>
>> For years I’ve deployed oVirt this way and it worked as expected.
>>
>> So if the new behaviour demands a private key on the hypervisor this
>> makes the deployment different.
>>
>> The purpose of the key and enabling root ssh without-password is to
>> enforce the security of the hosted engine, right? Not the security between
>> the hypervisor and hosted engine during the deployment phase. So the
>> setting without-password should be set at the end of hosted engine
>> deployment.
>>
>> If this assumptions are correct I will proceed to the ticket on bugzilla.
>>
>
> Now the whole flow, including engine-setup on the engine VM to create the
> DB and so on, is executed with ansible and this requires ansible, executed
> on the first host, to be able to authenticate to the engine VM over ssh.
> Currently the setup is configuring the root password and/or the root ssh
> pub key on the first boot with cloud-init and so this implicitly requires
> the user to enable password authentication or to configure the host to be
> able to access the engine VM with an ssh key.
>
> What you are proposing requires the setup to inject a temporary key
> generated on the fly and remove it at the end or configure without-password
> only after the deployment.
> It makes sense to me but on my opinion it's more an RFE than a real bug.
> Feel free to file it.
>
>
>
>>
>> Thanks,
>>
>>
>>
>>
>>>
>>> Thanks,
>>>
>>> On 7 Jan 2019, at 15:22, Vinícius Ferrão 
>>> wrote:
>>>
>>> Hello,
>>>
>>> On 7 Jan 2019, at 12:52, Simone Tiraboschi  wrote:
>>>
>>>
>>>
>>> On Mon, Jan 7, 2019 at 2:03 PM Vinícius Ferrão <
>>> fer...@versatushpc.com.br> wrote:
>>>
 Hello Simone,

 Sent from my iPhone

 On 7 Jan 2019, at 07:11, Simone Tiraboschi  wrote:



 On Sun, Jan 6, 2019 at 5:31 PM  wrote:

> Hello,
>
> I’ve a new oVirt installation using oVirt 4.2.7.1 Node and after
> deploying the hosted engine it does not show up on the interface even 
> after
> adding the first storage.
>
> The Datacenter is up but the engine VM and the engine storage does not
> appear.
>
> I have the following message repeated constantly on /var/log/messages:
>
> Jan  4 20:17:30 ovirt1 journal: ovirt-ha-agent
> ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR
> Unable to identify the OVF_STORE volume, falling back to initial vm.conf.
> Please ensure you already added your first data domain for regular VMs
>
> What’s wrong? Am I doing something different?
>

 The import of external VM is broken in 4.2.7 as for
 https://bugzilla.redhat.com/show_bug.cgi?id=1649615
 It will be fixed with 4.2.8.

 In the mean time I strongly suggest to use the regular flow for
 hosted-engine deployment (simply skip --noansible option) since only the
 

[ovirt-users] Re: Hosted Engine VM and Storage not showing up

[Vinícius Ferrão]

Simone, may I up this thread.

I will request the RFE on bugzilla. I just need some time to do this.

But I have another question on this issue. In a case of an already deployed 
oVirt installation with this bug. There’s a way to fix it? Production VMs are 
running and I would like to know if this can be fixed without interrupting the 
VMs.

I was thinking on getting a backup of the bugged SHE VM with hosted-engine 
command and then trying to restore it with ovirt-hosted-engine-setup with the 
Ansible backend. But I’m not sure if this will work.

If not, there’s a way to at least keep the VMs running and redeploy the engine 
from the ground without restoring the backup?

Thanks!

Sent from my iPhone

> On 8 Jan 2019, at 14:49, Simone Tiraboschi  wrote:
> 
> 
> 
>> On Tue, Jan 8, 2019 at 5:31 PM Vinícius Ferrão  
>> wrote:
>> Hello,
>> 
>>> On 8 Jan 2019, at 11:20, Simone Tiraboschi  wrote:
>>> 
>>> 
>>> 
>>> On Mon, Jan 7, 2019 at 10:43 PM Vinícius Ferrão  
>>> wrote:
 Simone,
 
 I have additional findings: Ansible was failing because I was defined the 
 option without-password on SSH root access. So it fails with an 
 authentication failure error during the deployment.
 
 After allowing root access over SSH the hosted engine deployement with 
 Ansible worked.
 
 Now I will check if everything else is working fine.
 
 Maybe I need to open a bug on Bugzilla on this issue?
>>> 
>>> Ok, from the logs I see that you set without-password and you correctly 
>>> entered a public ssh key when requested.
>>> But then ansible failed to authenticate to the engine VM, as root, with 
>>> that password.
>>> So, if you are sure that the correspondent private key was available in the 
>>> right place and with the right permissions, please open a bug.
>> 
>> Hello Simone, just to be sure. The private key was always on my personal 
>> computer. It was never on the oVirt Node.
>> 
>> For years I’ve deployed oVirt this way and it worked as expected.
>> 
>> So if the new behaviour demands a private key on the hypervisor this makes 
>> the deployment different. 
>> 
>> The purpose of the key and enabling root ssh without-password is to enforce 
>> the security of the hosted engine, right? Not the security between the 
>> hypervisor and hosted engine during the deployment phase. So the setting 
>> without-password should be set at the end of hosted engine deployment.
>> 
>> If this assumptions are correct I will proceed to the ticket on bugzilla.
> 
> Now the whole flow, including engine-setup on the engine VM to create the DB 
> and so on, is executed with ansible and this requires ansible, executed on 
> the first host, to be able to authenticate to the engine VM over ssh.
> Currently the setup is configuring the root password and/or the root ssh pub 
> key on the first boot with cloud-init and so this implicitly requires the 
> user to enable password authentication or to configure the host to be able to 
> access the engine VM with an ssh key.
> 
> What you are proposing requires the setup to inject a temporary key generated 
> on the fly and remove it at the end or configure without-password only after 
> the deployment.
> It makes sense to me but on my opinion it's more an RFE than a real bug.
> Feel free to file it.
> 
>  
>> 
>> Thanks, 
>> 
>>> 
>>>  
 
 Thanks,
 
> On 7 Jan 2019, at 15:22, Vinícius Ferrão  
> wrote:
> 
> Hello,
> 
>> On 7 Jan 2019, at 12:52, Simone Tiraboschi  wrote:
>> 
>> 
>> 
>> On Mon, Jan 7, 2019 at 2:03 PM Vinícius Ferrão 
>>  wrote:
>>> Hello Simone,
>>> 
>>> Sent from my iPhone
>>> 
 On 7 Jan 2019, at 07:11, Simone Tiraboschi  wrote:
 
 
 
> On Sun, Jan 6, 2019 at 5:31 PM  wrote:
> Hello,
> 
> I’ve a new oVirt installation using oVirt 4.2.7.1 Node and after 
> deploying the hosted engine it does not show up on the interface even 
> after adding the first storage.
> 
> The Datacenter is up but the engine VM and the engine storage does 
> not appear.
> 
> I have the following message repeated constantly on /var/log/messages:
> 
> Jan  4 20:17:30 ovirt1 journal: ovirt-ha-agent 
> ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm 
> ERROR Unable to identify the OVF_STORE volume, falling back to 
> initial vm.conf. Please ensure you already added your first data 
> domain for regular VMs
> 
> What’s wrong? Am I doing something different?
 
 The import of external VM is broken in 4.2.7 as for 
 https://bugzilla.redhat.com/show_bug.cgi?id=1649615
 It will be fixed with 4.2.8.
 
 In the mean time I strongly suggest to use the regular flow for 
 hosted-engine deployment (simply skip --noansible option) since only 
 the 

[ovirt-users] Re: Host non-responsive after yum update CentOS7/Ovirt3.6

[Sandro Bonazzola]

Il giorno mar 1 gen 2019 alle ore 03:26  ha scritto:

> Hi, I working on a CentOS7 based Ovirt 3.6 system (ovirt-engine/db on one
> machine, two separate ovirt vm hosts) which has been running fine but
> mostly ignored for 2-3 of years.  Recently it was decided to update the OS
> as it was far behind on security updates, so one host was put into
> maintenance mode, yum update'd, rebooted, and then it was attempted to take
> out of maintenance mode but it's "non-responsive" now.
>

Hi, please note oVirt 3.6 is no longer supported.
While waiting for 4.3 I would recommend to replace the non-responsive node
with an oVirt 4.2.8 + CentOS 7.6 or oVirt Node 4.2.8 and plan to upgrade
the whole data center.





>
> If I look in /var/log/ovirt-engine/engine.log on the engine machine I see
> for this host (vmserver2):
>
> "ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler_Worker-36) [2bc0978d] Command
> 'GetCapabilitiesVDSCommand(HostName = vmserver2,
> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='6725086f-42c0-40eb-91f1-0f2411ea9432',
> vds='Host[vmserver2,6725086f-42c0-40eb-91f1-0f2411ea9432]'})' execution
> failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection
> failed"  and thereafter more errors.  This keep repeating in the log.
>
> In the Ovirt GUI I see multiple occurrences of log entries for the problem
> host:
>
> "vmserver2...command failed: Vds timeout occurred"
> "vmserver2...command failed: Heartbeat exceeded"
> "vmserver2...command failed: internal error: Unknown CPU model
> Broadwell-noTSX-IBRS"
>
> Firewall rules look identical to the host which is working normally but
> has not been updated.
>
> Any thoughts about how to fix or further troubleshoot 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/HVP2YCIYGSFN7OCDOYWIFX2CDN4LTJBR/
>


-- 

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/HTSLJ4CZSUS5GTVZT22475V7URODR3KR/

[ovirt-users] Re: latest pycurl 7.43 brokes ovirtsdk4

[Nathanaël Blanchet]

And the AWX embedded pycurl 7.43 also brakes the ovirt4.py dynamic 
inventory!


 [WARNING]: Unable to parse /opt/awx/embedded/lib/python2.7/site-
packages/awx/plugins/inventory/ovirt4.py as an inventory source

Le 23/01/2019 à 11:55, Nathanaël Blanchet a écrit :



Le 23/01/2019 à 09:27, Ondra Machacek a écrit :

On 1/22/19 5:54 PM, Nathanaël Blanchet wrote:

Hi all,

If anyone uses latest pycurl 7.43 provided by pip or ansible 
tower/awx, any ovirtsdk4 calling will issue with the log:


The full traceback is:
WARNING: The below traceback may *not* be related to the actual 
failure.
   File "/tmp/ansible_ovirt_auth_payload_L1HK9E/__main__.py", line 
202, in 

 import ovirtsdk4 as sdk
   File 
"/opt/awx/embedded/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", 
line 22, in 

 import pycurl

fatal: [localhost]: FAILED! => {
 "changed": false,
 "invocation": {
 "module_args": {
 "ca_file": null,
 "compress": true,
 "headers": null,
 "hostname": null,
 "insecure": true,
 "kerberos": false,
 "ovirt_auth": null,
 "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
 "state": "present",
 "timeout": 0,
 "token": null,
 "url": "https://acore.v100.abes.fr/ovirt-engine/api;,
 "username": "admin@internal"
 }
 },
 "msg": "ovirtsdk4 version 4.2.4 or higher is required for this 
module"

}

The only way is to set the version of pycurl with

pip install -U "pycurl == 7.19.0"

(Before this, in tower/awx, you should  create venv)


What's the version of AWX, where pycurl 7.43 is provided? I use latest
and I have 7.19. But anyway, I've tried to update to 7.43, and this 
worked for me with nss:


AWX 2.1.2
/opt/awx/embedded/lib64/python2.7/site-packages/pycurl-7.43.0.1.dist-info



$ source venv/awx/bin/activate
$ export PYCURL_SSL_LIBRARY=nss; pip install pycurl --compile 
--no-cache-dir

$ python -c 'import pycurl; print pycurl.version'
PycURL/7.43.0.2 libcurl/7.29.0 NSS/3.36 zlib/1.2.7 libidn/1.28 
libssh2/1.4.3


Yes, I've tried your trick and 7.43 works with the nss support like 
you say, but...


  * how can anyone guess he needs the nss library
  * it doesn't work out the box with the awx embedded  pycurl, so we
must use venv

So it should be good to compile the embedded awx pycurl to natively 
support nss, out of venv.






--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr  


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


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

___
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/5HQNARKGBHGP37C5TTRAR5WCUVG7DVIQ/

[ovirt-users] Re: reinstallation information

[Sandro Bonazzola]

Il giorno mer 23 gen 2019 alle ore 15:15  ha scritto:

> Hi,
> after a blackout one host of my ovirt not working properly. I tried to
> Reinstall it but ends with the following error "Failed to install Host ov1.
> Failed to execute stage 'Closing up': Failed to start service 'vdsmd'." I
> tried to start manually but it not start .
> Now, I would like to reinstall from iso ovirt node.
> After I put the host is in maintenance must I remove host from the cluster
> (Hosts -> host1 -> Remove) or I can reinstall without remove it?
> If I remore it from the cluster the network configurations I lose them or
> not?
> My ovirt version is oVirt Engine Version: 4.1.9.1-1.el7.centos.
>

Hi,
please note oVirt 4.1 is no longer supported. While waiting for 4.3 to be
released I would suggest to use oVirt Node 4.2.8 to replace the failing
node and start upgrading the remaining nodes and the engine as well.
You should be able to reinstall the host without removing it from the
cluster.
See
https://ovirt.org/documentation/admin-guide/chap-Hosts.html#reinstalling-hosts
for further information.

Thanks,
-- 

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/6M3S22LN4P5SMAQMQJ4PT4G5FNMWGKLL/

[ovirt-users] Re: Ovirt snapshot issues

[Elad Ben Aharon]

Hi,

Can you please provide engine.log and vdsm.log?

On Wed, Jan 23, 2019 at 5:41 PM Alex K  wrote:

> Hi all,
>
> I have ovirt 4.2.7, self-hosted on top gluster, with two servers.
> I have a specific VM which has encountered some snapshot issues.
> The engine lists 4 snapshots and when trying to delete one of them I get 
> "General
> command validation failure".
>
> The VM was being backed up periodically by a python script which was
> creating a snapshot -> clone -> export -> delete clone -> delete snapshot.
> There were times where the VM was complaining of some illegal snapshots
> following such backup procedures and I had to delete such illegal snapshots
> references from the engine DB (following some steps found online),
> otherwise I would not be able to start the VM if it was shut down. Seems
> though that this is not a clean process and leaves the underlying image of
> the VM in an inconsistent state in regards to its snapshots as when
> checking the backing chain of the image file I get:
>
> *b46d8efe-885b-4a68-94ca-e8f437566bee* (active VM)* ->*
> *b7673dca-6e10-4a0f-9885-1c91b86616af ->*
> *4f636d91-a66c-4d68-8720-d2736a3765df ->*
> 6826cb76-6930-4b53-a9f5-fdeb0e8012ac ->
> 61eea475-1135-42f4-b8d1-da6112946bac ->
> *604d84c3-8d5f-4bb6-a2b5-0aea79104e43 ->*
> 1e75898c-9790-4163-ad41-847cfe84db40 ->
> *cf8707f2-bf1f-4827-8dc2-d7e6ffcc3d43 ->*
> 3f54c98e-07ca-4810-82d8-cbf3964c7ce5 (raw image)
>
> The bold ones are the ones shown at engine GUI. The VM runs normally
> without issues.
> I was thinking if I could use qemu-img commit to consolidate and remove
> the snapshots that are not referenced from engine anymore. Any ideas from
> your side?
>
> Thanx,
> Alex
> ___
> 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/DDZXH5UG6QEH76A5EO4STZ4YV7RIQQ2I/
>


-- 

Elad Ben Aharon

ASSOCIATE MANAGER, RHV storage QE
___
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/UNNDDTHP3YI2WMFDODIXFFMKSTSMZBWW/

[ovirt-users] Re: oVirt 4.2.8 CPU Compatibility

[Lucie Leistnerova]

Hello Uwe,

On 1/23/19 9:21 AM, Uwe Laverenz wrote:

Hi,

Am Dienstag, den 22.01.2019, 15:46 +0100 schrieb Lucie Leistnerova:


  Yes, it should be supported also in 4.2.8. According to Release
notes for 4.2.7 this warning is related to 4.3 version.

https://www.ovirt.org/release/4.2.7/

BZ 1623259 Mark clusters with deprecated CPU type
In the current release, for compatibility versions 4.2 and 4.3, a
warning in the Cluster screen indicates that the CPU types currently
used are not supported in 4.3. The warning enables the user to change
the cluster CPU type to a supported CPU type.

Does this mean that I would not be able to install OVirt 4.3 on
machines with Opteron 6174 cpu? Or would I just get a warning?

I was thinking of recycling our old DL385 machines for an OVirt/Gluster
testing lab. :)


As I understand it, you won't be able to add such host to cluster with 
compatibility version 4.3.
So after engine upgrade to 4.3, old cluster and hosts will still work. 
Until you will need to update also cluster compatibility version to 4.3



cu,
Uwe

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

Best regards,

--
Lucie Leistnerova
Quality Engineer, QE Cloud, RHVM
Red Hat EMEA

IRC: lleistne @ #rhev-qe
___
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/ZSLZRQGOAGN5TK4NZFQAA5YGINRBW23T/

[ovirt-users] Ovirt snapshot issues

[Alex K]

Hi all,

I have ovirt 4.2.7, self-hosted on top gluster, with two servers.
I have a specific VM which has encountered some snapshot issues.
The engine lists 4 snapshots and when trying to delete one of them I
get "General
command validation failure".

The VM was being backed up periodically by a python script which was
creating a snapshot -> clone -> export -> delete clone -> delete snapshot.
There were times where the VM was complaining of some illegal snapshots
following such backup procedures and I had to delete such illegal snapshots
references from the engine DB (following some steps found online),
otherwise I would not be able to start the VM if it was shut down. Seems
though that this is not a clean process and leaves the underlying image of
the VM in an inconsistent state in regards to its snapshots as when
checking the backing chain of the image file I get:

*b46d8efe-885b-4a68-94ca-e8f437566bee* (active VM)* ->*
*b7673dca-6e10-4a0f-9885-1c91b86616af ->*
*4f636d91-a66c-4d68-8720-d2736a3765df ->*
6826cb76-6930-4b53-a9f5-fdeb0e8012ac ->
61eea475-1135-42f4-b8d1-da6112946bac ->
*604d84c3-8d5f-4bb6-a2b5-0aea79104e43 ->*
1e75898c-9790-4163-ad41-847cfe84db40 ->
*cf8707f2-bf1f-4827-8dc2-d7e6ffcc3d43 ->*
3f54c98e-07ca-4810-82d8-cbf3964c7ce5 (raw image)

The bold ones are the ones shown at engine GUI. The VM runs normally
without issues.
I was thinking if I could use qemu-img commit to consolidate and remove the
snapshots that are not referenced from engine anymore. Any ideas from your
side?

Thanx,
Alex
___
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/DDZXH5UG6QEH76A5EO4STZ4YV7RIQQ2I/

[ovirt-users] reinstallation information

[nikkognt]

Hi, 
after a blackout one host of my ovirt not working properly. I tried to 
Reinstall it but ends with the following error "Failed to install Host ov1. 
Failed to execute stage 'Closing up': Failed to start service 'vdsmd'." I tried 
to start manually but it not start .
Now, I would like to reinstall from iso ovirt node.
After I put the host is in maintenance must I remove host from the cluster 
(Hosts -> host1 -> Remove) or I can reinstall without remove it?
If I remore it from the cluster the network configurations I lose them or not?
My ovirt version is oVirt Engine Version: 4.1.9.1-1.el7.centos.
___
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/Z2MA6DVBSPXML3OYRXENIREXPEDXKPJP/

[ovirt-users] Re: latest pycurl 7.43 brokes ovirtsdk4

[Nathanaël Blanchet]

Le 23/01/2019 à 09:27, Ondra Machacek a écrit :

On 1/22/19 5:54 PM, Nathanaël Blanchet wrote:

Hi all,

If anyone uses latest pycurl 7.43 provided by pip or ansible 
tower/awx, any ovirtsdk4 calling will issue with the log:


The full traceback is:
WARNING: The below traceback may *not* be related to the actual failure.
   File "/tmp/ansible_ovirt_auth_payload_L1HK9E/__main__.py", line 
202, in 

 import ovirtsdk4 as sdk
   File 
"/opt/awx/embedded/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", 
line 22, in 

 import pycurl

fatal: [localhost]: FAILED! => {
 "changed": false,
 "invocation": {
 "module_args": {
 "ca_file": null,
 "compress": true,
 "headers": null,
 "hostname": null,
 "insecure": true,
 "kerberos": false,
 "ovirt_auth": null,
 "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
 "state": "present",
 "timeout": 0,
 "token": null,
 "url": "https://acore.v100.abes.fr/ovirt-engine/api;,
 "username": "admin@internal"
 }
 },
 "msg": "ovirtsdk4 version 4.2.4 or higher is required for this 
module"

}

The only way is to set the version of pycurl with

pip install -U "pycurl == 7.19.0"

(Before this, in tower/awx, you should  create venv)


What's the version of AWX, where pycurl 7.43 is provided? I use latest
and I have 7.19. But anyway, I've tried to update to 7.43, and this 
worked for me with nss:


AWX 2.1.2
/opt/awx/embedded/lib64/python2.7/site-packages/pycurl-7.43.0.1.dist-info



$ source venv/awx/bin/activate
$ export PYCURL_SSL_LIBRARY=nss; pip install pycurl --compile 
--no-cache-dir

$ python -c 'import pycurl; print pycurl.version'
PycURL/7.43.0.2 libcurl/7.29.0 NSS/3.36 zlib/1.2.7 libidn/1.28 
libssh2/1.4.3


Yes, I've tried your trick and 7.43 works with the nss support like you 
say, but...


 * how can anyone guess he needs the nss library
 * it doesn't work out the box with the awx embedded  pycurl, so we
   must use venv

So it should be good to compile the embedded awx pycurl to natively 
support nss, out of venv.






--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

[ovirt-users] Adding host with local-storage VMs configured

[Callum Smith]

Dear All,

We’re in a world where we had to recover from outage by installing a clean 
hosted engine and importing VMs from storage. We do, however, have a host that 
is configured for local-storage and has a VM running on it. What is the best 
way to re-introduce this host to a new hosted-engine with minimal outage of the 
VM on that host.

Regards,
Callum

--

Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. cal...@well.ox.ac.uk

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

[ovirt-users] Q: "virsh list" on oVirt node

[Andrei Verovski]

Hi !

“virsh” can’t be executed on oVirt node directly due to authentication problem.
Only "virsh —readonly” are working.

Someone have recommended adding new password with this:
saslpasswd2 -a libvirt username

I know this is somewhat depreciated to hacking directly into oVirt node yet I’m 
still need this.

What is correct, non-destructive to accomplish this?
Thanks in advance.
Andrei
___
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/VUDGH7NUHOC35JMYMEE5EWC3J6SGWOU7/

[ovirt-users] Re: latest pycurl 7.43 brokes ovirtsdk4

[Ondra Machacek]

On 1/22/19 5:54 PM, Nathanaël Blanchet wrote:

Hi all,

If anyone uses latest pycurl 7.43 provided by pip or ansible tower/awx, 
any ovirtsdk4 calling will issue with the log:


The full traceback is:
WARNING: The below traceback may *not* be related to the actual failure.
   File "/tmp/ansible_ovirt_auth_payload_L1HK9E/__main__.py", line 202, 
in 

     import ovirtsdk4 as sdk
   File 
"/opt/awx/embedded/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", 
line 22, in 

     import pycurl

fatal: [localhost]: FAILED! => {
     "changed": false,
     "invocation": {
     "module_args": {
     "ca_file": null,
     "compress": true,
     "headers": null,
     "hostname": null,
     "insecure": true,
     "kerberos": false,
     "ovirt_auth": null,
     "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
     "state": "present",
     "timeout": 0,
     "token": null,
     "url": "https://acore.v100.abes.fr/ovirt-engine/api;,
     "username": "admin@internal"
     }
     },
     "msg": "ovirtsdk4 version 4.2.4 or higher is required for this module"
}

The only way is to set the version of pycurl with

pip install -U "pycurl == 7.19.0"

(Before this, in tower/awx, you should  create venv)


What's the version of AWX, where pycurl 7.43 is provided? I use latest
and I have 7.19. But anyway, I've tried to update to 7.43, and this 
worked for me with nss:


$ source venv/awx/bin/activate
$ export PYCURL_SSL_LIBRARY=nss; pip install pycurl --compile --no-cache-dir
$ python -c 'import pycurl; print pycurl.version'
PycURL/7.43.0.2 libcurl/7.29.0 NSS/3.36 zlib/1.2.7 libidn/1.28 libssh2/1.4.3





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

[ovirt-users] Re: oVirt 4.2.8 CPU Compatibility

[Uwe Laverenz]

Hi,

Am Dienstag, den 22.01.2019, 15:46 +0100 schrieb Lucie Leistnerova:

>  Yes, it should be supported also in 4.2.8. According to Release
> notes for 4.2.7 this warning is related to 4.3 version.
> 
> https://www.ovirt.org/release/4.2.7/
> 
> BZ 1623259 Mark clusters with deprecated CPU type
> In the current release, for compatibility versions 4.2 and 4.3, a
> warning in the Cluster screen indicates that the CPU types currently
> used are not supported in 4.3. The warning enables the user to change
> the cluster CPU type to a supported CPU type.

Does this mean that I would not be able to install OVirt 4.3 on
machines with Opteron 6174 cpu? Or would I just get a warning?

I was thinking of recycling our old DL385 machines for an OVirt/Gluster
testing lab. :)

cu,
Uwe

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