date:20170728

[ovirt-users] Hosted Engine increase memory

2017-07-28 Thread gregor

Hi,

is it possible to increase the memory of an hosted engine after the
installation?

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

[ovirt-users] ovirt and mixed selinux

2017-07-28 Thread Bill James


I was hoping to migrate my systems to using selinux gradually.
I added 3 new nodes with selinux in permissive mode.
Migration fails to any of the previous hosts that currently have selinux 
disabled.
Is it an all or nothing deal? Obviously not easy to reboot all nodes at 
once.


2017-07-28 09:35:43,616 ERROR (migsrc/8c566813) [virt.vm] 
(vmId='8c566813-4bee-4f04-be23-c9fc10e1e1f2') unsupported configuration: 
Unable to find security driver for model selinux (migration:265)
2017-07-28 09:35:43,641 ERROR (migsrc/8c566813) [virt.vm] 
(vmId='8c566813-4bee-4f04-be23-c9fc10e1e1f2') Failed to migrate 
(migration:405)

Traceback (most recent call last):


ovirt-engine-4.1.0.4-1.el7.centos.noarch
libselinux-utils-2.5-6.el7.x86_64


related: http://lists.ovirt.org/pipermail/users/2016-October/076878.html

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

[ovirt-users] Deploying training lab

2017-07-28 Thread Andy Michielsen

Hello all,

Don't know if this is the right place to ask this but I would like to set
up a trainingslab with oVirt.

I have deployed an engine and a host with local storage and want to run 1
server and 5 desktops off it.

But the desktops will be used on thin clients or old laptops with some
minimal os installation running spice client or a webbrowser.

I was wondering if anyone can give me pointer in how to set up a minimal
laptop which only need to run an spice client.

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

Re: [ovirt-users] Problemas with ovirtmgmt network used to connect VMs

2017-07-28 Thread Edward Haas

Hello Fernando,

Have you taken the tcpdump in the VM to see what traffic is sent out?
Your host is a Centos 7.3? If so how come it has such a kernel version?

Have you see anything in /var/log/messages when it gets disconnected?

Thanks,
Edy.


On Fri, Jul 28, 2017 at 9:01 PM, FERNANDO FREDIANI <
fernando.fredi...@upx.com> wrote:

> Hello Edwardh and all.
>
> I keep getting these disconnects, were you able to find anything about to
> suggest changing ?
>
> As I mentioned this machine different from the others where it never
> happened uses the ovirtmgmt network as VM network and has kernel 4.12
> instead of the default 3.10 from CentOS 7.3. It seems a particular
> situation that is triggering this behavior but could not gather any hint
> yet.
>
> I have tried to run a regular arping to force the bridge always learn the
> VMs MAC address but it doesn't seem to work and every in a while the bridge
> 'forgets' that particular VM mac address.
> I have also even rebuilt the VM completely changing its operating system
> from Ubuntu 16.04 to CentOS 7.3 and the same problem happened.
>
> Fernando
>
> On 24/07/2017 18:20, FERNANDO FREDIANI wrote:
>
> Hello Edward, this happened again today and I was able to check more
> details.
>
> So:
>
> - The VM stopped passing any network traffic.
> - Checking 'brctl showmacs ovirtmgmt' it showed the VM's mac address
> missing.
> - I then went to oVirt Engine, under VM's 'Network Interfaces' tab,
> clicked Edit and changed the Link State to Down then to Up and it recovered
> its connectivity.
> - Another 'brctl showmacs ovirtmgmt' showed the VM's mac address learned
> again by the bridge.
>
> This Node server has the particularity of sharing the ovirtmgmt with VMs.
> Could it possibly be the cause of the issue in any way ?
>
> Thanks
> Fernando
>
> On 24/07/2017 09:47, FERNANDO FREDIANI wrote:
>
> Not tried this yet Edwardh, but will do at next time it happens. THe
> source mac address should be the mac as the VM. I don't see any reason for
> it to change from within the VM ou outside.
>
> What type of things would make the bridge stop learning a given VM mac
> address ?
>
> Fernando
>
> On 23/07/2017 07:51, Edward Haas wrote:
>
> Have you tried to use tcpdump at the VM vNIC to examine if there is
> traffic trying to get out from there? And with what source mac address?
>
> Thanks,
> Edy,
>
> On Fri, Jul 21, 2017 at 5:36 PM, FERNANDO FREDIANI <
> fernando.fredi...@upx.com> wrote:
>
>> Has anyone had problem when using the ovirtmgmt bridge to connect VMs ?
>>
>> I am still facing a bizarre problem where some VMs connected to this
>> bridge stop passing traffic. Checking the problem further I see its mac
>> address stops being learned by the bridge and the problem is resolved only
>> with a VM reboot.
>>
>> When I last saw the problem I run brctl showmacs ovirtmgmt and it shows
>> me the VM's mac adress with agening timer 200.19. After the VM reboot I see
>> the same mac with agening timer 0.00.
>> I don't see it in another environment where the ovirtmgmt is not used for
>> VMs.
>>
>> Does anyone have any clue about this type of behavior ?
>>
>> Fernando
>> ___
>> 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] Problemas with ovirtmgmt network used to connect VMs

2017-07-28 Thread FERNANDO FREDIANI


Hello Edwardh and all.

I keep getting these disconnects, were you able to find anything about 
to suggest changing ?


As I mentioned this machine different from the others where it never 
happened uses the ovirtmgmt network as VM network and has kernel 4.12 
instead of the default 3.10 from CentOS 7.3. It seems a particular 
situation that is triggering this behavior but could not gather any hint 
yet.


I have tried to run a regular arping to force the bridge always learn 
the VMs MAC address but it doesn't seem to work and every in a while the 
bridge 'forgets' that particular VM mac address.
I have also even rebuilt the VM completely changing its operating system 
from Ubuntu 16.04 to CentOS 7.3 and the same problem happened.


Fernando


On 24/07/2017 18:20, FERNANDO FREDIANI wrote:


Hello Edward, this happened again today and I was able to check more 
details.


So:

- The VM stopped passing any network traffic.
- Checking 'brctl showmacs ovirtmgmt' it showed the VM's mac address 
missing.
- I then went to oVirt Engine, under VM's 'Network Interfaces' tab, 
clicked Edit and changed the Link State to Down then to Up and it 
recovered its connectivity.
- Another 'brctl showmacs ovirtmgmt' showed the VM's mac address 
learned again by the bridge.


This Node server has the particularity of sharing the ovirtmgmt with 
VMs. Could it possibly be the cause of the issue in any way ?


Thanks
Fernando


On 24/07/2017 09:47, FERNANDO FREDIANI wrote:


Not tried this yet Edwardh, but will do at next time it happens. THe 
source mac address should be the mac as the VM. I don't see any 
reason for it to change from within the VM ou outside.


What type of things would make the bridge stop learning a given VM 
mac address ?


Fernando


On 23/07/2017 07:51, Edward Haas wrote:
Have you tried to use tcpdump at the VM vNIC to examine if there is 
traffic trying to get out from there? And with what source mac address?


Thanks,
Edy,

On Fri, Jul 21, 2017 at 5:36 PM, FERNANDO FREDIANI 
> wrote:


Has anyone had problem when using the ovirtmgmt bridge to
connect VMs ?

I am still facing a bizarre problem where some VMs connected to
this bridge stop passing traffic. Checking the problem further I
see its mac address stops being learned by the bridge and the
problem is resolved only with a VM reboot.

When I last saw the problem I run brctl showmacs ovirtmgmt and
it shows me the VM's mac adress with agening timer 200.19. After
the VM reboot I see the same mac with agening timer 0.00.
I don't see it in another environment where the ovirtmgmt is not
used for VMs.

Does anyone have any clue about this type of behavior ?

Fernando
___
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] supervdsmd IOError to /dev/stdout

2017-07-28 Thread Richard Chan

After an upgrade to 4.0 I have a single host that cannot start supervdsmd
because of IOError on /dev/stdout. All other hosts upgraded correctly.

In the systemd unit I have to hack StandardOutput=null.

Any thing I have overlooked? The hosts are all identical and it is just
this one
that has this weird behaviour.


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

Re: [ovirt-users] Migration network used also as vm network

2017-07-28 Thread Edward Haas

There is a security drawback involved as well, the VM/s can access the host
through that IP.


On Tue, Jul 25, 2017 at 10:45 AM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

> Hello Gianluca,
>
> As far as i know this shouldn't be a problem, you can have ips on any
> interface.
>
> The only drawbacks can be related to performance of migrations if vms on
> that interface makes too much traffic.
>
> Luca
>
> Il 25 lug 2017 9:25 AM, "Gianluca Cecchi"  ha
> scritto:
>
>> Hello,
>> I have a 10Gbit vlan defined as migration network and currently not
>> enabled as vm network.
>> When you configure a host interface, assigning a vlan that is defined as
>> migration network, you must assign an ip to it on the host.
>>
>> Suppose I want to edit this vlan in DC so that I enable it to be also a
>> VM network, are there any drawbacks having for example on a host the ip for
>> this vlan (the migration ip) and also one or more running VMs with their
>> vnics configured on this vlan too...?
>>
>> Thanks in advance,
>> Gianluca
>>
>> ___
>> 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] oVirt and Foreman

2017-07-28 Thread Davide Ferrari




On 28/07/17 17:46, Juan Hernández wrote:


The oVirt access log indeed shows that three disks are added to the 
virtual machine. May it be that Foreman thinks that it has to 
explicitly add a boot disk? Ohad, Ivan, any idea?




I've explicitly added the template id to the hammer command line and 
still adds 3 disks but at least now two of them respect the size I'm 
passing through Hammer. But it still sets a random disk as the bootable 
one and I cannot find a way to force to use the disk already present in 
the oVirt template as the bootable one
Is there a way in oVirt to log the JSONs passed in the various POST 
requests?




More over, looking at 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks it 
throws a 404, the endpoint seems to be 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/diskattachments 
while 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
seems to work only with API v3. Maybe I should change the base URL 
for the ovirt's API in foreman config, shouldn't I?




I think you don't need to change anything there. Foreman uses 
'rbovirt', and 'rbovirt' explicitly requests version 3 of the API 
using the 'Version: 3' header. 


Well, I've added it anyway and it didn't break anything :)

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

Re: [ovirt-users] oVirt and Foreman

2017-07-28 Thread Juan Hernández


On 07/28/2017 04:53 PM, Davide Ferrari wrote:



On 28/07/17 16:14, Juan Hernández wrote:
Ah, I see, in your command you are listing Gluster volumes, not 
storage domains. They are different kinds of objects inside oVirt, and 
thus they have different identifiers. That is completely normal. If 
you want to get the identifiers of the storage domains use "list 
storagedomains".




Oh, got it. Thanks for the tip!

Anyway, I've replaced the storage domain UUID with the one that works 
with the REST API and something improved: now I don't get the 404 
from ovirt and the machine is not deleted BUT:  I've added 2 disks 
(20GB and 30GB) plus the base template 8Gb disk, and I get a VM with 
four (4) 8GB disks, and the bootable one is a random disk


I've attached the engine.log with the (I hope) relevant messages



Are you adding those disks and template using the Foreman CLI? Can you 
share the commands that you are using?




Yes, I'm using Hammer CLI

hammer host create --architecture-id=1 --domain billy.preprod 
--operatingsystem-id=7 --hostgroup-title Billy/Preprod --name foobar03 
--partition-table-id=192 --provision-method image --root-password 
billy12345 --compute-resource 'LeaseWeb VMs prod' --image CentOS_7.3 
--compute-attributes 
cluster=0002-0002-0002-0002-0345,cores=2,memory=4294967296,start=1 
--volume 
'"size_gb=20,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=0"' 
--volume 
'"size_gb=30,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=0"' 




Also, can you share again the relevant part of the 
/var/log/ovirt-engine/ssl_access_log file? There we can see what 
requests are actually sent to the oVirt engine. 


These are the requests arriving from Foreman:
192.168.10.158 - - [28/Jul/2017:14:19:42 +] "GET 
/ovirt-engine/api/vms/24831007-97ad-4f6d-9009-e6fb68a585f9 HTTP/1.1" 200 
2865
192.168.10.158 - - [28/Jul/2017:14:26:19 +] "GET 
/ovirt-engine/api/datacenters?search= HTTP/1.1" 200 408
192.168.10.158 - - [28/Jul/2017:14:26:19 +] "GET 
/ovirt-engine/api/operatingsystems HTTP/1.1" 200 2943
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/datacenters?search= HTTP/1.1" 200 408
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/operatingsystems HTTP/1.1" 200 2943
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/datacenters?search= HTTP/1.1" 200 408
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/clusters/ HTTP/1.1" 200 1091
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "POST 
/ovirt-engine/api/vms HTTP/1.1" 202 1612
192.168.10.158 - - [28/Jul/2017:14:26:22 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:22 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics 
HTTP/1.1" 200 409
192.168.10.158 - - [28/Jul/2017:14:26:22 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:23 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:26 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:30 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2252
192.168.10.158 - - [28/Jul/2017:14:26:30 +] "DELETE 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics/bf0dabd2-796b-4b07-bd69-db3915409939 
HTTP/1.1" 200 119
192.168.10.158 - - [28/Jul/2017:14:26:30 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics 
HTTP/1.1" 201 430
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics 
HTTP/1.1" 200 442
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "GET /ovirt-engine/api/ 
HTTP/1.1" 200 873
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "GET 
/ovirt-engine/api/datacenters/0001-0001-0001-0001-03e3 
HTTP/1.1" 200 396
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 201 674
192.168.10.158 - - [28/Jul/2017:14:26:32 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 201 676
192.168.10.158 - - [28/Jul/2017:14:26:33 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 201 677
192.168.10.158 - - [28/Jul/2017:14:26:33 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 200 1136
192.168.10.158 - - [28/Jul/2017:14:26:34 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2668
192.168.10.158 - - [28/Jul/2017:14:26:34 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2668
192.168.10.158 - - [28/Jul/2017:14:26:34 +] "GET

Re: [ovirt-users] Regarding Ovirt Node ISO

2017-07-28 Thread Yuval Turgeman

Hi,

Yes, you can find a manifest-rpm file in the exported artifacts for the
ovirt-node-ng jobs.

Thanks,
Yuval.

On Jul 28, 2017 8:41 AM, "TranceWorldLogic ." 
wrote:

> Hi,
>
> I want to know packages list in ovirt node ISO.
> Do we have some documentation or some auto output of jenkin job ?
>
> Please let me know.
>
> Thanks,
> ~Rohit
>
> ___
> 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] oVirt and Foreman

2017-07-28 Thread Davide Ferrari




On 28/07/17 16:14, Juan Hernández wrote:
Ah, I see, in your command you are listing Gluster volumes, not 
storage domains. They are different kinds of objects inside oVirt, and 
thus they have different identifiers. That is completely normal. If 
you want to get the identifiers of the storage domains use "list 
storagedomains".




Oh, got it. Thanks for the tip!

Anyway, I've replaced the storage domain UUID with the one that works 
with the REST API and something improved: now I don't get the 404 
from ovirt and the machine is not deleted BUT:  I've added 2 disks 
(20GB and 30GB) plus the base template 8Gb disk, and I get a VM with 
four (4) 8GB disks, and the bootable one is a random disk


I've attached the engine.log with the (I hope) relevant messages



Are you adding those disks and template using the Foreman CLI? Can you 
share the commands that you are using?




Yes, I'm using Hammer CLI

hammer host create --architecture-id=1 --domain billy.preprod 
--operatingsystem-id=7 --hostgroup-title Billy/Preprod --name foobar03 
--partition-table-id=192 --provision-method image --root-password 
billy12345 --compute-resource 'LeaseWeb VMs prod' --image CentOS_7.3 
--compute-attributes 
cluster=0002-0002-0002-0002-0345,cores=2,memory=4294967296,start=1 
--volume 
'"size_gb=20,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=0"' 
--volume 
'"size_gb=30,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=0"'



Also, can you share again the relevant part of the 
/var/log/ovirt-engine/ssl_access_log file? There we can see what 
requests are actually sent to the oVirt engine. 


These are the requests arriving from Foreman:
192.168.10.158 - - [28/Jul/2017:14:19:42 +] "GET 
/ovirt-engine/api/vms/24831007-97ad-4f6d-9009-e6fb68a585f9 HTTP/1.1" 200 
2865
192.168.10.158 - - [28/Jul/2017:14:26:19 +] "GET 
/ovirt-engine/api/datacenters?search= HTTP/1.1" 200 408
192.168.10.158 - - [28/Jul/2017:14:26:19 +] "GET 
/ovirt-engine/api/operatingsystems HTTP/1.1" 200 2943
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/datacenters?search= HTTP/1.1" 200 408
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/operatingsystems HTTP/1.1" 200 2943
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/datacenters?search= HTTP/1.1" 200 408
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "GET 
/ovirt-engine/api/clusters/ HTTP/1.1" 200 1091
192.168.10.158 - - [28/Jul/2017:14:26:20 +] "POST 
/ovirt-engine/api/vms HTTP/1.1" 202 1612
192.168.10.158 - - [28/Jul/2017:14:26:22 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:22 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics 
HTTP/1.1" 200 409
192.168.10.158 - - [28/Jul/2017:14:26:22 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:23 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:26 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2256
192.168.10.158 - - [28/Jul/2017:14:26:30 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2252
192.168.10.158 - - [28/Jul/2017:14:26:30 +] "DELETE 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics/bf0dabd2-796b-4b07-bd69-db3915409939 
HTTP/1.1" 200 119
192.168.10.158 - - [28/Jul/2017:14:26:30 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics 
HTTP/1.1" 201 430
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/nics 
HTTP/1.1" 200 442
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "GET /ovirt-engine/api/ 
HTTP/1.1" 200 873
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "GET 
/ovirt-engine/api/datacenters/0001-0001-0001-0001-03e3 
HTTP/1.1" 200 396
192.168.10.158 - - [28/Jul/2017:14:26:31 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 201 674
192.168.10.158 - - [28/Jul/2017:14:26:32 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 201 676
192.168.10.158 - - [28/Jul/2017:14:26:33 +] "POST 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 201 677
192.168.10.158 - - [28/Jul/2017:14:26:33 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1" 200 1136
192.168.10.158 - - [28/Jul/2017:14:26:34 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2668
192.168.10.158 - - [28/Jul/2017:14:26:34 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7 HTTP/1.1" 200 
2668
192.168.10.158 - - [28/Jul/2017:14:26:34 +] "GET 
/ovirt-engine/api/vms/47f5035a-696c-4578-ace9-b23d865c6aa7/disks 
HTTP/1.1"

Re: [ovirt-users] oVirt and Foreman

2017-07-28 Thread Juan Hernández


On 07/28/2017 01:27 PM, Davide Ferrari wrote:



On 28/07/17 10:50, Juan Hernández wrote:
[oVirt shell (connected)]# list glustervolumes --cluster-identifier 
0002-0002-0002-0002-0345


id : 23f8f1ae-a3ac-47bf-8223-5b5f7c29e508
name   : data_ssd

id : 6be35972-4720-4d34-b2b0-26ffc294f8a3
name   : engine

id : 66f33b1e-7bc8-44cf-9cca-9041b0e0dd15
name   : export

id : cc2c9765-6a3d-4281-8af8-c3526a81cfab
name   : iso

So there is something wrong with the "data_ssd" storage domain, 
apparently, as the identifier that can't be found corresponds to that 
storage domain. Can you try to retrieve that storage domain? Just use 
your browser to get the following URL:



https://yourovirt/ovirt-engine/api/storagedomains/23f8f1ae-a3ac-47bf-8223-5b5f7c29e508 



Also this, in case the problem is related to version 3 of the API:


https://yourovirt/ovirt-engine/api/v3/storagedomains/23f8f1ae-a3ac-47bf-8223-5b5f7c29e508 



Do they work?



Nope, 404 both v4 and v3 API, but if I go to the storagedomains/ root, I 
get completely different UUIDs listed there. For example, in the case of 
the "data_ssd" domain, the UUID is 7a28ea1a-df7e-4205-bb96-45ff2817f175


Why is the ovirt console showing a completely different UUID?



Ah, I see, in your command you are listing Gluster volumes, not storage 
domains. They are different kinds of objects inside oVirt, and thus they 
have different identifiers. That is completely normal. If you want to 
get the identifiers of the storage domains use "list storagedomains".


Anyway, I've replaced the storage domain UUID with the one that works 
with the REST API and something improved: now I don't get the 404 from 
ovirt and the machine is not deleted BUT:  I've added 2 disks (20GB and 
30GB) plus the base template 8Gb disk, and I get a VM with four (4) 8GB 
disks, and the bootable one is a random disk


I've attached the engine.log with the (I hope) relevant messages



Are you adding those disks and template using the Foreman CLI? Can you 
share the commands that you are using?


Also, can you share again the relevant part of the 
/var/log/ovirt-engine/ssl_access_log file? There we can see what 
requests are actually sent to the oVirt engine.


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

Re: [ovirt-users] oVirt and Foreman

2017-07-28 Thread Juan Hernández


On 07/28/2017 09:34 AM, Davide Ferrari wrote:



On 27/07/17 11:17, Juan Hernández wrote:


Looks like the oVirt engine is rejecting the request to add the disk 
because some of the related entities doesn't exist. This is the 
relevant message in the engine log:


  2017-07-25 08:28:03,063Z ERROR 
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] 
(default task-51) [] Operation Failed: Entity not found: 
23f8f1ae-a3ac-47bf-8223-5b5f7c29e508


Would be nice if you can check the /var/log/httpd/ssl_access_log in 
the oVirt engine machine. There should be a line there with the 404 
HTTP status, something like this:


  POST /ovirt-engine/api/vms//disks 404

What is the exact content of that line? Is the VM id the one that 
appears in the above message.


Bingo, there's definitely a 404 error log at the same hour:

192.168.10.158 - - [25/Jul/2017:08:28:02 +] "POST 
/ovirt-engine/api/vms/896098c2-5895-42c3-a419-0c3a43b5ff8b/disks 
HTTP/1.1" 404 169


But the ID is different



Also, can you check what are the identifiers of the relevant data 
center and storage domains?




DC and storage UUID "should" be correct, I've copied them from the oVirt 
CLI output into my hammer command
These are the storage IDs for the datacenter where I'm trying to create 
the VM in:


[oVirt shell (connected)]# list glustervolumes --cluster-identifier 
0002-0002-0002-0002-0345


id : 23f8f1ae-a3ac-47bf-8223-5b5f7c29e508
name   : data_ssd

id : 6be35972-4720-4d34-b2b0-26ffc294f8a3
name   : engine

id : 66f33b1e-7bc8-44cf-9cca-9041b0e0dd15
name   : export

id : cc2c9765-6a3d-4281-8af8-c3526a81cfab
name   : iso

and this is the command line I'm using

hammer host create --architecture-id=1 --domain billy.preprod 
--operatingsystem-id=7 --hostgroup-title Billy/Preprod --name foo01 
--partition-table-id=192 --provision-method image --root-password 
billy12345 --compute-resource 'LeaseWeb VMs prod' --image CentOS_7.3 
--compute-attributes 
cluster=0002-0002-0002-0002-0345,cores=2,memory=4294967296,start=1 
--volume 
'"size_gb=20,storage_domain=23f8f1ae-a3ac-47bf-8223-5b5f7c29e508,bootable=0"' 
--volume 
'"size_gb=30,storage_domain=23f8f1ae-a3ac-47bf-8223-5b5f7c29e508,bootable=0"' 



So there is something wrong with the "data_ssd" storage domain, 
apparently, as the identifier that can't be found corresponds to that 
storage domain. Can you try to retrieve that storage domain? Just use 
your browser to get the following URL:



https://yourovirt/ovirt-engine/api/storagedomains/23f8f1ae-a3ac-47bf-8223-5b5f7c29e508

Also this, in case the problem is related to version 3 of the API:


https://yourovirt/ovirt-engine/api/v3/storagedomains/23f8f1ae-a3ac-47bf-8223-5b5f7c29e508

Do they work?




There should also be additional details in the 
/var/log/ovirt-engine/server.log file. Please check it.


Nope, no log with the same timestamp in server.log :/

Thanks for your kind help!



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

Re: [ovirt-users] oVirt and Foreman

2017-07-28 Thread Davide Ferrari




On 27/07/17 11:17, Juan Hernández wrote:


Looks like the oVirt engine is rejecting the request to add the disk 
because some of the related entities doesn't exist. This is the 
relevant message in the engine log:


  2017-07-25 08:28:03,063Z ERROR 
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] 
(default task-51) [] Operation Failed: Entity not found: 
23f8f1ae-a3ac-47bf-8223-5b5f7c29e508


Would be nice if you can check the /var/log/httpd/ssl_access_log in 
the oVirt engine machine. There should be a line there with the 404 
HTTP status, something like this:


  POST /ovirt-engine/api/vms//disks 404

What is the exact content of that line? Is the VM id the one that 
appears in the above message.


Bingo, there's definitely a 404 error log at the same hour:

192.168.10.158 - - [25/Jul/2017:08:28:02 +] "POST 
/ovirt-engine/api/vms/896098c2-5895-42c3-a419-0c3a43b5ff8b/disks 
HTTP/1.1" 404 169


But the ID is different



Also, can you check what are the identifiers of the relevant data 
center and storage domains?




DC and storage UUID "should" be correct, I've copied them from the oVirt 
CLI output into my hammer command
These are the storage IDs for the datacenter where I'm trying to create 
the VM in:


[oVirt shell (connected)]# list glustervolumes --cluster-identifier 
0002-0002-0002-0002-0345


id : 23f8f1ae-a3ac-47bf-8223-5b5f7c29e508
name   : data_ssd

id : 6be35972-4720-4d34-b2b0-26ffc294f8a3
name   : engine

id : 66f33b1e-7bc8-44cf-9cca-9041b0e0dd15
name   : export

id : cc2c9765-6a3d-4281-8af8-c3526a81cfab
name   : iso

and this is the command line I'm using

hammer host create --architecture-id=1 --domain billy.preprod 
--operatingsystem-id=7 --hostgroup-title Billy/Preprod --name foo01 
--partition-table-id=192 --provision-method image --root-password 
billy12345 --compute-resource 'LeaseWeb VMs prod' --image CentOS_7.3 
--compute-attributes 
cluster=0002-0002-0002-0002-0345,cores=2,memory=4294967296,start=1 
--volume 
'"size_gb=20,storage_domain=23f8f1ae-a3ac-47bf-8223-5b5f7c29e508,bootable=0"' 
--volume 
'"size_gb=30,storage_domain=23f8f1ae-a3ac-47bf-8223-5b5f7c29e508,bootable=0"'



There should also be additional details in the 
/var/log/ovirt-engine/server.log file. Please check it.


Nope, no log with the same timestamp in server.log :/

Thanks for your kind help!

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

[ovirt-users] Hosted Engine increase memory

[ovirt-users] ovirt and mixed selinux

[ovirt-users] Deploying training lab

Re: [ovirt-users] Problemas with ovirtmgmt network used to connect VMs

Re: [ovirt-users] Problemas with ovirtmgmt network used to connect VMs

[ovirt-users] supervdsmd IOError to /dev/stdout

Re: [ovirt-users] Migration network used also as vm network

Re: [ovirt-users] oVirt and Foreman

Re: [ovirt-users] oVirt and Foreman

Re: [ovirt-users] Regarding Ovirt Node ISO

Re: [ovirt-users] oVirt and Foreman

Re: [ovirt-users] oVirt and Foreman

Re: [ovirt-users] oVirt and Foreman

Re: [ovirt-users] oVirt and Foreman

14 matches

Site Navigation

Mail list logo

Footer information