[ovirt-users] oVirt API (4.0 and 4.1) not reporting vms running on a given storage domain

[Luca 'remix_tj' Lorenzetto]

Hello,

i need to extract the list of the vms running on a given storage domain.
Copying some code from ansible's ovirt_storage_vms_facts simplified my
work but i stopped with a strange behavior: no vm is listed.

I thought it was an issue with my code, but looking more in detail at
api's i tried opening:

ovirt-engine/api/storagedomains/52b661fe-609e-48f9-beab-f90165b868c4/vms

And what i get is



And this for all the storage domains available.

Is there something wrong with the versions i'm running? Do i require
some options in the query?

I'm running RHV, so i can't upgrade to 4.2 yet

Luca

-- 
"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
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] windows vm

[Vincent Royer]

Broadwell

*Vincent Royer*
*778-825-1057*



*SUSTAINABLE MOBILE ENERGY SOLUTIONS*




On Thu, Mar 1, 2018 at 9:57 AM,  wrote:

> What CPU type do you have for your windows machines?
>
> --
> *De: *"Vincent Royer" 
> *Para: *supo...@logicworks.pt
> *Cc: *"ovirt users" 
> *Enviadas: *Quinta-feira, 1 De Março de 2018 17:50:23
> *Assunto: *Re: [ovirt-users] windows vm
>
> I have deployed a dozen or so on 4.2 without issues. I'd check your .iso
>
> *Vincent Royer*
> *778-825-1057 <(778)%20825-1057>*
>
>
> 
> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>
>
>
>
> On Thu, Mar 1, 2018 at 9:11 AM,  wrote:
>
>> Hi,
>>
>> I'm trying to install a windows VM on Ovirt 4.2 but when doing a run once
>> it freezes with the windows logo. Is there any special
>> requirements/parameter to run windows machines in this version?
>>
>> Thanks
>>
>> --
>> --
>> Jose Ferradeira
>> http://www.logicworks.pt
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] windows vm

[suporte]

What CPU type do you have for your windows machines? 


De: "Vincent Royer"  
Para: supo...@logicworks.pt 
Cc: "ovirt users"  
Enviadas: Quinta-feira, 1 De Março de 2018 17:50:23 
Assunto: Re: [ovirt-users] windows vm 

I have deployed a dozen or so on 4.2 without issues. I'd check your .iso 

Vincent Royer 
778-825-1057 



SUSTAINABLE MOBILE ENERGY SOLUTIONS 




On Thu, Mar 1, 2018 at 9:11 AM, < supo...@logicworks.pt > wrote: 



Hi, 

I'm trying to install a windows VM on Ovirt 4.2 but when doing a run once it 
freezes with the windows logo. Is there any special requirements/parameter to 
run windows machines in this version? 

Thanks 

-- 

Jose Ferradeira 
http://www.logicworks.pt 

___ 
Users mailing list 
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users 






___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] windows vm

[suporte]

Hi, 

I'm trying to install a windows VM on Ovirt 4.2 but when doing a run once it 
freezes with the windows logo. Is there any special requirements/parameter to 
run windows machines in this version? 

Thanks 

-- 

Jose Ferradeira 
http://www.logicworks.pt 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cannot activate storage domain

[Bruckner, Simone]

Hi,

  we are still struggling getting a storage domain online again. We tried to 
put the storage domain in maintenance mode, that led to "Failed to update OVF 
disks 809cc8d7-7687-46cf-a342-3be48674a9b3, OVF data isn't updated on those OVF 
stores".

Trying again with ignoring OVF update failures put the storage domain in 
"preparing for maintenance". We see the following message on all hosts: "Error 
releasing host id 26 for domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 
(monitor:578)".

Querying the storage domain using vdsm-client on the SPM resulted in
# vdsm-client StorageDomain getInfo 
"storagedomainID"="b83c159c-4ad6-4613-ba16-bab95ccd10c0"
vdsm-client: Command StorageDomain.getInfo with args {'storagedomainID': 
'b83c159c-4ad6-4613-ba16-bab95ccd10c0'} failed:
(code=358, message=Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',))

Any ideas?

Thank you and all the best,
Simone

Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Bruckner, Simone
Gesendet: Mittwoch, 28. Februar 2018 15:52
An: users@ovirt.org
Betreff: [ovirt-users] Cannot activate storage domain

Hi all,

  we run a small oVirt installation that we also use for automated testing 
(automatically creating, dropping vms).

We got an inactive FC storage domain that we cannot activate any more. We see 
several events at that time starting with:

VM perftest-c17 is down with error. Exit message: Unable to get volume size for 
domain b83c159c-4ad6-4613-ba16-bab95ccd10c0 volume 
686376c1-4be1-44c3-89a3-0a8addc8fdf2.

Trying to activate the strorage domain results in the following alert event for 
each host:

VDSM  command GetVGInfoVDS failed: Volume Group does not exist: 
(u'vg_uuid: 813oRe-64r8-mloU-k9G2-LFsS-dXSG-hpN4kf',)

And after those messages from all hosts we get:

VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'b83c159c-4ad6-4613-ba16-bab95ccd10c0',)
Failed to activate Storage Domain VMHOST_LUN_205 (Data Center Production) by 

Invalid status on Data Center Production. Setting status to Non Responsive.
Storage Pool Manager runs on Host vmhost003.fabagl.fabasoft.com (Address: 
vmhost003.fabagl.fabasoft.com), Data Center Production.

Checking the hosts with multipath -ll we see the LUN without errors.

We run oVirt 4.2.1 on CentOS 7.4. Hosts are CentOS 7.4 hosts with oVirt 
installed using oVirt engine.
Hosts are connected to about 30 FC LUNs (8 TB each) on two all-flash storage 
arrays.

Thank you,
Simone Bruckner



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VMs with multiple vdisks don't migrate

[Milan Zamazal]

"fsoyer"  writes:

> I tried to activate the debug mode, but the restart of libvirt crashed
> something on the host : it was no more possible to start any vm on it, and
> migration to it just never started. So I decided to restart it, and to be 
> sure,
> I've restarted all the hosts.
> And... now the migration of all VMs, simple or multi-disks, works ?!? So, 
> there
> was probably something hidden that was resetted or repaired by the global
> restart ! In french, we call that "tomber en marche" ;)

I'm always amazed how many problems in computing are eventually resolved
(and how many new ones introduced) by reboot :-).  I'm glad that it
works for you now.

Regards,
Milan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM Migrations

[Milan Zamazal]

"Bryan Sockel"  writes:

> I am having an issue migrating all vm's based on a specific template.  The 
> template was created in a previous ovirt environment (4.1), and all VM's 
> deployed from this template experience the same issue.
>
> I would like to find a resolution to both the template and vm's that are 
> already deployed from this template.  The VM in question is VDI-Bryan and 
> the migration starts around 12:25.  I have attached the engine.log and the 
> vdsm.log file from the destination server.

The VM died on the destination before it could be migrated and I can't
see the exact reason in the log.  However I can see there that you have
been hit by some 4.1->4.2 migration issues and it's likely to be the
problem as well as being a problem by itself in any case.

That will be fixed in 4.2.2.  If you don't want to wait until 4.2.2 is
released, you may want to try current 4.2.2 snapshot, which already
contains the fixes.

Regards,
Milan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VMs with multiple vdisks don't migrate

[fsoyer]

I Milan,
I tried to activate the debug mode, but the restart of libvirt crashed 
something on the host : it was no more possible to start any vm on it, and 
migration to it just never started. So I decided to restart it, and to be sure, 
I've restarted all the hosts.
And... now the migration of all VMs, simple or multi-disks, works ?!? So, there 
was probably something hidden that was resetted or repaired by the global 
restart ! In french, we call that "tomber en marche" ;)

So : solved. Thank you for the wasted time !

--

Cordialement,

Frank Soyer
Mob. 06 72 28 38 53 - Fix. 05 49 50 52 34

Le Lundi, Février 26, 2018 12:59 CET, Milan Zamazal  a 
écrit:
 "fsoyer"  writes:

> I don't beleive that this is relatd to a host, tests have been done from 
> victor
> source to ginger dest and ginger to victor. I don't see problems on storage
> (gluster 3.12 native managed by ovirt), when VMs with a uniq disk from 20 to
> 250G migrate without error in some seconds and with no downtime.

The host itself may be fine, but libvirt/QEMU running there may expose
problems, perhaps just for some VMs. According to your logs something
is not behaving as expected on the source host during the faulty
migration.

> How ca I enable this libvirt debug mode ?

Set the following options in /etc/libvirt/libvirtd.conf (look for
examples in comments there)

- log_level=1
- log_outputs="1:file:/var/log/libvirt/libvirtd.log"

and restart libvirt. Then /var/log/libvirt/libvirtd.log should contain
the log. It will be huge, so I suggest to enable it only for the time
of reproducing the problem.

> --
>
> Cordialement,
>
> Frank Soyer
>
>  
>
> Le Vendredi, Février 23, 2018 09:56 CET, Milan Zamazal  
> a écrit:
>  Maor Lipchuk  writes:
>
>> I encountered a bug (see [1]) which contains the same error mentioned in
>> your VDSM logs (see [2]), but I doubt it is related.
>
> Indeed, it's not related.
>
> The error in vdsm_victor.log just means that the info gathering call
> tries to access libvirt domain before the incoming migration is
> completed. It's ugly but harmless.
>
>> Milan, maybe you have any advice to troubleshoot the issue? Will the
>> libvirt/qemu logs can help?
>
> It seems there is something wrong on (at least) the source host. There
> are no migration progress messages in the vdsm_ginger.log and there are
> warnings about stale stat samples. That looks like problems with
> calling libvirt – slow and/or stuck calls, maybe due to storage
> problems. The possibly faulty second disk could cause that.
>
> libvirt debug logs could tell us whether that is indeed the problem and
> whether it is caused by storage or something else.
>
>> I would suggest to open a bug on that issue so we can track it more
>> properly.
>>
>> Regards,
>> Maor
>>
>>
>> [1]
>> https://bugzilla.redhat.com/show_bug.cgi?id=1486543 - Migration leads to
>> VM running on 2 Hosts
>>
>> [2]
>> 2018-02-16 09:43:35,236+0100 ERROR (jsonrpc/7) [jsonrpc.JsonRpcServer]
>> Internal server error (__init__:577)
>> Traceback (most recent call last):
>> File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 572,
>> in _handle_request
>> res = method(**params)
>> File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in
>> _dynamicMethod
>> result = fn(*methodArgs)
>> File "/usr/share/vdsm/API.py", line 1454, in getAllVmIoTunePolicies
>> io_tune_policies_dict = self._cif.getAllVmIoTunePolicies()
>> File "/usr/share/vdsm/clientIF.py", line 454, in getAllVmIoTunePolicies
>> 'current_values': v.getIoTune()}
>> File "/usr/share/vdsm/virt/vm.py", line 2859, in getIoTune
>> result = self.getIoTuneResponse()
>> File "/usr/share/vdsm/virt/vm.py", line 2878, in getIoTuneResponse
>> res = self._dom.blockIoTune(
>> File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 47,
>> in __getattr__
>> % self.vmid)
>> NotConnectedError: VM u'755cf168-de65-42ed-b22f-efe9136f7594' was not
>> started yet or was shut down
>>
>> On Thu, Feb 22, 2018 at 4:22 PM, fsoyer  wrote:
>>
>>> Hi,
>>> Yes, on 2018-02-16 (vdsm logs) I tried with a VM standing on ginger
>>> (192.168.0.6) migrated (or failed to migrate...) to victor (192.168.0.5),
>>> while the engine.log in the first mail on 2018-02-12 was for VMs standing
>>> on victor, migrated (or failed to migrate...) to ginger. Symptoms were
>>> exactly the same, in both directions, and VMs works like a charm before,
>>> and even after (migration "killed" by a poweroff of VMs).
>>> Am I the only one experimenting this problem ?
>>>
>>>
>>> Thanks
>>> --
>>>
>>> Cordialement,
>>>
>>> *Frank Soyer *
>>>
>>>
>>>
>>> Le Jeudi, Février 22, 2018 00:45 CET, Maor Lipchuk 
>>> a écrit:
>>>
>>>
>>> Hi Frank,
>>>
>>> Sorry about the delay repond.
>>> I've been going through the logs you attached, although I could not find
>>> any specific indication why the migration failed because of the disk you
>>> were 

Re: [ovirt-users] VM paused rather than migrate to another hosts

[Milan Zamazal]

Terry hey  writes:

> Dear Milan,
> Today, i just found that oVirt 4.2 support iLO5 and power management was
> set on all hosts (hypervisor).
> I found that if i choose VM lease and shutdown iSCSI network, the VM was
> shutdown.
> Then the VM will migrate to another host if the iSCSI network was resumed.

If the VM had been shut down then it was probably restarted on rather
than migrated to another host.

> If i just choose enable HA on VM setting, the VM was successfully migrate
> to another hosts.

There can be a special situation if the storage storing VM leases is
unavailable.

oVirt tries to do what it can in case of storage problems, but it all
depends on the overall state of the storage – for how long it remains
unavailable, if it is available at least on some hosts, and which parts
of the storage are available; there are more possible scenarios here.
Indeed, it's a good idea to experiment with failures and learn what
happens before real problems come!

> But i want to ask another question, what if the management network is down?
> What VM and hosts behavior would you expect?

The primary problem is that oVirt Engine can't communicate with the
hosts in such a case.  Unless there is another problem (especially
assuming storage is still reachable from the hosts) the hosts and VMs
will keep running, but the hosts will be displayed as unreachable and
VMs as unknown in Engine.  And you won't be able to manage your VMs from
Engine of course.  Once the management network is back, things should
return to normal state sooner or later.

Regards,
Milan

> Regards
> Terry Hung
>
> 2018-02-28 22:29 GMT+08:00 Milan Zamazal :
>
>> Terry hey  writes:
>>
>> > I am testing iSCSI bonding failover test on oVirt, but i observed that VM
>> > were paused and did not migrate to another host. Please see the details
>> as
>> > follows.
>> >
>> > I have two hypervisors. Since they are running iLO 5 and oVirt 4.2 cannot
>> > support iLO 5, thus i cannot setup power management.
>> >
>> > For the cluster setting, I set "Migrate Virtual Machines" under the
>> > Migration Policy.
>> >
>> > For each hypervisor, I bonded two iSCSI interface as bond 1.
>> >
>> > I created one Virtual machine and enable high availability on it.
>> > Also, I created one Virtual machine and did not enable high availability
>> on
>> > it.
>> >
>> > When i shutdown one of the iSCSI interface, nothing happened.
>> > But when i shutdown both iSCSI interface, VM in that hosts were paused
>> and
>> > did not migrate to another hosts. Is this behavior normal or i miss
>> > something?
>>
>> A paused VM can't be migrated, since there are no guarantees about the
>> storage state.  As the VMs were paused under erroneous (rather than
>> controlled such as putting the host into maintenance) situation,
>> migration policy can't help here.
>>
>> But highly available VMs can be restarted on another host automatically.
>> Do you have VM lease enabled for the highly available VM in High
>> Availability settings?  With a lease, Engine should be able to restart
>> the VM elsewhere after a while, without it Engine can't do that since
>> there is danger of resuming the VM on the original host, resulting in
>> multiple instances of the same VM running at the same time.
>>
>> VMs without high availability must be restarted manually (unless storage
>> domain becomes available again).
>>
>> HTH,
>> Milan
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] cannot remove vm.

[nicola gentile]

Hi,
I have a problem. I try to remove a pool and than I remove every vm
but one of this display the message "Cannot remove VM. Related
operation is currently in progress. Please try again later."

I try to unlock with this command

PGPASSWORD=... /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh
-t all -u engine

but not working

in /var/log/ovirt-engine/engine.log

2018-03-01 17:02:47,799+01 INFO
[org.ovirt.engine.core.bll.RemoveVmCommand] (default task-33)
[0217d710-afb6-4450-9897-02748d871aa1] Failed to Acquire Lock to
object 'EngineLock:{exclusiveLocks='[d623ad44-a645-4fd0-9993-d21374e99eb5=VM]',
sharedLocks=''}'
2018-03-01 17:02:47,799+01 WARN
[org.ovirt.engine.core.bll.RemoveVmCommand] (default task-33)
[0217d710-afb6-4450-9897-02748d871aa1] Validation of action 'RemoveVm'
failed for user admin@internal-authz. Reasons:
VAR__ACTION__REMOVE,VAR__TYPE__VM,ACTION_TYPE_FAILED_OBJECT_LOCKED

please help

thanks

Nick
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2.x and ManageIQ : Adding 'cfme' credentials

[Nicolas Ecarnot]

Le 01/03/2018 à 15:50, Nicolas Ecarnot a écrit :

Couldn't the Redhat documentation mentioned above be more accurate?


Something like 'scl enable rh-postgrsql95' should help.


Not that much...

root@serv-mvm-prds01:/etc/ovirt-engine-setup.conf.d# cd /tmp
root@serv-mvm-prds01:/tmp# su - postgres
Dernière connexion : jeudi  1 mars 2018 à 15:42:40 CET sur pts/2
-bash-4.2$ scl enable rh-postgrsql95
Need at least 3 arguments.
Run scl --help to get help.


After reading and reading again :

For the record, here are the steps allowing me to add this user :

su - postgres

scl enable rh-postgresql95 'psql ovirt_engine_history'

CREATE ROLE cfme with LOGIN ENCRYPTED PASSWORD 'xxx';

SELECT 'GRANT SELECT ON ' || relname || ' TO cfme;' FROM pg_class JOIN 
pg_namespace ON pg_namespace.oid = pg_class.relnamespace WHERE nspname = 
'public' AND relkind IN ('r', 'v','S');


\q

exit



--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM paused rather than migrate to another hosts

[Milan Zamazal]

Terry hey  writes:

> Dear Milan,
> Today, i just found that oVirt 4.2 support iLO5 and power management was
> set on all hosts (hypervisor).
> I found that if i choose VM lease and shutdown iSCSI network, the VM was
> shutdown.
> Then the VM will migrate to another host if the iSCSI network was resumed.

If the VM had been shut down then it was probably restarted on rather
than migrated to another host.

> If i just choose enable HA on VM setting, the VM was successfully migrate
> to another hosts.

There can be a special situation if the storage storing VM leases is
unavailable.

oVirt tries to do what it can in case of storage problems, but it all
depends on the overall state of the storage – for how long it remains
unavailable, if it is available at least on some hosts, and which parts
of the storage are available; there are more possible scenarios here.
Indeed, it's a good idea to experiment with failures and learn what
happens before real problems come!

> But i want to ask another question, what if the management network is down?
> What VM and hosts behavior would you expect?

The primary problem is that oVirt Engine can't communicate with the
hosts in such a case.  Unless there is another problem (especially
assuming storage is still reachable from the hosts) the hosts and VMs
will keep running, but the hosts will be displayed as unreachable and
VMs as unknown in Engine.  And you won't be able to manage your VMs from
Engine of course.  Once the management network is back, things should
return to normal state sooner or later.

Regards,
Milan

> Regards
> Terry Hung
>
> 2018-02-28 22:29 GMT+08:00 Milan Zamazal :
>
>> Terry hey  writes:
>>
>> > I am testing iSCSI bonding failover test on oVirt, but i observed that VM
>> > were paused and did not migrate to another host. Please see the details
>> as
>> > follows.
>> >
>> > I have two hypervisors. Since they are running iLO 5 and oVirt 4.2 cannot
>> > support iLO 5, thus i cannot setup power management.
>> >
>> > For the cluster setting, I set "Migrate Virtual Machines" under the
>> > Migration Policy.
>> >
>> > For each hypervisor, I bonded two iSCSI interface as bond 1.
>> >
>> > I created one Virtual machine and enable high availability on it.
>> > Also, I created one Virtual machine and did not enable high availability
>> on
>> > it.
>> >
>> > When i shutdown one of the iSCSI interface, nothing happened.
>> > But when i shutdown both iSCSI interface, VM in that hosts were paused
>> and
>> > did not migrate to another hosts. Is this behavior normal or i miss
>> > something?
>>
>> A paused VM can't be migrated, since there are no guarantees about the
>> storage state.  As the VMs were paused under erroneous (rather than
>> controlled such as putting the host into maintenance) situation,
>> migration policy can't help here.
>>
>> But highly available VMs can be restarted on another host automatically.
>> Do you have VM lease enabled for the highly available VM in High
>> Availability settings?  With a lease, Engine should be able to restart
>> the VM elsewhere after a while, without it Engine can't do that since
>> there is danger of resuming the VM on the original host, resulting in
>> multiple instances of the same VM running at the same time.
>>
>> VMs without high availability must be restarted manually (unless storage
>> domain becomes available again).
>>
>> HTH,
>> Milan
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2.x and ManageIQ : Adding 'cfme' credentials

[Nicolas Ecarnot]

Le 01/03/2018 à 15:00, Yaniv Kaul a écrit :



On Thu, Mar 1, 2018 at 2:13 PM, Nicolas Ecarnot > wrote:


Hello,

As for my 4 previous oVirt DCs, I'm trying to add them to ManageIQ
providers.

I tried to follow this guide :


https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html-single/deployment_planning_guide/#data_collection_for_rhev_33_34



But when trying to run psql, the shell tells me the command is not
found.




Hello Yanniv,

Thank you for answering.


Because you are probably on PG 9.5 SCL, I assume?


I've never heard about that before today.
I installed a bare-metal CentOS 7.4 on which I installed oVirt 4.2.
I saw no reference to SCL nowhere, neither during the setup, neither in 
the oVirt install documentation.


How an average user is supposed to behave in such a situation?
(In my case, as usual, I read and read again)

Couldn't the Redhat documentation mentioned above be more accurate?


Something like 'scl enable rh-postgrsql95' should help.


Not that much...

root@serv-mvm-prds01:/etc/ovirt-engine-setup.conf.d# cd /tmp
root@serv-mvm-prds01:/tmp# su - postgres
Dernière connexion : jeudi  1 mars 2018 à 15:42:40 CET sur pts/2
-bash-4.2$ scl enable rh-postgrsql95
Need at least 3 arguments.
Run scl --help to get help.

--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2.x and ManageIQ : Adding 'cfme' credentials

[Yaniv Kaul]

On Thu, Mar 1, 2018 at 2:13 PM, Nicolas Ecarnot  wrote:

> Hello,
>
> As for my 4 previous oVirt DCs, I'm trying to add them to ManageIQ
> providers.
>
> I tried to follow this guide :
>
> https://access.redhat.com/documentation/en-us/red_hat_cloudf
> orms/4.6/html-single/deployment_planning_guide/#data_collect
> ion_for_rhev_33_34
>
> But when trying to run psql, the shell tells me the command is not found.
>

Because you are probably on PG 9.5 SCL, I assume?
Something like 'scl enable rh-postgrsql95' should help.
Y.




>
> I made a very simple setup : when running engine-setup, I answered the
> default question about DWH, so the DB is local.
>
> When viewing (with pgAdmin) the roles of this new PostgreSQL DB, I see
> there is no 'cfme' user.
> Do I have to re-run the setup and answer different things to ensure other
> packages and setup are made?
>
> I saw https://access.redhat.com/documentation/en-us/red_hat_virtua
> lization/4.1/html-single/data_warehouse_guide/#Overview_of_C
> onfiguring_Data_Warehouse telling me to re-run.
>
> But I see that :
> rpm -qa|grep -i dwh
> ovirt-engine-dwh-4.2.1.2-1.el7.centos.noarch
> ovirt-engine-dwh-setup-4.2.1.2-1.el7.centos.noarch
>
> so I thought it was already enough... ?
>
> --
> Nicolas ECARNOT
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt 4.2.x and ManageIQ : Adding 'cfme' credentials

[Nicolas Ecarnot]

Hello,

As for my 4 previous oVirt DCs, I'm trying to add them to ManageIQ 
providers.


I tried to follow this guide :

https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html-single/deployment_planning_guide/#data_collection_for_rhev_33_34

But when trying to run psql, the shell tells me the command is not found.

I made a very simple setup : when running engine-setup, I answered the 
default question about DWH, so the DB is local.


When viewing (with pgAdmin) the roles of this new PostgreSQL DB, I see 
there is no 'cfme' user.
Do I have to re-run the setup and answer different things to ensure 
other packages and setup are made?


I saw 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/data_warehouse_guide/#Overview_of_Configuring_Data_Warehouse 
telling me to re-run.


But I see that :
rpm -qa|grep -i dwh
ovirt-engine-dwh-4.2.1.2-1.el7.centos.noarch
ovirt-engine-dwh-setup-4.2.1.2-1.el7.centos.noarch

so I thought it was already enough... ?

--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Backup & Restore

[suporte]

Yes, it happens in a clean machine. I try it twice and restore always fails. 


From: "Yedidyah Bar David"  
To: supo...@logicworks.pt, "Eli Mesika"  
Cc: "ovirt users"  
Sent: Thursday, March 1, 2018 7:28:13 AM 
Subject: Re: [ovirt-users] Backup & Restore 

On Wed, Feb 28, 2018 at 4:44 PM,  wrote: 
> If I run 
> 
> # engine-backup --mode=restore --file=back_futur --log=log_futur 
> --provision-db --restore-permissions --provision-dwh-db --log=/root/rest-log 
> 
> to create a log, I found these errors: 
> 
> 2018-02-28 14:36:31 6339: pg_cmd running: psql -w -U ovirt_engine_history -h 
> localhost -p 5432 ovirt_engine_history -t -c show lc_messages 
> 2018-02-28 14:36:31 6339: pg_cmd running: pg_dump -w -U ovirt_engine_history 
> -h localhost -p 5432 ovirt_engine_history -s 
> 2018-02-28 14:36:31 6339: OUTPUT: - Engine database 'engine' 
> 2018-02-28 14:36:31 6339: Restoring engine database backup at 
> /tmp/engine-backup.VVkcNuYAkV/db/engine_backup.db 
> 2018-02-28 14:36:31 6339: restoreDB: backupfile 
> /tmp/engine-backup.VVkcNuYAkV/db/engine_backup.db user engine host localhost 
> port 5432 database engine orig_user compressor format custom jobsnum 2 
> 2018-02-28 14:36:31 6339: pg_cmd running: pg_restore -w -U engine -h 
> localhost -p 5432 -d engine -j 2 
> /tmp/engine-backup.VVkcNuYAkV/db/engine_backup.db 
> pg_restore: [archiver (db)] Error while PROCESSING TOC: 
> pg_restore: [archiver (db)] Error from TOC entry 7314; 0 0 COMMENT EXTENSION 
> plpgsql 
> pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of 
> extension plpgsql 
> Command was: COMMENT ON EXTENSION plpgsql IS 'PL/pgSQL procedural language'; 
> 
> 
> 
> pg_restore: [archiver (db)] Error from TOC entry 693; 1255 211334 FUNCTION 
> uuid_generate_v1() engine 
> pg_restore: [archiver (db)] could not execute query: ERROR: function 
> "uuid_generate_v1" already exists with same argument types 

This is the error that fails you. I have a pending patch to make this more 
visible in the log [1], need to find time to verify it... 

Does this happen on a clean machine? Perhaps 'engine-cleanup' after such 
a failed restore is not enough. Please try reinstalling the OS and trying 
again. 

If it's not an important machine (test/dev/etc), this will probably be 
enough, as a faster replacement for a full OS reinstall: 

engine-cleanup 
systemctl stop postgresql 
systemctl stop rh-postgresql95-postgresql 
rm -rf /var/lib/pgsql/data /var/opt/rh/rh-postgresql95/lib/pgsql/data 

Then try restore again. 

[1] https://gerrit.ovirt.org/86395 

> Command was: CREATE FUNCTION uuid_generate_v1() RETURNS uuid 
> LANGUAGE plpgsql STABLE 
> AS ' 
> DECLARE 
> v_val BIGINT; 
> v_4_1_par... 
> pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of 
> function uuid_generate_v1 
> Command was: ALTER FUNCTION public.uuid_generate_v1() OWNER TO engine; 

Adding also Eli. Eli - perhaps we need to patch engine-backup to ignore 
also this error? I think the minimal flow to reproduce is: 

engine-setup 
engine-backup --mode=backup --file=f1 --log=l1 
engine-cleanup 
engine-backup --mode=restore --file=f1 --provision-db 
--provision-dwh-db --log=l2 

Didn't try this myself. 

> 
> 
> pg_restore: WARNING: column "user_role_title" has type "unknown" 
> DETAIL: Proceeding with relation creation anyway. 
> pg_restore: WARNING: no privileges could be revoked for "public" 
> pg_restore: WARNING: no privileges could be revoked for "public" 
> pg_restore: WARNING: no privileges were granted for "public" 
> pg_restore: WARNING: no privileges were granted for "public" 
> WARNING: errors ignored on restore: 3 
> 2018-02-28 14:37:23 6339: FATAL: Errors while restoring database engine 
> 
>  
> De: supo...@logicworks.pt 
> Para: "Yedidyah Bar David"  
> Cc: "ovirt users"  
> Enviadas: Quarta-feira, 28 De Fevereiro de 2018 12:45:04 
> 
> Assunto: Re: [ovirt-users] Backup & Restore 
> 
> Still no luck: 
> 
> # engine-backup --mode=restore --file=back_futur --log=log_futur 
> --provision-db --restore-permissions --provision-dwh-db 
> Preparing to restore: 
> - Unpacking file 'back_futur' 
> Restoring: 
> - Files 
> Provisioning PostgreSQL users/databases: 
> - user 'engine', database 'engine' 
> - user 'ovirt_engine_history', database 'ovirt_engine_history' 
> Restoring: 
> - Engine database 'engine' 
> FATAL: Errors while restoring database engine 
> 
> I did a engine-cleanup, try it again but still the same error. 
> 
>  
> De: "Yedidyah Bar David"  
> Para: supo...@logicworks.pt 
> Cc: "ovirt users"  
> Enviadas: Quarta-feira, 28 De Fevereiro de 2018 12:24:50 
> Assunto: Re: [ovirt-users] Backup & Restore 
> 
> On Wed, Feb 28, 2018 at 2:10 PM,  wrote: 
>> Hi, 
>> 
>> I'm testing backup & restore on Ovirt 4.2. 
>> 

[ovirt-users] Troubleshooting VM SSO on Windows 10 (ovirt 4.2.1)

[Cristian Mammoli]

Hi, I'm trying to setup sso on Windows 10, vm is domain joined, has 
agent installed and credential provider registered.Of course I setup an 
AD domain and the vm has sso enabled


Whenever I log to the user portal and open a VM I'm presented with the 
login screen and nothing happens, it's like the engine doesn't send the 
command to autologin.


In the agent logs there's nothing interesting but the communication 
between the engine and the agent is ok: for example the command to 
lock-screen on console close runs and works:


Dummy-2::INFO::2018-03-01 
09:01:39,124::ovirtagentlogic::322::root::Received an external command: 
lock-screen...


This is an extract from engine logs when I login in the user portal and 
start a connection:


2018-03-01 11:30:01,558+01 INFO 
[org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-30) 
[] User c.mamm...@apra.it successfully logged in with scopes: 
ovirt-app-admin ovirt-app-api ovirt-app-portal 
ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all 
ovirt-ext=token-info:authz-search 
ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate 
ovirt-ext=token:password-access
2018-03-01 11:30:01,606+01 INFO 
[org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default 
task-31) [7bc265f] Running command: CreateUserSessionCommand internal: 
false.
2018-03-01 11:30:01,623+01 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-31) [7bc265f] EVENT_ID: USER_VDC_LOGIN(30), User 
c.mamm...@apra.it@apra.it connecting from '192.168.1.100' using session 
'5NMjCbUiehNLAGMeeWsr4L5TatL+uUGsNHOxQtCvSa9i0DaQ7uoGSi6zaZdXu08vrEk5gyQUJAsB2+COzLwtEw==' 
logged in.
2018-03-01 11:30:02,163+01 ERROR 
[org.ovirt.engine.core.bll.GetSystemStatisticsQuery] (default task-39) 
[14276418-5de7-44a6-bb64-c60965de0acf] Query execution failed due to 
insufficient permissions.
2018-03-01 11:30:02,664+01 INFO 
[org.ovirt.engine.core.bll.SetVmTicketCommand] (default task-54) 
[617f130b] Running command: SetVmTicketCommand internal: false. Entities 
affected :  ID: c0250fe0-5d8b-44de-82bc-04610952f453 Type: VMAction 
group CONNECT_TO_VM with role type USER
2018-03-01 11:30:02,683+01 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(default task-54) [617f130b] START, SetVmTicketVDSCommand(HostName = 
r630-01.apra.it, 
SetVmTicketVDSCommandParameters:{hostId='d99a8356-72e8-4130-a1cc-e148762eca57', 
vmId='c0250fe0-5d8b-44de-82bc-04610952f453', protocol='SPICE', 
ticket='u2b1nv+rH+pw', validTime='120', userName='c.mamm...@apra.it', 
userId='39f9d718-6e65-456a-8a6f-71976bcbbf2f', 
disconnectAction='LOCK_SCREEN'}), log id: 18fa2ef
2018-03-01 11:30:02,703+01 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] 
(default task-54) [617f130b] FINISH, SetVmTicketVDSCommand, log id: 18fa2ef
2018-03-01 11:30:02,713+01 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-54) [617f130b] EVENT_ID: VM_SET_TICKET(164), User 
c.mamm...@apra.it@apra.it initiated console session for VM testvdi02
2018-03-01 11:30:11,558+01 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engineScheduled-Thread-49) [] EVENT_ID: 
VM_CONSOLE_CONNECTED(167), User c.mamm...@apra.it is connected to VM 
testvdi02.


Any help would be appreciated
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] open source backup solution for ovirt/VMs

[Junaid Jadoon]

Bareos is compatible with FC tape library ???

On Thu, Mar 1, 2018 at 7:26 AM, Vincent Royer  wrote:

> Can you tell us more about this implementation?
>
> *Vincent Royer*
> *778-825-1057*
>
>
> 
> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>
>
>
>
> On Wed, Feb 28, 2018 at 2:10 PM, Brett Holcomb 
> wrote:
>
>> I use Bareos for backup.  It is open source.
>>
>>
>>
>> On 02/28/2018 01:14 PM, Junaid Jadoon wrote:
>>
>> HI,
>> Can you please suggest me open source backup solution for ovirt Virtual
>> machines.
>>
>> My backup media is FC tape library which directly  attached to my ovirt
>> node.
>>
>> I really appreciate you help
>>
>> thanks.
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM paused rather than migrate to another hosts

[Terry hey]

Dear Milan,
Today, i just found that oVirt 4.2 support iLO5 and power management was
set on all hosts (hypervisor).
I found that if i choose VM lease and shutdown iSCSI network, the VM was
shutdown.
Then the VM will migrate to another host if the iSCSI network was resumed.

If i just choose enable HA on VM setting, the VM was successfully migrate
to another hosts.

But i want to ask another question, what if the management network is down?
What VM and hosts behavior would you expect?

Regards
Terry Hung

2018-02-28 22:29 GMT+08:00 Milan Zamazal :

> Terry hey  writes:
>
> > I am testing iSCSI bonding failover test on oVirt, but i observed that VM
> > were paused and did not migrate to another host. Please see the details
> as
> > follows.
> >
> > I have two hypervisors. Since they are running iLO 5 and oVirt 4.2 cannot
> > support iLO 5, thus i cannot setup power management.
> >
> > For the cluster setting, I set "Migrate Virtual Machines" under the
> > Migration Policy.
> >
> > For each hypervisor, I bonded two iSCSI interface as bond 1.
> >
> > I created one Virtual machine and enable high availability on it.
> > Also, I created one Virtual machine and did not enable high availability
> on
> > it.
> >
> > When i shutdown one of the iSCSI interface, nothing happened.
> > But when i shutdown both iSCSI interface, VM in that hosts were paused
> and
> > did not migrate to another hosts. Is this behavior normal or i miss
> > something?
>
> A paused VM can't be migrated, since there are no guarantees about the
> storage state.  As the VMs were paused under erroneous (rather than
> controlled such as putting the host into maintenance) situation,
> migration policy can't help here.
>
> But highly available VMs can be restarted on another host automatically.
> Do you have VM lease enabled for the highly available VM in High
> Availability settings?  With a lease, Engine should be able to restart
> the VM elsewhere after a while, without it Engine can't do that since
> there is danger of resuming the VM on the original host, resulting in
> multiple instances of the same VM running at the same time.
>
> VMs without high availability must be restarted manually (unless storage
> domain becomes available again).
>
> HTH,
> Milan
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users