subject:"\[ovirt\-devel\] Re\: OST fails"




On 3/23/20 8:51 PM, Galit Rosenthal wrote:
I run it now locally using the extra sources as it runs in the CQ and 
it didn't fail for me.


I will continue to investigate tomorrow,

Marcin, did you see this issue also in check_patch or only in CQ?
I wasn't aware of the issue till Nir raised it - I was working with the 
patch previously
and both check-patch and manual runs were fine. I think it concerns only 
CQ then.



Regards,
Galit

On Mon, Mar 23, 2020 at 4:29 PM Galit Rosenthal > wrote:


I will look at it.

On Mon, Mar 23, 2020 at 4:18 PM Martin Perina mailto:mper...@redhat.com>> wrote:



On Mon, Mar 23, 2020 at 3:16 PM Marcin Sobczyk
mailto:msobc...@redhat.com>> wrote:



On 3/23/20 3:10 PM, Marcin Sobczyk wrote:
>
>
> On 3/23/20 2:53 PM, Nir Soffer wrote:
>> On Mon, Mar 23, 2020 at 3:26 PM Marcin Sobczyk
mailto:msobc...@redhat.com>>
>> wrote:
>>>
>>>
>>> On 3/23/20 2:17 PM, Nir Soffer wrote:
 On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk
 mailto:msobc...@redhat.com>> wrote:
>
> On 3/21/20 1:18 AM, Nir Soffer wrote:
>
> On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer
mailto:nsof...@redhat.com>>
> wrote:
>> Looks like infrastructure issue setting up storage
on engine host.
>>
>> Here are 2 failing builds with unrelated changes:
>>
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
>>
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
> Rebuilding still fails in setup_storage:
>
>

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/

>
>

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/

>
>
>> Is this a known issue?
>>
>> Error Message
>>
>> AssertionError: setup_storage.sh failed. Exit code
is 1 assert 1
>> == 0   -1   +0
>>
>> Stacktrace
>>
>> prefix = 
>>
>> @pytest.mark.run(order=14)
>>   def test_configure_storage(prefix):
>>   engine = prefix.virt_env.engine_vm()
>>   result = engine.ssh(
>>   [
>> '/tmp/setup_storage.sh',
>>   ],
>>   )
>>>     assert result.code == 0, 'setup_storage.sh
failed. Exit
>>> code is %s' % result.code
>> E   AssertionError: setup_storage.sh failed.
Exit code is 1
>> E   assert 1 == 0
>> E -1
>> E +0
>>
>>
>> The pytest traceback is nice, but in this case it
is does not
>> show any useful info.
>>
>> Since we run a script using ssh, the error message
should include
>> the process stdout and stderr
>> which probably can explain the failure.
> I posted https://gerrit.ovirt.org/#/c/107830/ to
improve logging
> during storage setup.
> Unfortunately AFAICS it didn't fail, so I guess
we'll have to
> merge it and wait for a failed job to get some
helpful logs.
 Thanks.

 It still fails for me with current code:


https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/



 Same when using current vdsm master.
>>> Updated the patch according to your suggestions and
currently trying
>>> out
>>> OST for the 4th time -
>>> all previous runs succeeded. I guess I'm out of luck :)
>> It succeeds on your local OST setup but fail on Jenkins?
> No, I mean jenkins - both check-patch runs didn't fail
on this script.
> I also tried running OST manually twice and same thing
happened.
> Anyway - the patch has been merged now so if any failure
occurs in CQ
> we should know what's going on.
Ok, finally caught a failure in CQ [1]:

[2020-03-23T14:14:09.836Z] if result.code != 0:

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

2020-03-23 Thread Galit Rosenthal

I run it now locally using the extra sources as it runs in the CQ and it
didn't fail for me.

I will continue to investigate tomorrow,

Marcin, did you see this issue also in check_patch or only in CQ?
Regards,
Galit

On Mon, Mar 23, 2020 at 4:29 PM Galit Rosenthal  wrote:

> I will look at it.
>
> On Mon, Mar 23, 2020 at 4:18 PM Martin Perina  wrote:
>
>>
>>
>> On Mon, Mar 23, 2020 at 3:16 PM Marcin Sobczyk 
>> wrote:
>>
>>>
>>>
>>> On 3/23/20 3:10 PM, Marcin Sobczyk wrote:
>>> >
>>> >
>>> > On 3/23/20 2:53 PM, Nir Soffer wrote:
>>> >> On Mon, Mar 23, 2020 at 3:26 PM Marcin Sobczyk 
>>> >> wrote:
>>> >>>
>>> >>>
>>> >>> On 3/23/20 2:17 PM, Nir Soffer wrote:
>>>  On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk
>>>   wrote:
>>> >
>>> > On 3/21/20 1:18 AM, Nir Soffer wrote:
>>> >
>>> > On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer 
>>> > wrote:
>>> >> Looks like infrastructure issue setting up storage on engine host.
>>> >>
>>> >> Here are 2 failing builds with unrelated changes:
>>> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
>>> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
>>> > Rebuilding still fails in setup_storage:
>>> >
>>> >
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
>>> >
>>> >
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/
>>> >
>>> >
>>> >> Is this a known issue?
>>> >>
>>> >> Error Message
>>> >>
>>> >> AssertionError: setup_storage.sh failed. Exit code is 1 assert 1
>>> >> == 0   -1   +0
>>> >>
>>> >> Stacktrace
>>> >>
>>> >> prefix = 
>>> >>
>>> >>   @pytest.mark.run(order=14)
>>> >>   def test_configure_storage(prefix):
>>> >>   engine = prefix.virt_env.engine_vm()
>>> >>   result = engine.ssh(
>>> >>   [
>>> >>   '/tmp/setup_storage.sh',
>>> >>   ],
>>> >>   )
>>> >>> assert result.code == 0, 'setup_storage.sh failed. Exit
>>> >>> code is %s' % result.code
>>> >> E   AssertionError: setup_storage.sh failed. Exit code is 1
>>> >> E   assert 1 == 0
>>> >> E -1
>>> >> E +0
>>> >>
>>> >>
>>> >> The pytest traceback is nice, but in this case it is does not
>>> >> show any useful info.
>>> >>
>>> >> Since we run a script using ssh, the error message should include
>>> >> the process stdout and stderr
>>> >> which probably can explain the failure.
>>> > I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging
>>> > during storage setup.
>>> > Unfortunately AFAICS it didn't fail, so I guess we'll have to
>>> > merge it and wait for a failed job to get some helpful logs.
>>>  Thanks.
>>> 
>>>  It still fails for me with current code:
>>> 
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/
>>> 
>>> 
>>>  Same when using current vdsm master.
>>> >>> Updated the patch according to your suggestions and currently trying
>>> >>> out
>>> >>> OST for the 4th time -
>>> >>> all previous runs succeeded. I guess I'm out of luck :)
>>> >> It succeeds on your local OST setup but fail on Jenkins?
>>> > No, I mean jenkins - both check-patch runs didn't fail on this script.
>>> > I also tried running OST manually twice and same thing happened.
>>> > Anyway - the patch has been merged now so if any failure occurs in CQ
>>> > we should know what's going on.
>>> Ok, finally caught a failure in CQ [1]:
>>>
>>> [2020-03-23T14:14:09.836Z] if result.code != 0:
>>> [2020-03-23T14:14:09.836Z] msg = (
>>> [2020-03-23T14:14:09.836Z] 'setup_storage.sh failed with
>>> exit code: {}.\n'
>>> [2020-03-23T14:14:09.836Z] 'stdout:\n{}'
>>> [2020-03-23T14:14:09.836Z] 'stderr:\n{}'
>>> [2020-03-23T14:14:09.836Z] ).format(result.code, result.out,
>>> result.err)
>>> [2020-03-23T14:14:09.836Z] >   raise RuntimeError(msg)
>>> [2020-03-23T14:14:09.836Z] E   RuntimeError: setup_storage.sh
>>> failed with exit code: 1.
>>> [2020-03-23T14:14:09.836Z] E   stdout:
>>> [2020-03-23T14:14:09.836Z] E   Reposync & Extra Sources
>>> Content0.0  B/s |   0  B 00:00
>>> [2020-03-23T14:14:09.836Z] E   stderr:
>>> [2020-03-23T14:14:09.836Z] E   + set -xe
>>> [2020-03-23T14:14:09.836Z] E   +
>>> MAIN_NFS_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_2
>>> [2020-03-23T14:14:09.836Z] E   +
>>> ISCSI_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_3
>>> [2020-03-23T14:14:09.836Z] E   + NUM_LUNS=5
>>> [2020-03-23T14:14:09.836Z] E   ++ uname -r
>>> [2020-03-23T14:14:09.836Z] E   ++ awk -F. '{print $(NF-1)}'
>>> [2020-03-23T14:14:09.836Z] E   + DIST=el8_1
>>> [2020-03-23T14:14:09.836Z] E   +

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

2020-03-23 Thread Galit Rosenthal

I will look at it.

On Mon, Mar 23, 2020 at 4:18 PM Martin Perina  wrote:

>
>
> On Mon, Mar 23, 2020 at 3:16 PM Marcin Sobczyk 
> wrote:
>
>>
>>
>> On 3/23/20 3:10 PM, Marcin Sobczyk wrote:
>> >
>> >
>> > On 3/23/20 2:53 PM, Nir Soffer wrote:
>> >> On Mon, Mar 23, 2020 at 3:26 PM Marcin Sobczyk 
>> >> wrote:
>> >>>
>> >>>
>> >>> On 3/23/20 2:17 PM, Nir Soffer wrote:
>>  On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk
>>   wrote:
>> >
>> > On 3/21/20 1:18 AM, Nir Soffer wrote:
>> >
>> > On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer 
>> > wrote:
>> >> Looks like infrastructure issue setting up storage on engine host.
>> >>
>> >> Here are 2 failing builds with unrelated changes:
>> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
>> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
>> > Rebuilding still fails in setup_storage:
>> >
>> >
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
>> >
>> >
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/
>> >
>> >
>> >> Is this a known issue?
>> >>
>> >> Error Message
>> >>
>> >> AssertionError: setup_storage.sh failed. Exit code is 1 assert 1
>> >> == 0   -1   +0
>> >>
>> >> Stacktrace
>> >>
>> >> prefix = 
>> >>
>> >>   @pytest.mark.run(order=14)
>> >>   def test_configure_storage(prefix):
>> >>   engine = prefix.virt_env.engine_vm()
>> >>   result = engine.ssh(
>> >>   [
>> >>   '/tmp/setup_storage.sh',
>> >>   ],
>> >>   )
>> >>> assert result.code == 0, 'setup_storage.sh failed. Exit
>> >>> code is %s' % result.code
>> >> E   AssertionError: setup_storage.sh failed. Exit code is 1
>> >> E   assert 1 == 0
>> >> E -1
>> >> E +0
>> >>
>> >>
>> >> The pytest traceback is nice, but in this case it is does not
>> >> show any useful info.
>> >>
>> >> Since we run a script using ssh, the error message should include
>> >> the process stdout and stderr
>> >> which probably can explain the failure.
>> > I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging
>> > during storage setup.
>> > Unfortunately AFAICS it didn't fail, so I guess we'll have to
>> > merge it and wait for a failed job to get some helpful logs.
>>  Thanks.
>> 
>>  It still fails for me with current code:
>> 
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/
>> 
>> 
>>  Same when using current vdsm master.
>> >>> Updated the patch according to your suggestions and currently trying
>> >>> out
>> >>> OST for the 4th time -
>> >>> all previous runs succeeded. I guess I'm out of luck :)
>> >> It succeeds on your local OST setup but fail on Jenkins?
>> > No, I mean jenkins - both check-patch runs didn't fail on this script.
>> > I also tried running OST manually twice and same thing happened.
>> > Anyway - the patch has been merged now so if any failure occurs in CQ
>> > we should know what's going on.
>> Ok, finally caught a failure in CQ [1]:
>>
>> [2020-03-23T14:14:09.836Z] if result.code != 0:
>> [2020-03-23T14:14:09.836Z] msg = (
>> [2020-03-23T14:14:09.836Z] 'setup_storage.sh failed with
>> exit code: {}.\n'
>> [2020-03-23T14:14:09.836Z] 'stdout:\n{}'
>> [2020-03-23T14:14:09.836Z] 'stderr:\n{}'
>> [2020-03-23T14:14:09.836Z] ).format(result.code, result.out,
>> result.err)
>> [2020-03-23T14:14:09.836Z] >   raise RuntimeError(msg)
>> [2020-03-23T14:14:09.836Z] E   RuntimeError: setup_storage.sh
>> failed with exit code: 1.
>> [2020-03-23T14:14:09.836Z] E   stdout:
>> [2020-03-23T14:14:09.836Z] E   Reposync & Extra Sources
>> Content0.0  B/s |   0  B 00:00
>> [2020-03-23T14:14:09.836Z] E   stderr:
>> [2020-03-23T14:14:09.836Z] E   + set -xe
>> [2020-03-23T14:14:09.836Z] E   +
>> MAIN_NFS_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_2
>> [2020-03-23T14:14:09.836Z] E   +
>> ISCSI_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_3
>> [2020-03-23T14:14:09.836Z] E   + NUM_LUNS=5
>> [2020-03-23T14:14:09.836Z] E   ++ uname -r
>> [2020-03-23T14:14:09.836Z] E   ++ awk -F. '{print $(NF-1)}'
>> [2020-03-23T14:14:09.836Z] E   + DIST=el8_1
>> [2020-03-23T14:14:09.836Z] E   + main
>> [2020-03-23T14:14:09.836Z] E   ++ hostname
>> [2020-03-23T14:14:09.836Z] E   + [[
>> lago-basic-suite-master-engine == *\i\p\v\6* ]]
>> [2020-03-23T14:14:09.836Z] E   + install_deps
>> [2020-03-23T14:14:09.836Z] E   + systemctl disable --now
>> kdump.service
>> [2020-03-23T14:14:09.836Z] E   Removed
>>

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

2020-03-23 Thread Martin Perina

On Mon, Mar 23, 2020 at 3:16 PM Marcin Sobczyk  wrote:

>
>
> On 3/23/20 3:10 PM, Marcin Sobczyk wrote:
> >
> >
> > On 3/23/20 2:53 PM, Nir Soffer wrote:
> >> On Mon, Mar 23, 2020 at 3:26 PM Marcin Sobczyk 
> >> wrote:
> >>>
> >>>
> >>> On 3/23/20 2:17 PM, Nir Soffer wrote:
>  On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk
>   wrote:
> >
> > On 3/21/20 1:18 AM, Nir Soffer wrote:
> >
> > On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer 
> > wrote:
> >> Looks like infrastructure issue setting up storage on engine host.
> >>
> >> Here are 2 failing builds with unrelated changes:
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
> > Rebuilding still fails in setup_storage:
> >
> >
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
> >
> >
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/
> >
> >
> >> Is this a known issue?
> >>
> >> Error Message
> >>
> >> AssertionError: setup_storage.sh failed. Exit code is 1 assert 1
> >> == 0   -1   +0
> >>
> >> Stacktrace
> >>
> >> prefix = 
> >>
> >>   @pytest.mark.run(order=14)
> >>   def test_configure_storage(prefix):
> >>   engine = prefix.virt_env.engine_vm()
> >>   result = engine.ssh(
> >>   [
> >>   '/tmp/setup_storage.sh',
> >>   ],
> >>   )
> >>> assert result.code == 0, 'setup_storage.sh failed. Exit
> >>> code is %s' % result.code
> >> E   AssertionError: setup_storage.sh failed. Exit code is 1
> >> E   assert 1 == 0
> >> E -1
> >> E +0
> >>
> >>
> >> The pytest traceback is nice, but in this case it is does not
> >> show any useful info.
> >>
> >> Since we run a script using ssh, the error message should include
> >> the process stdout and stderr
> >> which probably can explain the failure.
> > I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging
> > during storage setup.
> > Unfortunately AFAICS it didn't fail, so I guess we'll have to
> > merge it and wait for a failed job to get some helpful logs.
>  Thanks.
> 
>  It still fails for me with current code:
> 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/
> 
> 
>  Same when using current vdsm master.
> >>> Updated the patch according to your suggestions and currently trying
> >>> out
> >>> OST for the 4th time -
> >>> all previous runs succeeded. I guess I'm out of luck :)
> >> It succeeds on your local OST setup but fail on Jenkins?
> > No, I mean jenkins - both check-patch runs didn't fail on this script.
> > I also tried running OST manually twice and same thing happened.
> > Anyway - the patch has been merged now so if any failure occurs in CQ
> > we should know what's going on.
> Ok, finally caught a failure in CQ [1]:
>
> [2020-03-23T14:14:09.836Z] if result.code != 0:
> [2020-03-23T14:14:09.836Z] msg = (
> [2020-03-23T14:14:09.836Z] 'setup_storage.sh failed with
> exit code: {}.\n'
> [2020-03-23T14:14:09.836Z] 'stdout:\n{}'
> [2020-03-23T14:14:09.836Z] 'stderr:\n{}'
> [2020-03-23T14:14:09.836Z] ).format(result.code, result.out,
> result.err)
> [2020-03-23T14:14:09.836Z] >   raise RuntimeError(msg)
> [2020-03-23T14:14:09.836Z] E   RuntimeError: setup_storage.sh
> failed with exit code: 1.
> [2020-03-23T14:14:09.836Z] E   stdout:
> [2020-03-23T14:14:09.836Z] E   Reposync & Extra Sources
> Content0.0  B/s |   0  B 00:00
> [2020-03-23T14:14:09.836Z] E   stderr:
> [2020-03-23T14:14:09.836Z] E   + set -xe
> [2020-03-23T14:14:09.836Z] E   +
> MAIN_NFS_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_2
> [2020-03-23T14:14:09.836Z] E   +
> ISCSI_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_3
> [2020-03-23T14:14:09.836Z] E   + NUM_LUNS=5
> [2020-03-23T14:14:09.836Z] E   ++ uname -r
> [2020-03-23T14:14:09.836Z] E   ++ awk -F. '{print $(NF-1)}'
> [2020-03-23T14:14:09.836Z] E   + DIST=el8_1
> [2020-03-23T14:14:09.836Z] E   + main
> [2020-03-23T14:14:09.836Z] E   ++ hostname
> [2020-03-23T14:14:09.836Z] E   + [[
> lago-basic-suite-master-engine == *\i\p\v\6* ]]
> [2020-03-23T14:14:09.836Z] E   + install_deps
> [2020-03-23T14:14:09.836Z] E   + systemctl disable --now
> kdump.service
> [2020-03-23T14:14:09.836Z] E   Removed
> /etc/systemd/system/multi-user.target.wants/kdump.service.
> [2020-03-23T14:14:09.836Z] E   + yum install --nogpgcheck -y
> nfs-utils rpcbind lvm2 targetcli sg3_utils iscsi-initiator-utils lsscsi
> policycoreutils-python-utils
>

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh




On 3/23/20 3:10 PM, Marcin Sobczyk wrote:



On 3/23/20 2:53 PM, Nir Soffer wrote:
On Mon, Mar 23, 2020 at 3:26 PM Marcin Sobczyk  
wrote:



On 3/23/20 2:17 PM, Nir Soffer wrote:
On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk 
 wrote:


On 3/21/20 1:18 AM, Nir Soffer wrote:

On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer  
wrote:

Looks like infrastructure issue setting up storage on engine host.

Here are 2 failing builds with unrelated changes:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/

Rebuilding still fails in setup_storage:

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/ 

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/ 




Is this a known issue?

Error Message

AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 
== 0   -1   +0


Stacktrace

prefix = 

  @pytest.mark.run(order=14)
  def test_configure_storage(prefix):
  engine = prefix.virt_env.engine_vm()
  result = engine.ssh(
  [
  '/tmp/setup_storage.sh',
  ],
  )
    assert result.code == 0, 'setup_storage.sh failed. Exit 
code is %s' % result.code

E   AssertionError: setup_storage.sh failed. Exit code is 1
E   assert 1 == 0
E -1
E +0


The pytest traceback is nice, but in this case it is does not 
show any useful info.


Since we run a script using ssh, the error message should include 
the process stdout and stderr

which probably can explain the failure.
I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging 
during storage setup.
Unfortunately AFAICS it didn't fail, so I guess we'll have to 
merge it and wait for a failed job to get some helpful logs.

Thanks.

It still fails for me with current code:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/ 



Same when using current vdsm master.
Updated the patch according to your suggestions and currently trying 
out

OST for the 4th time -
all previous runs succeeded. I guess I'm out of luck :)

It succeeds on your local OST setup but fail on Jenkins?

No, I mean jenkins - both check-patch runs didn't fail on this script.
I also tried running OST manually twice and same thing happened.
Anyway - the patch has been merged now so if any failure occurs in CQ
we should know what's going on.

Ok, finally caught a failure in CQ [1]:

[2020-03-23T14:14:09.836Z] if result.code != 0:
[2020-03-23T14:14:09.836Z] msg = (
[2020-03-23T14:14:09.836Z] 'setup_storage.sh failed with 
exit code: {}.\n'

[2020-03-23T14:14:09.836Z] 'stdout:\n{}'
[2020-03-23T14:14:09.836Z] 'stderr:\n{}'
[2020-03-23T14:14:09.836Z] ).format(result.code, result.out, 
result.err)

[2020-03-23T14:14:09.836Z] >   raise RuntimeError(msg)
[2020-03-23T14:14:09.836Z] E   RuntimeError: setup_storage.sh 
failed with exit code: 1.

[2020-03-23T14:14:09.836Z] E   stdout:
[2020-03-23T14:14:09.836Z] E   Reposync & Extra Sources 
Content    0.0  B/s |   0  B 00:00

[2020-03-23T14:14:09.836Z] E   stderr:
[2020-03-23T14:14:09.836Z] E   + set -xe
[2020-03-23T14:14:09.836Z] E   + 
MAIN_NFS_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_2
[2020-03-23T14:14:09.836Z] E   + 
ISCSI_DEV=disk/by-id/scsi-0QEMU_QEMU_HARDDISK_3

[2020-03-23T14:14:09.836Z] E   + NUM_LUNS=5
[2020-03-23T14:14:09.836Z] E   ++ uname -r
[2020-03-23T14:14:09.836Z] E   ++ awk -F. '{print $(NF-1)}'
[2020-03-23T14:14:09.836Z] E   + DIST=el8_1
[2020-03-23T14:14:09.836Z] E   + main
[2020-03-23T14:14:09.836Z] E   ++ hostname
[2020-03-23T14:14:09.836Z] E   + [[ 
lago-basic-suite-master-engine == *\i\p\v\6* ]]

[2020-03-23T14:14:09.836Z] E   + install_deps
[2020-03-23T14:14:09.836Z] E   + systemctl disable --now 
kdump.service
[2020-03-23T14:14:09.836Z] E   Removed 
/etc/systemd/system/multi-user.target.wants/kdump.service.
[2020-03-23T14:14:09.836Z] E   + yum install --nogpgcheck -y 
nfs-utils rpcbind lvm2 targetcli sg3_utils iscsi-initiator-utils lsscsi 
policycoreutils-python-utils
[2020-03-23T14:14:09.836Z] E   Failed to download metadata for 
repo 'alocalsync'
[2020-03-23T14:14:09.836Z] E   Error: Failed to download 
metadata for repo 'alocalsync'



[1] 
https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-master_change-queue-tester/detail/ovirt-master_change-queue-tester/21420/pipeline






Also I wonder why this code is called as a test 
(test_configure_storage). This looks like setup

step so it should run as a fixture.
That's true, but the pytest porting effort was about providing a 
bare minimum to move away from nose.
Organizing the tests into proper setup/fixtures is a huge task and 
will be probably implemented

incrementally in the nearest

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

On 3/23/20 2:53 PM, Nir Soffer wrote:

On Mon, Mar 23, 2020 at 3:26 PM Marcin Sobczyk wrote:

On 3/23/20 2:17 PM, Nir Soffer wrote:

On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk wrote:

On 3/21/20 1:18 AM, Nir Soffer wrote:

On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer wrote:

Looks like infrastructure issue setting up storage on engine host.

Here are 2 failing builds with unrelated changes:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/

Rebuilding still fails in setup_storage:

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/

Is this a known issue?

Error Message

AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 == 0 -1 +0

Stacktrace

prefix =

@pytest.mark.run(order=14)
def test_configure_storage(prefix):
engine = prefix.virt_env.engine_vm()
result = engine.ssh(
[
'/tmp/setup_storage.sh',
],
)

assert result.code == 0, 'setup_storage.sh failed. Exit code is %s' %
result.code

E AssertionError: setup_storage.sh failed. Exit code is 1
E assert 1 == 0
E -1
E +0

The pytest traceback is nice, but in this case it is does not show any useful
info.

Since we run a script using ssh, the error message should include the process
stdout and stderr
which probably can explain the failure.

I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging during storage
setup.
Unfortunately AFAICS it didn't fail, so I guess we'll have to merge it and wait
for a failed job to get some helpful logs.

Thanks.

It still fails for me with current code:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/

Same when using current vdsm master.

Updated the patch according to your suggestions and currently trying out
OST for the 4th time -
all previous runs succeeded. I guess I'm out of luck :)

It succeeds on your local OST setup but fail on Jenkins?

No, I mean jenkins - both check-patch runs didn't fail on this script.
I also tried running OST manually twice and same thing happened.
Anyway - the patch has been merged now so if any failure occurs in CQ
we should know what's going on.

Also I wonder why this code is called as a test (test_configure_storage). This
looks like setup
step so it should run as a fixture.

That's true, but the pytest porting effort was about providing a bare minimum
to move away from nose.
Organizing the tests into proper setup/fixtures is a huge task and will be
probably implemented
incrementally in the nearest future.

Understood

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/53CVZBUF5PQU7UJKCGYBGYUIJH32JYGI/

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

2020-03-23 Thread Nir Soffer

On Mon, Mar 23, 2020 at 3:26 PM Marcin Sobczyk  wrote:
>
>
>
> On 3/23/20 2:17 PM, Nir Soffer wrote:
> > On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk  wrote:
> >>
> >>
> >> On 3/21/20 1:18 AM, Nir Soffer wrote:
> >>
> >> On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer  wrote:
> >>> Looks like infrastructure issue setting up storage on engine host.
> >>>
> >>> Here are 2 failing builds with unrelated changes:
> >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
> >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
> >>
> >> Rebuilding still fails in setup_storage:
> >>
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/
> >>
> >>>
> >>> Is this a known issue?
> >>>
> >>> Error Message
> >>>
> >>> AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 == 0   
> >>> -1   +0
> >>>
> >>> Stacktrace
> >>>
> >>> prefix = 
> >>>
> >>>  @pytest.mark.run(order=14)
> >>>  def test_configure_storage(prefix):
> >>>  engine = prefix.virt_env.engine_vm()
> >>>  result = engine.ssh(
> >>>  [
> >>>  '/tmp/setup_storage.sh',
> >>>  ],
> >>>  )
> assert result.code == 0, 'setup_storage.sh failed. Exit code is 
>  %s' % result.code
> >>> E   AssertionError: setup_storage.sh failed. Exit code is 1
> >>> E   assert 1 == 0
> >>> E -1
> >>> E +0
> >>>
> >>>
> >>> The pytest traceback is nice, but in this case it is does not show any 
> >>> useful info.
> >>>
> >>> Since we run a script using ssh, the error message should include the 
> >>> process stdout and stderr
> >>> which probably can explain the failure.
> >> I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging during 
> >> storage setup.
> >> Unfortunately AFAICS it didn't fail, so I guess we'll have to merge it and 
> >> wait for a failed job to get some helpful logs.
> > Thanks.
> >
> > It still fails for me with current code:
> > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/
> >
> > Same when using current vdsm master.
> Updated the patch according to your suggestions and currently trying out
> OST for the 4th time -
> all previous runs succeeded. I guess I'm out of luck :)

It succeeds on your local OST setup but fail on Jenkins?

> >>> Also I wonder why this code is called as a test (test_configure_storage). 
> >>> This looks like setup
> >>> step so it should run as a fixture.
> >> That's true, but the pytest porting effort was about providing a bare 
> >> minimum to move away from nose.
> >> Organizing the tests into proper setup/fixtures is a huge task and will be 
> >> probably implemented
> >> incrementally in the nearest future.
> > Understood
> >
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ENQHFTYQJLBWXAI2MMY7OB6GQNURLBIA/

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

On 3/23/20 2:17 PM, Nir Soffer wrote:

On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk wrote:

On 3/21/20 1:18 AM, Nir Soffer wrote:

On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer wrote:

Looks like infrastructure issue setting up storage on engine host.

Here are 2 failing builds with unrelated changes:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/

Rebuilding still fails in setup_storage:

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/

Is this a known issue?

Error Message

AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 == 0 -1 +0

Stacktrace

prefix =

@pytest.mark.run(order=14)
def test_configure_storage(prefix):
engine = prefix.virt_env.engine_vm()
result = engine.ssh(
[
'/tmp/setup_storage.sh',
],
)

assert result.code == 0, 'setup_storage.sh failed. Exit code is %s' %
result.code

E AssertionError: setup_storage.sh failed. Exit code is 1
E assert 1 == 0
E -1
E +0

The pytest traceback is nice, but in this case it is does not show any useful
info.

Since we run a script using ssh, the error message should include the process
stdout and stderr
which probably can explain the failure.

Thanks.

It still fails for me with current code:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/

Same when using current vdsm master.
Updated the patch according to your suggestions and currently trying out
OST for the 4th time -

all previous runs succeeded. I guess I'm out of luck :)

Also I wonder why this code is called as a test (test_configure_storage). This
looks like setup
step so it should run as a fixture.

Understood

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

2020-03-23 Thread Nir Soffer

On Mon, Mar 23, 2020 at 1:25 PM Marcin Sobczyk  wrote:
>
>
>
> On 3/21/20 1:18 AM, Nir Soffer wrote:
>
> On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer  wrote:
>>
>> Looks like infrastructure issue setting up storage on engine host.
>>
>> Here are 2 failing builds with unrelated changes:
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
>
>
> Rebuilding still fails in setup_storage:
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/
>
>>
>>
>> Is this a known issue?
>>
>> Error Message
>>
>> AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 == 0   -1   
>> +0
>>
>> Stacktrace
>>
>> prefix = 
>>
>> @pytest.mark.run(order=14)
>> def test_configure_storage(prefix):
>> engine = prefix.virt_env.engine_vm()
>> result = engine.ssh(
>> [
>> '/tmp/setup_storage.sh',
>> ],
>> )
>> >   assert result.code == 0, 'setup_storage.sh failed. Exit code is %s' 
>> > % result.code
>> E   AssertionError: setup_storage.sh failed. Exit code is 1
>> E   assert 1 == 0
>> E -1
>> E +0
>>
>>
>> The pytest traceback is nice, but in this case it is does not show any 
>> useful info.
>>
>> Since we run a script using ssh, the error message should include the 
>> process stdout and stderr
>> which probably can explain the failure.
>
> I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging during 
> storage setup.
> Unfortunately AFAICS it didn't fail, so I guess we'll have to merge it and 
> wait for a failed job to get some helpful logs.

Thanks.

It still fails for me with current code:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6689/testReport/

Same when using current vdsm master.

>> Also I wonder why this code is called as a test (test_configure_storage). 
>> This looks like setup
>> step so it should run as a fixture.
>
> That's true, but the pytest porting effort was about providing a bare minimum 
> to move away from nose.
> Organizing the tests into proper setup/fixtures is a huge task and will be 
> probably implemented
> incrementally in the nearest future.

Understood
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/5AP27PDBW6GU4E6ADXUDV5COD63477IC/

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

On 3/21/20 1:18 AM, Nir Soffer wrote:
On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer > wrote:

Looks like infrastructure issue setting up storage on engine host.

Here are 2 failing builds with unrelated changes:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/

Rebuilding still fails in setup_storage:

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/

Is this a known issue?

Error Message

AssertionError: setup_storage.sh failed. Exit code is 1 assert
1 == 0 -1 +0

Stacktrace

prefix =

@pytest.mark.run(order=14)
def test_configure_storage(prefix):
engine = prefix.virt_env.engine_vm()
result = engine.ssh(
[
'/tmp/setup_storage.sh',
],
)
> assert result.code == 0, 'setup_storage.sh failed.
Exit code is %s' % result.code
E AssertionError: setup_storage.sh failed. Exit code is 1
E assert 1 == 0
E -1
E +0

The pytest traceback is nice, but in this case it is does not show
any useful info.

Since we run a script using ssh, the error message should include
the process stdout and stderr
which probably can explain the failure.

I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging during
storage setup.
Unfortunately AFAICS it didn't fail, so I guess we'll have to merge it
and wait for a failed job to get some helpful logs.

Also I wonder why this code is called as a test
(test_configure_storage). This looks like setup
step so it should run as a fixture.

That's true, but the pytest porting effort was about providing a bare
minimum to move away from nose.
Organizing the tests into proper setup/fixtures is a huge task and will
be probably implemented

incrementally in the nearest future.

Nir

[ovirt-devel] Re: OST fails in 002_bootstrap_pytest.py - setup_storage.sh

2020-03-20 Thread Nir Soffer

On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer  wrote:

> Looks like infrastructure issue setting up storage on engine host.
>
> Here are 2 failing builds with unrelated changes:
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
>

Rebuilding still fails in setup_storage:

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6679/testReport/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6680/testReport/


>
> Is this a known issue?
>
> Error Message
>
> AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 == 0   -1
>   +0
>
> Stacktrace
>
> prefix = 
>
> @pytest.mark.run(order=14)
> def test_configure_storage(prefix):
> engine = prefix.virt_env.engine_vm()
> result = engine.ssh(
> [
> '/tmp/setup_storage.sh',
> ],
> )
> >   assert result.code == 0, 'setup_storage.sh failed. Exit code is
> %s' % result.code
> E   AssertionError: setup_storage.sh failed. Exit code is 1
> E   assert 1 == 0
> E -1
> E +0
>
>
> The pytest traceback is nice, but in this case it is does not show any
> useful info.
>
> Since we run a script using ssh, the error message should include the
> process stdout and stderr
> which probably can explain the failure.
>
> Also I wonder why this code is called as a test (test_configure_storage).
> This looks like setup
> step so it should run as a fixture.
>
> Nir
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MET62OLXJPMC2K7C25QAGJ7PX6BQ4VGQ/

[ovirt-devel] Re: OST Fails for missing glusterfs mirrors at host-deploy

2020-01-01 Thread Ehud Yonasi

Hi Amit,
It's probably caused by repo under maintenance / unavailability.
We do not mirror yet centos8 because of new features it adds and we do not
support it yet.

Regards,
Ehud.

On Wed, Jan 1, 2020 at 11:55 PM Amit Bawer  wrote:

> Snippet From:
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6293/console
>
> 23:31:25 + cd
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/deployment-basic-suite-master
> 23:31:25 + lago ovirt deploy
> 23:31:26 @ Deploy oVirt environment:
> 23:31:26   # Deploy environment:
> 23:31:26 * [Thread-2] Deploy VM lago-basic-suite-master-host-0:
> 23:31:26 * [Thread-3] Deploy VM lago-basic-suite-master-host-1:
> 23:31:26 * [Thread-4] Deploy VM lago-basic-suite-master-engine:
> 23:32:15 * [Thread-3] Deploy VM lago-basic-suite-master-host-1:
> Success (in 0:00:49)
> 23:32:39 STDERR
> 23:32:39 + yum -y install ovirt-host
> 23:32:39 Error: Error downloading packages:
> 23:32:39   Cannot download glusterfs-6.6-1.el8.x86_64.rpm: All mirrors
> were tried
> 23:32:39
> 23:32:39   - STDERR
> 23:32:39 + yum -y install ovirt-host
> 23:32:39 Error: Error downloading packages:
> 23:32:39   Cannot download glusterfs-6.6-1.el8.x86_64.rpm: All mirrors
> were tried
> 23:32:39
> 23:32:39 * [Thread-2] Deploy VM lago-basic-suite-master-host-0: ERROR
> (in 0:01:13)
> 23:38:05 * [Thread-4] Deploy VM lago-basic-suite-master-engine: ERROR
> (in 0:06:39)
> 23:38:05   # Deploy environment: ERROR (in 0:06:39)
> 23:38:06 @ Deploy oVirt environment: ERROR (in 0:06:39)
> 23:38:06 Error occured, aborting
> 23:38:06 Traceback (most recent call last):
> 23:38:06   File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line
> 383, in do_run
> 23:38:06 self.cli_plugins[args.ovirtverb].do_run(args)
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py",
> line 184, in do_run
> 23:38:06 self._do_run(**vars(args))
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/utils.py", line
> 573, in wrapper
> 23:38:06 return func(*args, **kwargs)
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/utils.py", line
> 584, in wrapper
> 23:38:06 return func(*args, prefix=prefix, **kwargs)
> 23:38:06   File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line
> 181, in do_deploy
> 23:38:06 prefix.deploy()
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line
> 636, in wrapper
> 23:38:06 return func(*args, **kwargs)
> 23:38:06   File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py",
> line 127, in wrapper
> 23:38:06 return func(*args, **kwargs)
> 23:38:06   File "/usr/lib/python2.7/site-packages/ovirtlago/prefix.py",
> line 284, in deploy
> 23:38:06 return super(OvirtPrefix, self).deploy()
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/sdk_utils.py", line
> 50, in wrapped
> 23:38:06 return func(*args, **kwargs)
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line
> 636, in wrapper
> 23:38:06 return func(*args, **kwargs)
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/prefix.py", line
> 1671, in deploy
> 23:38:06 self.virt_env.get_vms().values()
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/utils.py", line
> 104, in invoke_in_parallel
> 23:38:06 return vt.join_all()
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58,
> in _ret_via_queue
> 23:38:06 queue.put({'return': func()})
> 23:38:06   File "/usr/lib/python2.7/site-packages/lago/prefix.py", line
> 1662, in _deploy_host
> 23:38:06 host.name(),
> 23:38:06 LagoDeployError:
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/deployment-basic-suite-master/default/scripts/_home_jenkins_agent_workspace_ovirt-system-tests_manual_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_1st_host_el7.sh
> failed with status 1 on lago-basic-suite-master-host-0
> 23:38:06 + res=1
> 23:38:06 + cd -
> 23:38:06
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests
> 23:38:06 + return 1
> 23:38:06 + env_collect
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master/post-000_deploy
> 23:38:06 + local
> tests_out_dir=/home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master/post-000_deploy
> 23:38:06 + [[ -e
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master
> ]]
> 23:38:06 + mkdir -p
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master
> 23:38:06 + cd
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/deployment-basic-suite-master/current
> 23:38:06 + lago collect --output
> /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master/post-000_deploy
> 23:38:08 @ Collect artifacts:
> 23:38:08   # [Thread-1]

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-27 Thread Dominik Holler

On Wed, Nov 27, 2019 at 5:44 PM Nir Soffer  wrote:

> On Wed, Nov 27, 2019 at 5:54 PM Tal Nisan  wrote:
>
>>
>>
>> On Wed, Nov 27, 2019 at 1:27 PM Marcin Sobczyk 
>> wrote:
>>
>>> Hi,
>>>
>>> I ran OST on my physical server.
>>> I'm experiencing probably the same issues as described in the thread
>>> below.
>>>
>>> On one of the hosts:
>>>
>>> [root@lago-basic-suite-master-host-0 tmp]# ls -l /rhev/data-center/mnt/
>>> ls: cannot access '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1':
>>> Operation not permitted
>>> ls: cannot access '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share2':
>>> Operation not permitted
>>> ls: cannot access 
>>> '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_exported':
>>> Operation not permitted
>>> total 0
>>> d?? ? ???? 192.168.200.4:
>>> _exports_nfs_exported
>>> d?? ? ???? 192.168.200.4:_exports_nfs_share1
>>> d?? ? ???? 192.168.200.4:_exports_nfs_share2
>>> drwxr-xr-x. 3 vdsm kvm 50 Nov 27 04:22 blockSD
>>>
>>> I think there's some problem with the nfs shares on engine.
>>>
>> We saw it recently with the move to RHEL8, Nir isn't that the same issue
>> with the NFS squashing?
>>
>
> root not being able to access NFS is expected if the NFS server is not
> configured
> with annonuid=36,annongid=36.
>
> This is not new and did not change in rhel8. The change is probably in
> libvirt, trying to
> access disk it should not access since we disable dac in the xml for disks.
>
> When this happens vms do not start, and here the issue seems to be that vm
> get paused after
> some time because storage becomes inaccessible.
>
> I can mount engine's nfs shares directly from server's native OS:
>>>
>>> ➜  /tmp mkdir -p /tmp/aaa && mount "192.168.200.4:/exports/nfs/share1"
>>> /tmp/aaa
>>> ➜  /tmp ls -l /tmp/aaa
>>> total 4
>>> drwxr-xr-x. 5 36 kvm 4096 Nov 27 10:18
>>> 3332759c-a943-4fbd-80aa-a5f72cd87c7c
>>> ➜  /tmp
>>>
>>> But trying to do that from one of the hosts fails:
>>>
>>> [root@lago-basic-suite-master-host-0 tmp]# mkdir -p /tmp/aaa && mount
>>> -v "192.168.200.4:/exports/nfs/share1" /tmp/aaa
>>> mount.nfs: timeout set for Wed Nov 27 06:26:19 2019
>>> mount.nfs: trying text-based options
>>> 'vers=4.2,addr=192.168.200.4,clientaddr=192.168.201.2'
>>> mount.nfs: mount(2): Operation not permitted
>>> mount.nfs: trying text-based options 'addr=192.168.200.4'
>>> mount.nfs: prog 13, trying vers=3, prot=6
>>> mount.nfs: portmap query failed: RPC: Remote system error - No route to
>>> host
>>>
>>
> Smells like broken network.
>
>

As I reproduced this scenario, ping was working, while NFS not working.


> On the engine side, '/var/log/messages' seems to be flooded with nfs
>>> issues, example failures:
>>>
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel:
>>> __find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence:
>>> slotid 0
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid
>>> enter. seqid 405 slot_seqid 404
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>>> 9042fc202080 opcnt 3 #1: 53: status 0
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>>> #2/3: 22 (OP_PUTFH)
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd:
>>> fh_verify(28: 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request
>>> from insecure port 192.168.200.1, port=51529!
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>>> 9042fc202080 opcnt 3 #2: 22: status 1
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound
>>> returned 1
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: -->
>>> nfsd4_store_cache_entry slot 9042c4d97000
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: renewing client
>>> (clientid 5dde5a1f/cc80daed)
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd_dispatch:
>>> vers 4 proc 1
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>>> #1/3: 53 (OP_SEQUENCE)
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel:
>>> __find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence:
>>> slotid 0
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid
>>> enter. seqid 406 slot_seqid 405
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>>> 9042fc202080 opcnt 3 #1: 53: status 0
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>>> #2/3: 22 (OP_PUTFH)
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd:
>>> fh_verify(28: 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
>>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request
>>> from insecure port

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-27 Thread Nir Soffer

On Wed, Nov 27, 2019 at 5:54 PM Tal Nisan  wrote:

>
>
> On Wed, Nov 27, 2019 at 1:27 PM Marcin Sobczyk 
> wrote:
>
>> Hi,
>>
>> I ran OST on my physical server.
>> I'm experiencing probably the same issues as described in the thread
>> below.
>>
>> On one of the hosts:
>>
>> [root@lago-basic-suite-master-host-0 tmp]# ls -l /rhev/data-center/mnt/
>> ls: cannot access '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1':
>> Operation not permitted
>> ls: cannot access '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share2':
>> Operation not permitted
>> ls: cannot access 
>> '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_exported':
>> Operation not permitted
>> total 0
>> d?? ? ???? 192.168.200.4:
>> _exports_nfs_exported
>> d?? ? ???? 192.168.200.4:_exports_nfs_share1
>> d?? ? ???? 192.168.200.4:_exports_nfs_share2
>> drwxr-xr-x. 3 vdsm kvm 50 Nov 27 04:22 blockSD
>>
>> I think there's some problem with the nfs shares on engine.
>>
> We saw it recently with the move to RHEL8, Nir isn't that the same issue
> with the NFS squashing?
>

root not being able to access NFS is expected if the NFS server is not
configured
with annonuid=36,annongid=36.

This is not new and did not change in rhel8. The change is probably in
libvirt, trying to
access disk it should not access since we disable dac in the xml for disks.

When this happens vms do not start, and here the issue seems to be that vm
get paused after
some time because storage becomes inaccessible.

I can mount engine's nfs shares directly from server's native OS:
>>
>> ➜  /tmp mkdir -p /tmp/aaa && mount "192.168.200.4:/exports/nfs/share1"
>> /tmp/aaa
>> ➜  /tmp ls -l /tmp/aaa
>> total 4
>> drwxr-xr-x. 5 36 kvm 4096 Nov 27 10:18
>> 3332759c-a943-4fbd-80aa-a5f72cd87c7c
>> ➜  /tmp
>>
>> But trying to do that from one of the hosts fails:
>>
>> [root@lago-basic-suite-master-host-0 tmp]# mkdir -p /tmp/aaa && mount -v
>> "192.168.200.4:/exports/nfs/share1" /tmp/aaa
>> mount.nfs: timeout set for Wed Nov 27 06:26:19 2019
>> mount.nfs: trying text-based options
>> 'vers=4.2,addr=192.168.200.4,clientaddr=192.168.201.2'
>> mount.nfs: mount(2): Operation not permitted
>> mount.nfs: trying text-based options 'addr=192.168.200.4'
>> mount.nfs: prog 13, trying vers=3, prot=6
>> mount.nfs: portmap query failed: RPC: Remote system error - No route to
>> host
>>
>
Smells like broken network.


> On the engine side, '/var/log/messages' seems to be flooded with nfs
>> issues, example failures:
>>
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel:
>> __find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence:
>> slotid 0
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid
>> enter. seqid 405 slot_seqid 404
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>> 9042fc202080 opcnt 3 #1: 53: status 0
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>> #2/3: 22 (OP_PUTFH)
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd:
>> fh_verify(28: 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request from
>> insecure port 192.168.200.1, port=51529!
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>> 9042fc202080 opcnt 3 #2: 22: status 1
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound
>> returned 1
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: -->
>> nfsd4_store_cache_entry slot 9042c4d97000
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: renewing client
>> (clientid 5dde5a1f/cc80daed)
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd_dispatch:
>> vers 4 proc 1
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>> #1/3: 53 (OP_SEQUENCE)
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel:
>> __find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence:
>> slotid 0
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid
>> enter. seqid 406 slot_seqid 405
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>> 9042fc202080 opcnt 3 #1: 53: status 0
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>> #2/3: 22 (OP_PUTFH)
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd:
>> fh_verify(28: 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request from
>> insecure port 192.168.200.1, port=51529!
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
>> 9042fc202080 opcnt 3 #2: 22: status 1
>> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound
>> returned 1
>> Nov 27 06:25:25

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-27 Thread Tal Nisan

On Wed, Nov 27, 2019 at 1:27 PM Marcin Sobczyk  wrote:

> Hi,
>
> I ran OST on my physical server.
> I'm experiencing probably the same issues as described in the thread below.
>
> On one of the hosts:
>
> [root@lago-basic-suite-master-host-0 tmp]# ls -l /rhev/data-center/mnt/
> ls: cannot access '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1':
> Operation not permitted
> ls: cannot access '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share2':
> Operation not permitted
> ls: cannot access '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_exported':
> Operation not permitted
> total 0
> d?? ? ???? 192.168.200.4:_exports_nfs_exported
> d?? ? ???? 192.168.200.4:_exports_nfs_share1
> d?? ? ???? 192.168.200.4:_exports_nfs_share2
> drwxr-xr-x. 3 vdsm kvm 50 Nov 27 04:22 blockSD
>
> I think there's some problem with the nfs shares on engine.
>
We saw it recently with the move to RHEL8, Nir isn't that the same issue
with the NFS squashing?

>
> I can mount engine's nfs shares directly from server's native OS:
>
> ➜  /tmp mkdir -p /tmp/aaa && mount "192.168.200.4:/exports/nfs/share1"
> /tmp/aaa
> ➜  /tmp ls -l /tmp/aaa
> total 4
> drwxr-xr-x. 5 36 kvm 4096 Nov 27 10:18 3332759c-a943-4fbd-80aa-a5f72cd87c7c
> ➜  /tmp
>
> But trying to do that from one of the hosts fails:
>
> [root@lago-basic-suite-master-host-0 tmp]# mkdir -p /tmp/aaa && mount -v
> "192.168.200.4:/exports/nfs/share1" /tmp/aaa
> mount.nfs: timeout set for Wed Nov 27 06:26:19 2019
> mount.nfs: trying text-based options
> 'vers=4.2,addr=192.168.200.4,clientaddr=192.168.201.2'
> mount.nfs: mount(2): Operation not permitted
> mount.nfs: trying text-based options 'addr=192.168.200.4'
> mount.nfs: prog 13, trying vers=3, prot=6
> mount.nfs: portmap query failed: RPC: Remote system error - No route to
> host
>
> On the engine side, '/var/log/messages' seems to be flooded with nfs
> issues, example failures:
>
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel:
> __find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence:
> slotid 0
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid
> enter. seqid 405 slot_seqid 404
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
> 9042fc202080 opcnt 3 #1: 53: status 0
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
> #2/3: 22 (OP_PUTFH)
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: fh_verify(28:
> 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request from
> insecure port 192.168.200.1, port=51529!
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
> 9042fc202080 opcnt 3 #2: 22: status 1
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound
> returned 1
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: -->
> nfsd4_store_cache_entry slot 9042c4d97000
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: renewing client
> (clientid 5dde5a1f/cc80daed)
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd_dispatch: vers
> 4 proc 1
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
> #1/3: 53 (OP_SEQUENCE)
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel:
> __find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence:
> slotid 0
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid
> enter. seqid 406 slot_seqid 405
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
> 9042fc202080 opcnt 3 #1: 53: status 0
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
> #2/3: 22 (OP_PUTFH)
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: fh_verify(28:
> 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request from
> insecure port 192.168.200.1, port=51529!
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op
> 9042fc202080 opcnt 3 #2: 22: status 1
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound
> returned 1
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: -->
> nfsd4_store_cache_entry slot 9042c4d97000
> Nov 27 06:25:25 lago-basic-suite-master-engine kernel: renewing client
> (clientid 5dde5a1f/cc80daed)
>
> Regards, Marcin
>
> On 11/26/19 8:40 PM, Martin Perina wrote:
>
> I've just merged https://gerrit.ovirt.org/105111 which only silence the
> issue, but we really need to unblock OST, as it's suffering from this for
> more than 2 weeks now.
>
> Tal/Nir, could someone really investigate why the storage become
> unavailable after some time? It may be caused by recent switch of hosts to
> CentOS 8, but may be not related
>
>

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-27 Thread Marcin Sobczyk


Hi,

I ran OST on my physical server.
I'm experiencing probably the same issues as described in the thread below.

On one of the hosts:

[root@lago-basic-suite-master-host-0 tmp]# ls -l /rhev/data-center/mnt/
ls: cannot access 
'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1': Operation not 
permitted
ls: cannot access 
'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share2': Operation not 
permitted
ls: cannot access 
'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_exported': Operation 
not permitted

total 0
d?? ? ?    ?    ?    ? 192.168.200.4:_exports_nfs_exported
d?? ? ?    ?    ?    ? 192.168.200.4:_exports_nfs_share1
d?? ? ?    ?    ?    ? 192.168.200.4:_exports_nfs_share2
drwxr-xr-x. 3 vdsm kvm 50 Nov 27 04:22 blockSD

I think there's some problem with the nfs shares on engine.

I can mount engine's nfs shares directly from server's native OS:

➜  /tmp mkdir -p /tmp/aaa && mount "192.168.200.4:/exports/nfs/share1" 
/tmp/aaa

➜  /tmp ls -l /tmp/aaa
total 4
drwxr-xr-x. 5 36 kvm 4096 Nov 27 10:18 3332759c-a943-4fbd-80aa-a5f72cd87c7c
➜  /tmp

But trying to do that from one of the hosts fails:

[root@lago-basic-suite-master-host-0 tmp]# mkdir -p /tmp/aaa && mount -v 
"192.168.200.4:/exports/nfs/share1" /tmp/aaa

mount.nfs: timeout set for Wed Nov 27 06:26:19 2019
mount.nfs: trying text-based options 
'vers=4.2,addr=192.168.200.4,clientaddr=192.168.201.2'

mount.nfs: mount(2): Operation not permitted
mount.nfs: trying text-based options 'addr=192.168.200.4'
mount.nfs: prog 13, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Remote system error - No route to host

On the engine side, '/var/log/messages' seems to be flooded with nfs 
issues, example failures:


Nov 27 06:25:25 lago-basic-suite-master-engine kernel: 
__find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence: 
slotid 0
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid 
enter. seqid 405 slot_seqid 404
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op 
9042fc202080 opcnt 3 #1: 53: status 0
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op 
#2/3: 22 (OP_PUTFH)
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: 
fh_verify(28: 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request 
from insecure port 192.168.200.1, port=51529!
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op 
9042fc202080 opcnt 3 #2: 22: status 1
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound 
returned 1
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: --> 
nfsd4_store_cache_entry slot 9042c4d97000
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: renewing client 
(clientid 5dde5a1f/cc80daed)
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd_dispatch: 
vers 4 proc 1
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op 
#1/3: 53 (OP_SEQUENCE)
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: 
__find_in_sessionid_hashtbl: 1574853151:3430996717:11:0
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd4_sequence: 
slotid 0
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: check_slot_seqid 
enter. seqid 406 slot_seqid 405
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op 
9042fc202080 opcnt 3 #1: 53: status 0
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op 
#2/3: 22 (OP_PUTFH)
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: 
fh_verify(28: 00070001 00340001  e50ae88b 5c44c45a 2b7c3991)
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsd: request 
from insecure port 192.168.200.1, port=51529!
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound op 
9042fc202080 opcnt 3 #2: 22: status 1
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: nfsv4 compound 
returned 1
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: --> 
nfsd4_store_cache_entry slot 9042c4d97000
Nov 27 06:25:25 lago-basic-suite-master-engine kernel: renewing client 
(clientid 5dde5a1f/cc80daed)


Regards, Marcin

On 11/26/19 8:40 PM, Martin Perina wrote:
I've just merged https://gerrit.ovirt.org/105111 which only silence 
the issue, but we really need to unblock OST, as it's suffering from 
this for more than 2 weeks now.


Tal/Nir, could someone really investigate why the storage become 
unavailable after some time? It may be caused by recent switch of 
hosts to CentOS 8, but may be not related


Thanks,
Martin


On Tue, Nov 26, 2019 at 9:17 AM Dominik Holler > wrote:




On Mon, Nov 25, 2019 at 7:12 PM Nir Soffer mailto:nsof...@redhat.com>> wrote:

On Mon, Nov 25, 2019 at 7:15 PM Dominik Holler
mailto:dhol...@redhat.com>> wrote:
>
>
>

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-26 Thread Martin Perina

I've just merged https://gerrit.ovirt.org/105111 which only silence the
issue, but we really need to unblock OST, as it's suffering from this for
more than 2 weeks now.

Tal/Nir, could someone really investigate why the storage become
unavailable after some time? It may be caused by recent switch of hosts to
CentOS 8, but may be not related

Thanks,
Martin


On Tue, Nov 26, 2019 at 9:17 AM Dominik Holler  wrote:

>
>
> On Mon, Nov 25, 2019 at 7:12 PM Nir Soffer  wrote:
>
>> On Mon, Nov 25, 2019 at 7:15 PM Dominik Holler 
>> wrote:
>> >
>> >
>> >
>> > On Mon, Nov 25, 2019 at 6:03 PM Nir Soffer  wrote:
>> >>
>> >> On Mon, Nov 25, 2019 at 6:48 PM Dominik Holler 
>> wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Nov 25, 2019 at 5:16 PM Nir Soffer 
>> wrote:
>> >> >>
>> >> >> On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler 
>> wrote:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer 
>> wrote:
>> >> >> >>
>> >> >> >> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer <
>> nsof...@redhat.com> wrote:
>> >> >> >> 
>> >> >> >> 
>> >> >> >> 
>> >> >> >>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk <
>> msobc...@redhat.com> wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On 11/22/19 4:54 PM, Martin Perina wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora
>> Barroso  wrote:
>> >> >> >> 
>> >> >> >>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek <
>> vjura...@redhat.com> wrote:
>> >> >> >>  >
>> >> >> >>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte
>> de Mora Barroso wrote:
>> >> >> >>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
>> vjura...@redhat.com>
>> >> >> >>  > > wrote:
>> >> >> >>  > > >
>> >> >> >>  > > >
>> >> >> >>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik
>> Holler wrote:
>> >> >> >>  > > >
>> >> >> >>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
>> dhol...@redhat.com>
>> >> >> >>  > > > > wrote:
>> >> >> >>  > > > >
>> >> >> >>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
>> nsof...@redhat.com>
>> >> >> >>  > > > > > wrote:
>> >> >> >>  > > > > >
>> >> >> >>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech
>> Juranek
>> >> >> >>  > > > > >> 
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> wrote:
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> > Hi,
>> >> >> >>  > > > > >> > OST fails (see e.g. [1]) in
>> 002_bootstrap.check_update_host. It
>> >> >> >>  > > > > >> > fails
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> with
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> >  FAILED! => {"changed": false, "failures":
>> [], "msg": "Depsolve
>> >> >> >>  > > > > >> >  Error
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> occured:
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> > \n Problem 1: cannot install the best
>> update candidate for package
>> >> >> >>  > > > > >> > vdsm-
>> >> >> >>  > > > > >> >
>> network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing provides
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> nmstate
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> > needed by
>> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> >> >> >>  > > > > >> > Problem 2:
>> >> >> >>  > > > > >> > package
>> vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> vdsm-network
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  >

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-26 Thread Dan Kenigsberg

On Tue, 26 Nov 2019, 10:19 Dominik Holler,  wrote:

>
>
> On Mon, Nov 25, 2019 at 7:12 PM Nir Soffer  wrote:
>
>> On Mon, Nov 25, 2019 at 7:15 PM Dominik Holler 
>> wrote:
>> >
>> >
>> >
>> > On Mon, Nov 25, 2019 at 6:03 PM Nir Soffer  wrote:
>> >>
>> >> On Mon, Nov 25, 2019 at 6:48 PM Dominik Holler 
>> wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Nov 25, 2019 at 5:16 PM Nir Soffer 
>> wrote:
>> >> >>
>> >> >> On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler 
>> wrote:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer 
>> wrote:
>> >> >> >>
>> >> >> >> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer <
>> nsof...@redhat.com> wrote:
>> >> >> >> 
>> >> >> >> 
>> >> >> >> 
>> >> >> >>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk <
>> msobc...@redhat.com> wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On 11/22/19 4:54 PM, Martin Perina wrote:
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler <
>> dhol...@redhat.com> wrote:
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora
>> Barroso  wrote:
>> >> >> >> 
>> >> >> >>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek <
>> vjura...@redhat.com> wrote:
>> >> >> >>  >
>> >> >> >>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte
>> de Mora Barroso wrote:
>> >> >> >>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
>> vjura...@redhat.com>
>> >> >> >>  > > wrote:
>> >> >> >>  > > >
>> >> >> >>  > > >
>> >> >> >>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik
>> Holler wrote:
>> >> >> >>  > > >
>> >> >> >>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
>> dhol...@redhat.com>
>> >> >> >>  > > > > wrote:
>> >> >> >>  > > > >
>> >> >> >>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
>> nsof...@redhat.com>
>> >> >> >>  > > > > > wrote:
>> >> >> >>  > > > > >
>> >> >> >>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech
>> Juranek
>> >> >> >>  > > > > >> 
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> wrote:
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> > Hi,
>> >> >> >>  > > > > >> > OST fails (see e.g. [1]) in
>> 002_bootstrap.check_update_host. It
>> >> >> >>  > > > > >> > fails
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> with
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> >  FAILED! => {"changed": false, "failures":
>> [], "msg": "Depsolve
>> >> >> >>  > > > > >> >  Error
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> occured:
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> > \n Problem 1: cannot install the best
>> update candidate for package
>> >> >> >>  > > > > >> > vdsm-
>> >> >> >>  > > > > >> >
>> network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing provides
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> nmstate
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> > needed by
>> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> >> >> >>  > > > > >> > Problem 2:
>> >> >> >>  > > > > >> > package
>> vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> vdsm-network
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none
>> of the providers can be
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >> installed\n
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>  > > > > >>
>> >> >> >>

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-26 Thread Dominik Holler

On Mon, Nov 25, 2019 at 7:12 PM Nir Soffer  wrote:

> On Mon, Nov 25, 2019 at 7:15 PM Dominik Holler  wrote:
> >
> >
> >
> > On Mon, Nov 25, 2019 at 6:03 PM Nir Soffer  wrote:
> >>
> >> On Mon, Nov 25, 2019 at 6:48 PM Dominik Holler 
> wrote:
> >> >
> >> >
> >> >
> >> > On Mon, Nov 25, 2019 at 5:16 PM Nir Soffer 
> wrote:
> >> >>
> >> >> On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler 
> wrote:
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer 
> wrote:
> >> >> >>
> >> >> >> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >> >>>
> >> >> >> >>>
> >> >> >> >>>
> >> >> >> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer <
> nsof...@redhat.com> wrote:
> >> >> >> 
> >> >> >> 
> >> >> >> 
> >> >> >>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk <
> msobc...@redhat.com> wrote:
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > On 11/22/19 4:54 PM, Martin Perina wrote:
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >> >>>
> >> >> >> >>>
> >> >> >> >>>
> >> >> >> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora
> Barroso  wrote:
> >> >> >> 
> >> >> >>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek <
> vjura...@redhat.com> wrote:
> >> >> >>  >
> >> >> >>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte
> de Mora Barroso wrote:
> >> >> >>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
> vjura...@redhat.com>
> >> >> >>  > > wrote:
> >> >> >>  > > >
> >> >> >>  > > >
> >> >> >>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik
> Holler wrote:
> >> >> >>  > > >
> >> >> >>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
> dhol...@redhat.com>
> >> >> >>  > > > > wrote:
> >> >> >>  > > > >
> >> >> >>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
> nsof...@redhat.com>
> >> >> >>  > > > > > wrote:
> >> >> >>  > > > > >
> >> >> >>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech
> Juranek
> >> >> >>  > > > > >> 
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> wrote:
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> > Hi,
> >> >> >>  > > > > >> > OST fails (see e.g. [1]) in
> 002_bootstrap.check_update_host. It
> >> >> >>  > > > > >> > fails
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> with
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> >  FAILED! => {"changed": false, "failures":
> [], "msg": "Depsolve
> >> >> >>  > > > > >> >  Error
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> occured:
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> > \n Problem 1: cannot install the best
> update candidate for package
> >> >> >>  > > > > >> > vdsm-
> >> >> >>  > > > > >> >
> network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing provides
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> nmstate
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> >> >> >>  > > > > >> > Problem 2:
> >> >> >>  > > > > >> > package
> vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> vdsm-network
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of
> the providers can be
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> installed\n
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >>
> >> >> >>  > > > > >> > - cannot install the best update candidate
> for package vdsm-
> >> >> >>  > > > > >> >
> python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing provides
> >> >> >>  > > > >

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Mon, Nov 25, 2019 at 7:15 PM Dominik Holler  wrote:
>
>
>
> On Mon, Nov 25, 2019 at 6:03 PM Nir Soffer  wrote:
>>
>> On Mon, Nov 25, 2019 at 6:48 PM Dominik Holler  wrote:
>> >
>> >
>> >
>> > On Mon, Nov 25, 2019 at 5:16 PM Nir Soffer  wrote:
>> >>
>> >> On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler  wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer  wrote:
>> >> >>
>> >> >> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler  
>> >> >> wrote:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler  
>> >> >> > wrote:
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler  
>> >> >> >> wrote:
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  
>> >> >> >>> wrote:
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  
>> >> >>  wrote:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On 11/22/19 4:54 PM, Martin Perina wrote:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler 
>> >> >> >  wrote:
>> >> >> >>
>> >> >> >>
>> >> >> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
>> >> >> >>  wrote:
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso 
>> >> >> >>>  wrote:
>> >> >> 
>> >> >>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
>> >> >>   wrote:
>> >> >>  >
>> >> >>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de 
>> >> >>  > Mora Barroso wrote:
>> >> >>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek 
>> >> >>  > > 
>> >> >>  > > wrote:
>> >> >>  > > >
>> >> >>  > > >
>> >> >>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler 
>> >> >>  > > > wrote:
>> >> >>  > > >
>> >> >>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler 
>> >> >>  > > > > 
>> >> >>  > > > > wrote:
>> >> >>  > > > >
>> >> >>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer 
>> >> >>  > > > > > 
>> >> >>  > > > > > wrote:
>> >> >>  > > > > >
>> >> >>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>> >> >>  > > > > >> 
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> wrote:
>> >> >>  > > > > >>
>> >> >>  > > > > >> > Hi,
>> >> >>  > > > > >> > OST fails (see e.g. [1]) in 
>> >> >>  > > > > >> > 002_bootstrap.check_update_host. It
>> >> >>  > > > > >> > fails
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> with
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> >  FAILED! => {"changed": false, "failures": [], 
>> >> >>  > > > > >> > "msg": "Depsolve
>> >> >>  > > > > >> >  Error
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> occured:
>> >> >>  > > > > >>
>> >> >>  > > > > >> > \n Problem 1: cannot install the best update 
>> >> >>  > > > > >> > candidate for package
>> >> >>  > > > > >> > vdsm-
>> >> >>  > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - 
>> >> >>  > > > > >> > nothing provides
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> nmstate
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> > needed by 
>> >> >>  > > > > >> > vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> >> >>  > > > > >> > Problem 2:
>> >> >>  > > > > >> > package 
>> >> >>  > > > > >> > vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch 
>> >> >>  > > > > >> > requires
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> vdsm-network
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the 
>> >> >>  > > > > >> > providers can be
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> installed\n
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >>
>> >> >>  > > > > >> > - cannot install the best update candidate for 
>> >> >>  > > > > >> > package vdsm-
>> >> >>  > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - 
>> >> >>  > > > > >> > nothing provides
>> >> >>  > > > > >> >

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Mon, Nov 25, 2019 at 6:03 PM Nir Soffer  wrote:

> On Mon, Nov 25, 2019 at 6:48 PM Dominik Holler  wrote:
> >
> >
> >
> > On Mon, Nov 25, 2019 at 5:16 PM Nir Soffer  wrote:
> >>
> >> On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler 
> wrote:
> >> >
> >> >
> >> >
> >> > On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer 
> wrote:
> >> >>
> >> >> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler 
> wrote:
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler 
> wrote:
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer 
> wrote:
> >> >> 
> >> >> 
> >> >> 
> >> >>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk 
> wrote:
> >> >> >
> >> >> >
> >> >> >
> >> >> > On 11/22/19 4:54 PM, Martin Perina wrote:
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >>
> >> >> >>
> >> >> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora
> Barroso  wrote:
> >> >> 
> >> >>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek <
> vjura...@redhat.com> wrote:
> >> >>  >
> >> >>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de
> Mora Barroso wrote:
> >> >>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
> vjura...@redhat.com>
> >> >>  > > wrote:
> >> >>  > > >
> >> >>  > > >
> >> >>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik
> Holler wrote:
> >> >>  > > >
> >> >>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
> dhol...@redhat.com>
> >> >>  > > > > wrote:
> >> >>  > > > >
> >> >>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
> nsof...@redhat.com>
> >> >>  > > > > > wrote:
> >> >>  > > > > >
> >> >>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
> >> >>  > > > > >> 
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> wrote:
> >> >>  > > > > >>
> >> >>  > > > > >> > Hi,
> >> >>  > > > > >> > OST fails (see e.g. [1]) in
> 002_bootstrap.check_update_host. It
> >> >>  > > > > >> > fails
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> with
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> >  FAILED! => {"changed": false, "failures": [],
> "msg": "Depsolve
> >> >>  > > > > >> >  Error
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> occured:
> >> >>  > > > > >>
> >> >>  > > > > >> > \n Problem 1: cannot install the best update
> candidate for package
> >> >>  > > > > >> > vdsm-
> >> >>  > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n
> - nothing provides
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> nmstate
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> >> >>  > > > > >> > Problem 2:
> >> >>  > > > > >> > package
> vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> vdsm-network
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of
> the providers can be
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> installed\n
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> > - cannot install the best update candidate for
> package vdsm-
> >> >>  > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n
> - nothing provides
> >> >>  > > > > >> > nmstate
> >> >>  > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >>
> >> >>  > > > > >> nmstate should be provided by copr repo enabled
> by
> >> >>  > > > > >> ovirt-release-master.
> >> >>  > > > > >
> >> >>  > > > > >
> >> >>  > > > > >
> >> >>  > > > > > I re-triggered as
> >> >>  > > > > >
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> >> >>  > > > > >

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Mon, Nov 25, 2019 at 6:48 PM Dominik Holler  wrote:
>
>
>
> On Mon, Nov 25, 2019 at 5:16 PM Nir Soffer  wrote:
>>
>> On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler  wrote:
>> >
>> >
>> >
>> > On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer  wrote:
>> >>
>> >> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler  
>> >> wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler  
>> >> > wrote:
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler  
>> >> >> wrote:
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  wrote:
>> >> 
>> >> 
>> >> 
>> >>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  
>> >>  wrote:
>> >> >
>> >> >
>> >> >
>> >> > On 11/22/19 4:54 PM, Martin Perina wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler  
>> >> > wrote:
>> >> >>
>> >> >>
>> >> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
>> >> >>  wrote:
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso 
>> >> >>>  wrote:
>> >> 
>> >>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
>> >>   wrote:
>> >>  >
>> >>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora 
>> >>  > Barroso wrote:
>> >>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek 
>> >>  > > 
>> >>  > > wrote:
>> >>  > > >
>> >>  > > >
>> >>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler 
>> >>  > > > wrote:
>> >>  > > >
>> >>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler 
>> >>  > > > > 
>> >>  > > > > wrote:
>> >>  > > > >
>> >>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer 
>> >>  > > > > > 
>> >>  > > > > > wrote:
>> >>  > > > > >
>> >>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>> >>  > > > > >> 
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> wrote:
>> >>  > > > > >>
>> >>  > > > > >> > Hi,
>> >>  > > > > >> > OST fails (see e.g. [1]) in 
>> >>  > > > > >> > 002_bootstrap.check_update_host. It
>> >>  > > > > >> > fails
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> with
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> >  FAILED! => {"changed": false, "failures": [], 
>> >>  > > > > >> > "msg": "Depsolve
>> >>  > > > > >> >  Error
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> occured:
>> >>  > > > > >>
>> >>  > > > > >> > \n Problem 1: cannot install the best update 
>> >>  > > > > >> > candidate for package
>> >>  > > > > >> > vdsm-
>> >>  > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - 
>> >>  > > > > >> > nothing provides
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> nmstate
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> > needed by 
>> >>  > > > > >> > vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> >>  > > > > >> > Problem 2:
>> >>  > > > > >> > package 
>> >>  > > > > >> > vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch 
>> >>  > > > > >> > requires
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> vdsm-network
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the 
>> >>  > > > > >> > providers can be
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> installed\n
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> > - cannot install the best update candidate for 
>> >>  > > > > >> > package vdsm-
>> >>  > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - 
>> >>  > > > > >> > nothing provides
>> >>  > > > > >> > nmstate
>> >>  > > > > >> > needed by 
>> >>  > > > > >> > vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >>
>> >>  > > > > >> nmstate should be provided by copr repo enabled by
>> >>  > > > > >> ovirt-release-master.
>> >>  > > > > >
>> >>  > > > > >
>> >>  > > > > >
>> >>  > > > > > I re-triggered as
>> >>  > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>> >>

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Mon, Nov 25, 2019 at 5:16 PM Nir Soffer  wrote:

> On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler  wrote:
> >
> >
> >
> > On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer  wrote:
> >>
> >> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler 
> wrote:
> >> >
> >> >
> >> >
> >> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler 
> wrote:
> >> >>
> >> >>
> >> >>
> >> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler 
> wrote:
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer 
> wrote:
> >> 
> >> 
> >> 
> >>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk 
> wrote:
> >> >
> >> >
> >> >
> >> > On 11/22/19 4:54 PM, Martin Perina wrote:
> >> >
> >> >
> >> >
> >> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >>
> >> >>
> >> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler <
> dhol...@redhat.com> wrote:
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
> mdbarr...@redhat.com> wrote:
> >> 
> >>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek <
> vjura...@redhat.com> wrote:
> >>  >
> >>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de
> Mora Barroso wrote:
> >>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
> vjura...@redhat.com>
> >>  > > wrote:
> >>  > > >
> >>  > > >
> >>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler
> wrote:
> >>  > > >
> >>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
> dhol...@redhat.com>
> >>  > > > > wrote:
> >>  > > > >
> >>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
> nsof...@redhat.com>
> >>  > > > > > wrote:
> >>  > > > > >
> >>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
> >>  > > > > >> 
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> wrote:
> >>  > > > > >>
> >>  > > > > >> > Hi,
> >>  > > > > >> > OST fails (see e.g. [1]) in
> 002_bootstrap.check_update_host. It
> >>  > > > > >> > fails
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> with
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> >  FAILED! => {"changed": false, "failures": [],
> "msg": "Depsolve
> >>  > > > > >> >  Error
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> occured:
> >>  > > > > >>
> >>  > > > > >> > \n Problem 1: cannot install the best update
> candidate for package
> >>  > > > > >> > vdsm-
> >>  > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  -
> nothing provides
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> nmstate
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> >>  > > > > >> > Problem 2:
> >>  > > > > >> > package
> vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> vdsm-network
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the
> providers can be
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> installed\n
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> > - cannot install the best update candidate for
> package vdsm-
> >>  > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  -
> nothing provides
> >>  > > > > >> > nmstate
> >>  > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >>
> >>  > > > > >> nmstate should be provided by copr repo enabled by
> >>  > > > > >> ovirt-release-master.
> >>  > > > > >
> >>  > > > > >
> >>  > > > > >
> >>  > > > > > I re-triggered as
> >>  > > > > >
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> >>  > > > > > maybe
> >>  > > > > > https://gerrit.ovirt.org/#/c/104825/
> >>  > > > > > was missing
> >>  > > > >
> >>  > > > >
> >>  > > > >
> >>  > > > > Looks like
> >>  > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by
> OST.
> >>  > > >
> >>  > > >
> >>  > > >
> >>  > > > maybe not. You re-triggered with [1], which really
> missed this patch.
> >>  > > > I did a rebase and now running with this

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Mon, Nov 25, 2019 at 6:05 PM Dominik Holler  wrote:
>
>
>
> On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer  wrote:
>>
>> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler  wrote:
>> >
>> >
>> >
>> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler  wrote:
>> >>
>> >>
>> >>
>> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler  wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  wrote:
>> 
>> 
>> 
>>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  wrote:
>> >
>> >
>> >
>> > On 11/22/19 4:54 PM, Martin Perina wrote:
>> >
>> >
>> >
>> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler  
>> > wrote:
>> >>
>> >>
>> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler  
>> >> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso 
>> >>>  wrote:
>> 
>>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
>>   wrote:
>>  >
>>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora 
>>  > Barroso wrote:
>>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek 
>>  > > 
>>  > > wrote:
>>  > > >
>>  > > >
>>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
>>  > > >
>>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler 
>>  > > > > 
>>  > > > > wrote:
>>  > > > >
>>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer 
>>  > > > > > 
>>  > > > > > wrote:
>>  > > > > >
>>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>>  > > > > >> 
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> wrote:
>>  > > > > >>
>>  > > > > >> > Hi,
>>  > > > > >> > OST fails (see e.g. [1]) in 
>>  > > > > >> > 002_bootstrap.check_update_host. It
>>  > > > > >> > fails
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> with
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg": 
>>  > > > > >> > "Depsolve
>>  > > > > >> >  Error
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> occured:
>>  > > > > >>
>>  > > > > >> > \n Problem 1: cannot install the best update candidate 
>>  > > > > >> > for package
>>  > > > > >> > vdsm-
>>  > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - 
>>  > > > > >> > nothing provides
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> nmstate
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> > needed by 
>>  > > > > >> > vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>>  > > > > >> > Problem 2:
>>  > > > > >> > package 
>>  > > > > >> > vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch 
>>  > > > > >> > requires
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> vdsm-network
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the 
>>  > > > > >> > providers can be
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> installed\n
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> > - cannot install the best update candidate for package 
>>  > > > > >> > vdsm-
>>  > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - 
>>  > > > > >> > nothing provides
>>  > > > > >> > nmstate
>>  > > > > >> > needed by 
>>  > > > > >> > vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>>  > > > > >>
>>  > > > > >>
>>  > > > > >>
>>  > > > > >> nmstate should be provided by copr repo enabled by
>>  > > > > >> ovirt-release-master.
>>  > > > > >
>>  > > > > >
>>  > > > > >
>>  > > > > > I re-triggered as
>>  > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>>  > > > > > maybe
>>  > > > > > https://gerrit.ovirt.org/#/c/104825/
>>  > > > > > was missing
>>  > > > >
>>  > > > >
>>  > > > >
>>  > > > > Looks like
>>  > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
>>  > > >
>>  > > >
>>  > > >
>>  > > > maybe not. You re-triggered with [1], which really missed 
>>  > > > this patch.
>>  > > > I did a rebase and now running with this patch in build #6132 
>>  > > > [2]. Let's
>>  > > > wait
>>  >  for it

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Mon, Nov 25, 2019 at 4:50 PM Nir Soffer  wrote:

> On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler 
> wrote:
> >
> >
> >
> > On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler 
> wrote:
> >>
> >>
> >>
> >> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler 
> wrote:
> >>>
> >>>
> >>>
> >>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  wrote:
> 
> 
> 
>  On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk 
> wrote:
> >
> >
> >
> > On 11/22/19 4:54 PM, Martin Perina wrote:
> >
> >
> >
> > On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler 
> wrote:
> >>
> >>
> >> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
> wrote:
> >>>
> >>>
> >>>
> >>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
> mdbarr...@redhat.com> wrote:
> 
>  On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek <
> vjura...@redhat.com> wrote:
>  >
>  > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora
> Barroso wrote:
>  > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
> vjura...@redhat.com>
>  > > wrote:
>  > > >
>  > > >
>  > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler
> wrote:
>  > > >
>  > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
> dhol...@redhat.com>
>  > > > > wrote:
>  > > > >
>  > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
> nsof...@redhat.com>
>  > > > > > wrote:
>  > > > > >
>  > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>  > > > > >> 
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> wrote:
>  > > > > >>
>  > > > > >> > Hi,
>  > > > > >> > OST fails (see e.g. [1]) in
> 002_bootstrap.check_update_host. It
>  > > > > >> > fails
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> with
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> >  FAILED! => {"changed": false, "failures": [],
> "msg": "Depsolve
>  > > > > >> >  Error
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> occured:
>  > > > > >>
>  > > > > >> > \n Problem 1: cannot install the best update
> candidate for package
>  > > > > >> > vdsm-
>  > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  -
> nothing provides
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> nmstate
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>  > > > > >> > Problem 2:
>  > > > > >> > package
> vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> vdsm-network
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the
> providers can be
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> installed\n
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> > - cannot install the best update candidate for
> package vdsm-
>  > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  -
> nothing provides
>  > > > > >> > nmstate
>  > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>  > > > > >>
>  > > > > >>
>  > > > > >>
>  > > > > >> nmstate should be provided by copr repo enabled by
>  > > > > >> ovirt-release-master.
>  > > > > >
>  > > > > >
>  > > > > >
>  > > > > > I re-triggered as
>  > > > > >
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>  > > > > > maybe
>  > > > > > https://gerrit.ovirt.org/#/c/104825/
>  > > > > > was missing
>  > > > >
>  > > > >
>  > > > >
>  > > > > Looks like
>  > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
>  > > >
>  > > >
>  > > >
>  > > > maybe not. You re-triggered with [1], which really missed
> this patch.
>  > > > I did a rebase and now running with this patch in build
> #6132 [2]. Let's
>  > > > wait
>  >  for it to see if gerrit #104825 helps.
>  > > >
>  > > >
>  > > >
>  > > > [1]
> https://jenkins.ovirt.org/job/standard-manual-runner/909/
>  > > > [2]
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
>  > > >
>  > > >
>  > > >
>  > > > > Miguel, do you think merging
>  > > > >
>  > > > >
>  > > > >
>  > > > >
>

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Mon, Nov 25, 2019 at 11:00 AM Dominik Holler  wrote:
>
>
>
> On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler  wrote:
>>
>>
>>
>> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler  wrote:
>>>
>>>
>>>
>>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  wrote:



 On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  wrote:
>
>
>
> On 11/22/19 4:54 PM, Martin Perina wrote:
>
>
>
> On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler  wrote:
>>
>>
>> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler  
>> wrote:
>>>
>>>
>>>
>>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso 
>>>  wrote:

 On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek  
 wrote:
 >
 > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora 
 > Barroso wrote:
 > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek 
 > > 
 > > wrote:
 > > >
 > > >
 > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
 > > >
 > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler 
 > > > > 
 > > > > wrote:
 > > > >
 > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer 
 > > > > > 
 > > > > > wrote:
 > > > > >
 > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
 > > > > >> 
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> wrote:
 > > > > >>
 > > > > >> > Hi,
 > > > > >> > OST fails (see e.g. [1]) in 
 > > > > >> > 002_bootstrap.check_update_host. It
 > > > > >> > fails
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> with
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg": 
 > > > > >> > "Depsolve
 > > > > >> >  Error
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> occured:
 > > > > >>
 > > > > >> > \n Problem 1: cannot install the best update candidate 
 > > > > >> > for package
 > > > > >> > vdsm-
 > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing 
 > > > > >> > provides
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> nmstate
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> > needed by 
 > > > > >> > vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
 > > > > >> > Problem 2:
 > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch 
 > > > > >> > requires
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> vdsm-network
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers 
 > > > > >> > can be
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> installed\n
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> > - cannot install the best update candidate for package 
 > > > > >> > vdsm-
 > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing 
 > > > > >> > provides
 > > > > >> > nmstate
 > > > > >> > needed by 
 > > > > >> > vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> nmstate should be provided by copr repo enabled by
 > > > > >> ovirt-release-master.
 > > > > >
 > > > > >
 > > > > >
 > > > > > I re-triggered as
 > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
 > > > > > maybe
 > > > > > https://gerrit.ovirt.org/#/c/104825/
 > > > > > was missing
 > > > >
 > > > >
 > > > >
 > > > > Looks like
 > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
 > > >
 > > >
 > > >
 > > > maybe not. You re-triggered with [1], which really missed this 
 > > > patch.
 > > > I did a rebase and now running with this patch in build #6132 
 > > > [2]. Let's
 > > > wait
 >  for it to see if gerrit #104825 helps.
 > > >
 > > >
 > > >
 > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
 > > > [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
 > > >
 > > >
 > > >
 > > > > Miguel, do you think merging
 > > > >
 > > > >
 > > > >
 > > > > https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
 > > > > t-cq
 >  .repo.in
 > > > >
 > > > >
 > > > >
 > > > > would solve this?

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Fri, Nov 22, 2019 at 8:57 PM Dominik Holler  wrote:

>
>
> On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler  wrote:
>
>>
>>
>> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  wrote:
>>
>>>
>>>
>>> On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  wrote:
>>>


 On 11/22/19 4:54 PM, Martin Perina wrote:



 On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler 
 wrote:

>
> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
> wrote:
>
>>
>>
>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
>> mdbarr...@redhat.com> wrote:
>>
>>> On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek <
>>> vjura...@redhat.com> wrote:
>>> >
>>> > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora
>>> Barroso wrote:
>>> > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
>>> vjura...@redhat.com>
>>> > > wrote:
>>> > > >
>>> > > >
>>> > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
>>> > > >
>>> > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
>>> dhol...@redhat.com>
>>> > > > > wrote:
>>> > > > >
>>> > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
>>> nsof...@redhat.com>
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>>> > > > > >> 
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> wrote:
>>> > > > > >>
>>> > > > > >> > Hi,
>>> > > > > >> > OST fails (see e.g. [1]) in
>>> 002_bootstrap.check_update_host. It
>>> > > > > >> > fails
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> with
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg":
>>> "Depsolve
>>> > > > > >> >  Error
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> occured:
>>> > > > > >>
>>> > > > > >> > \n Problem 1: cannot install the best update candidate
>>> for package
>>> > > > > >> > vdsm-
>>> > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  -
>>> nothing provides
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> nmstate
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> > needed by
>>> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>>> > > > > >> > Problem 2:
>>> > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch
>>> requires
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> vdsm-network
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the
>>> providers can be
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> installed\n
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> > - cannot install the best update candidate for package
>>> vdsm-
>>> > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing
>>> provides
>>> > > > > >> > nmstate
>>> > > > > >> > needed by
>>> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> nmstate should be provided by copr repo enabled by
>>> > > > > >> ovirt-release-master.
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > I re-triggered as
>>> > > > > >
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>>> > > > > > maybe
>>> > > > > > https://gerrit.ovirt.org/#/c/104825/
>>> > > > > > was missing
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > Looks like
>>> > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
>>> > > >
>>> > > >
>>> > > >
>>> > > > maybe not. You re-triggered with [1], which really missed this
>>> patch.
>>> > > > I did a rebase and now running with this patch in build #6132
>>> [2]. Let's
>>> > > > wait
>>> >  for it to see if gerrit #104825 helps.
>>> > > >
>>> > > >
>>> > > >
>>> > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
>>> > > > [2]
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
>>> > > >
>>> > > >
>>> > > >
>>> > > > > Miguel, do you think merging
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > >
>>> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
>>> > > > > t-cq
>>> >  .repo.in
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > would solve this?
>>> > >
>>> > >
>>> > > I've split the patch Dominik mentions above in two, one of them
>>> adding
>>> > > the nmstate / networkmanager copr repos - [3].
>>> > >
>>> > > Let's see if it fixes it.
>>> >
>>> > it fixes original issue, but OST still

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Fri, Nov 22, 2019 at 5:54 PM Dominik Holler  wrote:

>
>
> On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  wrote:
>
>>
>>
>> On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  wrote:
>>
>>>
>>>
>>> On 11/22/19 4:54 PM, Martin Perina wrote:
>>>
>>>
>>>
>>> On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler 
>>> wrote:
>>>

 On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
 wrote:

>
>
> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
> mdbarr...@redhat.com> wrote:
>
>> On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
>> wrote:
>> >
>> > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora
>> Barroso wrote:
>> > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
>> vjura...@redhat.com>
>> > > wrote:
>> > > >
>> > > >
>> > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
>> > > >
>> > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
>> dhol...@redhat.com>
>> > > > > wrote:
>> > > > >
>> > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
>> nsof...@redhat.com>
>> > > > > > wrote:
>> > > > > >
>> > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>> > > > > >> 
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >> > Hi,
>> > > > > >> > OST fails (see e.g. [1]) in
>> 002_bootstrap.check_update_host. It
>> > > > > >> > fails
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> with
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg":
>> "Depsolve
>> > > > > >> >  Error
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> occured:
>> > > > > >>
>> > > > > >> > \n Problem 1: cannot install the best update candidate
>> for package
>> > > > > >> > vdsm-
>> > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing
>> provides
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> nmstate
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> > needed by
>> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> > > > > >> > Problem 2:
>> > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch
>> requires
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> vdsm-network
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the
>> providers can be
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> installed\n
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> > - cannot install the best update candidate for package
>> vdsm-
>> > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing
>> provides
>> > > > > >> > nmstate
>> > > > > >> > needed by
>> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> nmstate should be provided by copr repo enabled by
>> > > > > >> ovirt-release-master.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > I re-triggered as
>> > > > > >
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>> > > > > > maybe
>> > > > > > https://gerrit.ovirt.org/#/c/104825/
>> > > > > > was missing
>> > > > >
>> > > > >
>> > > > >
>> > > > > Looks like
>> > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
>> > > >
>> > > >
>> > > >
>> > > > maybe not. You re-triggered with [1], which really missed this
>> patch.
>> > > > I did a rebase and now running with this patch in build #6132
>> [2]. Let's
>> > > > wait
>> >  for it to see if gerrit #104825 helps.
>> > > >
>> > > >
>> > > >
>> > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
>> > > > [2]
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
>> > > >
>> > > >
>> > > >
>> > > > > Miguel, do you think merging
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
>> > > > > t-cq
>> >  .repo.in
>> > > > >
>> > > > >
>> > > > >
>> > > > > would solve this?
>> > >
>> > >
>> > > I've split the patch Dominik mentions above in two, one of them
>> adding
>> > > the nmstate / networkmanager copr repos - [3].
>> > >
>> > > Let's see if it fixes it.
>> >
>> > it fixes original issue, but OST still fails in
>> > 098_ovirt_provider_ovn.use_ovn_provider:
>> >
>> > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134
>>
>> I think Dominik was looking into this issue; +Dominik Holler please
>> confirm.
>>
>> Let

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Fri, Nov 22, 2019 at 5:48 PM Nir Soffer  wrote:

>
>
> On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  wrote:
>
>>
>>
>> On 11/22/19 4:54 PM, Martin Perina wrote:
>>
>>
>>
>> On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler 
>> wrote:
>>
>>>
>>> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
>>> wrote:
>>>


 On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
 mdbarr...@redhat.com> wrote:

> On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
> wrote:
> >
> > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora
> Barroso wrote:
> > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
> vjura...@redhat.com>
> > > wrote:
> > > >
> > > >
> > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
> > > >
> > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
> dhol...@redhat.com>
> > > > > wrote:
> > > > >
> > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
> nsof...@redhat.com>
> > > > > > wrote:
> > > > > >
> > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
> > > > > >> 
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hi,
> > > > > >> > OST fails (see e.g. [1]) in
> 002_bootstrap.check_update_host. It
> > > > > >> > fails
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> with
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg":
> "Depsolve
> > > > > >> >  Error
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> occured:
> > > > > >>
> > > > > >> > \n Problem 1: cannot install the best update candidate
> for package
> > > > > >> > vdsm-
> > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing
> provides
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> nmstate
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > > >> > Problem 2:
> > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch
> requires
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> vdsm-network
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers
> can be
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> installed\n
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> > - cannot install the best update candidate for package
> vdsm-
> > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing
> provides
> > > > > >> > nmstate
> > > > > >> > needed by
> vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> nmstate should be provided by copr repo enabled by
> > > > > >> ovirt-release-master.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I re-triggered as
> > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> > > > > > maybe
> > > > > > https://gerrit.ovirt.org/#/c/104825/
> > > > > > was missing
> > > > >
> > > > >
> > > > >
> > > > > Looks like
> > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
> > > >
> > > >
> > > >
> > > > maybe not. You re-triggered with [1], which really missed this
> patch.
> > > > I did a rebase and now running with this patch in build #6132
> [2]. Let's
> > > > wait
> >  for it to see if gerrit #104825 helps.
> > > >
> > > >
> > > >
> > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
> > > > [2]
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
> > > >
> > > >
> > > >
> > > > > Miguel, do you think merging
> > > > >
> > > > >
> > > > >
> > > > >
> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
> > > > > t-cq
> >  .repo.in
> > > > >
> > > > >
> > > > >
> > > > > would solve this?
> > >
> > >
> > > I've split the patch Dominik mentions above in two, one of them
> adding
> > > the nmstate / networkmanager copr repos - [3].
> > >
> > > Let's see if it fixes it.
> >
> > it fixes original issue, but OST still fails in
> > 098_ovirt_provider_ovn.use_ovn_provider:
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134
>
> I think Dominik was looking into this issue; +Dominik Holler please
> confirm.
>
> Let me know if you need any help Dominik.
>


 Thanks.
 The problem is that the hosts lost connection to storage:

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-22 Thread Nir Soffer

On Fri, Nov 22, 2019, 18:18 Marcin Sobczyk  wrote:

>
>
> On 11/22/19 4:54 PM, Martin Perina wrote:
>
>
>
> On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler  wrote:
>
>>
>> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
>> wrote:
>>
>>>
>>>
>>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
>>> mdbarr...@redhat.com> wrote:
>>>
 On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
 wrote:
 >
 > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora Barroso
 wrote:
 > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek <
 vjura...@redhat.com>
 > > wrote:
 > > >
 > > >
 > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
 > > >
 > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
 dhol...@redhat.com>
 > > > > wrote:
 > > > >
 > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
 nsof...@redhat.com>
 > > > > > wrote:
 > > > > >
 > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
 > > > > >> 
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> wrote:
 > > > > >>
 > > > > >> > Hi,
 > > > > >> > OST fails (see e.g. [1]) in
 002_bootstrap.check_update_host. It
 > > > > >> > fails
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> with
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg":
 "Depsolve
 > > > > >> >  Error
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> occured:
 > > > > >>
 > > > > >> > \n Problem 1: cannot install the best update candidate for
 package
 > > > > >> > vdsm-
 > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing
 provides
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> nmstate
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> > needed by
 vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
 > > > > >> > Problem 2:
 > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch
 requires
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> vdsm-network
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers
 can be
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> installed\n
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> > - cannot install the best update candidate for package
 vdsm-
 > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing
 provides
 > > > > >> > nmstate
 > > > > >> > needed by
 vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
 > > > > >>
 > > > > >>
 > > > > >>
 > > > > >> nmstate should be provided by copr repo enabled by
 > > > > >> ovirt-release-master.
 > > > > >
 > > > > >
 > > > > >
 > > > > > I re-triggered as
 > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
 > > > > > maybe
 > > > > > https://gerrit.ovirt.org/#/c/104825/
 > > > > > was missing
 > > > >
 > > > >
 > > > >
 > > > > Looks like
 > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
 > > >
 > > >
 > > >
 > > > maybe not. You re-triggered with [1], which really missed this
 patch.
 > > > I did a rebase and now running with this patch in build #6132
 [2]. Let's
 > > > wait
 >  for it to see if gerrit #104825 helps.
 > > >
 > > >
 > > >
 > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
 > > > [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
 > > >
 > > >
 > > >
 > > > > Miguel, do you think merging
 > > > >
 > > > >
 > > > >
 > > > >
 https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
 > > > > t-cq
 >  .repo.in
 > > > >
 > > > >
 > > > >
 > > > > would solve this?
 > >
 > >
 > > I've split the patch Dominik mentions above in two, one of them
 adding
 > > the nmstate / networkmanager copr repos - [3].
 > >
 > > Let's see if it fixes it.
 >
 > it fixes original issue, but OST still fails in
 > 098_ovirt_provider_ovn.use_ovn_provider:
 >
 > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134

 I think Dominik was looking into this issue; +Dominik Holler please
 confirm.

 Let me know if you need any help Dominik.

>>>
>>>
>>> Thanks.
>>> The problem is that the hosts lost connection to storage:
>>>
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134/artifact/exported-artifacts/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/lago-basic-suite-master-host-0/_var_log/vdsm/vdsm.log
>>> :
>>>
>>> 2019-11-22 05:39:12,326-0500 DEBUG (jsonrpc/5) [common.commands] 
>>> /usr/bin/taskset --cpu-list 0-1 /usr/bin/sudo -n /sbin/lvm

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-22 Thread Marcin Sobczyk




On 11/22/19 4:54 PM, Martin Perina wrote:



On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler > wrote:



On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler
mailto:dhol...@redhat.com>> wrote:



On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso
mailto:mdbarr...@redhat.com>> wrote:

On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek
mailto:vjura...@redhat.com>> wrote:
>
> On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de
Mora Barroso wrote:
> > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek
mailto:vjura...@redhat.com>>
> > wrote:
> > >
> > >
> > > On pátek 22. listopadu 2019 9:41:26 CET Dominik
Holler wrote:
> > >
> > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler
mailto:dhol...@redhat.com>>
> > > > wrote:
> > > >
> > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer
mailto:nsof...@redhat.com>>
> > > > > wrote:
> > > > >
> > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
> > > > >> mailto:vjura...@redhat.com>>
> > > > >>
> > > > >>
> > > > >>
> > > > >> wrote:
> > > > >>
> > > > >> > Hi,
> > > > >> > OST fails (see e.g. [1]) in
002_bootstrap.check_update_host. It
> > > > >> > fails
> > > > >>
> > > > >>
> > > > >>
> > > > >> with
> > > > >>
> > > > >>
> > > > >>
> > > > >> >  FAILED! => {"changed": false, "failures":
[], "msg": "Depsolve
> > > > >> >  Error
> > > > >>
> > > > >>
> > > > >>
> > > > >> occured:
> > > > >>
> > > > >> > \n Problem 1: cannot install the best update
candidate for package
> > > > >> > vdsm-
> > > > >> >
network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing
provides
> > > > >>
> > > > >>
> > > > >>
> > > > >> nmstate
> > > > >>
> > > > >>
> > > > >>
> > > > >> > needed by
vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > >> > Problem 2:
> > > > >> > package
vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
> > > > >>
> > > > >>
> > > > >>
> > > > >> vdsm-network
> > > > >>
> > > > >>
> > > > >>
> > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of
the providers can be
> > > > >>
> > > > >>
> > > > >>
> > > > >> installed\n
> > > > >>
> > > > >>
> > > > >>
> > > > >> > - cannot install the best update candidate
for package vdsm-
> > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n 
- nothing provides
> > > > >> > nmstate
> > > > >> > needed by
vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > >>
> > > > >>
> > > > >>
> > > > >> nmstate should be provided by copr repo enabled by
> > > > >> ovirt-release-master.
> > > > >
> > > > >
> > > > >
> > > > > I re-triggered as
> > > > >
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> > > > > maybe
> > > > > https://gerrit.ovirt.org/#/c/104825/
> > > > > was missing
> > > >
> > > >
> > > >
> > > > Looks like
> > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by
OST.
> > >
> > >
> > >
> > > maybe not. You re-triggered with [1], which really
missed this patch.
> > > I did a rebase and now running with this patch in
build #6132 [2]. Let's
> > > wait
>  for it to see if gerrit #104825 helps.
> > >
> > >
> > >
> > > [1]
https://jenkins.ovirt.org/job/standard-manual-runner/909/
> > > [2]
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
> > >
> > >
> > >
> > > > Miguel, do you think merging
> > > >
> > > >
> > > >
> > > >

https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
> > > > t-cq
>

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-22 Thread Martin Perina

On Fri, Nov 22, 2019 at 4:43 PM Dominik Holler  wrote:

>
> On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler 
> wrote:
>
>>
>>
>> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
>> mdbarr...@redhat.com> wrote:
>>
>>> On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
>>> wrote:
>>> >
>>> > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora Barroso
>>> wrote:
>>> > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek >> >
>>> > > wrote:
>>> > > >
>>> > > >
>>> > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
>>> > > >
>>> > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
>>> dhol...@redhat.com>
>>> > > > > wrote:
>>> > > > >
>>> > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer <
>>> nsof...@redhat.com>
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>>> > > > > >> 
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> wrote:
>>> > > > > >>
>>> > > > > >> > Hi,
>>> > > > > >> > OST fails (see e.g. [1]) in
>>> 002_bootstrap.check_update_host. It
>>> > > > > >> > fails
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> with
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg":
>>> "Depsolve
>>> > > > > >> >  Error
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> occured:
>>> > > > > >>
>>> > > > > >> > \n Problem 1: cannot install the best update candidate for
>>> package
>>> > > > > >> > vdsm-
>>> > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing
>>> provides
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> nmstate
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>>> > > > > >> > Problem 2:
>>> > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch
>>> requires
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> vdsm-network
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers
>>> can be
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> installed\n
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> > - cannot install the best update candidate for package vdsm-
>>> > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing
>>> provides
>>> > > > > >> > nmstate
>>> > > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>>> > > > > >>
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> nmstate should be provided by copr repo enabled by
>>> > > > > >> ovirt-release-master.
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > I re-triggered as
>>> > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>>> > > > > > maybe
>>> > > > > > https://gerrit.ovirt.org/#/c/104825/
>>> > > > > > was missing
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > Looks like
>>> > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
>>> > > >
>>> > > >
>>> > > >
>>> > > > maybe not. You re-triggered with [1], which really missed this
>>> patch.
>>> > > > I did a rebase and now running with this patch in build #6132 [2].
>>> Let's
>>> > > > wait
>>> >  for it to see if gerrit #104825 helps.
>>> > > >
>>> > > >
>>> > > >
>>> > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
>>> > > > [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
>>> > > >
>>> > > >
>>> > > >
>>> > > > > Miguel, do you think merging
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > >
>>> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
>>> > > > > t-cq
>>> >  .repo.in
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > would solve this?
>>> > >
>>> > >
>>> > > I've split the patch Dominik mentions above in two, one of them
>>> adding
>>> > > the nmstate / networkmanager copr repos - [3].
>>> > >
>>> > > Let's see if it fixes it.
>>> >
>>> > it fixes original issue, but OST still fails in
>>> > 098_ovirt_provider_ovn.use_ovn_provider:
>>> >
>>> > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134
>>>
>>> I think Dominik was looking into this issue; +Dominik Holler please
>>> confirm.
>>>
>>> Let me know if you need any help Dominik.
>>>
>>
>>
>> Thanks.
>> The problem is that the hosts lost connection to storage:
>>
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134/artifact/exported-artifacts/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/lago-basic-suite-master-host-0/_var_log/vdsm/vdsm.log
>> :
>>
>> 2019-11-22 05:39:12,326-0500 DEBUG (jsonrpc/5) [common.commands] 
>> /usr/bin/taskset --cpu-list 0-1 /usr/bin/sudo -n /sbin/lvm vgs --config 
>> 'devices {  preferred_names=["^/dev/mapper/"]  ignore_suspended_devices=1  
>> write_cache_state=0  disable_after_error_count=3  
>>

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Fri, Nov 22, 2019 at 12:17 PM Dominik Holler  wrote:

>
>
> On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
> mdbarr...@redhat.com> wrote:
>
>> On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
>> wrote:
>> >
>> > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora Barroso
>> wrote:
>> > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek 
>> > > wrote:
>> > > >
>> > > >
>> > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
>> > > >
>> > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler <
>> dhol...@redhat.com>
>> > > > > wrote:
>> > > > >
>> > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer > >
>> > > > > > wrote:
>> > > > > >
>> > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
>> > > > > >> 
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >> > Hi,
>> > > > > >> > OST fails (see e.g. [1]) in 002_bootstrap.check_update_host.
>> It
>> > > > > >> > fails
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> with
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg":
>> "Depsolve
>> > > > > >> >  Error
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> occured:
>> > > > > >>
>> > > > > >> > \n Problem 1: cannot install the best update candidate for
>> package
>> > > > > >> > vdsm-
>> > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing
>> provides
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> nmstate
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> > > > > >> > Problem 2:
>> > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch
>> requires
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> vdsm-network
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers
>> can be
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> installed\n
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> > - cannot install the best update candidate for package vdsm-
>> > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing
>> provides
>> > > > > >> > nmstate
>> > > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> nmstate should be provided by copr repo enabled by
>> > > > > >> ovirt-release-master.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > I re-triggered as
>> > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>> > > > > > maybe
>> > > > > > https://gerrit.ovirt.org/#/c/104825/
>> > > > > > was missing
>> > > > >
>> > > > >
>> > > > >
>> > > > > Looks like
>> > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
>> > > >
>> > > >
>> > > >
>> > > > maybe not. You re-triggered with [1], which really missed this
>> patch.
>> > > > I did a rebase and now running with this patch in build #6132 [2].
>> Let's
>> > > > wait
>> >  for it to see if gerrit #104825 helps.
>> > > >
>> > > >
>> > > >
>> > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
>> > > > [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
>> > > >
>> > > >
>> > > >
>> > > > > Miguel, do you think merging
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
>> > > > > t-cq
>> >  .repo.in
>> > > > >
>> > > > >
>> > > > >
>> > > > > would solve this?
>> > >
>> > >
>> > > I've split the patch Dominik mentions above in two, one of them adding
>> > > the nmstate / networkmanager copr repos - [3].
>> > >
>> > > Let's see if it fixes it.
>> >
>> > it fixes original issue, but OST still fails in
>> > 098_ovirt_provider_ovn.use_ovn_provider:
>> >
>> > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134
>>
>> I think Dominik was looking into this issue; +Dominik Holler please
>> confirm.
>>
>> Let me know if you need any help Dominik.
>>
>
>
> Thanks.
> The problem is that the hosts lost connection to storage:
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134/artifact/exported-artifacts/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/lago-basic-suite-master-host-0/_var_log/vdsm/vdsm.log
> :
>
> 2019-11-22 05:39:12,326-0500 DEBUG (jsonrpc/5) [common.commands] 
> /usr/bin/taskset --cpu-list 0-1 /usr/bin/sudo -n /sbin/lvm vgs --config 
> 'devices {  preferred_names=["^/dev/mapper/"]  ignore_suspended_devices=1  
> write_cache_state=0  disable_after_error_count=3  
> filter=["a|^/dev/mapper/36001405107ea8b4e3ac4ddeb3e19890f$|^/dev/mapper/360014054924c91df75e41178e4b8a80c$|^/dev/mapper/3600140561c0d02829924b77ab7323f17$|^/dev/mapper/3600140582feebc04ca5409a99660dbbc$|^/dev/mapper/36001405c3c53755c13c474dada6be354$|",
>  "r|.*|"] } global {  locking_type=1  prioritise_write_locks=1  
> wait_for_locks=1  use_lvmetad=0 } backup {  retain_min=50  retain_days=0 }' 
> --noheadings

[ovirt-devel] Re: OST fails, nothing provides nmstate

On Fri, Nov 22, 2019 at 12:00 PM Miguel Duarte de Mora Barroso <
mdbarr...@redhat.com> wrote:

> On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek 
> wrote:
> >
> > On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora Barroso
> wrote:
> > > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek 
> > > wrote:
> > > >
> > > >
> > > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
> > > >
> > > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler  >
> > > > > wrote:
> > > > >
> > > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer 
> > > > > > wrote:
> > > > > >
> > > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
> > > > > >> 
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hi,
> > > > > >> > OST fails (see e.g. [1]) in 002_bootstrap.check_update_host.
> It
> > > > > >> > fails
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> with
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> >  FAILED! => {"changed": false, "failures": [], "msg":
> "Depsolve
> > > > > >> >  Error
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> occured:
> > > > > >>
> > > > > >> > \n Problem 1: cannot install the best update candidate for
> package
> > > > > >> > vdsm-
> > > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing
> provides
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> nmstate
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > > >> > Problem 2:
> > > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch
> requires
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> vdsm-network
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers can
> be
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> installed\n
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> > - cannot install the best update candidate for package vdsm-
> > > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing
> provides
> > > > > >> > nmstate
> > > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> nmstate should be provided by copr repo enabled by
> > > > > >> ovirt-release-master.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I re-triggered as
> > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> > > > > > maybe
> > > > > > https://gerrit.ovirt.org/#/c/104825/
> > > > > > was missing
> > > > >
> > > > >
> > > > >
> > > > > Looks like
> > > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
> > > >
> > > >
> > > >
> > > > maybe not. You re-triggered with [1], which really missed this patch.
> > > > I did a rebase and now running with this patch in build #6132 [2].
> Let's
> > > > wait
> >  for it to see if gerrit #104825 helps.
> > > >
> > > >
> > > >
> > > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
> > > > [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
> > > >
> > > >
> > > >
> > > > > Miguel, do you think merging
> > > > >
> > > > >
> > > > >
> > > > >
> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
> > > > > t-cq
> >  .repo.in
> > > > >
> > > > >
> > > > >
> > > > > would solve this?
> > >
> > >
> > > I've split the patch Dominik mentions above in two, one of them adding
> > > the nmstate / networkmanager copr repos - [3].
> > >
> > > Let's see if it fixes it.
> >
> > it fixes original issue, but OST still fails in
> > 098_ovirt_provider_ovn.use_ovn_provider:
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134
>
> I think Dominik was looking into this issue; +Dominik Holler please
> confirm.
>
> Let me know if you need any help Dominik.
>


Thanks.
The problem is that the hosts lost connection to storage:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134/artifact/exported-artifacts/test_logs/basic-suite-master/post-098_ovirt_provider_ovn.py/lago-basic-suite-master-host-0/_var_log/vdsm/vdsm.log
:

2019-11-22 05:39:12,326-0500 DEBUG (jsonrpc/5) [common.commands]
/usr/bin/taskset --cpu-list 0-1 /usr/bin/sudo -n /sbin/lvm vgs
--config 'devices {  preferred_names=["^/dev/mapper/"]
ignore_suspended_devices=1  write_cache_state=0
disable_after_error_count=3
filter=["a|^/dev/mapper/36001405107ea8b4e3ac4ddeb3e19890f$|^/dev/mapper/360014054924c91df75e41178e4b8a80c$|^/dev/mapper/3600140561c0d02829924b77ab7323f17$|^/dev/mapper/3600140582feebc04ca5409a99660dbbc$|^/dev/mapper/36001405c3c53755c13c474dada6be354$|",
"r|.*|"] } global {  locking_type=1  prioritise_write_locks=1
wait_for_locks=1  use_lvmetad=0 } backup {  retain_min=50
retain_days=0 }' --noheadings --units b --nosuffix --separator '|'
--ignoreskippedcluster -o
uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name
(cwd None) (commands:153)
2019-11-22 05:39:12,415-0500 ERROR (check/loop) [storage.Monitor]
Error

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-22 Thread Miguel Duarte de Mora Barroso

On Fri, Nov 22, 2019 at 11:54 AM Vojtech Juranek  wrote:
>
> On pátek 22. listopadu 2019 9:56:56 CET Miguel Duarte de Mora Barroso wrote:
> > On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek 
> > wrote:
> > >
> > >
> > > On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
> > >
> > > > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler 
> > > > wrote:
> > > >
> > > > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer 
> > > > > wrote:
> > > > >
> > > > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek
> > > > >> 
> > > > >>
> > > > >>
> > > > >>
> > > > >> wrote:
> > > > >>
> > > > >> > Hi,
> > > > >> > OST fails (see e.g. [1]) in 002_bootstrap.check_update_host. It
> > > > >> > fails
> > > > >>
> > > > >>
> > > > >>
> > > > >> with
> > > > >>
> > > > >>
> > > > >>
> > > > >> >  FAILED! => {"changed": false, "failures": [], "msg": "Depsolve
> > > > >> >  Error
> > > > >>
> > > > >>
> > > > >>
> > > > >> occured:
> > > > >>
> > > > >> > \n Problem 1: cannot install the best update candidate for package
> > > > >> > vdsm-
> > > > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing provides
> > > > >>
> > > > >>
> > > > >>
> > > > >> nmstate
> > > > >>
> > > > >>
> > > > >>
> > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > >> > Problem 2:
> > > > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
> > > > >>
> > > > >>
> > > > >>
> > > > >> vdsm-network
> > > > >>
> > > > >>
> > > > >>
> > > > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers can be
> > > > >>
> > > > >>
> > > > >>
> > > > >> installed\n
> > > > >>
> > > > >>
> > > > >>
> > > > >> > - cannot install the best update candidate for package vdsm-
> > > > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing provides
> > > > >> > nmstate
> > > > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > > > >>
> > > > >>
> > > > >>
> > > > >> nmstate should be provided by copr repo enabled by
> > > > >> ovirt-release-master.
> > > > >
> > > > >
> > > > >
> > > > > I re-triggered as
> > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> > > > > maybe
> > > > > https://gerrit.ovirt.org/#/c/104825/
> > > > > was missing
> > > >
> > > >
> > > >
> > > > Looks like
> > > > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
> > >
> > >
> > >
> > > maybe not. You re-triggered with [1], which really missed this patch.
> > > I did a rebase and now running with this patch in build #6132 [2]. Let's
> > > wait
>  for it to see if gerrit #104825 helps.
> > >
> > >
> > >
> > > [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
> > > [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
> > >
> > >
> > >
> > > > Miguel, do you think merging
> > > >
> > > >
> > > >
> > > > https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-hos
> > > > t-cq
>  .repo.in
> > > >
> > > >
> > > >
> > > > would solve this?
> >
> >
> > I've split the patch Dominik mentions above in two, one of them adding
> > the nmstate / networkmanager copr repos - [3].
> >
> > Let's see if it fixes it.
>
> it fixes original issue, but OST still fails in
> 098_ovirt_provider_ovn.use_ovn_provider:
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6134

I think Dominik was looking into this issue; +Dominik Holler please confirm.

Let me know if you need any help Dominik.
>
> > [3] - https://gerrit.ovirt.org/#/c/104897/
> >
> >
> > > >
> > > >
> > > > >> Who installs this rpm in OST?
> > > > >
> > > > >
> > > > >
> > > > > I do not understand the question.
> > > > >
> > > > >
> > > > >
> > > > >> > [...]
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > See [2] for full error.
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > Can someone please take a look?
> > > > >> > Thanks
> > > > >> > Vojta
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/
> > > > >> > [2]
> > > > >>
> > > > >>
> > > > >>
> > > > >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/artifact
> > > > >> /
> > > > >>
> > > > >>
> > > > >>
> > > > >> > exported-artifacts/test_logs/basic-suite-master/
> > > > >>
> > > > >>
> > > > >>
> > > > >> post-002_bootstrap.py/lago-
> > > > >>
> > > > >>
> > > > >>
> > > > >> basic-suite-master-engine/_var_log/ovirt-engine/engine.log___
> > > > >> 
> > > > >> >>
> > > > >>
> > > > >> > Devel mailing list -- devel@ovirt.org
> > > > >> > To unsubscribe send an email to devel-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/devel@ovirt.org/message/4K5N3VQ
> > > > >> N26B
> > > > >> L73K7D45A2IR7R3UMMM23/

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-22 Thread Miguel Duarte de Mora Barroso

On Fri, Nov 22, 2019 at 9:49 AM Vojtech Juranek  wrote:
>
> On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
> > On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler  wrote:
> > > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer  wrote:
> > >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek 
> > >>
> > >> wrote:
> > >> > Hi,
> > >> > OST fails (see e.g. [1]) in 002_bootstrap.check_update_host. It fails
> > >>
> > >> with
> > >>
> > >> >  FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error
> > >>
> > >> occured:
> > >> > \n Problem 1: cannot install the best update candidate for package
> > >> > vdsm-
> > >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing provides
> > >>
> > >> nmstate
> > >>
> > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n Problem 2:
> > >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
> > >>
> > >> vdsm-network
> > >>
> > >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers can be
> > >>
> > >> installed\n
> > >>
> > >> > - cannot install the best update candidate for package vdsm-
> > >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing provides
> > >> > nmstate
> > >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> > >>
> > >> nmstate should be provided by copr repo enabled by ovirt-release-master.
> > >
> > > I re-triggered as
> > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> > > maybe
> > > https://gerrit.ovirt.org/#/c/104825/
> > > was missing
> >
> > Looks like
> > https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.
>
> maybe not. You re-triggered with [1], which really missed this patch.
> I did a rebase and now running with this patch in build #6132 [2]. Let's wait
> for it to see if gerrit #104825 helps.
>
> [1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
> [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/
>
> > Miguel, do you think merging
> >
> > https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-host-cq
> > .repo.in
> >
> > would solve this?

I've split the patch Dominik mentions above in two, one of them adding
the nmstate / networkmanager copr repos - [3].

Let's see if it fixes it.

[3] - https://gerrit.ovirt.org/#/c/104897/

> >
> > >> Who installs this rpm in OST?
> > >
> > > I do not understand the question.
> > >
> > >> > [...]
> > >> >
> > >> > See [2] for full error.
> > >> >
> > >> > Can someone please take a look?
> > >> > Thanks
> > >> > Vojta
> > >> >
> > >> > [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/
> > >> > [2]
> > >>
> > >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/artifact/
> > >>
> > >> > exported-artifacts/test_logs/basic-suite-master/
> > >>
> > >> post-002_bootstrap.py/lago-
> > >>
> > >> basic-suite-master-engine/_var_log/ovirt-engine/engine.log___
> > >> >>
> > >> > Devel mailing list -- devel@ovirt.org
> > >> > To unsubscribe send an email to devel-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/devel@ovirt.org/message/4K5N3VQN26B
> > >> L73K7D45A2IR7R3UMMM23/ ___
> > >> Devel mailing list -- devel@ovirt.org
> > >> To unsubscribe send an email to devel-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/devel@ovirt.org/message/JN7MNUZN5K3
> > >> NS5TGXFCILYES77KI5TZU/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/UPJ5SEAV5Z65H5BQ3SCHOYZX6JMTQPBW/

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-22 Thread Vojtech Juranek

On pátek 22. listopadu 2019 9:41:26 CET Dominik Holler wrote:
> On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler  wrote:
> > On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer  wrote:
> >> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek 
> >> 
> >> wrote:
> >> > Hi,
> >> > OST fails (see e.g. [1]) in 002_bootstrap.check_update_host. It fails
> >> 
> >> with
> >> 
> >> >  FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error
> >> 
> >> occured:
> >> > \n Problem 1: cannot install the best update candidate for package
> >> > vdsm-
> >> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing provides
> >> 
> >> nmstate
> >> 
> >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n Problem 2:
> >> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires
> >> 
> >> vdsm-network
> >> 
> >> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers can be
> >> 
> >> installed\n
> >> 
> >> > - cannot install the best update candidate for package vdsm-
> >> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing provides
> >> > nmstate
> >> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
> >> 
> >> nmstate should be provided by copr repo enabled by ovirt-release-master.
> > 
> > I re-triggered as
> > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
> > maybe
> > https://gerrit.ovirt.org/#/c/104825/
> > was missing
> 
> Looks like
> https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.

maybe not. You re-triggered with [1], which really missed this patch.
I did a rebase and now running with this patch in build #6132 [2]. Let's wait 
for it to see if gerrit #104825 helps.

[1] https://jenkins.ovirt.org/job/standard-manual-runner/909/
[2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6132/

> Miguel, do you think merging
> 
> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-host-cq
> .repo.in
> 
> would solve this?
> 
> >> Who installs this rpm in OST?
> > 
> > I do not understand the question.
> > 
> >> > [...]
> >> > 
> >> > See [2] for full error.
> >> > 
> >> > Can someone please take a look?
> >> > Thanks
> >> > Vojta
> >> > 
> >> > [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/
> >> > [2]
> >> 
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/artifact/
> >> 
> >> > exported-artifacts/test_logs/basic-suite-master/
> >> 
> >> post-002_bootstrap.py/lago-
> >> 
> >> basic-suite-master-engine/_var_log/ovirt-engine/engine.log___
> >> >> 
> >> > Devel mailing list -- devel@ovirt.org
> >> > To unsubscribe send an email to devel-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/devel@ovirt.org/message/4K5N3VQN26B
> >> L73K7D45A2IR7R3UMMM23/ ___
> >> Devel mailing list -- devel@ovirt.org
> >> To unsubscribe send an email to devel-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/devel@ovirt.org/message/JN7MNUZN5K3
> >> NS5TGXFCILYES77KI5TZU/



signature.asc
Description: This is a digitally signed message part.
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/EO5N4T5JPIPXBMHUBDL7XU3QCYV3BH2U/

[ovirt-devel] Re: OST fails, nothing provides nmstate

2019-11-22 Thread Miguel Duarte de Mora Barroso

On Fri, Nov 22, 2019 at 9:41 AM Dominik Holler  wrote:
>
>
>
> On Fri, Nov 22, 2019 at 8:40 AM Dominik Holler  wrote:
>>
>>
>>
>> On Thu, Nov 21, 2019 at 10:54 PM Nir Soffer  wrote:
>>>
>>> On Thu, Nov 21, 2019 at 11:24 PM Vojtech Juranek  
>>> wrote:
>>> >
>>> > Hi,
>>> > OST fails (see e.g. [1]) in 002_bootstrap.check_update_host. It fails with
>>> >
>>> >  FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error 
>>> > occured:
>>> > \n Problem 1: cannot install the best update candidate for package vdsm-
>>> > network-4.40.0-1236.git63ea8cb8b.el8.x86_64\n  - nothing provides nmstate
>>> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n Problem 2:
>>> > package vdsm-python-4.40.0-1271.git524e08c8a.el8.noarch requires 
>>> > vdsm-network
>>> > = 4.40.0-1271.git524e08c8a.el8, but none of the providers can be 
>>> > installed\n
>>> > - cannot install the best update candidate for package vdsm-
>>> > python-4.40.0-1236.git63ea8cb8b.el8.noarch\n  - nothing provides nmstate
>>> > needed by vdsm-network-4.40.0-1271.git524e08c8a.el8.x86_64\n
>>>
>>> nmstate should be provided by copr repo enabled by ovirt-release-master.
>>
>>
>>
>> I re-triggered as
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6131
>> maybe
>> https://gerrit.ovirt.org/#/c/104825/
>> was missing
>>
>
> Looks like
> https://gerrit.ovirt.org/#/c/104825/ is ignored by OST.

Right.

>
> Miguel, do you think merging
>
> https://gerrit.ovirt.org/#/c/104495/15/common/yum-repos/ovirt-master-host-cq.repo.in

It should.

I'll break down patch patch into smaller pieces - one adding the
nmstate / NM copr repos, another w/ enabling nmstate.

>
> would solve this?
>
>>
>>
>>>
>>> Who installs this rpm in OST?
>>>
>>
>> I do not understand the question.
>>
>>>
>>> > [...]
>>> >
>>> > See [2] for full error.
>>> >
>>> > Can someone please take a look?
>>> > Thanks
>>> > Vojta
>>> >
>>> > [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/
>>> > [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6128/artifact/
>>> > exported-artifacts/test_logs/basic-suite-master/post-002_bootstrap.py/lago-
>>> > basic-suite-master-engine/_var_log/ovirt-engine/engine.log___
>>> > Devel mailing list -- devel@ovirt.org
>>> > To unsubscribe send an email to devel-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/devel@ovirt.org/message/4K5N3VQN26BL73K7D45A2IR7R3UMMM23/
>>> ___
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-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/devel@ovirt.org/message/JN7MNUZN5K3NS5TGXFCILYES77KI5TZU/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-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/devel@ovirt.org/message/JEUPQR4EC2SBHIQ5FNX2U44N6AERRWD5/

[ovirt-devel] Re: OST fails, nothing provides nmstate