[ovirt-users] Re: how to use oVirt engine API to retrieve the attached VM list by a disk id.

2018-05-31 Thread Ondra Machacek

Looking the API, the Disk type has element 'vms', but we don't feed it
with data:


https://github.com/oVirt/ovirt-engine-api-model/blob/master/src/main/java/types/Device.java#L50

I can fix the API so it returns it. So feel free to open a bug if you
need it.

But maybe, can you describe your exact use case? You user just input
disk 'id' and you are suppose to return the VM which it's attached to?
If you need to know only if it's attached 'true/false', you can use

  /api/disks?search=number_of_vms=1

On 06/01/2018 04:57 AM, Joey Ma wrote:

Hi Ondra,

I tried your URL but it not worked. I want to retrieve all the attached 
vms by a disk, so I cloud not provide a specified vm name for searching. 
Also tried with https://fqdn/ovirt-engine/api/vms?search= 
_disk=DISKNAME_, 
unfortunately the `disk` parameter is not supported.



Put it differently, how could I get the disk list by rest API as same as 
shown by visiting admin portal at 
https://fqdn/ovirt-engine/webadmin/?#disks, which indicates the attached 
vm name for each disk.






On Fri, Jun 1, 2018 at 8:51 AM, Joey Ma > wrote:


OK, got it. Search is a powerful solution. Thank you very much.

On Thu, May 31, 2018 at 6:49 PM, Ondra Machacek mailto:omach...@redhat.com>> wrote:

On 05/31/2018 09:28 AM, iterjpnic  wrote:

Hi all,

I use oVirt engine API v4.2 for implementing terraform oVirt
provider. And I want to check if a Disk has been attached to
a VM, so I need to find all vms attached by this disk.
But after I checked the GET-Response data from the
"/ovirt-engine/api/disks/" rest url, there has no
disk-attachment/vm related properties or links. I could get
a trade-off, by the following steps:
1. getting all vms
2. get all disk-attachments of each vm
3. check if the given disk id equals to the `disk` property
of each disk-attachment`
4. If equals, append the vm to result list

Is there any simpler and smarter way to get this? Thanks.


Hi, you can use following:

https://fqdn/ovirt-engine/api/disks?search=vm_names=myvmname


___
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/6LVOIVEUUO7PXVV36GH3V6GSURQV4ALO/






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


[ovirt-users] Re: Non-responsive vm's due to crashed host and hosted vm liveliness check fails

2018-05-31 Thread clam2718
> Hi,
> 
> You could try accessing the engine VM using the VNC.
> First, set the VNC password using 'hosted-engine --add-console-password',
> and then connect to the host using a VNC viewer, for example:
> 'remove-viewer vnc://HOST_IP:5900'
> 
> The liveliness check just checks if the web UI is running and reachable.
> If the VNC works, try checking if the 'ovirt-engine' service is running on
> the VM and that the network is configured properly.
> 
> 
> Andrej
> 
> On 30 May 2018 at 18:31, 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/5W4N6BGVCCABUQTFZFOAE6ITYVCD2E2H/


[ovirt-users] Re: how to use oVirt engine API to retrieve the attached VM list by a disk id.

2018-05-31 Thread Joey Ma
Hi Ondra,

I tried your URL but it not worked. I want to retrieve all the attached vms
by a disk, so I cloud not provide a specified vm name for searching. Also
tried with https://fqdn/ovirt-engine/api/vms?search=

*disk=DISKNAME*, unfortunately the `disk` parameter is not supported.


Put it differently, how could I get the disk list by rest API as same as
shown by visiting admin portal at https://fqdn/ovirt-engine/webadmin/?#disks,
which indicates the attached vm name for each disk.





On Fri, Jun 1, 2018 at 8:51 AM, Joey Ma  wrote:

> OK, got it. Search is a powerful solution. Thank you very much.
>
> On Thu, May 31, 2018 at 6:49 PM, Ondra Machacek 
> wrote:
>
>> On 05/31/2018 09:28 AM, iterjpnic  wrote:
>>
>>> Hi all,
>>>
>>> I use oVirt engine API v4.2 for implementing terraform oVirt provider.
>>> And I want to check if a Disk has been attached to a VM, so I need to find
>>> all vms attached by this disk.
>>> But after I checked the GET-Response data from the
>>> "/ovirt-engine/api/disks/" rest url, there has no
>>> disk-attachment/vm related properties or links. I could get a trade-off, by
>>> the following steps:
>>> 1. getting all vms
>>> 2. get all disk-attachments of each vm
>>> 3. check if the given disk id equals to the `disk` property of each
>>> disk-attachment`
>>> 4. If equals, append the vm to result list
>>>
>>> Is there any simpler and smarter way to get this? Thanks.
>>>
>>
>> Hi, you can use following:
>>
>>  https://fqdn/ovirt-engine/api/disks?search=vm_names=myvmname
>>
>> ___
>>> 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/communit
>>> y/about/community-guidelines/
>>> List Archives: https://lists.ovirt.org/archiv
>>> es/list/users@ovirt.org/message/6LVOIVEUUO7PXVV36GH3V6GSURQV4ALO/
>>>
>>>
>
___
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/GLB5Y6TNGA7YIGAB3PW4CDGDUDVP66NZ/


[ovirt-users] Re: how to use oVirt engine API to retrieve the attached VM list by a disk id.

2018-05-31 Thread Joey Ma
OK, got it. Search is a powerful solution. Thank you very much.

On Thu, May 31, 2018 at 6:49 PM, Ondra Machacek  wrote:

> On 05/31/2018 09:28 AM, iterjpnic  wrote:
>
>> Hi all,
>>
>> I use oVirt engine API v4.2 for implementing terraform oVirt provider.
>> And I want to check if a Disk has been attached to a VM, so I need to find
>> all vms attached by this disk.
>> But after I checked the GET-Response data from the
>> "/ovirt-engine/api/disks/" rest url, there has no
>> disk-attachment/vm related properties or links. I could get a trade-off, by
>> the following steps:
>> 1. getting all vms
>> 2. get all disk-attachments of each vm
>> 3. check if the given disk id equals to the `disk` property of each
>> disk-attachment`
>> 4. If equals, append the vm to result list
>>
>> Is there any simpler and smarter way to get this? Thanks.
>>
>
> Hi, you can use following:
>
>  https://fqdn/ovirt-engine/api/disks?search=vm_names=myvmname
>
> ___
>> 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/communit
>> y/about/community-guidelines/
>> List Archives: https://lists.ovirt.org/archiv
>> es/list/users@ovirt.org/message/6LVOIVEUUO7PXVV36GH3V6GSURQV4ALO/
>>
>>
___
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/VVTFASSMJJ3S5OFW3WEXLGUAPLXTSAEU/


[ovirt-users] Re: VMs hung after migration

2018-05-31 Thread Peter Hudec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

the BZ is private, but I had the same problem. The VM hung after
migration, but not all.

After migration the VM works for a while and hangs after that, but
during upgrade to 4.2.3 and hosts update this did not happened.

Peter

On 31/05/2018 17:54, Kapetanakis Giannis wrote:
> Hi,
> 
> Please have a look at BZ
> https://bugzilla.redhat.com/show_bug.cgi?id=1584775 about VM hung
> problems I have with latest kernels.
> 
> Problem appeared after upgrading to 4.2.3 but I believe it has only
> to do with newer kernel and not any part of
> ovirt/vdsm/libvirt/qemu
> 
> regards,
> 
> Giannis ___ 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/IPORS7MN
ZJMCP5PYUUMBHBW7BWPK7PDO/
>
> 
- -- 
*Peter Hudec*
Infraštruktúrny architekt
phu...@cnc.sk 

*CNC, a.s.*
Borská 6, 841 04 Bratislava
Recepcia: +421 2  35 000 100

Mobil:+421 905 997 203
*www.cnc.sk* 

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEqSUbhuEwhryifNeVQnvVWOJ35BAFAlsQctgACgkQQnvVWOJ3
5BCcUhAAjbLs9fEx17bwxBC4QukR3rc2WUEgsb85sByZYJDuaSepELkWNkUPY+DO
QK8WHApI1QrnxCKSt1DEPTY0T5uQO9YTYBuyvamML+mLAqYWGyiWkbITNpVZBvHl
IrlsjLrUGV78ULwsfWYkvdsd2VyQlnL4PWpfw5NQL88wj6glySdMqREJM7aTYtlZ
SCFFuvjawbjCDi5dAN1WwYoWYlmGM2LF+wYalV9yGFtqq85dEiXCLL+BFJ+RbzVf
ayKcvL2vzBAt6DepAv6JxgGfIwmyLjBajWLB3hGShYd6nfJucx8SeGuGf9MYg6Ll
GR8QRTwSQha6XhGM5wHAjdzhlpwlQcwEXz4jIPvj7oL0ATw8XX8duW2VBKcPbMVC
9mJcP7XKpe2vfy7AATrlAiVDbfMh5+NDaTQwyCy9Ul24sLVhVMfJmkrCz+UL68rl
5myVmk3D/aB4dE2niJOr1cY4CCs79VymjNu69Li18fwF656Fnk7+vPu0Hq1r8yTC
3O//F8JLyXac/iYXuJ6V7wFzafvyZkJAqpg0vmIj10cLT1uqXv8RGJyNTw1YM3ll
J5P2xgiz8ZUtv6qoZcwLDDmueyVivpPqUgLtxGpOEhlRRQPP1/wcoMrrxn1vCRqi
FS/qZOSIqdCJxZU6NlcWAkdxXr/uMNXoowl17bYDKFfKaTfqYek=
=fcLm
-END PGP SIGNATURE-
___
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/Z2CV3XZVSGE44O5HYAGXE3AS6KFXZUKE/


[ovirt-users] Re: Debugging ceph access

2018-05-31 Thread Nir Soffer
On Thu, May 31, 2018 at 1:55 AM Bernhard Dick  wrote:

> Hi,
>
> I found the reason for my timeout problems: It is the version of librbd1
> (which is 0.94.5) in conjunction with my CEPH test-environment which is
> running the luminous release.
> When I install the librbd1 (and librados2) packages from the
> centos-ceph-luminous repository (version 12.2.5) I'm able to start and
> migrate VMs inbetween the hosts.
>

vdsm does not require librbd since qemu brings this dependency, and vdsm
does not access ceph directly yet.

Maybe qemu should require newer version of librbd?

Nir


>
>Regards
>  Bernhard
>
> Am 25.05.2018 um 17:08 schrieb Bernhard Dick:
> > Hi,
> >
> > as you might already know I try to use ceph with openstack in an oVirt
> > test environment. I'm able to create and remove volumes. But if I try to
> > run a VM which contains a ceph volume it is in the "Wait for launch"
> > state for a very long time. Then it gets into "down" state again. The
> > qemu log states
> >
> > 2018-05-25T15:03:41.100401Z qemu-kvm: -drive
> >
> file=rbd:rbd/volume-3bec499e-d0d0-45ef-86ad-2c187cdb2811:id=cinder:auth_supported=cephx\;none:mon_host=[mon0]\:6789\;[mon1]\:6789,file.password-secret=scsi0-0-0-0-secret0,format=raw,if=none,id=drive-scsi0-0-0-0,serial=3bec499e-d0d0-45ef-86ad-2c187cdb2811,cache=none,werror=stop,rerror=stop,aio=threads:
>
> > error connecting: Connection timed out
> >
> > 2018-05-25 15:03:41.109+: shutting down, reason=failed
> >
> > On the monitor hosts I see traffic with the ceph-mon-port, but not on
> > other ports (the osds for example). In the ceph logs however I don't
> > really see what happens.
> > Do you have some tips how to debug this problem?
> >
> >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/N6ODADRIIYRJPSSX23ITWLNQLX3ER3Q4/
>
___
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/Q7I6KVGELTU7CTDV3FPVIEZMXHJ3VPZ2/


[ovirt-users] oVirt 4.2 and CLI options

2018-05-31 Thread Simon Coter
Hi,

what is the best choice for a CLI interface vs oVirt 4.2 ?
I've looked for it and I saw that ovirt-shell is already deprecated.
Thanks

Simon
___
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/IUSAU6HO776435P7DZ36CJ2AVHZLDGDW/


[ovirt-users] Re: [ANN] oVirt 4.2.4 Second Release Candidate is now available

2018-05-31 Thread Karli Sjöberg
Den 31 maj 2018 19:16 skrev Christopher Cox :On 05/31/2018 11:55 AM, Karli Sjöberg wrote:> > > Den 31 maj 2018 17:57 skrev Christopher Cox :> > I found some humor in the signature... so, my own spin.> > TRIED (by a few). TESTED (a bit). TRUSTED (for now).> > > Hah, that is awesome, LOL! :) Nothing negative towards any devs, I know > you do your best, but with some self-distance, the above is very apt.> > 1) Our community isn't that large> 2) You test what you can but certainly not all possible (sometimes > impossible :)) scenarios> 3) Alot of the community, myself included are hesitant of upgrading > until the next major release, always staying one major behind.> > Not complaining one bit, I have what I payed for; not a dime, yet gotten > so much out of it, it's amazing! Big thanks to everyone involved for the > work you do!> I second the sentiment to all the devs who work on oVirt.  It's really really good stuff considering.But as a FOSS contributor, I stand behind my modification of the sig above.  It's akin to the "Linux sucks" motto (it just sucks less).Totally agreed!/K___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/DZ5W37EDV2DW4F6WG7QRRQKPHBCRJETA/___
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/NLAIQ42C4ZPFWENDW2DC45KPQQFM2W5A/


[ovirt-users] Re: [ANN] oVirt 4.2.4 Second Release Candidate is now available

2018-05-31 Thread Christopher Cox

On 05/31/2018 11:55 AM, Karli Sjöberg wrote:



Den 31 maj 2018 17:57 skrev Christopher Cox :

I found some humor in the signature... so, my own spin.

TRIED (by a few). TESTED (a bit). TRUSTED (for now).


Hah, that is awesome, LOL! :) Nothing negative towards any devs, I know 
you do your best, but with some self-distance, the above is very apt.


1) Our community isn't that large
2) You test what you can but certainly not all possible (sometimes 
impossible :)) scenarios
3) Alot of the community, myself included are hesitant of upgrading 
until the next major release, always staying one major behind.


Not complaining one bit, I have what I payed for; not a dime, yet gotten 
so much out of it, it's amazing! Big thanks to everyone involved for the 
work you do!




I second the sentiment to all the devs who work on oVirt.  It's really 
really good stuff considering.


But as a FOSS contributor, I stand behind my modification of the sig 
above.  It's akin to the "Linux sucks" motto (it just sucks less).

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


[ovirt-users] Re: [ANN] oVirt 4.2.4 Second Release Candidate is now available

2018-05-31 Thread Karli Sjöberg
Den 31 maj 2018 17:57 skrev Christopher Cox :I found some humor in the signature... so, my own spin.TRIED (by a few). TESTED (a bit). TRUSTED (for now).Hah, that is awesome, LOL! :) Nothing negative towards any devs, I know you do your best, but with some self-distance, the above is very apt. 1) Our community isn't that large2) You test what you can but certainly not all possible (sometimes impossible :)) scenarios3) Alot of the community, myself included are hesitant of upgrading until the next major release, always staying one major behind.Not complaining one bit, I have what I payed for; not a dime, yet gotten so much out of it, it's amazing! Big thanks to everyone involved for the work you do!/K(sort of the FOSS mantra, you know?)___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/KWAQ42RZI2YQZALY4HS3I2D3E74Y4FT2/___
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/WADHMJJEP2SXSDY5GGAHJ4WRTXLCMYLF/


[ovirt-users] VMs hung after migration

2018-05-31 Thread Kapetanakis Giannis
Hi,

Please have a look at BZ https://bugzilla.redhat.com/show_bug.cgi?id=1584775
about VM hung problems I have with latest kernels.

Problem appeared after upgrading to 4.2.3 but I believe it has only to do with 
newer kernel and not any part of ovirt/vdsm/libvirt/qemu

regards,

Giannis
___
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/IPORS7MNZJMCP5PYUUMBHBW7BWPK7PDO/


[ovirt-users] Re: [ANN] oVirt 4.2.4 Second Release Candidate is now available

2018-05-31 Thread Christopher Cox

I found some humor in the signature... so, my own spin.

TRIED (by a few). TESTED (a bit). TRUSTED (for now).

(sort of the FOSS mantra, you know?)
___
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/KWAQ42RZI2YQZALY4HS3I2D3E74Y4FT2/


[ovirt-users] [ANN] oVirt 4.2.4 Second Release Candidate is now available

2018-05-31 Thread Lev Veyde
The oVirt Project is pleased to announce the availability of the oVirt
4.2.4 Second Release Candidate, as of May 31st, 2018

This update is a release candidate of the fourth in a series of
stabilization updates to the 4.2
series.
This is pre-release software. This pre-release should not to be used in
production.

This release is available now for:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.5 or later
* CentOS Linux (or similar) 7.5 or later

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is available
- oVirt Node is available [2]

Additional Resources:
* Read more about the oVirt 4.2.4 release highlights:
http://www.ovirt.org/release/4.2.4/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.2.4/
[2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
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/CY3IG345HHJPTRCJUTKJ44JLK4MFP2OB/


[ovirt-users] Setting up new VM

2018-05-31 Thread 03ce007
I have self-hosted-engine (4.2) running on centos (7.4), the engine is running 
fine so I am trying to deploy a test vm to check ssh connectivity. 

however, the vm-infra role runs without any issues and I can see the new VM is 
in "up" state but it does not have any IP assigned eventhough I have defined it 
in the cloud_init dict. What I have noticed is that the reported_devices array 
comes out empty and hence the "Wait for VMs IP" task within create_vm.yml is 
keep getting skipped. 

TASK [oVirt.vm-infra : Wait for VMs IP] 
**
task path: /ansible/roles/oVirt.vm-infra/tasks/main.yml:102
skipping: [hypervisor-ovirt] => (item={'name': 'mytest01-vm', 'tag': 
'httpd_vm', 'profile': {'cluster': 'Default', 'domain': 'node.dev.dw', 
'template': 'rhel7', 'memory': '2GiB', 'cores': 2, 'ssh_key': 'ssh-rsa 
AAA...LGx user@fqdn', 'disks': [{'size': '10GiB', 'name': 'data', 
'storage_domain': 'hosted_storage', 'interface': 'virtio'}]}, 'cloud_init': 
{'host_name': 'mytestvm', 'dns_servers': '10.90.x.y 10.90.x.z', 
'nic_boot_protocol': 'static', 'nic_ip_address': '10.90.0.160', 'nic_netmask': 
'255.255.255.0', 'nic_gateway': '10.90.0.a', 'nic_name': 'eth0', 'nic_on_boot': 
True, 'custom_script': "write_files:\n - content: |\n Hello, world!\n   
path: /tmp/greeting.txt\n   permissions: '0644'\n", 'user_name': 'root', 
'root_password': 'super_pass'}, 'cloud_init_persist': True})  => {
"changed": false,
"item": {
"cloud_init": {
"custom_script": "write_files:\n - content: |\n Hello, world!\n 
  path: /tmp/greeting.txt\n   permissions: '0644'\n",
"dns_servers": "10.90.x.y 10.90.x.z",
"host_name": "mytestvm",
"nic_boot_protocol": "static",
"nic_gateway": "10.90.x.a",
"nic_ip_address": "10.90.x.b",
"nic_name": "eth0",
"nic_netmask": "255.255.255.0",
"nic_on_boot": true,
"root_password": "super_pass",
"user_name": "root"
},
"cloud_init_persist": true,
"name": "mytest01-vm",
"profile": {
"cluster": "Default",
"cores": 2,
"disks": [
{
"interface": "virtio",
"name": "data",
"size": "10GiB",
"storage_domain": "hosted_storage"
}
],
"domain": "node.dev.dw",
"memory": "2GiB",
"ssh_key": "ssh-rsa AAA...LGx user@fqdn",
"template": "rhel7"
},
"tag": "httpd_vm"
},
"skip_reason": "Conditional result was False"
}

I think this is the very last stage I am once the ssh connection works, I will 
be able to use with install yum repo, etc. 

Please advise. 
___
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/HPISGO6RI6CMS7VYXYLHNNMS2QT2HYYE/


[ovirt-users] Re: Unable to login after upgrade

2018-05-31 Thread Michael Watters

On 05/31/2018 06:43 AM, Ondra Machacek wrote:
> That's very strange, can you please share the upgrade log if you still
> have it?
>
Here's a copy of the upgrade log.  The file is pretty large.

https://paste.fedoraproject.org/paste/I3WapJfAnzk81gEgKeeIDg/

> Also can you please share the output of:
>
> $ select * from users;

Users table looks like this.

https://paste.fedoraproject.org/paste/1634vd5v75YOOOL7X96tzg/

Despite having two different "admin" accounts I can log in now.

>
> and
>
> $ select * from permissions;

https://paste.fedoraproject.org/paste/p9Bl2elvFDOn~Qgzm5J3eA

>
> and also please share content of:
>
>  /etc/ovirt-engine/extensions.d/internal-authn.properties
https://paste.fedoraproject.org/paste/hePCFb1ufc0NMlelTLyX-g/

>  /etc/ovirt-engine/extensions.d/internal-auth.properties
>  /etc/ovirt-engine/aaa/internal.properties

These files do not exist.  There is an internal-authz.properties file
which looks like this.

https://paste.fedoraproject.org/paste/gyhOj0FQvO~R5lFd4-5Z0Q/

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


[ovirt-users] Re: Non-responsive vm's due to crashed host and hosted vm liveliness check fails

2018-05-31 Thread Andrej Krejcir
Hi,

You could try accessing the engine VM using the VNC.
First, set the VNC password using 'hosted-engine --add-console-password',
and then connect to the host using a VNC viewer, for example:
'remove-viewer vnc://HOST_IP:5900'

The liveliness check just checks if the web UI is running and reachable.
If the VNC works, try checking if the 'ovirt-engine' service is running on
the VM and that the network is configured properly.


Andrej

On 30 May 2018 at 18:31,  wrote:

> Hi,
>
> I am still working to resolve my issue - is there any further detail or
> clarification I can provide that might help?  I really appreciate your time.
>
> Thank you,
> Charles
> ___
> 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/XE37L37BGTWIWXOYP5PTYM64I2NNKRO5/
>
___
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/KX6OEDEUVK43SXK3ICDO6KLW53YXH2BV/


[ovirt-users] Re: how to use oVirt engine API to retrieve the attached VM list by a disk id.

2018-05-31 Thread Ondra Machacek

On 05/31/2018 09:28 AM, iterjpnic  wrote:

Hi all,

I use oVirt engine API v4.2 for implementing terraform oVirt provider. And I 
want to check if a Disk has been attached to a VM, so I need to find all vms 
attached by this disk.
But after I checked the GET-Response data from the 
"/ovirt-engine/api/disks/" rest url, there has no disk-attachment/vm 
related properties or links. I could get a trade-off, by the following steps:
1. getting all vms
2. get all disk-attachments of each vm
3. check if the given disk id equals to the `disk` property of each 
disk-attachment`
4. If equals, append the vm to result list

Is there any simpler and smarter way to get this? Thanks.


Hi, you can use following:

 https://fqdn/ovirt-engine/api/disks?search=vm_names=myvmname


___
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/6LVOIVEUUO7PXVV36GH3V6GSURQV4ALO/


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


[ovirt-users] Re: Unable to login after upgrade

2018-05-31 Thread Ondra Machacek
That's very strange, can you please share the upgrade log if you still 
have it?


Also can you please share the output of:

$ select * from users;

and

$ select * from permissions;

and also please share content of:

 /etc/ovirt-engine/extensions.d/internal-authn.properties
 /etc/ovirt-engine/extensions.d/internal-auth.properties
 /etc/ovirt-engine/aaa/internal.properties

On 05/30/2018 06:12 PM, Michael Watters wrote:
It looks like the issue was caused by a new admin account being created 
in the internal-authz domain.  Here is what the engine logs show.


2018-05-30 11:15:21,893-04 INFO 
[org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-9) 
[] User admin@internal 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-05-30 11:15:22,175-04 INFO 
[org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default 
task-11) [77362b19] Running command: CreateUserSessionCommand internal: 
false.


2018-05-30 11:15:22,252-04 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-11) [77362b19] EVENT_ID: USER_VDC_LOGIN_FAILED(114), User 
admin@internal-authz connecting from '10.209.44.27' failed to log 
in.


2018-05-30 11:15:22,253-04 ERROR 
[org.ovirt.engine.core.aaa.servlet.SsoPostLoginServlet] (default 
task-11) [] The user admin@internal is not authorized to perform login


I was able to login after updating the permissions table to use the new 
user ID as follows.


update permissions set ad_element_id = (select user_id from users where 
domain = 'internal-authz' and username = 'admin') where ad_element_id = 
(select user_id from users where domain = 'internal' and username = 
'admin') ;


Despite this the ovirt-aaa-jdbc-tool still shows the wrong user ID when 
querying the admin account.  For example:


[root@mdct-ovirt-engine-dev ~]# ovirt-aaa-jdbc-tool user show admin
-- User admin(fdfc627c-d875-11e0-90f0-83df133b58cc) --
Namespace: *
Name: admin
ID: fdfc627c-d875-11e0-90f0-83df133b58cc
Display Name:
Email:
First Name: admin
Last Name:
Department:
Title:
Description:
Account Disabled: false
Account Locked: false
Account Unlocked At: 1970-01-01 00:00:00Z
Account Valid From: 2016-11-16 15:27:01Z
Account Valid To: 2216-11-16 15:27:01Z
Account Without Password: false
Last successful Login At: 2018-05-30 16:02:46Z
Last unsuccessful Login At: 2018-05-29 19:25:28Z
Password Valid To: 2216-09-29 15:27:01Z

Is there a way to resolve this conflict?  Where does the 
admin@internal-authz account come from?  I tried renaming the account 
but it is recreated every time that the engine is restarted.



On 05/29/2018 04:31 PM, Alex K wrote:
Are you using engine IP to login? Perhaps the sso default file was 
overwritten?


Alex

On Tue, May 29, 2018, 20:32 Michael Watters > wrote:


I recently upgraded one of our ovirt engines from 4.1 to the 4.2.3
release and the admin account is no longer able to login. After
entering the user name and password I receive a message that
states "The
user admin@internal is not authorized to perform login".

Is there a way to resolve this?  Resetting the password did not work.
___
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/FT3NKC36NMNDQEIWCVPMYSYSLVZSGJOM/





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


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


[ovirt-users] Re: VM status and issue with cloud_init

2018-05-31 Thread Arik Hadas
On Thu, May 31, 2018 at 10:08 AM, 03CE 007 <03ce...@gmail.com> wrote:

> Ok thanks, when you say guest agent, could you please provide the full
> name and how to have it installed, and I am assuming it should be installed
> on the the engineVM or the new VM I want to spin and boot up.
>

Generally speaking, we are transitioning from ovirt-guest-agent to
qemu-guest-agent.
I don't know what's the status of this transition with respect to centos as
I typically use latest-fedora.
Tomas, can you please advice what needs to be installed in centos 7.4?

And it should be installed in the new VM.


>
> On Thu, 31 May 2018, 7:57 am Arik Hadas,  wrote:
>
>>
>>
>> On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:
>>
>>> Some what new to the VM and Ovirt world here and need some help
>>> understanding terminologies and get the VM to work as per requirement.
>>>
>>> I have a self-hosted-engine (4.2) running on centos (7.4). The engine is
>>> in good health and I have deployed a test VM using below playbook
>>> successfully. It is currently in "up" state.
>>>
>>>
>>> - name: oVirt Self-Hosted-Engine - Manage VMs
>>>   hosts: hypervisor_ovirt
>>>   gather_facts: false
>>>
>>>   vars_files:
>>> # Contains encrypted `engine_password` varibale using ansible-vault
>>> - ovirt-secrets.yml
>>>
>>>   vars:
>>> engine_url: https://engine-ovirt.dw/ovirt-engine/api
>>> engine_user: admin@internal
>>> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>>>
>>> mytest_vm:
>>>   cluster: Default
>>>   memory: 64GiB
>>>   memory_guaranteed: 1GiB
>>>   cores: 2
>>>   nics:
>>> - name: vnet0
>>>   network: ovirtmgmt
>>>   profile: ovirtmgmt
>>>   interface: virtio
>>>   wait: true
>>>   domain: node.dev.dw
>>>   os_type: rhel_7x64
>>>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>>>   root_password: super_password
>>>   disks:
>>> - size: 20GiB
>>>   name: data
>>>   storage_domain: hosted_storage
>>>   interface: virtio
>>>   bootable: true
>>>   nics:
>>> - name: vnet0
>>>   network: ovirtmgmt
>>>   profile: ovirtmgmt
>>>   interface: virtio
>>>
>>> vms:
>>>   - name: mytest_vm
>>> tag: mytest_vm
>>> profile: "{{ mytest_vm }}"
>>> cloud_init:
>>>   dns_servers:
>>> - 10.90.x.1
>>> - 10.90.x.1
>>>   nic_boot_protocol: static
>>>   nic_ip_address: 10.90.x.y
>>>   nic_netmask: 255.255.255.0
>>>   nic_gateway: 10.90.x.z
>>>   nic_name: eth0
>>>   nic_on_boot: true
>>>   host_name: mytestvm.test.dw
>>>   custom_script: |
>>> write_files:
>>>  - content: |
>>>  Hello, world!
>>>path: /tmp/greeting.txt
>>>permissions: '0644'
>>>   user_name: root
>>>   root_password: super_password
>>> cloud_init_persist: true
>>>
>>>   roles:
>>> - oVirt.vm-infra
>>>
>>>
>>> Above playbook runs fine, but when i see summary using ovirt4.py, i do
>>> not see ipaddr for this test vm.
>>>
>>> - I do not see the ipaddr for this VM despite specifying it using
>>> cloud_init
>>>
>>
>> You need to install a guest agent in order to be provided with ip
>> addresses.
>>
>>
>>> - does the "up" status mean it has "booted" or I need to do something
>>> else to boot it with centos 7.4 minimal
>>>
>>
>> Without a guest agent installed we know nothing about the state of the
>> guest so in this case the UP status only means that the VM process is
>> running for more than 1 minute.
>>
>>
>>>
>>> Thank you in advance.
>>> ___
>>> 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/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>>>
>>
>>
___
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/RNDG6JSHOCRPT2OX4OJZFGK4CVTEH4LB/


[ovirt-users] Re: VM status and issue with cloud_init

2018-05-31 Thread 03CE 007
upon checking  yum install ovirt-guest-agent-common, I can get

Package ovirt-guest-agent-common-1.0.14-1.el7.noarch already installed and
latest version
Nothing to do

systemctl status ovirt-guest-agent.service shows that service is enabled
and has been running.

Is there something else I need to check/do ?


On 31 May 2018 at 07:57, Arik Hadas  wrote:

>
>
> On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:
>
>> Some what new to the VM and Ovirt world here and need some help
>> understanding terminologies and get the VM to work as per requirement.
>>
>> I have a self-hosted-engine (4.2) running on centos (7.4). The engine is
>> in good health and I have deployed a test VM using below playbook
>> successfully. It is currently in "up" state.
>>
>>
>> - name: oVirt Self-Hosted-Engine - Manage VMs
>>   hosts: hypervisor_ovirt
>>   gather_facts: false
>>
>>   vars_files:
>> # Contains encrypted `engine_password` varibale using ansible-vault
>> - ovirt-secrets.yml
>>
>>   vars:
>> engine_url: https://engine-ovirt.dw/ovirt-engine/api
>> engine_user: admin@internal
>> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>>
>> mytest_vm:
>>   cluster: Default
>>   memory: 64GiB
>>   memory_guaranteed: 1GiB
>>   cores: 2
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>   wait: true
>>   domain: node.dev.dw
>>   os_type: rhel_7x64
>>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>>   root_password: super_password
>>   disks:
>> - size: 20GiB
>>   name: data
>>   storage_domain: hosted_storage
>>   interface: virtio
>>   bootable: true
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>
>> vms:
>>   - name: mytest_vm
>> tag: mytest_vm
>> profile: "{{ mytest_vm }}"
>> cloud_init:
>>   dns_servers:
>> - 10.90.x.1
>> - 10.90.x.1
>>   nic_boot_protocol: static
>>   nic_ip_address: 10.90.x.y
>>   nic_netmask: 255.255.255.0
>>   nic_gateway: 10.90.x.z
>>   nic_name: eth0
>>   nic_on_boot: true
>>   host_name: mytestvm.test.dw
>>   custom_script: |
>> write_files:
>>  - content: |
>>  Hello, world!
>>path: /tmp/greeting.txt
>>permissions: '0644'
>>   user_name: root
>>   root_password: super_password
>> cloud_init_persist: true
>>
>>   roles:
>> - oVirt.vm-infra
>>
>>
>> Above playbook runs fine, but when i see summary using ovirt4.py, i do
>> not see ipaddr for this test vm.
>>
>> - I do not see the ipaddr for this VM despite specifying it using
>> cloud_init
>>
>
> You need to install a guest agent in order to be provided with ip
> addresses.
>
>
>> - does the "up" status mean it has "booted" or I need to do something
>> else to boot it with centos 7.4 minimal
>>
>
> Without a guest agent installed we know nothing about the state of the
> guest so in this case the UP status only means that the VM process is
> running for more than 1 minute.
>
>
>>
>> Thank you in advance.
>> ___
>> 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/communit
>> y/about/community-guidelines/
>> List Archives: https://lists.ovirt.org/archiv
>> es/list/users@ovirt.org/message/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>>
>
>
___
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/EUG3IUI6QF6AMWG7XZRJHEGETHDVVZL3/


[ovirt-users] how to use oVirt engine API to retrieve the attached VM list by a disk id.

2018-05-31 Thread iterjpnic
Hi all,

I use oVirt engine API v4.2 for implementing terraform oVirt provider. And I 
want to check if a Disk has been attached to a VM, so I need to find all vms 
attached by this disk. 
But after I checked the GET-Response data from the 
"/ovirt-engine/api/disks/" rest url, there has no disk-attachment/vm 
related properties or links. I could get a trade-off, by the following steps:
1. getting all vms
2. get all disk-attachments of each vm
3. check if the given disk id equals to the `disk` property of each 
disk-attachment`
4. If equals, append the vm to result list

Is there any simpler and smarter way to get this? Thanks.
___
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/6LVOIVEUUO7PXVV36GH3V6GSURQV4ALO/


[ovirt-users] Re: Simple API call to start VM

2018-05-31 Thread Fred Rolland
Try to use:
--data ''

On Thu, May 31, 2018 at 5:30 AM, Kirin van der Veer <
kirin.vanderv...@planetinnovation.com.au> wrote:

> Many thanks to:
> gsswzt, Luca, Andrej, Fred, Karli, Ondra and Bohdan for their replies.
>
> A number of people mentioned the need to specify a CA cert, but curl was
> able to find my organizations CA locally - so that was not an issue.
> Correcting my url to include ovirt-engine in the path and my username to
> admin@internal as suggested by Andrej as per below:
> curl --user "admin@internal:SECRETPASSWORD" --request POST --header
> "Content-Type: application/xml" --header "Accept: application/xml" --data
> '' https://ovirt-engine.localnet:443/ovirt-engine/api/vms/
> 69c47a91-bbv1-4eda-b71d-7bddf82ee8ab/start
>
> Got me a new error message:
> 
> 
> For correct usage, see: https://ovirt-engine.localnet/
> ovirt-engine/apidoc#services/vm/methods/start
> Request syntactically incorrect.
> 
>
> I followed the URL, but it just seemed to repeat the information already
> available at http://ovirt.github.io/ovirt-engine-api-model/4.2/#
> services/vm/methods/start
>
> Here is the relevant section of engine.log on ovirt-engine.localnet:
> 2018-05-31 10:48:15,550+10 INFO  
> [org.ovirt.engine.core.sso.utils.AuthenticationUtils]
> (default task-25) [] User admin@internal successfully logged in with
> scopes: ovirt-app-api ovirt-ext=token-info:authz-search
> ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate
> ovirt-ext=token:password-access
> 2018-05-31 10:48:15,569+10 INFO  
> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand]
> (default task-29) [8ffa0f3] Running command: CreateUserSessionCommand
> internal: false.
> 2018-05-31 10:48:15,581+10 INFO  [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] (default task-29) [8ffa0f3]
> EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from
> '192.168.1.0' using session 'JNweIEHoHhw9U+wMt7Z03Ovb5Pc1zR3WyvTcSfRTpdHj
> d55CHbcspfDcJgToMVshtlgXamzvUSW2rzHB9ApJHA==' logged in.
> 2018-05-31 10:48:15,587+10 ERROR [org.ovirt.engine.api.restapi.
> resource.validation.IOExceptionMapper] (default task-29) [] IO exception
> while processing "POST" request for path "/vms/69c47a91-bbv1-4eda-b71d-
> 7bddf82ee8ab/start"
> 2018-05-31 10:48:15,587+10 ERROR [org.ovirt.engine.api.restapi.
> resource.validation.IOExceptionMapper] (default task-29) [] Exception:
> java.io.IOException: javax.xml.stream.XMLStreamException: ParseError at
> [row,col]:[1,2]
> Message: The markup in the document preceding the root element must be
> well-formed.
> at 
> org.ovirt.engine.api.restapi.xml.JAXBProvider.readFrom(JAXBProvider.java:200)
> [restapi-jaxrs.jar:]
> at 
> org.ovirt.engine.api.restapi.xml.JAXBProvider.readFrom(JAXBProvider.java:162)
> [restapi-jaxrs.jar:]
> at org.jboss.resteasy.core.interception.AbstractReaderInterceptorConte
> xt.readFrom(AbstractReaderInterceptorContext.java:66)
> [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final]
> at org.jboss.resteasy.core.interception.ServerReaderInterceptorContext
> .readFrom(ServerReaderInterceptorContext.java:61)
> [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final]
> at org.jboss.resteasy.core.interception.AbstractReaderInterceptorConte
> xt.proceed(AbstractReaderInterceptorContext.java:56)
> [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final]
> at org.jboss.resteasy.security.doseta.DigitalVerificationInterceptor
> .aroundReadFrom(DigitalVerificationInterceptor.java:36)
> [resteasy-crypto-3.0.24.Final.jar:3.0.24.Final]
> 
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at
> [row,col]:[1,2]
> Message: The markup in the document preceding the root element must be
> well-formed.
> at 
> com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:604)
> [rt.jar:1.8.0_171]
> at com.sun.xml.bind.v2.runtime.unmarshaller.
> StAXStreamConnector.bridge(StAXStreamConnector.java:164)
> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.
> unmarshal0(UnmarshallerImpl.java:415)
> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.
> unmarshal(UnmarshallerImpl.java:386)
> at 
> org.ovirt.engine.api.restapi.xml.JAXBProvider.readFrom(JAXBProvider.java:187)
> [restapi-jaxrs.jar:]
> ... 104 more
> 2018-05-31 10:48:15,593+10 INFO  
> [org.ovirt.engine.core.bll.aaa.LogoutSessionCommand]
> (default task-29) [4531c52a] Running command: LogoutSessionCommand
> internal: false.
> 2018-05-31 10:48:15,598+10 INFO  [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] (default task-29) [4531c52a]
> EVENT_ID: USER_VDC_LOGOUT(31), User admin@internal-authz connected from
> '192.168.1.0' using session 'JNweIEHoHhw9U+wMt7Z03Ovb5Pc1zR3WyvTcSfRTpdHj
> d55CHbcspfDcJgToMVshtlgXamzvUSW2rzHB9ApJHA==' logged out.
> 2018-05-31 10:48:27,542+10 INFO  
> [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet]
> (defa

[ovirt-users] Re: VM status and issue with cloud_init

2018-05-31 Thread 03CE 007
Ok thanks, when you say guest agent, could you please provide the full name
and how to have it installed, and I am assuming it should be installed on
the the engineVM or the new VM I want to spin and boot up.

On Thu, 31 May 2018, 7:57 am Arik Hadas,  wrote:

>
>
> On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:
>
>> Some what new to the VM and Ovirt world here and need some help
>> understanding terminologies and get the VM to work as per requirement.
>>
>> I have a self-hosted-engine (4.2) running on centos (7.4). The engine is
>> in good health and I have deployed a test VM using below playbook
>> successfully. It is currently in "up" state.
>>
>>
>> - name: oVirt Self-Hosted-Engine - Manage VMs
>>   hosts: hypervisor_ovirt
>>   gather_facts: false
>>
>>   vars_files:
>> # Contains encrypted `engine_password` varibale using ansible-vault
>> - ovirt-secrets.yml
>>
>>   vars:
>> engine_url: https://engine-ovirt.dw/ovirt-engine/api
>> engine_user: admin@internal
>> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>>
>> mytest_vm:
>>   cluster: Default
>>   memory: 64GiB
>>   memory_guaranteed: 1GiB
>>   cores: 2
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>   wait: true
>>   domain: node.dev.dw
>>   os_type: rhel_7x64
>>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>>   root_password: super_password
>>   disks:
>> - size: 20GiB
>>   name: data
>>   storage_domain: hosted_storage
>>   interface: virtio
>>   bootable: true
>>   nics:
>> - name: vnet0
>>   network: ovirtmgmt
>>   profile: ovirtmgmt
>>   interface: virtio
>>
>> vms:
>>   - name: mytest_vm
>> tag: mytest_vm
>> profile: "{{ mytest_vm }}"
>> cloud_init:
>>   dns_servers:
>> - 10.90.x.1
>> - 10.90.x.1
>>   nic_boot_protocol: static
>>   nic_ip_address: 10.90.x.y
>>   nic_netmask: 255.255.255.0
>>   nic_gateway: 10.90.x.z
>>   nic_name: eth0
>>   nic_on_boot: true
>>   host_name: mytestvm.test.dw
>>   custom_script: |
>> write_files:
>>  - content: |
>>  Hello, world!
>>path: /tmp/greeting.txt
>>permissions: '0644'
>>   user_name: root
>>   root_password: super_password
>> cloud_init_persist: true
>>
>>   roles:
>> - oVirt.vm-infra
>>
>>
>> Above playbook runs fine, but when i see summary using ovirt4.py, i do
>> not see ipaddr for this test vm.
>>
>> - I do not see the ipaddr for this VM despite specifying it using
>> cloud_init
>>
>
> You need to install a guest agent in order to be provided with ip
> addresses.
>
>
>> - does the "up" status mean it has "booted" or I need to do something
>> else to boot it with centos 7.4 minimal
>>
>
> Without a guest agent installed we know nothing about the state of the
> guest so in this case the UP status only means that the VM process is
> running for more than 1 minute.
>
>
>>
>> Thank you in advance.
>> ___
>> 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/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>>
>
>
___
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/JPKSV7NABF64XRQIESB6LHADERXAQPMO/


[ovirt-users] Re: Attaching previously owned storage domain to 4.2 Cluster

2018-05-31 Thread Luca 'remix_tj' Lorenzetto
On Wed, May 30, 2018 at 4:59 PM, John Nguyen  wrote:

> Hi Guys,
>
> I'm working through a disaster recovery of a failed cluster.  And I found
> the documentation for attaching the old storage domain as an import domain
> to a new Cluster.  Both clusters are 4.2.
>
> https://ovirt.org/develop/release-management/features/
> storage/importstoragedomain/
>
> The documentation is referencing 3.5 and I would like to know if its still
> applies to the 4.2 release.
>
> When I try to do the import I see warnings below:
>
>
>
> I know that its really hard to say this operation may not be destructive.
> But is the general work flow outlined in the 3.5 documentation still valid?
>
>
Hello John,

this is an expected message if your source cluster has been shut in a bad
manner. You can import with no problems and then import all VMS.

If you want to automate this task, i suggest you to take a look to
https://github.com/oVirt/ovirt-ansible-disaster-recovery

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 , <
lorenzetto.l...@gmail.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/EK234XU7AHA6X34BWWCNLKKI3V2ERMP7/