Re: [ovirt-devel] Memory size (1024MB) cannot exceed maximum memory size (0MB).] - when trying to create an instance type

2017-12-25 Thread Arik Hadas
On Mon, Dec 25, 2017 at 8:29 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> > On 25 Dec 2017, at 18:41, Juan Hernández  wrote:
> >
> > On 12/25/2017 05:46 PM, Yaniv Kaul wrote:
> >> While trying to add an instance type, I fail with the error:
> >> Operation Failed". Fault detail is "[Cannot add Template. Memory size
> >> (1024MB) cannot exceed maximum memory size (0MB).]
> >> The code is taken from the example in the SDK, so I'm not sure what I'm
> >> doing wrong here.
> >> Code:
> >> instance_types_service.add(
> >> types.InstanceType(
> >> name='myinstancetype',
> >> description='My instance type',
> >> memory=1 * 2**30,
> >> high_availability=types.HighAvailability(
> >> enabled=True,
> >> ),
> >> cpu=types.Cpu(
> >> topology=types.CpuTopology(
> >> cores=2,
> >> sockets=2,
> >> ),
> >> ),
> >> ),
> >> )
> >> engine.log:
> >> 2017-12-25 10:58:19,825-05 INFO
> >> [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
> >> [265ff704-d89f-471b-8207-fc0e1b8816fd] Lock Acquired to object
> >> 'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
> >> 703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
> >> 2017-12-25 10:58:19,831-05 WARN
> >> [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
> >> [265ff704-d89f-471b-8207-fc0e1b8816fd] Validation of action
> 'AddVmTemplate'
> >> failed for user admin@internal-authz. Reasons:
> >> VAR__ACTION__ADD,VAR__TYPE__VM_TEMPLATE,ACTION_TYPE_
> FAILED_MAX_MEMORY_CANNOT_BE_SMALLER_THAN_MEMORY_SIZE,$maxMemory
> >> 0,$memory 1024
> >> 2017-12-25 10:58:19,832-05 INFO
> >> [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
> >> [265ff704-d89f-471b-8207-fc0e1b8816fd] Lock freed to object
> >> 'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
> >> 703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
> >> 2017-12-25 10:58:19,839-05 DEBUG
> >> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
> >> (default task-13) [265ff704-d89f-471b-8207-fc0e1b8816fd] method:
> runAction,
> >> params: [AddVmTemplate,
> >> AddVmTemplateParameters:{commandId='179df9ed-209c-4882-
> a19a-b76a4fe1adb8',
> >> user='null', commandType='Unknown'}], timeElapsed: 33ms
> >> 2017-12-25 10:58:19,846-05 ERROR
> >> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource]
> (default
> >> task-13) [] Operation Failed: [Cannot add Template. Memory size (1024MB)
> >> cannot exceed maximum memory size (0MB).]
> >> TIA,
> >> Y.
> >
> > I think this is related to the new `memory_policy.max` attribute that
> was introduced in 4.1. I think that for virtual machines it has a default
> value so that it isn't necessary to explicitly provide it. It may not have
> a default value fro instance types. Can you try adding this to the request
> to create the instance type?
> >
> >  memory_policy=types.MemoryPolicy(
> >max=1 * 2**30
> >  )
> >
> > Then try again. If it works I think that we need to fix the engine so
> that it assigns a default value, like it does for virtual machines.
>
> The default for VMs comes from the Blank template. There’s no template for
> instance types, so it always needs to be provided
>

That's true in general, but not for max-memory. Let the blank template be
defined with memory=1024mb and max-memory=4096mb. When a request to add a
VM based on the blank template with memory=8192mb arrives with no
max-memory specified, we cannot take the value of max-memory from the
template since then the operation will fail (as the memory exceeds max
memory)
When adding a VM from rest-api and max-memory is not specified then we set
max-memory = memory * 4 [1, 2].
We can do the same for templates/instance types..

[1]
https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/restapi/jaxrs/src/main/java/org/ovirt/engine/api/restapi/resource/BackendVmsResource.java#L163
[2] and that logic is problematic since the result may exceed the max
memory limitation defined for the OS in os-info and then the operation will
fail..


>
>
> ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Memory size (1024MB) cannot exceed maximum memory size (0MB).] - when trying to create an instance type

2017-12-25 Thread Michal Skrivanek


> On 25 Dec 2017, at 18:41, Juan Hernández  wrote:
> 
> On 12/25/2017 05:46 PM, Yaniv Kaul wrote:
>> While trying to add an instance type, I fail with the error:
>> Operation Failed". Fault detail is "[Cannot add Template. Memory size
>> (1024MB) cannot exceed maximum memory size (0MB).]
>> The code is taken from the example in the SDK, so I'm not sure what I'm
>> doing wrong here.
>> Code:
>> instance_types_service.add(
>> types.InstanceType(
>> name='myinstancetype',
>> description='My instance type',
>> memory=1 * 2**30,
>> high_availability=types.HighAvailability(
>> enabled=True,
>> ),
>> cpu=types.Cpu(
>> topology=types.CpuTopology(
>> cores=2,
>> sockets=2,
>> ),
>> ),
>> ),
>> )
>> engine.log:
>> 2017-12-25 10:58:19,825-05 INFO
>> [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
>> [265ff704-d89f-471b-8207-fc0e1b8816fd] Lock Acquired to object
>> 'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
>> 703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
>> 2017-12-25 10:58:19,831-05 WARN
>> [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
>> [265ff704-d89f-471b-8207-fc0e1b8816fd] Validation of action 'AddVmTemplate'
>> failed for user admin@internal-authz. Reasons:
>> VAR__ACTION__ADD,VAR__TYPE__VM_TEMPLATE,ACTION_TYPE_FAILED_MAX_MEMORY_CANNOT_BE_SMALLER_THAN_MEMORY_SIZE,$maxMemory
>> 0,$memory 1024
>> 2017-12-25 10:58:19,832-05 INFO
>> [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
>> [265ff704-d89f-471b-8207-fc0e1b8816fd] Lock freed to object
>> 'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
>> 703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
>> 2017-12-25 10:58:19,839-05 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-13) [265ff704-d89f-471b-8207-fc0e1b8816fd] method: runAction,
>> params: [AddVmTemplate,
>> AddVmTemplateParameters:{commandId='179df9ed-209c-4882-a19a-b76a4fe1adb8',
>> user='null', commandType='Unknown'}], timeElapsed: 33ms
>> 2017-12-25 10:58:19,846-05 ERROR
>> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
>> task-13) [] Operation Failed: [Cannot add Template. Memory size (1024MB)
>> cannot exceed maximum memory size (0MB).]
>> TIA,
>> Y.
> 
> I think this is related to the new `memory_policy.max` attribute that was 
> introduced in 4.1. I think that for virtual machines it has a default value 
> so that it isn't necessary to explicitly provide it. It may not have a 
> default value fro instance types. Can you try adding this to the request to 
> create the instance type?
> 
>  memory_policy=types.MemoryPolicy(
>max=1 * 2**30
>  )
> 
> Then try again. If it works I think that we need to fix the engine so that it 
> assigns a default value, like it does for virtual machines.

The default for VMs comes from the Blank template. There’s no template for 
instance types, so it always needs to be provided

> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
> 
> 

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Memory size (1024MB) cannot exceed maximum memory size (0MB).] - when trying to create an instance type

2017-12-25 Thread Juan Hernández

On 12/25/2017 05:46 PM, Yaniv Kaul wrote:

While trying to add an instance type, I fail with the error:
Operation Failed". Fault detail is "[Cannot add Template. Memory size
(1024MB) cannot exceed maximum memory size (0MB).]

The code is taken from the example in the SDK, so I'm not sure what I'm
doing wrong here.
Code:
 instance_types_service.add(
 types.InstanceType(
 name='myinstancetype',
 description='My instance type',
 memory=1 * 2**30,
 high_availability=types.HighAvailability(
 enabled=True,
 ),
 cpu=types.Cpu(
 topology=types.CpuTopology(
 cores=2,
 sockets=2,
 ),
 ),
 ),
 )


engine.log:
2017-12-25 10:58:19,825-05 INFO
[org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
[265ff704-d89f-471b-8207-fc0e1b8816fd] Lock Acquired to object
'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
2017-12-25 10:58:19,831-05 WARN
[org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
[265ff704-d89f-471b-8207-fc0e1b8816fd] Validation of action 'AddVmTemplate'
failed for user admin@internal-authz. Reasons:
VAR__ACTION__ADD,VAR__TYPE__VM_TEMPLATE,ACTION_TYPE_FAILED_MAX_MEMORY_CANNOT_BE_SMALLER_THAN_MEMORY_SIZE,$maxMemory
0,$memory 1024
2017-12-25 10:58:19,832-05 INFO
[org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
[265ff704-d89f-471b-8207-fc0e1b8816fd] Lock freed to object
'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
2017-12-25 10:58:19,839-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-13) [265ff704-d89f-471b-8207-fc0e1b8816fd] method: runAction,
params: [AddVmTemplate,
AddVmTemplateParameters:{commandId='179df9ed-209c-4882-a19a-b76a4fe1adb8',
user='null', commandType='Unknown'}], timeElapsed: 33ms
2017-12-25 10:58:19,846-05 ERROR
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
task-13) [] Operation Failed: [Cannot add Template. Memory size (1024MB)
cannot exceed maximum memory size (0MB).]


TIA,
Y.



I think this is related to the new `memory_policy.max` attribute that 
was introduced in 4.1. I think that for virtual machines it has a 
default value so that it isn't necessary to explicitly provide it. It 
may not have a default value fro instance types. Can you try adding this 
to the request to create the instance type?


  memory_policy=types.MemoryPolicy(
max=1 * 2**30
  )

Then try again. If it works I think that we need to fix the engine so 
that it assigns a default value, like it does for virtual machines.

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-12-24 ] [add_hosts]

2017-12-25 Thread Barak Korren
On 25 December 2017 at 16:59, Eyal Edri  wrote:

>
>
> On Mon, Dec 25, 2017 at 2:20 PM, Barak Korren  wrote:
>
>>
>>
>> On 25 December 2017 at 10:50, Eyal Edri  wrote:
>>
>>> I'm testing a revert of the patch [1], but it looks like it is very
>>> related and suspicion is around ansible not configured firewalld and thus
>>> causing the failure.
>>> Gal has been debugging the same issue downstream yesterday.
>>>
>>>
>>> [1] https://gerrit.ovirt.org/#/c/85723/
>>>
>>>
>>>
>> Revet patch failed to pass CQ:
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4518/
>>
>> I'm rerunning just in case it passes a 2nd time:
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4520/
>>
>> Maybe we need to revert the firewalld patch too:
>> https://gerrit.ovirt.org/c/85326 (engine: Let backend choose default
>> firewall type)
>>
>
>
> OK, Thanks for Gal for debugging this further, it seems that a different
> patch was causing the failure:
> https://gerrit.ovirt.org/#/c/85611/ - core: ansible: Don't print errors
> when files not found
>
> I've tested a revert patch [1]( rebased on master ) and it passed here [2].
>
> Details on why it caused the failure will be added to the revert patch
> commit msg.
>


This had now finally passed OST/CQ:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4522/



-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Memory size (1024MB) cannot exceed maximum memory size (0MB).] - when trying to create an instance type

2017-12-25 Thread Yaniv Kaul
While trying to add an instance type, I fail with the error:
Operation Failed". Fault detail is "[Cannot add Template. Memory size
(1024MB) cannot exceed maximum memory size (0MB).]

The code is taken from the example in the SDK, so I'm not sure what I'm
doing wrong here.
Code:
instance_types_service.add(
types.InstanceType(
name='myinstancetype',
description='My instance type',
memory=1 * 2**30,
high_availability=types.HighAvailability(
enabled=True,
),
cpu=types.Cpu(
topology=types.CpuTopology(
cores=2,
sockets=2,
),
),
),
)


engine.log:
2017-12-25 10:58:19,825-05 INFO
[org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
[265ff704-d89f-471b-8207-fc0e1b8816fd] Lock Acquired to object
'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
2017-12-25 10:58:19,831-05 WARN
[org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
[265ff704-d89f-471b-8207-fc0e1b8816fd] Validation of action 'AddVmTemplate'
failed for user admin@internal-authz. Reasons:
VAR__ACTION__ADD,VAR__TYPE__VM_TEMPLATE,ACTION_TYPE_FAILED_MAX_MEMORY_CANNOT_BE_SMALLER_THAN_MEMORY_SIZE,$maxMemory
0,$memory 1024
2017-12-25 10:58:19,832-05 INFO
[org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-13)
[265ff704-d89f-471b-8207-fc0e1b8816fd] Lock freed to object
'EngineLock:{exclusiveLocks='[myinstancetype=TEMPLATE_NAME,
703e1265-e160-4a76-82e6-06974156b7b9=TEMPLATE]', sharedLocks='[]'}'
2017-12-25 10:58:19,839-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-13) [265ff704-d89f-471b-8207-fc0e1b8816fd] method: runAction,
params: [AddVmTemplate,
AddVmTemplateParameters:{commandId='179df9ed-209c-4882-a19a-b76a4fe1adb8',
user='null', commandType='Unknown'}], timeElapsed: 33ms
2017-12-25 10:58:19,846-05 ERROR
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
task-13) [] Operation Failed: [Cannot add Template. Memory size (1024MB)
cannot exceed maximum memory size (0MB).]


TIA,
Y.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] upgrade_check and upgrade API calls (v4)

2017-12-25 Thread Juan Hernández

On 12/25/2017 04:21 PM, Yaniv Kaul wrote:

I'm trying to check if a certain host can be upgraded.
1. I'm calling it through the host_service, something like:

host_service = connection.system_service().hosts_service().host_service(
host.id)
is_upgrade = host_service.upgrade_check()

To my surprise, is_upgrade is None. I expected a Boolean.

2. In addition, when trying to upgrade via:
host_service.upgrade()

I'm getting Operation Failed - and it complains there are no upgrades
available.
Alas, in the UI it shows that upgrades available and upgrade does work
through the UI.

Am I misusing the functions?
(The host is a regular host, not ovirt-node btw).

TIA,
Y.



The "upgrade_check" method doesn't return anything, it just triggers the 
execution of the process to check for upgrades. Then only result will be 
that an icon will be displayed in the UI.


That isn't very useful, to be honest, so I'd suggest to open a bug to 
modify this so that the upgrade runs synchronously, and so that the 
method returns the boolean that you expected.

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


[ovirt-devel] upgrade_check and upgrade API calls (v4)

2017-12-25 Thread Yaniv Kaul
I'm trying to check if a certain host can be upgraded.
1. I'm calling it through the host_service, something like:

host_service = connection.system_service().hosts_service().host_service(
host.id)
is_upgrade = host_service.upgrade_check()

To my surprise, is_upgrade is None. I expected a Boolean.

2. In addition, when trying to upgrade via:
host_service.upgrade()

I'm getting Operation Failed - and it complains there are no upgrades
available.
Alas, in the UI it shows that upgrades available and upgrade does work
through the UI.

Am I misusing the functions?
(The host is a regular host, not ovirt-node btw).

TIA,
Y.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-12-24 ] [add_hosts]

2017-12-25 Thread Eyal Edri
On Mon, Dec 25, 2017 at 2:20 PM, Barak Korren  wrote:

>
>
> On 25 December 2017 at 10:50, Eyal Edri  wrote:
>
>> I'm testing a revert of the patch [1], but it looks like it is very
>> related and suspicion is around ansible not configured firewalld and thus
>> causing the failure.
>> Gal has been debugging the same issue downstream yesterday.
>>
>>
>> [1] https://gerrit.ovirt.org/#/c/85723/
>>
>>
>>
> Revet patch failed to pass CQ:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4518/
>
> I'm rerunning just in case it passes a 2nd time:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4520/
>
> Maybe we need to revert the firewalld patch too:
> https://gerrit.ovirt.org/c/85326 (engine: Let backend choose default
> firewall type)
>


OK, Thanks for Gal for debugging this further, it seems that a different
patch was causing the failure:
https://gerrit.ovirt.org/#/c/85611/ - core: ansible: Don't print errors
when files not found

I've tested a revert patch [1]( rebased on master ) and it passed here [2].

Details on why it caused the failure will be added to the revert patch
commit msg.



[1] https://gerrit.ovirt.org/#/c/85737/
[2]
http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/1928/


>
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>



-- 

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] node zero Networking

2017-12-25 Thread Yedidyah Bar David
Hi all,

I spent quite some time trying to deploy node zero, trying to look at
https://bugzilla.redhat.com/show_bug.cgi?id=1528253 , and always fail
around the end, with:

ERROR fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true,
"cmd": "ip rule list | grep ovirtmgmt | sed s/[.*]\\ //g | awk
'{ print $9 }'", "delta": "0:00:00.008292", "end": "2017-12-25
11:51:39.146800", "rc": 0, "start": "2017-12-25 11:51:39.138508",
"stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
ERROR Failed to execute stage 'Closing up': Failed executing ansible-playbook
ERROR Hosted Engine deployment failed: this system is not reliable,
please check the issue,fix and redeploy

I use the following setup:

I have a libvirt vm on my laptop, with a single virtual nic eth0.

This nic is connected to a bridge called intbr on my laptop. This
bridge has no access to outside, and VMs on it have no default route.
There is a local dhcp+dns serving this bridge, using the address range
192.168.3.0/24.

The vm serves as a nested-kvm hosted-engine host.

eth0 gets a static IP address 192.168.3.42 from dhcpd.

There is also (didn't check who/what exactly creates it, I think it's
libvirt's default) a bridge there called virbr0. virbr0 has IP address
192.168.122.1/24 .

When I deploy HE, the engine machine gets also a single virtual nic,
which is connected to virbr0, and gets an IP address in that range
(192.168.122.85, currently).

deploy fails when running the task:

  - name: Get ovirtmgmt route table id
shell: ip rule list | grep ovirtmgmt | sed s/\\[.*\\]\ //g | awk
'{ print $9 }'
register: ovirtmgmt_table_id
until: ovirtmgmt_table_id.stdout_lines|length >= 1
retries: 50
delay: 10
changed_when: True

The output of 'ip rule list' is:

0:  from all lookup local
32766:  from all lookup main
32767:  from all lookup default

So does not include 'ovirtmgmt'.

I do have:

# brctl show
bridge name bridge id   STP enabled interfaces
;vdsmdummy; 8000.   no
ovirtmgmt   8000.06d1bd012412   no  eth0
virbr0  8000.525400012499   yes virbr0-nic
vnet0
And:

# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast
master ovirtmgmt state UP qlen 1000
link/ether 06:d1:bd:01:24:12 brd ff:ff:ff:ff:ff:ff
18: virbr0:  mtu 1500 qdisc noqueue
state UP qlen 1000
link/ether 52:54:00:01:24:99 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
   valid_lft forever preferred_lft forever
19: virbr0-nic:  mtu 1500 qdisc pfifo_fast master
virbr0 state DOWN qlen 1000
link/ether 52:54:00:01:24:99 brd ff:ff:ff:ff:ff:ff
20: vnet0:  mtu 1500 qdisc pfifo_fast
master virbr0 state UNKNOWN qlen 1000
link/ether fe:d1:bd:01:24:04 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcd1:bdff:fe01:2404/64 scope link
   valid_lft forever preferred_lft forever
21: ;vdsmdummy;:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 1e:1b:84:c2:51:ff brd ff:ff:ff:ff:ff:ff
22: ovirtmgmt:  mtu 1500 qdisc
noqueue state UP qlen 1000
link/ether 06:d1:bd:01:24:12 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.42/24 brd 192.168.3.255 scope global dynamic ovirtmgmt
   valid_lft 70927sec preferred_lft 70927sec
inet6 fe80::4d1:bdff:fe01:2412/64 scope link
   valid_lft forever preferred_lft forever

(And of course told deploy that I want to use eth0).

Questions:

1. Did this already work for anyone at all? If so, can you please
share details? Specifically, how was networking configured?

2. It might be that my problems are due to not having a (default)
route for ovirtmgmt bridge/network. If so, then I consider this a bug,
but do not mind configuring one for now.

3. All of the relevant section of the playbook has a comment preceding it:

  # all of the next is a workaroud for the network issue, vdsm
installation breaks the routing and it needs to be fixed
  # once we'll fix the host installation it could be removed

Do we have specific details/bug/whatever about the problem we are
working around? Perhaps it's already solved and I can try to remove
this part?

4. Both now (with (3.) being worked around) and eventually (when it's
(what?) fixed), how should this work? Should the engine local vm
indeed start connected to virbr0, and then move to ovirtmgmt? Or only
the new engine vm (residing on the shared storage) should be in
ovirtmgmt?

5. In particular, what should I supply for the 

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 24/12/2017 ] [use_ovn_provider]

2017-12-25 Thread Dominik Holler
On Mon, 25 Dec 2017 14:14:36 +0200
Dan Kenigsberg  wrote:

> On Mon, Dec 25, 2017 at 2:09 PM, Dominik Holler 
> wrote:
> > A helpful hint is in
> >
> > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4492/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
> >  :
> > Caused by: org.jboss.resteasy.spi.ReaderException:
> > org.codehaus.jackson.map.JsonMappingException: Can not construct
> > instance of java.util.Calendar from String value '2017-12-27
> > 13:19:51Z': not a valid representation (error: Can not parse date
> > "2017-12-27 13:19:51Z": not compatible with any of standard forms
> > ("-MM-dd'T'HH:mm:ss.SSSZ", "-MM-dd'T'HH:mm:ss.SSS'Z'",
> > "EEE, dd MMM  HH:mm:ss zzz", "-MM-dd")) at [Source:
> > org.jboss.resteasy.client.core.BaseClientResponse$InputStreamWrapper@72c184c5;
> > line: 1, column: 23] (through reference chain:
> > com.woorea.openstack.keystone.model.Access["token"]->com.woorea.openstack.keystone.model.Token["expires"])
> >
> >
> > This problem was introduced by
> > https://gerrit.ovirt.org/#/c/85702/
> >
> > I created a fix:
> > https://gerrit.ovirt.org/85734  
> 
> Thanks for the quick fix.
> 
> Is the new format accpetable to other users of the keystone-like API
> (such at the neutron cli)?


Yes, I verified ovirt-engine via webadmin, and neutron CLI and ansible
on command line:

[user@fedora-25-gui ovirt-system-tests]$ cat createNetwok.yml 
---
- hosts: localhost
  tasks:
  - os_network:
  auth:
auth_url: http://0.0.0.0:35357/v2.0
username: admin@internal
password: 123456
  state: present
  name: myNewAnsibleNet

[user@fedora-25-gui ovirt-system-tests]$ ansible-playbook createNetwok.yml 
 [WARNING]: Could not match supplied host pattern, ignoring: all

 [WARNING]: provided hosts list is empty, only localhost is available


PLAY [localhost] 
***

TASK [Gathering Facts] 
*
ok: [localhost]

TASK [os_network] 
**
changed: [localhost]

PLAY RECAP 
*
localhost  : ok=2changed=1unreachable=0failed=0   

[user@fedora-25-gui ovirt-system-tests]$ ansible-playbook createNetwok.yml 
 [WARNING]: Could not match supplied host pattern, ignoring: all

 [WARNING]: provided hosts list is empty, only localhost is available


PLAY [localhost] 
***

TASK [Gathering Facts] 
*
ok: [localhost]

TASK [os_network] 
**
ok: [localhost]

PLAY RECAP 
*
localhost  : ok=2changed=0unreachable=0failed=0
[user@fedora-25-gui ovirt-system-tests]$ OS_USERNAME=admin@internal 
OS_PASSWORD=123456 OS_AUTH_URL=http://0.0.0.0:35357/v2.0 neutron net-list
Failed to discover available identity versions when contacting 
http://0.0.0.0:35357/v2.0. Attempting to parse version from URL.
+--+-+
| id   | name|
+--+-+
| 97b653b0-623e-4b5d-a7a0-e05c6d95fdf2 | ansibleNet2 |
| e1f36f9b-bfb2-4779-880f-d8b8f8d9c64a | myNewAnsibleNet |
| 31172fec-1d6e-42eb-acb4-ab5bf77a1296 | osnet   |
| 05e680b8-544a-4278-9ac0-403fb5e83af2 | test.json   |
| 60f74925-adb9-4ae2-9751-2a3f1315bd2e | net877  |
| 18687d84-0923-4e1a-b349-4030c6f9c11e | net111  |
| c20b5484-dde1-4729-bae4-5f073c3e14ef | net1114 |
| ddd9741b-6874-4075-abba-615fb1777b62 | ansibleNet  |
| 2b913120-260f-4750-9fc2-c0e44f3d51e9 | net11149|
| a3db332f-5b2b-478c-a90e-73ee5fbee3ce | net412  |
+--+-+



___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-12-24 ] [add_hosts]

2017-12-25 Thread Barak Korren
On 25 December 2017 at 10:50, Eyal Edri  wrote:

> I'm testing a revert of the patch [1], but it looks like it is very
> related and suspicion is around ansible not configured firewalld and thus
> causing the failure.
> Gal has been debugging the same issue downstream yesterday.
>
>
> [1] https://gerrit.ovirt.org/#/c/85723/
>
>
>
Revet patch failed to pass CQ:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4518/

I'm rerunning just in case it passes a 2nd time:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4520/

Maybe we need to revert the firewalld patch too:
https://gerrit.ovirt.org/c/85326 (engine: Let backend choose default
firewall type)

-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 24/12/2017 ] [use_ovn_provider]

2017-12-25 Thread Dan Kenigsberg
On Mon, Dec 25, 2017 at 2:09 PM, Dominik Holler  wrote:
> A helpful hint is in
>
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4492/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
>  :
> Caused by: org.jboss.resteasy.spi.ReaderException: 
> org.codehaus.jackson.map.JsonMappingException: Can not construct instance of 
> java.util.Calendar from String value '2017-12-27 13:19:51Z': not a valid 
> representation (error: Can not parse date "2017-12-27 13:19:51Z": not 
> compatible with any of standard forms ("-MM-dd'T'HH:mm:ss.SSSZ", 
> "-MM-dd'T'HH:mm:ss.SSS'Z'", "EEE, dd MMM  HH:mm:ss zzz", 
> "-MM-dd"))
>  at [Source: 
> org.jboss.resteasy.client.core.BaseClientResponse$InputStreamWrapper@72c184c5;
>  line: 1, column: 23] (through reference chain: 
> com.woorea.openstack.keystone.model.Access["token"]->com.woorea.openstack.keystone.model.Token["expires"])
>
>
> This problem was introduced by
> https://gerrit.ovirt.org/#/c/85702/
>
> I created a fix:
> https://gerrit.ovirt.org/85734

Thanks for the quick fix.

Is the new format accpetable to other users of the keystone-like API
(such at the neutron cli)?
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 24/12/2017 ] [use_ovn_provider]

2017-12-25 Thread Dominik Holler
A helpful hint is in

http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4492/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
 :
Caused by: org.jboss.resteasy.spi.ReaderException: 
org.codehaus.jackson.map.JsonMappingException: Can not construct instance of 
java.util.Calendar from String value '2017-12-27 13:19:51Z': not a valid 
representation (error: Can not parse date "2017-12-27 13:19:51Z": not 
compatible with any of standard forms ("-MM-dd'T'HH:mm:ss.SSSZ", 
"-MM-dd'T'HH:mm:ss.SSS'Z'", "EEE, dd MMM  HH:mm:ss zzz", "-MM-dd"))
 at [Source: 
org.jboss.resteasy.client.core.BaseClientResponse$InputStreamWrapper@72c184c5; 
line: 1, column: 23] (through reference chain: 
com.woorea.openstack.keystone.model.Access["token"]->com.woorea.openstack.keystone.model.Token["expires"])


This problem was introduced by 
https://gerrit.ovirt.org/#/c/85702/

I created a fix:
https://gerrit.ovirt.org/85734



On Mon, 25 Dec 2017 11:30:19 +0200
Eyal Edri  wrote:

> Adding ovn maintainers.
> 
> On Sun, Dec 24, 2017 at 9:25 AM, Barak Korren 
> wrote:
> 
> > Test failed: [ 098_ovirt_provider_ovn.use_ovn_provider ]
> >
> > Link to suspected patches:
> >
> > - Linked test failed on:
> >https://gerrit.ovirt.org/#/c/85703/3
> > - It seems OVN patches had been failing tests ever since:
> >https://gerrit.ovirt.org/#/c/85645/2
> >
> > Link to Job:
> > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4492/
> >
> > Link to all logs:
> > http://jenkins.ovirt.org/job/ovirt-master_change-queue-
> > tester/4492/artifact/exported-artifacts/basic-suit-master-
> > el7/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/
> >
> > Error snippet from log:
> >
> > 
> >
> > Fault reason is "Operation Failed". Fault detail is "Failed to
> > communicate with the external provider, see log for additional
> > details.". HTTP response code is 400.  
> >  >> begin captured logging <<
> >  requests.packages.urllib3.connectionpool:
> > INFO: * Starting new HTTPS connection (1): 192.168.201.4
> > py.warnings: WARNING: * Unverified HTTPS request is being made.
> > Adding certificate verification is strongly advised. See:
> > https://urllib3.readthedocs.org/en/latest/security.html
> > requests.packages.urllib3.connectionpool: DEBUG: "POST /v2.0/tokens/
> > HTTP/1.1" 200 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG:
> > "GET /v2.0/networks/ HTTP/1.1" 200 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/ports/
> > HTTP/1.1" 200 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/subnets/
> > HTTP/1.1" 200 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG:
> > "POST /v2.0/networks/ HTTP/1.1" 201 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG:
> > "POST /v2.0/subnets/ HTTP/1.1" 201 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG: "POST /v2.0/ports/
> > HTTP/1.1" 201 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG:
> > "GET /v2.0/networks/ HTTP/1.1" 200 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/ports/
> > HTTP/1.1" 200 None
> > requests.packages.urllib3.connectionpool: INFO: * Starting new
> > HTTPS connection (1): 192.168.201.4
> > requests.packages.urllib3.connectionpool: DEBUG: "GET /v2.0/subnets/
> > HTTP/1.1" 200 None  
> > - >> end captured logging <<
> > -  
> >
> >
> >
> > 
> >
> >
> >
> > --
> > Barak Korren
> > RHV DevOps team , RHCE, RHCi
> > Red Hat EMEA
> > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
> >  
> 
> 

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-12-24 ] [add_hosts]

2017-12-25 Thread Eyal Edri
I'm testing a revert of the patch [1], but it looks like it is very related
and suspicion is around ansible not configured firewalld and thus
causing the failure.
Gal has been debugging the same issue downstream yesterday.


[1] https://gerrit.ovirt.org/#/c/85723/

On Mon, Dec 25, 2017 at 9:57 AM, Dan Kenigsberg  wrote:

> On Mon, Dec 25, 2017 at 12:20 AM, Barak Korren  wrote:
> > On 24 December 2017 at 21:40, Dan Kenigsberg  wrote:
> >> On Sun, Dec 24, 2017 at 5:37 PM, Barak Korren 
> wrote:
> >>> Test failed: [ 002_bootstrap.add_hosts ]
> >>>
> >>> Link to suspected patches:
> >>>
> >>> - Linked test is failing with the failing engine patch:
> >>>https://gerrit.ovirt.org/#/c/85533/2
> >>
> >> This patch "webadmin: vnic mapping - initial match target to source"
> >> seems utterly unrelated.
> >>
> >>> - Tests with engine patches had been failing since:
> >>>https://gerrit.ovirt.org/#/c/85668/2
> >>
> >> "core: ansible: Replace include with include_tasks" this is more
> >> related to add-host flow.
> >>
> >
> > Here is a test with just that patch to confirm is causes the same issue:
> > http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1924
>
> In future breakage reports, may ask to include the patch title when
> you declare it as suspicious? It helps readers understand what (and
> who) are to blame.
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>


-- 

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel