[ovirt-devel] vdsm network tests fail on centos 9

[Vojtech Juranek]

Hi Ales,
vdsm network tests started to fail on centos 9 with 

Error: executable file `/usr/sbin/init` not found in $PATH

see [1]. Any idea what's wrong? Could be related to recent container changes 
[2]? (however, CI has passed for this change, so probably not?)

Thanks
Vojta

[1] https://github.com/oVirt/vdsm/runs/5038009780?check_suite_focus=true
[2] https://github.com/oVirt/vdsm/commit/
dc15a96500b3add9d330b1fd3c36a451c79102fc

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/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/PYON2T2OSAJXMPR3UMHX6EKFGL4NEGFT/

[ovirt-devel] OST failing

[Vojtech Juranek]

Hi,
OST is constantly failing today in test_verify_add_hosts with 

19:34:33 E assert find_up_host() - False != True after 1800 seconds
19:34:33 E + where find_up_host() - False != True after 1800 seconds = 
function true_within at 0x7fa62ac860d0(function 
test_verify_add_hosts.locals.find_up_host at 0x7fa628f97940, 
timeout=1800)
19:34:33 E + where function true_within at 0x7fa62ac860d0 = 
assert_utils.true_within
19:34:33 E + and 1800 = constants.ADD_HOST_TIMEOUT

See e.g.  https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/23661

Any idea what's wrong?
Thanks
Vojta

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/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/ZWYQGIIPXRJGX4YD5UJTIC43KGIZ6RX7/

[ovirt-devel] Re: Vdsm: Failing storage test

[Vojtech Juranek]

> I missed this error in the morning as there is another failure (CodeQL
> fails) and the tests didn't run after the merge.

Checking it again, this is actually not true, tests run in another action and 
they were run.
I didn't noticed if probably as everything was read and I didn't noticed each 
commit if failed twice.

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/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/FAXIV2DNTT2FSTAE7VMOR5TIHEXKCYJO/

[ovirt-devel] Re: Vdsm: Failing storage test

[Vojtech Juranek]

On Thursday, 16 December 2021 14:11:34 CET Nir Soffer wrote:
> On Thu, Dec 16, 2021 at 1:36 PM Milan Zamazal  wrote:
> > Hi,
> > 
> > it seems a recent commit causes a storage test failure on GitHub:
> >   == FAILURES
> >   === 
> >   test_prepare_connection_without_initiator_name >   
> >   def test_prepare_connection_without_initiator_name():
> >   con_def = [{
> >   
> >   "password": "password",
> >   "port": "3260",
> >   "iqn": "iqn.2016-01.com.ovirt:444",
> >   "connection": "192.168.1.2",
> >   "ipv6_enabled": "false",
> >   "id": "994a711a-60f3-411a-aca2-0b60f01e8b8c",
> >   "user": "",
> >   "tpgt": "1",
> >   
> >   }]
> >   
> >   >   conn = storageServer._prepare_connections(sd.ISCSI_DOMAIN,
> >   >   con_def)
> >   
> >   E   AttributeError: module 'vdsm.storage.storageServer' has no
> >   attribute '_prepare_connections'> 
> > Could you please fix it quickly or disable the test?
> > 
> > @all: Beware that CI on Vdsm no longer runs the tests and patches must
> > be tested on GitHub before merging.
> 
> Thanks for reporting, fixed in
> https://gerrit.ovirt.org/c/vdsm/+/118071

Fix is now merged in the master. Sorry for that and thanks Nir for the fix.
I missed this error in the morning as there is another failure (CodeQL fails) 
and the tests didn't run after the merge.

Vojta

> I guess this is a side effect of testing only the top patch in github.
> It is much faster but misses inconsistencies in the series.
> 
> Once we move to github this should not happen since in github
> you cannot merge a partial PR. It can still happen if we checkout
> random patch from a PR that was never tested alone, but this is
> not very interesting.
> 
> Nir



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/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/3SBPWBNLCRPZX3C2SKRI2A5LYTBLNA6Y/

[ovirt-devel] Re: CI not working again

[Vojtech Juranek]

On Tuesday, 14 December 2021 09:44:44 CET Nir Soffer wrote:
> On Tue, Dec 14, 2021 at 10:14 AM Milan Zamazal  wrote:
> >
> >
> > Nir Soffer  writes:
> >
> >
> >
> > > I'm using github CI now, no issue seen in the last week.
> > >
> > >
> > >
> > > But we have now a wrose issue, build-artifacts job fail randomly in one
> > > of
> > > the targets. This means there is no way to use the automatic OST run.
> > >
> > >
> > >
> > > Should we disable all vdsm tests on gerrit, and enable only x64_64 el8
> > > build artifacts so we can at least get working OST?
> >
> >
> >
> > Since tests on gerrit are unusable, we should do it this way, good idea.
> >
> >
> >
> > Nevertheless manually testing patches by pushing them to GitHub is
> > tiresome,
> 
> 
> This is not that bad, I'm using this flow for a few years:
> 
> while work needed:
> hack...
> push -f github # push to my github fork
> check the build in github
> 
> git review  # push to gerrit for review

which is basically the same workflow which we used when we run test also in 
Travis IIRC, so actually no change here ...

> 
> > we should move to GitHub completely ASAP.  The only thing
> > missing is OST, right?
> 
> 
> Yes. I think what we need is a way to start OST build with a github
> pull request url:
> 
> CUSTOM_REPOS=https://github.com/oVirt/{project}/pull/{7}
> 
> Or if it is easier, a way to upload zip files to jenkins for running OST.

If Jenkins wipes the workspace before/after each build, that won't be probably 
the most easy way to go. Github actions deliver the rpm in zip file, so we 
basically need
* download this zip file before build and unzip
* create local repo from it (vdsm.repo with baseurl=file://$PATH_TO_UNZIP_DIR)
* use this local repo instead of previous Jenkins build artifact job URL

So we just need to implement this or am I missing something and there are some 
issues with this approach and it's more complicated?

> Once we have something like this, we can move vdsm to github.
> 
> Triggering OST builds automatically ("gating") is nice to have and
> can be done later.
> 
> 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/Y6CO6UJG6SD4P
> IUTPWTMBDT7CC6DGDOH/



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/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/L4ZFAC4I7AOKHDGESONS5K5R5CLQCZAW/

[ovirt-devel] Re: Cannot install latest oVirt engine

[Vojtech Juranek]

On Tuesday, 21 September 2021 12:43:19 CEST Michal Skrivanek wrote:
> > On 21. 9. 2021, at 11:56, Vojtech Juranek  wrote:
> > 
> > On Tuesday, 21 September 2021 10:40:56 CEST Ales Musil wrote:
> >> On Tue, Sep 21, 2021 at 10:06 AM Vojtech Juranek 
> >> 
> >> wrote:
> >>> Hi,
> >>> 
> >>>> I'm trying to install engine build [1] to verify test a patch [2], but
> >>> 
> >>> I'm
> >>> 
> >>>> getting following error:
> >>> I was bale to install the engine, but adding new hosts fails with
> >>> 
> >>> 2021-09-21 03:52:15 EDT - TASK [ovirt-provider-ovn-driver : Configure
> >>> OVN
> >>> for oVirt] *
> >>> 2021-09-21 03:52:15 EDT -
> >>> 2021-09-21 03:52:15 EDT - fatal: [192.168.122.201]: FAILED! =>
> >>> {"changed":
> >>> true, "cmd": ["vdsm-tool", "ovn-config", "192.168.122.192",
> >>> "192.168.122.201", "192.168.122.201"], "delta": "0:00:00.355651", "end":
> >>> "2021-09-21 03:52:13.433094", "msg": "non-zer
> >>> o return code", "rc": 1, "start": "2021-09-21 03:52:13.077443",
> >>> "stderr":
> >>> "usage: \n /usr/bin/vdsm-tool [options] ovn-config IP-central
> >>> [tunneling-IP|tunneling-network]\nConfigures the ovn-controller on
> >>> the
> >>> host.\n\nParameters:\nIP-central -
> >>> 
> >>> the IP of the engine (the host where OVN central is located)\n
> >>> 
> >>> tunneling-IP - the local IP which is to be used for OVN tunneling\n
> >>> tunneling-network - the vdsm network meant to be used for OVN
> >>> tunneling\n
> >>> 
> >>>  ", "stderr_lines": ["usage: ", " /usr/
> >>> 
> >>> bin/vdsm-tool [options] ovn-config IP-central
> >>> [tunneling-IP|tunneling-network]", "Configures the ovn-controller on
> >>> the host.", "", "Parameters:", "IP-central - the IP of the
> >>> engine
> >>> (the host where OVN central is located)", "tunneling-IP
> >>> - the local IP which is to be used for OVN tunneling", "
> >>> tunneling-network - the vdsm network meant to be used for OVN
> >>> tunneling",
> >>> ""], "stdout": "", "stdout_lines": []}
> >>> 
> >>> 
> >>> There's additional 192.168.122.201 and the command should be
> >>> 
> >>> vdsm-tool ovn-config 192.168.122.192 192.168.122.201
> >>> 
> >>> I can run it manually, but the network is not configured properly as the
> >>> host setup fails always at this point.
> >>> Again some issue on my side or is this a known issue? Is there any
> >>> workaround for it?
> >>> 
> >>> Thanks for hits.
> >>> Vojta
> >> 
> >> This looks like you have an older ovirt-provider-ovn-driver, that does
> >> not
> >> support the third argument of ovn-config.
> >> Try to upgrade the driver package.
> > 
> > thanks, but ovirt-provider-ovn-driver seems to be up-to-date:
> > 
> > [root@localhost ~]# rpm -qa|grep ovirt-provider-ovn-driver
> > ovirt-provider-ovn-driver-1.2.35-0.20210902122827.git6140625.el8.noarch
> 
> you’re supposed to use
> https://resources.ovirt.org/repos/ovirt/tested/master/rpm/el8/noarch/
> update from there

Right, Ales gave me same advice on IRC and I can confirm it works.
Thanks you and Ales as well!

> > it seems to be an issue in vdsm-tool, running it manually fails:
> > 
> > [root@localhost ~]# vdsm-tool ovn-config 192.168.122.192 192.168.122.201
> > 192.168.122.201 usage:
> > /usr/bin/vdsm-tool [options] ovn-config IP-central
> > [tunneling-IP|tunneling-network]> 
> >Configures the ovn-controller on the host.
> >
> >Parameters:
> >IP-central - the IP of the engine (the host where OVN central is
> >located)
> >tunneling-IP - the local IP which is to be used for OVN tunneling
> >tunneling-network - the vdsm network meant to be used for OVN tunneling
> > 
> > [root@localhost ~]# echo $?
> > 1
> > 
> > 
> > ___
> > Devel mailing list -- devel@ovirt.org <mailto:devel@ovirt.org>
> > To unsubscribe send an email to devel-le...@ovirt.org
> > <mailto:devel-le...@ovirt.org> Privacy Statement:
> > https://www.ovirt.org/privacy-policy.html
> > <https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > <https://www.ovirt.org/community/about/community-guidelines/> List
> > Archives:
> > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/UYQZRKPZ7Y4
> > 52USEU5WNOXZSAZXG6VSL/
> > <https://lists.ovirt.org/archives/list/devel@ovirt.org/message/UYQZRKPZ7Y
> > 452USEU5WNOXZSAZXG6VSL/>



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/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/6LLGJKA4LOK7YFNLU6RBE2SEJT262O3A/

[ovirt-devel] Re: Cannot install latest oVirt engine

[Vojtech Juranek]

On Tuesday, 21 September 2021 10:40:56 CEST Ales Musil wrote:
> On Tue, Sep 21, 2021 at 10:06 AM Vojtech Juranek 
> 
> wrote:
> > Hi,
> > 
> > > I'm trying to install engine build [1] to verify test a patch [2], but
> > 
> > I'm
> > 
> > > getting following error:
> > I was bale to install the engine, but adding new hosts fails with
> > 
> > 2021-09-21 03:52:15 EDT - TASK [ovirt-provider-ovn-driver : Configure OVN
> > for oVirt] *
> > 2021-09-21 03:52:15 EDT -
> > 2021-09-21 03:52:15 EDT - fatal: [192.168.122.201]: FAILED! => {"changed":
> > true, "cmd": ["vdsm-tool", "ovn-config", "192.168.122.192",
> > "192.168.122.201", "192.168.122.201"], "delta": "0:00:00.355651", "end":
> > "2021-09-21 03:52:13.433094", "msg": "non-zer
> > o return code", "rc": 1, "start": "2021-09-21 03:52:13.077443", "stderr":
> > "usage: \n /usr/bin/vdsm-tool [options] ovn-config IP-central
> > [tunneling-IP|tunneling-network]\nConfigures the ovn-controller on the
> > host.\n\nParameters:\nIP-central -
> > 
> >  the IP of the engine (the host where OVN central is located)\n
> > 
> > tunneling-IP - the local IP which is to be used for OVN tunneling\n
> > tunneling-network - the vdsm network meant to be used for OVN tunneling\n
> > 
> >   ", "stderr_lines": ["usage: ", " /usr/
> > 
> > bin/vdsm-tool [options] ovn-config IP-central
> > [tunneling-IP|tunneling-network]", "Configures the ovn-controller on
> > the host.", "", "Parameters:", "IP-central - the IP of the engine
> > (the host where OVN central is located)", "tunneling-IP
> > - the local IP which is to be used for OVN tunneling", "
> > tunneling-network - the vdsm network meant to be used for OVN tunneling",
> > ""], "stdout": "", "stdout_lines": []}
> > 
> > 
> > There's additional 192.168.122.201 and the command should be
> > 
> > vdsm-tool ovn-config 192.168.122.192 192.168.122.201
> > 
> > I can run it manually, but the network is not configured properly as the
> > host setup fails always at this point.
> > Again some issue on my side or is this a known issue? Is there any
> > workaround for it?
> > 
> > Thanks for hits.
> > Vojta
> 
> This looks like you have an older ovirt-provider-ovn-driver, that does not
> support the third argument of ovn-config.
> Try to upgrade the driver package.

thanks, but ovirt-provider-ovn-driver seems to be up-to-date:

[root@localhost ~]# rpm -qa|grep ovirt-provider-ovn-driver
ovirt-provider-ovn-driver-1.2.35-0.20210902122827.git6140625.el8.noarch


it seems to be an issue in vdsm-tool, running it manually fails:

[root@localhost ~]# vdsm-tool ovn-config 192.168.122.192 192.168.122.201 
192.168.122.201
usage: 
 /usr/bin/vdsm-tool [options] ovn-config IP-central 
[tunneling-IP|tunneling-network]
Configures the ovn-controller on the host.

Parameters:
IP-central - the IP of the engine (the host where OVN central is located)
tunneling-IP - the local IP which is to be used for OVN tunneling
tunneling-network - the vdsm network meant to be used for OVN tunneling

[root@localhost ~]# echo $?
1




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/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/UYQZRKPZ7Y452USEU5WNOXZSAZXG6VSL/

[ovirt-devel] Re: Cannot install latest oVirt engine

[Vojtech Juranek]

Hi,

> I'm trying to install engine build [1] to verify test a patch [2], but I'm
> getting following error:

I was bale to install the engine, but adding new hosts fails with

2021-09-21 03:52:15 EDT - TASK [ovirt-provider-ovn-driver : Configure OVN for 
oVirt] *
2021-09-21 03:52:15 EDT - 
2021-09-21 03:52:15 EDT - fatal: [192.168.122.201]: FAILED! => {"changed": 
true, "cmd": ["vdsm-tool", "ovn-config", "192.168.122.192", "192.168.122.201", 
"192.168.122.201"], "delta": "0:00:00.355651", "end": "2021-09-21 
03:52:13.433094", "msg": "non-zer
o return code", "rc": 1, "start": "2021-09-21 03:52:13.077443", "stderr": 
"usage: \n /usr/bin/vdsm-tool [options] ovn-config IP-central 
[tunneling-IP|tunneling-network]\nConfigures the ovn-controller on the 
host.\n\nParameters:\nIP-central -
 the IP of the engine (the host where OVN central is located)\ntunneling-IP 
- the local IP which is to be used for OVN tunneling\ntunneling-network - 
the vdsm network meant to be used for OVN tunneling\n", "stderr_lines": 
["usage: ", " /usr/
bin/vdsm-tool [options] ovn-config IP-central 
[tunneling-IP|tunneling-network]", "Configures the ovn-controller on the 
host.", "", "Parameters:", "IP-central - the IP of the engine (the host 
where OVN central is located)", "tunneling-IP 
- the local IP which is to be used for OVN tunneling", "tunneling-network - 
the vdsm network meant to be used for OVN tunneling", ""], "stdout": "", 
"stdout_lines": []}


There's additional 192.168.122.201 and the command should be

vdsm-tool ovn-config 192.168.122.192 192.168.122.201

I can run it manually, but the network is not configured properly as the host 
setup fails always at this point.
Again some issue on my side or is this a known issue? Is there any workaround 
for it?

Thanks for hits.
Vojta

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/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/45UTMVZHJBVCWBQDPEDK2Q2UPJJRQC4Q/

[ovirt-devel] Re: Cannot install latest oVirt engine

[Vojtech Juranek]

On Friday, 17 September 2021 07:09:28 CEST Ales Musil wrote:
> On Thu, Sep 16, 2021 at 4:53 PM Vojtech Juranek  wrote:
> > Hi,
> > I'm trying to install engine build [1] to verify test a patch [2], but I'm
> > getting following error:
> > 
> > [root@localhost ~]# dnf install ovirt-engine
> > Last metadata expiration check: 0:20:02 ago on Thu Sep 16 10:24:54 2021.
> > Package
> > ovirt-engine-4.4.9.1-0.0.master.20210915185633.git016f27be31a.el8.noarch
> > is
> > already installed.
> > 
> > Error:
> >  Problem: package
> > 
> > ovirt-engine-setup-4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8.noar
> > ch requires ovirt-engine-setup-plugin-ovirt-engine =
> > 4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8, but none of the
> > providers can be installed
> > 
> >   - package
> > 
> > ovirt-engine-4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8.noarch
> > requires ovirt-engine-setup >=
> > 4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8, but none of the
> > providers can be installed
> > 
> >   - package
> > 
> > ovirt-engine-setup-plugin-ovirt-engine-4.5.0-0.0.master.20210916115243.git
> > f26fbb5598f.el8.noarch requires ovirt-openvswitch-ovn-central >= 2.15, but
> > none of the providers can be installed
> > 
> >   - cannot install the best candidate for the job
> >   - nothing provides ovn-2021-central needed by
> > 
> > ovirt-openvswitch-ovn-central-2.15-1.el8.noarch
> > 
> > 
> > ovirt-engine-setup-plugin-ovirt-engine doesn't seem to be built and
> > ovn-2021-central seems to be available only for centos stream 9 (on the
> > other hand, oVirt packaged are not build for centos stream 9 AFAICT).
> > 
> > Any ideas how to solve it and install latest engine build?
> > 
> > Thanks
> > Vojta
> > 
> > 
> > [1]
> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/14243/arti
> > fact/check-patch.el8stream.x86_64/ [2]
> > https://gerrit.ovirt.org/c/ovirt-engine/+/116747
> > ___
> > 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/GZ3CPN6VVZ7T
> > RMJ3KTNM3AXGGCS4UPS4/
> Hi,
> 
> ovn-2021-central is also available on CentOS Stream 8 [0].

thanks, somehow I missed it

> I guess you are trying to install an engine on Centos 8.4? 

It's Centos 8.4 which I switched to Centos Stream. Looks like some issue with 
switching ovirt dependencies repo. Adding this repo manually works.

> That won't work
> as oVirt master for now requires CentOS stream.
> 
> Regards,
> Ales
> 
> 
> [0]
> http://mirror.centos.org/centos/8-stream/nfv/x86_64/openvswitch-2/Packages/o
> /



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/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/DGMZ355XKNCYRNUND5VQQFHBKMSTM4UA/

[ovirt-devel] Cannot install latest oVirt engine

[Vojtech Juranek]

Hi,
I'm trying to install engine build [1] to verify test a patch [2], but I'm 
getting following error:

[root@localhost ~]# dnf install ovirt-engine
Last metadata expiration check: 0:20:02 ago on Thu Sep 16 10:24:54 2021.
Package 
ovirt-engine-4.4.9.1-0.0.master.20210915185633.git016f27be31a.el8.noarch is 
already installed.
Error: 
 Problem: package 
ovirt-engine-setup-4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8.noarch 
requires ovirt-engine-setup-plugin-ovirt-engine = 
4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8, but none of the providers 
can be installed
  - package 
ovirt-engine-4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8.noarch requires 
ovirt-engine-setup >= 4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8, but 
none of the providers can be installed
  - package 
ovirt-engine-setup-plugin-ovirt-engine-4.5.0-0.0.master.20210916115243.gitf26fbb5598f.el8.noarch
 requires ovirt-openvswitch-ovn-central >= 2.15, but none of the providers can 
be installed
  - cannot install the best candidate for the job
  - nothing provides ovn-2021-central needed by 
ovirt-openvswitch-ovn-central-2.15-1.el8.noarch


ovirt-engine-setup-plugin-ovirt-engine doesn't seem to be built and
ovn-2021-central seems to be available only for centos stream 9 (on the
other hand, oVirt packaged are not build for centos stream 9 AFAICT).

Any ideas how to solve it and install latest engine build?

Thanks
Vojta


[1] 
https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/14243/artifact/check-patch.el8stream.x86_64/
[2] https://gerrit.ovirt.org/c/ovirt-engine/+/116747

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/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/GZ3CPN6VVZ7TRMJ3KTNM3AXGGCS4UPS4/

[ovirt-devel] Re: ovirt-imageio fails tests on CentOS Stream 9 / qemu-6.1.0

[Vojtech Juranek]

On Thursday, 9 September 2021 16:44:30 CEST Sandro Bonazzola wrote:
> Il giorno gio 9 set 2021 alle ore 16:22 Michal Skrivanek <
> 
> michal.skriva...@redhat.com> ha scritto:
> > > On 9. 9. 2021, at 11:47, Vojtech Juranek  wrote:
> > > 
> > > On Wednesday, 8 September 2021 16:19:39 CEST Sandro Bonazzola wrote:
> > >> Hi,
> > >> running ovirt-imageio check-patch on CentOS Stream 9 fails.
> > > 
> > > do we have some CentOS Stream 9 images somewhere which I can use?
> > 
> > not yet.
> > I guess we should be adding it to OST at some point, rather sooner than
> > later.
> > volunteers welcomed;)
> 
> If for "image" you intend...
> 
> ISO:
> https://composes.stream.centos.org/production/latest-CentOS-Stream/compose/B
> aseOS/x86_64/iso/ container: quay.io/centos/centos:stream9-development
> image on glance.ovirt.org: CentOS Stream 9 Generic Cloud Image v20210803.0
> for x86_64 (0ee4ad3)

thanks, this is what I was looking for


> :-)
> :
> > >> Is anyone around from the storage team who can have a look?
> > 
> > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/3974//art
> > if> 
> > >> act/check-patch.el9stream.x86_64/mock_logs/script/stdout_stderr.log
> > >> 
> > >> Thanks,
> > > 
> > > ___
> > > 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/FU5UZT3KA2TE
> > SXI3RT2RPBSKG5RJGDWL/ ___
> > 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/ZQKYWQRBNECS
> > SBU3ENVRDVBQAVJPBV4S/



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/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/RO5YYGLKQKKIYKXW2JH3QYRNTZ3SGC4N/

[ovirt-devel] Re: ovirt-imageio fails tests on CentOS Stream 9 / qemu-6.1.0

[Vojtech Juranek]

On Wednesday, 8 September 2021 16:19:39 CEST Sandro Bonazzola wrote:
> Hi,
> running ovirt-imageio check-patch on CentOS Stream 9 fails.

do we have some CentOS Stream 9 images somewhere which I can use?

> Is anyone around from the storage team who can have a look?
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/3974//artif
> act/check-patch.el9stream.x86_64/mock_logs/script/stdout_stderr.log
> 
> Thanks,



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/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/FU5UZT3KA2TESXI3RT2RPBSKG5RJGDWL/

[ovirt-devel] Re: Moving #vdsm to #ovirt?

[Vojtech Juranek]

On Monday, 21 June 2021 14:36:43 CEST Nir Soffer wrote:
> We had mostly dead #vdsm channel in freenode[1].
> 
> Recently there was a hostile takeover of freenode, and old freenode
> folks created
> libera[2] network. Most (all?) projects moved to this network.
> 
> We can move #vdsm to libera, but I think we have a better option, use
> #ovirt channel
> in oftc[3], which is pretty lively.

+1

> Having vdsm developers in #ovirt channel is good for the project and
> will make it easier
> to reach developers.
> 
> Moving to libera require registration work. Moving to #ovirt requires no
> change. In both cases we need to update vdsm readme and ovirt.org.
> 
> What do you think?
> 
> [1] https://freenode.net/
> [2] https://libera.chat/
> [3] https://www.oftc.net/
> 
> Nir



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/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/NBKIPN2Z5PWW5VNU2SOYTPYMRLHHT2Q4/

[ovirt-devel] libvirtError: internal error: unknown feature amd-sev-es

[Vojtech Juranek]

Hi,
I moved to CentOS stream on the hosts as I need recent sanlock package due to 
vdsm dependency on it. 
After moving to Stream and updating packages, all my hosts fails with exception 
bellow. Bellow are also
libvirt and vdsm versions and VM XML dump.

Yesterday I tried more recent libvirt, but IIRC got SeLinux exception when 
connecting to libvirt.

Do you know how to fix this issue or basically how to create working env. where 
I would be
able to install recent vdsm?

Thanks
Vojta

2021-06-16 05:23:01,275-0400 ERROR (jsonrpc/5) [root] Error while getting 
domain capabilities (machinetype:92)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/common/cache.py", line 41, in 
__call__
return self.cache[args]
KeyError: ()

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/machinetype.py", line 90, in 
_get_domain_capabilities
domcaps = conn.getDomainCapabilities(None, arch, None, virt_type, 0)
  File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", 
line 131, in wrapper
ret = f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in 
wrapper
return func(inst, *args, **kwargs)
  File "/usr/lib64/python3.6/site-packages/libvirt.py", line 4493, in 
getDomainCapabilities
raise libvirtError('virConnectGetDomainCapabilities() failed')
libvirt.libvirtError: internal error: unknown feature amd-sev-es
2021-06-16 05:23:01,277-0400 ERROR (jsonrpc/5) [root] Error while getting CPU 
features: no domain capabilities found (machinetype:188)
2021-06-16 05:23:01,278-0400 ERROR (jsonrpc/5) [root] Error while getting 
domain capabilities (machinetype:92)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/common/cache.py", line 41, in 
__call__
return self.cache[args]
KeyError: ()

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/machinetype.py", line 90, in 
_get_domain_capabilities
domcaps = conn.getDomainCapabilities(None, arch, None, virt_type, 0)
  File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", 
line 131, in wrapper
ret = f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in 
wrapper
return func(inst, *args, **kwargs)
  File "/usr/lib64/python3.6/site-packages/libvirt.py", line 4493, in 
getDomainCapabilities
raise libvirtError('virConnectGetDomainCapabilities() failed')
libvirt.libvirtError: internal error: unknown feature amd-sev-es



[root@localhost ~]# rpm -qa|grep libvirt
libvirt-daemon-driver-storage-logical-7.0.0-14.1.el8.x86_64
python3-libvirt-7.0.0-1.el8.x86_64
libvirt-daemon-config-nwfilter-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-interface-7.0.0-14.1.el8.x86_64
libvirt-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-disk-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-iscsi-7.0.0-14.1.el8.x86_64
libvirt-client-7.0.0-14.1.el8.x86_64
libvirt-admin-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-network-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-secret-7.0.0-14.1.el8.x86_64
libvirt-lock-sanlock-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-gluster-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-rbd-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-7.0.0-14.1.el8.x86_64
libvirt-daemon-7.0.0-14.1.el8.x86_64
libvirt-daemon-config-network-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-iscsi-direct-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-scsi-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-nodedev-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-qemu-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-core-7.0.0-14.1.el8.x86_64
libvirt-daemon-kvm-7.0.0-14.1.el8.x86_64
libvirt-bash-completion-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-storage-mpath-7.0.0-14.1.el8.x86_64
libvirt-libs-7.0.0-14.1.el8.x86_64
libvirt-daemon-driver-nwfilter-7.0.0-14.1.el8.x86_64


[root@localhost ~]# rpm -qa|grep vdsm
vdsm-http-4.40.60.7-1.el8.noarch
vdsm-hook-fcoe-4.40.60.7-1.el8.noarch
vdsm-network-4.40.60.7-1.el8.x86_64
vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
vdsm-api-4.40.60.7-1.el8.noarch
vdsm-hook-openstacknet-4.40.60.7-1.el8.noarch
vdsm-python-4.40.60.7-1.el8.noarch
vdsm-hook-vhostmd-4.40.60.7-1.el8.noarch
vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
vdsm-common-4.40.60.7-1.el8.noarch
vdsm-client-4.40.60.7-1.el8.noarch
vdsm-4.40.60.7-1.el8.x86_64
vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch
vdsm-jsonrpc-4.40.60.7-1.el8.noarch


Host VM xml dump:


  centos82-host2-mig
  e1ee2430-37af-4ce1-b74a-7981895b5789
  
http://libosinfo.org/xmlns/libvirt/domain/1.0;>
  http://centos.org/centos/8"/>

  
  2097152
  2097152
  2
  
/machine
  
  
hvm

  
  



  
  
  



  
  destroy
  restart
  destroy
  


  
  

[ovirt-devel] Re: Why can not package the ovirt SDK ?

[Vojtech Juranek]

On Monday, 31 May 2021 10:18:31 CEST tommy wrote:
> There are metamodel-concept jar file in local repo:
> 
> [root@test1 metamodel-concepts]# ll
> total 8
> drwxr-xr-x. 2 root root 4096 May 29 12:12 1.3.4
> [root@test1 metamodel-concepts]#
> [root@test1 metamodel-concepts]#
> [root@test1 metamodel-concepts]#
> [root@test1 metamodel-concepts]# cd 1.3.4
> [root@test1 1.3.4]#
> [root@test1 1.3.4]#
> [root@test1 1.3.4]# ll
> total 64
> -rw-r--r--. 1 root root 45472 May 29 12:09 metamodel-concepts-1.3.4.jar
> -rw-r--r--. 1 root root40 May 29 12:09
> metamodel-concepts-1.3.4.jar.sha1
 -rw-r--r--. 1 root root  1490 May 29
> 12:08 metamodel-concepts-1.3.4.pom -rw-r--r--. 1 root root40 May 29
> 12:08 metamodel-concepts-1.3.4.pom.sha1 -rw-r--r--. 1 root root   216 May
> 29 12:09 _remote.repositories
> 
> 
> 
> And the pom config about is is:
> 
> 
>   org.ovirt.engine.api
>   metamodel-concepts
>   ${metamodel.version}
> 
> 
> 
> 
> Why cannot import it ?

no idea, but very likely some issue with your setup. I tired with clean repo 
and everything works. Try to run `maven clean` and/or remove these artifacts 
from local repo and let maven to download them again

> And {metamodel.version} is what value ?

currently 1.3.4, it's defined in pom.xml:

https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/pom.xml#L78

> 
> 
> 
> 
> 
> 
> -Original Message-
> From: Vojtech Juranek  
> Sent: Monday, May 31, 2021 3:59 PM
> To: 'oVirt development list' 
> Cc: tommy 
> Subject: Re: [ovirt-devel] Why can not package the ovirt SDK ?
> 
> On Saturday, 29 May 2021 15:33:15 CEST tommy wrote:
> 
> > Why can not package the ovirt SDK ?
> > 
> > 
> > 
> > The error line is :
> > 
> > import org.ovirt.api.metamodel.concepts.ListType;
> > 
> > There is not such class, where to download it ?
> 
> 
> it's part of org.ovirt.engine.api:metamodel-concepts artefact, you can
> download it e.g. from central repository [1]
> 
> 
> > 
> > Should maven download it auto ?
> > 
> 
> 
> yes, it should and it's also in available in central repo, check your maven
> settings if you have this repo enabled, use right profile etc.
> 
> [1]
> https://search.maven.org/artifact/org.ovirt.engine.api/metamodel-concepts
> 
> 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > [root@test1 ovirt-engine-sdk-java]# mvn package
> > 
> > [INFO] Scanning for projects...
> > 
> > [INFO]
> > --
> > --
> > 
> > [INFO] Reactor Build Order:
> > 
> > [INFO]
> > 
> > [INFO] oVirt Java SDK Parent
> > 
> > [INFO] oVirt Java SDK Generator
> > 
> > [INFO] oVirt Java SDK
> > 
> > [INFO]
> > 
> > [INFO]
> > --
> > --
> > 
> > [INFO] Building oVirt Java SDK Parent 4.4.6-SNAPSHOT
> > 
> > [INFO]
> > --
> > --
> > 
> > [INFO]
> > 
> > [INFO] --- maven-source-plugin:2.4:jar-no-fork (attach-sources) @ 
> > java-sdk-parent ---
> > 
> > [INFO]
> > 
> > [INFO]
> > --
> > --
> > 
> > [INFO] Building oVirt Java SDK Generator 4.4.6-SNAPSHOT
> > 
> > [INFO]
> > --
> > --
> > 
> > [INFO]
> > 
> > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> > java-sdk-generator ---
> > 
> > [INFO] Using 'UTF-8' encoding to copy filtered resources.
> > 
> > [INFO] Copying 2 resources
> > 
> > [INFO]
> > 
> > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
> > java-sdk-generator ---
> > 
> > [INFO] Compiling 3 source files to
> > /root/test/ovirt-engine-sdk-java/generator/target/classes
> > 
> > [INFO] -
> > 
> > [ERROR] COMPILATION ERROR :
> > 
> > [INFO] -
> > 
> > [ERROR]
> > /root/test/ovirt-engine-sdk-java/generator/src/main/java/org/ovirt/sdk
> > /java/ ServicesGenerator.java:[26,39] error: cannot access ListType
> > 
> > [INFO] 1 error
> > 
> > [INFO] 

[ovirt-devel] Re: Why can not package the ovirt SDK ?

[Vojtech Juranek]

On Saturday, 29 May 2021 15:33:15 CEST tommy wrote:
> Why can not package the ovirt SDK ?
> 
> 
> 
> The error line is :
> 
> import org.ovirt.api.metamodel.concepts.ListType;
> 
> There is not such class, where to download it ?

it's part of org.ovirt.engine.api:metamodel-concepts artefact, you can 
download it e.g. from central repository [1]

> 
> Should maven download it auto ?
> 

yes, it should and it's also in available in central repo, check your maven 
settings if you have this repo enabled, use right profile etc.

[1] https://search.maven.org/artifact/org.ovirt.engine.api/metamodel-concepts

> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> [root@test1 ovirt-engine-sdk-java]# mvn package
> 
> [INFO] Scanning for projects...
> 
> [INFO]
> 
> 
> [INFO] Reactor Build Order:
> 
> [INFO]
> 
> [INFO] oVirt Java SDK Parent
> 
> [INFO] oVirt Java SDK Generator
> 
> [INFO] oVirt Java SDK
> 
> [INFO]
> 
> [INFO]
> 
> 
> [INFO] Building oVirt Java SDK Parent 4.4.6-SNAPSHOT
> 
> [INFO]
> 
> 
> [INFO]
> 
> [INFO] --- maven-source-plugin:2.4:jar-no-fork (attach-sources) @
> java-sdk-parent ---
> 
> [INFO]
> 
> [INFO]
> 
> 
> [INFO] Building oVirt Java SDK Generator 4.4.6-SNAPSHOT
> 
> [INFO]
> 
> 
> [INFO]
> 
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> java-sdk-generator ---
> 
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> 
> [INFO] Copying 2 resources
> 
> [INFO]
> 
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> java-sdk-generator ---
> 
> [INFO] Compiling 3 source files to
> /root/test/ovirt-engine-sdk-java/generator/target/classes
> 
> [INFO] -
> 
> [ERROR] COMPILATION ERROR :
> 
> [INFO] -
> 
> [ERROR]
> /root/test/ovirt-engine-sdk-java/generator/src/main/java/org/ovirt/sdk/java/
> ServicesGenerator.java:[26,39] error: cannot access ListType
> 
> [INFO] 1 error
> 
> [INFO] -
> 
> [INFO]
> 
> 
> [INFO] Reactor Summary:
> 
> [INFO]
> 
> [INFO] oVirt Java SDK Parent .. SUCCESS [  1.259
> s]
> 
> [INFO] oVirt Java SDK Generator ... FAILURE [  2.234
> s]
> 
> [INFO] oVirt Java SDK . SKIPPED
> 
> [INFO]
> 
> 
> [INFO] BUILD FAILURE
> 
> [INFO]
> 
> 
> [INFO] Total time: 3.780 s
> 
> [INFO] Finished at: 2021-05-28T21:57:53+08:00
> 
> [INFO] Final Memory: 16M/40M
> 
> [INFO]
> 
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project java-sdk-generator: Compilation failure
> 
> [ERROR]
> /root/test/ovirt-engine-sdk-java/generator/src/main/java/org/ovirt/sdk/java/
> ServicesGenerator.java:[26,39] error: cannot access ListType
> 
> [ERROR]
> 
> [ERROR] -> [Help 1]
> 
> [ERROR]
> 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> 
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 
> [ERROR]
> 
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> 
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> 
> [ERROR]
> 
> [ERROR] After correcting the problems, you can resume the build with the
> command
> 
> [ERROR]   mvn  -rf :java-sdk-generator



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/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/UIFJMCPPAL3W4PHSHQE6ZD455TBZ2TIW/

[ovirt-devel] CI whitelist exception

[Vojtech Juranek]

Hi,
do we have a way how to run CI build for a patch from someone who is not on CI 
whitelist? CI doesn't care who triggered the build and check only the 
commiter. Or is adding commiter to whitelist the only way? I'd like to me some 
progress with gerrit #114723 [1].

I tired to run it on Travis build seems to be broken, failing on nmstate [2]. 
Could someone from network team please take a look?

Thanks
Vojta

[1] https://gerrit.ovirt.org/c/vdsm/+/114723
[2] https://travis-ci.org/github/vjuranek/vdsm/builds/771874636

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/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/HFBNOVKFK4HIE3WLF4AUN4HRIGYQ4ZGE/

[ovirt-devel] CI whitelist exception

[Vojtech Juranek]

Hi,
do we have a way how to run CI build for a patch from someone who is not on CI 
whitelist? CI doesn't care who triggered the build and check only the 
commiter. Or is adding commiter to whitelist the only way? I'd like to me some 
progress with gerrit #114723 [1].

I tired to run it on Travis build seems to be broken, failing on nmstate [2]. 
Could someone from network team please take a look?

Thanks
Vojta

[1] https://gerrit.ovirt.org/c/vdsm/+/114723
[2] https://travis-ci.org/github/vjuranek/vdsm/builds/771874636

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/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/CDUH62OEZCCBV6QLC75YZS7JWMCTFLWZ/

[ovirt-devel] Re: DB error during engine upgrade in dev environment

[Vojtech Juranek]

On Monday, 12 April 2021 15:13:32 CEST Benny Zlotnik wrote:
> I've encountered this a long time ago, not sure what the root cause
> was but I think a refresh of the schema helped:
> $ $PREFIX/share/ovirt-engine/dbscripts/schema.sh -c refresh

thanks, but doesn't seem to work, fails with some other error in the DB 
(probably somehow completely broken DB).
Probably would be more easy to start from scratch.

Just for the reference, if someone needs this in the future, needs to be run 
with

$PREFIX/share/ovirt-engine/dbscripts/schema.sh -c refresh -s 127.0.0.1 -p 
5432 -u engine -d engine

and 

export DBFUNC_DB_="/home/engine/pgpass"

which has

127.0.0.1:5432:engine:engine:engine

otherwise fails with "fe_sendauth: no password supplied"


> On Mon, Apr 12, 2021 at 4:03 PM Vojtech Juranek  wrote:
> > Hi,
> > I'm trying to upgrade my engine dev environment to latest master, but
> > during> 
> > $HOME/ovirt-engine/bin/engine-setup
> > 
> > I'm getting error bellow even when I run with full DB vacuum.
> > Any idea how to fix it?
> > 
> > Thanks
> > Vojta
> > 
> > 2021-04-12 08:45:41,395-0400 DEBUG otopi.context
> > context._executeMethod:145 method exception> 
> > Traceback (most recent call last):
> >   File "/usr/lib/python3.7/site-packages/otopi/context.py", line 132, in
> >   _executeMethod>   
> > method['method']()
> >   
> >   File
> >   "/home/**FILTERED**/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/b
> >   in/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/config/public_
> >   glance_repository.py", line 69, in _misc>   
> > storage_domain_id="072fbaa1-08f3-4a40-9f34-a5ca22dd1d74"
> >   
> >   File
> >   "/home/**FILTERED**/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/o
> >   virt_**FILTERED**_setup/**FILTERED**_common/database.py", line 258, in
> >   execute>   
> > args,
> > 
> > psycopg2.ProgrammingError: function inst_add_glance_provider(unknown,
> > unknown, unknown, unknown, unknown) does not exist LINE 2:   
> >  select inst_add_glance_provider(
> > 
> >^
> > 
> > HINT:  No function matches the given name and argument types. You might
> > need to add explicit type casts.
> > 
> > 2021-04-12 08:45:41,396-0400 ERROR otopi.context
> > context._executeMethod:154 Failed to execute stage 'Misc configuration':
> > function inst_add_glance_provider(unknown, unknown, unknown, unknown,
> > unknown) does not exist LINE 2: select
> > inst_add_glance_provider(
> > 
> >^
> > 
> > HINT:  No function matches the given name and argument types. You might
> > need to add explicit type
> > casts.___ 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/CJPPQALDD3M
> > CCFDLEMWF7423DYGA73XO/



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/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/EAQI3WFTXT4MUQ6TMZPUC5I5ECDEQ4MA/

[ovirt-devel] DB error during engine upgrade in dev environment

[Vojtech Juranek]

Hi,
I'm trying to upgrade my engine dev environment to latest master, but during

$HOME/ovirt-engine/bin/engine-setup

I'm getting error bellow even when I run with full DB vacuum.
Any idea how to fix it?

Thanks
Vojta

2021-04-12 08:45:41,395-0400 DEBUG otopi.context context._executeMethod:145 
method exception
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/otopi/context.py", line 132, in 
_executeMethod
method['method']()
  File 
"/home/**FILTERED**/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/config/public_glance_repository.py",
 line 69, in _misc
storage_domain_id="072fbaa1-08f3-4a40-9f34-a5ca22dd1d74"
  File 
"/home/**FILTERED**/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/ovirt_**FILTERED**_setup/**FILTERED**_common/database.py",
 line 258, in execute
args,
psycopg2.ProgrammingError: function inst_add_glance_provider(unknown, unknown, 
unknown, unknown, unknown) does not exist
LINE 2: select inst_add_glance_provider(
   ^
HINT:  No function matches the given name and argument types. You might need to 
add explicit type casts.

2021-04-12 08:45:41,396-0400 ERROR otopi.context context._executeMethod:154 
Failed to execute stage 'Misc configuration': function 
inst_add_glance_provider(unknown, unknown, unknown, unknown, unknown) does not 
exist
LINE 2: select inst_add_glance_provider(
   ^
HINT:  No function matches the given name and argument types. You might need to 
add explicit type casts.

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/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/CJPPQALDD3MCCFDLEMWF7423DYGA73XO/

[ovirt-devel] Re: Snapshot Deletion Issue

[Vojtech Juranek]

On Tuesday, 23 March 2021 04:25:25 CET Shubha Kulkarni wrote:
> Hello,
> 
> I am investigating an issue with deleting snapshot in oVirt 4.3.10.
> Basically the delete snapshot operation fails and I am seeing following
> error in VDSM(vdsm-4.30.46) log -
> 
> 
> = 2021-03-17
> 21:38:01,346-0400 INFO  (jsonrpc/1) [virt.vm]
> (vmId='4b04639c-386e-463c-8a8a-dfd3bc46d306') Starting merge with
> jobUUID=u'e6206d9f-6899-40b7-857a-3be3dd42d77d', original
> chain=ac065664-ad6c-4ad6-aea2-9558df71d41d <
> 210900dd-ff19-4a00-8706-926cb192b0db < 273fc001-1c18-4234-b2b6-f0485e5d13ef
> < e1e10354-ae43-456f-9341-1bb81c5bf960 <
> 7985a853-4d47-428b-bb5b-b34a38cc57e0 (top), disk='sda', base='sda[2]',
> top='sda[1]', bandwidth=0, flags=8 (vm:5954) 2021-03-17 21:38:01,354-0400
> ERROR (jsonrpc/1) [virt.vm] (vmId='4b04639c-386e-463c-8a8a-dfd3bc46d306')
> Live merge failed (job: e6206d9f-6899-40b7-857a-3be3dd42d77d) (vm:5960)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5958, in
> merge bandwidth, flags)
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 100,
> in f ret = attr(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
> line 131, in wrapper ret = f(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94,
> in wrapper return func(inst, *args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 719, in
> blockCommit if ret == -1: raise libvirtError ('virDomainBlockCommit()
> failed', dom=self) libvirtError: internal error: qemu block name
> 'json:{"backing": {"backing": {"backing": {"driver": "raw", "file":
> {"driver": "file", "filename":
> "/rhev/data-center/mnt/nash-nfs7:_nfs_shubha__ovirt__2_data/8bce5be7-aede-4
> 743-b3fd-1c199880892f/images/eb3cb8f2-9544-472f-946b-646eab9c621f/ac065664-a
> d6c-4ad6-aea2-9558df71d41d"}}, "driver": "qcow2", "file": {"driver": "file",
> "filename":
> "/rhev/data-center/mnt/nash-nfs7:_nfs_shubha__ovirt__2_data/8bce5be7-aede-4
> 743-b3fd-1c199880892f/images/eb3cb8f2-9544-472f-946b-646eab9c621f/210900dd-f
> f19-4a00-8706-926cb192b0db"}}, "driver": "qcow2", "file": {"driver": "file",
> "filename":
> "/rhev/data-center/mnt/nash-nfs7:_nfs_shubha__ovirt__2_data/8bce5be7-aede-4
> 743-b3fd-1c199880892f/images/eb3cb8f2-9544-472f-946b-646eab9c621f/273fc001-1
> c18-4234-b2b6-f0485e5d13ef"}}, "driver": "qcow2", "file": {"driver": "file",
> "filename":
> "/rhev/data-center/mnt/nash-nfs7:_nfs_shubha__ovirt__2_data/8bce5be7-aede-4
> 743-b3fd-1c199880892f/images/eb3cb8f2-9544-472f-946b-646eab9c621f/e1e10354-a
> e43-456f-9341-1bb81c5bf960"}}' doesn 2021-03-17 21:38:01,368-0400 INFO 
> (jsonrpc/1) [api.virt] FINISH merge return={'status': {'message': 'Merge
> failed', 'code': 52}}
> ===
> =
> 
> I found out that there is an issue logged here
> https://bugzilla.redhat.com/show_bug.cgi?id=1785939. However I am not able
> to see how it was fixed 

see https://bugzilla.redhat.com/show_bug.cgi?id=1785939#c10

> and whether it was merged in oVirt. Where can I
> find the relevant commit (in vdsm and/or libvirt)?
> 
> Thanks



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/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/7KBV6OL3VKEWIHXFCYX7GU33QIXUPQRS/

[ovirt-devel] Re: Engine upgrade fails with virtio_scsi_multi_queues_enabled does not exist

[Vojtech Juranek]

On Tuesday, 16 March 2021 08:48:46 CET Benny Zlotnik wrote:
> I think you had an issue because you clashed with the script number
> (or something like that, since you have a patch with an upgrade
> script), I think if you run manually the SQL in[1] and rerun
> engine-setup it should sort it out

Thanks Benny and Didi, indeed, in my patch I *had* upgrade script 
04_04_1010_something, which I renamed after to 04_04_1020_something after I 
rebased on top of gerrit #112642. However, DB remembers it and skips 
04_04_1010_*.

Running 04_04_1010_add_virtio_scsi_multi_queues_enabled_to_vm_static.sq 
manually fixed the issue.

Thanks!
Vojta

> [1]
> https://gerrit.ovirt.org/c/ovirt-engine/+/112642/16/packaging/dbscripts/upg
> rade/04_04_1010_add_virtio_scsi_multi_queues_enabled_to_vm_static.sql#1
 
> On Tue, Mar 16, 2021 at 9:40 AM Vojtech Juranek 
> wrote:
> >
> >
> > On Tuesday, 16 March 2021 08:29:07 CET Ales Musil wrote:
> > 
> > > On Tue, Mar 16, 2021 at 8:24 AM Vojtech Juranek 
> > > wrote:
> > 
> > > > On Tuesday, 16 March 2021 07:08:31 CET Yedidyah Bar David wrote:
> > > > 
> > > > > On Mon, Mar 15, 2021 at 10:48 PM Vojtech Juranek
> > > > > 
> > > >
> > > >
> > > >
> > > > wrote:
> > > > 
> > > > > > Hi,
> > > > > > when I try to upgrade my engine with built artifacts (e.g. [1]),
> > > > > > it
> > > >
> > > >
> > > >
> > > > fails
> > > >
> > > >
> > > >
> > > > > > with:
> > > > > >
> > > > > >
> > > > > >
> > > > > > psql:/usr/share/ovirt-engine/dbscripts/create_views.sql:1000:
> > > > > > ERROR:
> > > > > > column vm_templates.virtio_scsi_multi_queues_enabled does not
> > > > > > exist
> > > >
> > > >
> > > >
> > > > LINE
> > > >
> > > >
> > > >
> > > > > > 86: vm_templates.virtio_scsi_multi_queues_enabled AS
> > > > > > virtio_...>
> > > > > >
> > > > > >
> > > > > >
> > > > > >  ^
> > > > > >
> > > > > >
> > > > > >
> > > > > > FATAL: Cannot execute sql command:
> > > > > > --file=/usr/share/ovirt-engine/dbscripts/create_views.sql
> > > > > >
> > > > > >
> > > > > >
> > > > > > Same issue happens when I tried to update my dev engine with
> > > > > > local
> > > >
> > > >
> > > >
> > > > build.
> > > >
> > > >
> > > >
> > > > > > However, OST is passing [2].
> > > > > >
> > > > > >
> > > > > >
> > > > > > Any idea what's wrong? I don't see anything wrong in [3], which
> > > > > > is
> > > > > > probably the culprit, but I haven't much experience with
> > > > > > engine/db
> > > > > > though. Or maybe some issue on my side?
> > > > >
> > > > >
> > > > >
> > > > > I suppose this failure happens in engine-setup, right? Please share
> > > > > its logs. Thanks.
> > > >
> > > >
> > > >
> > > > attached
> > > >
> > > >
> > > >
> > > > > Best regards,
> > > > >
> > > > >
> > > > >
> > > > > > Thanks
> > > > > > Vojta
> > > > > >
> > > > > >
> > > > > >
> > > > > > [1]
> > > >
> > > >
> > > >
> > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/11174/
> > > > art
> > > >
> > > >
> > > >
> > > > > > ifact/check-patch.el8.x86_64/ [2]
> > > > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7880/
> > > > > > [3]
> > > >
> > > >
> > > >
> > > > https://github.com/oVirt/ovirt-engine/commit/52caf76e60ace2266d8283c13
> > > > 1d4
> > > >
> > > >
> > > >
> > > > > > 673a2dd79289_

[ovirt-devel] Re: Engine upgrade fails with virtio_scsi_multi_queues_enabled does not exist

[Vojtech Juranek]

On Tuesday, 16 March 2021 08:29:07 CET Ales Musil wrote:
> On Tue, Mar 16, 2021 at 8:24 AM Vojtech Juranek  wrote:
> > On Tuesday, 16 March 2021 07:08:31 CET Yedidyah Bar David wrote:
> > > On Mon, Mar 15, 2021 at 10:48 PM Vojtech Juranek 
> > 
> > wrote:
> > > > Hi,
> > > > when I try to upgrade my engine with built artifacts (e.g. [1]), it
> > 
> > fails
> > 
> > > > with:
> > > > 
> > > > psql:/usr/share/ovirt-engine/dbscripts/create_views.sql:1000: ERROR:
> > > > column vm_templates.virtio_scsi_multi_queues_enabled does not exist
> > 
> > LINE
> > 
> > > > 86: vm_templates.virtio_scsi_multi_queues_enabled AS virtio_...>
> > > > 
> > > >  ^
> > > > 
> > > > FATAL: Cannot execute sql command:
> > > > --file=/usr/share/ovirt-engine/dbscripts/create_views.sql
> > > > 
> > > > Same issue happens when I tried to update my dev engine with local
> > 
> > build.
> > 
> > > > However, OST is passing [2].
> > > > 
> > > > Any idea what's wrong? I don't see anything wrong in [3], which is
> > > > probably the culprit, but I haven't much experience with engine/db
> > > > though. Or maybe some issue on my side?
> > > 
> > > I suppose this failure happens in engine-setup, right? Please share
> > > its logs. Thanks.
> > 
> > attached
> > 
> > > Best regards,
> > > 
> > > > Thanks
> > > > Vojta
> > > > 
> > > > [1]
> > 
> > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/11174/art
> > 
> > > > ifact/check-patch.el8.x86_64/ [2]
> > > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7880/
> > > > [3]
> > 
> > https://github.com/oVirt/ovirt-engine/commit/52caf76e60ace2266d8283c131d4
> > 
> > > > 673a2dd79289___ 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/DWCUVM4HRGV
> > 
> > > > SUNLCS3TWL4LHKXDD2NPO/
> > 
> > ___
> > 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/TDSBKKXB42Y4
> > V644AI3PDRMV5QWWUF5J/
> Hi,
> it happened to me as well on my dev engine.
> I workaround this by cleaning my engine and running setup again from
> scratch.

this would very likely work as OST is passing, but I'd like to avoid it as I 
have quite a lot of stuff configured there and don't want to do it again

> I suspect that it is related to [0].
> 
> Thanks,
> Ales
> 
> [0] https://gerrit.ovirt.org/c/ovirt-engine/+/112642



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/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/XUSTEKEJT67E5TEVO2WYHNPUHSIPC2AR/

[ovirt-devel] Engine upgrade fails with virtio_scsi_multi_queues_enabled does not exist

[Vojtech Juranek]

Hi,
when I try to upgrade my engine with built artifacts (e.g. [1]), it fails with:

psql:/usr/share/ovirt-engine/dbscripts/create_views.sql:1000: ERROR:  column 
vm_templates.virtio_scsi_multi_queues_enabled does not exist
LINE 86: vm_templates.virtio_scsi_multi_queues_enabled AS virtio_...
 ^
FATAL: Cannot execute sql command: 
--file=/usr/share/ovirt-engine/dbscripts/create_views.sql

Same issue happens when I tried to update my dev engine with local build.
However, OST is passing [2].

Any idea what's wrong? I don't see anything wrong in [3], which is probably the 
culprit,
but I haven't much experience with engine/db though. Or maybe some issue on my 
side?

Thanks
Vojta

[1] 
https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/11174/artifact/check-patch.el8.x86_64/
[2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7880/
[3] 
https://github.com/oVirt/ovirt-engine/commit/52caf76e60ace2266d8283c131d4673a2dd79289

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/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/DWCUVM4HRGVSUNLCS3TWL4LHKXDD2NPO/

[ovirt-devel] Re: Support for 5K volumes

[Vojtech Juranek]

On Tuesday, 9 March 2021 13:29:19 CET Eyal Shenitzky wrote:
> Adding +Nir Soffer  +Vojtech Juranek
> 
> 
> On Mon, 8 Mar 2021 at 17:35, Sandro Bonazzola  wrote:
> > Hi,
> > Gluster 9 introduced support for 5k volumes (
> > https://docs.gluster.org/en/latest/release-notes/9.0/ ).
> > Is there interest in getting this in oVirt too?

we support max 400 data centers and 50 domains per data center [1], so 
theoretically yes, but in really I don't think there is a need for so many 
data centers to use all 5k volumes. Is there any customer/user hitting current 
gluster limits?

[1] https://access.redhat.com/articles/906543

> > Any thoughts about rebasing on Gluster 9 for oVirt 4.4.6?
> > 
> > Thanks,
> > --
> > 
> > Sandro Bonazzola
> > 
> > MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> > 
> > Red Hat EMEA <https://www.redhat.com/>
> > 
> > sbona...@redhat.com
> > <https://www.redhat.com/>
> > 
> > *Red Hat respects your work life balance. Therefore there is no need to
> > answer this email out of your office hours.*



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/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/P3V2O6KM7CA2NWLDQ77SHOMC5IRTWVYY/

[ovirt-devel] Re: basic suite failing on test_004_basic_sanity.test_verify_template_disk_copied_and_removed

[Vojtech Juranek]

It looks like OST in meantime got broken even more
and now fails before running tests with:

21:39:51 
../basic-suite-master/test-scenarios/test_098_ovirt_provider_ovn.py:26: in 

21:39:51 import requests
21:39:51 E   ModuleNotFoundError: No module named 'requests'

I don't see any recent commit which can cause this. So maybe
some issue with OST images?


On Tuesday, 2 March 2021 13:40:07 CET Benny Zlotnik wrote:
> I started the OST job two hours ago[1], but it's still pending and I
> see another job stuck in pending, not sure if there's an issue with
> the workers
> 
> 
> [1]
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test
> s_manual/7828
 
> On Tue, Mar 2, 2021 at 12:52 PM Benny Zlotnik  wrote:
> 
> >
> >
> > I posted a patch https://gerrit.ovirt.org/c/ovirt-engine/+/113740
> >
> >
> >
> > On Tue, Mar 2, 2021 at 12:44 PM Eyal Shenitzky 
> > wrote:
> 
> > >
> > >
> > > Hi Marcin,
> > >
> > >
> > >
> > > There were no changes in the test or with the verification recently.
> > > Did something change with cirros_image_glance_disk_name?
> > >
> > >
> > >
> > > On Tue, 2 Mar 2021 at 11:12, Marcin Sobczyk 
> > > wrote:
> > > 
> > >>
> > >>
> > >> Hi All,
> > >>
> > >>
> > >>
> > >> basic suite started failing on
> > >> 'test_verify_template_disk_copied_and_removed'.
> > >> Looking at the error reported (i.e. [1][2]) it seems that we can't get
> > >> a
> > >> valid handle to the glance disk.
> > >>
> > >>
> > >>
> > >> Can someone take a look at this?
> > >>
> > >>
> > >>
> > >> Regards, Marcin
> > >>
> > >>
> > >>
> > >> [1]
> > >> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-
> > >> tests_manual/7826/consoleFull#L2,310
 [2]
> > >> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests
> > >> _standard-check-patch/detail/ovirt-system-tests_standard-check-patch/15
> > >> 774/pipeline#step-220-log-1064
> > >> ___
> > >> 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/J5O6DPZQ
> > >> PSF7UT3L2NUG5FNLCS3FVHI4/> >
> > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Eyal Shenitzky
> > > ___
> > > 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/TA466HK3Q
> > > 4FUWUUUZN7NHFPTEQTDA3YH/
> ___
> 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/AB6GI5KHJDSQ3
> ABYIHKMAICUMLNW2OE2/



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/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/I66XVC6N6S6EYPVJK5GMRVKKXZTPVZU7/

[ovirt-devel] OST fails with NPE in VmDeviceUtils.updateUsbSlots

[Vojtech Juranek]

Hi,
OST fails constantly in test_check_snapshot_with_memory [1] with NPE  in 
VmDeviceUtils.updateUsbSlots [2]. Build with any additional changes (custom 
repo) is on [3].

Unfortunately, I wasn't able to find the root cause. Could someone please take
a look?

Thanks
Vojta

[1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7720/consoleFull
[2] 
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7720/artifact/exported-artifacts/test_logs/basic-suite-master/lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
[3] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7718/parameters/

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/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/M5LFINFRHR3T56UDVBD53EOTUFPDXOPC/

[ovirt-devel] OST fails, please review gerrit #113140

[Vojtech Juranek]

Hi,
OST fails AFAICT due to flake8 issue. Please review [1], it should fix the 
issue.
Thanks
Vojta

[1] https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/113140/

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/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/4LR6RLCGGO7GCT4UPJZUQ7EYERXQEKNI/

[ovirt-devel] Re: vdsm CI is failing

[Vojtech Juranek]

On úterý 17. listopadu 2020 19:17:55 CET Nir Soffer wrote:
> On Mon, Nov 16, 2020 at 1:00 PM Marcin Sobczyk  wrote:
> > Hi,
> > 
> > vdsm CI is failing with:
> > 
> > [2020-11-16T10:51:40.132Z] No match for argument:
> > ovirt-imageio-client-2.1.1 [2020-11-16T10:51:40.132Z] Error: Unable to
> > find a match:
> > ovirt-imageio-client-2.1.1
> 
> Should be fixed by
> https://gerrit.ovirt.org/c/112258/

what about container caching issue, which was the reason for adding version? 
Is it solved somehow?

> > example run:
> > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-p
> > atch/detail/vdsm_standard-check-patch/24926/pipeline
> > 
> > could you please take a look at it?
> > 
> > Regards, Marcin



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/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/3DN2OWPCTZP6JABPGKWB4VF347XBYPMK/

[ovirt-devel] Re: Travis builds

[Vojtech Juranek]

On středa 11. listopadu 2020 15:17:52 CET Michal Skrivanek wrote:
> > On 11 Nov 2020, at 11:17, Nir Soffer  wrote:
> > 
> > On Wed, Nov 11, 2020 at 10:33 AM Vojtech Juranek  
wrote:
> >> Hi,
> >> recently, I noticed Travis builds waits in the queue for a very long
> >> time.
> >> Looking around I found out Travis probably reduced resources for OSS
> >> projects.
> >> 
> >> Also I found out all projects should migrate from travis-ci.org to
> >> travis-
> >> ci.com by end of December 2020 [1] (see Q. When will the migration from
> >> travis-ci.org to travis-ci.com be completed?). Recently they announce new
> >> pricing model [2] when OSS projects will get some initial credit and
> >> after
> >> that either has to pay or ask the support for another credit (see section
> >> "Building on a public repositories only" in [2]).
> >> 
> >> Maybe time to migrate away from travis-ci to something else, e.g. GH
> >> Actions?> 
> > I would avoid github only dependency. Libvrt and qemu moved to gitlab
> > recently, I think we should check this option instead.
> 
> or our jenkins?
> 
> we are getting rid of that awful mock environment, slowly, but it’s
> progressing… is there still any reason to run a separate thing then?

if the builds are comparably fast as on Travis, yes, this would the best 
option

> >> Thoughts?
> >> 
> >> Vojta
> >> 
> >> [1]
> >> https://docs.travis-ci.com/user/migrate/open-source-repository-migration
> >> [2]
> >> https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing_
> >> __ 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/PFRTNEBW3I
> >> FCUGPI5R3VN3LEMV7DGD4Z/> 
> > ___
> > 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/JSPSQ2AZBKT
> > BWUKFLVXJQSDIQ5D5UNX5/



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/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/VLH7XRWFXNH7ZG5OXRH6A5VFBYFID656/

[ovirt-devel] Travis builds

[Vojtech Juranek]

Hi,
recently, I noticed Travis builds waits in the queue for a very long time. 
Looking around I found out Travis probably reduced resources for OSS projects. 

Also I found out all projects should migrate from travis-ci.org to travis-
ci.com by end of December 2020 [1] (see Q. When will the migration from 
travis-ci.org to travis-ci.com be completed?). Recently they announce new 
pricing model [2] when OSS projects will get some initial credit and after 
that either has to pay or ask the support for another credit (see section 
"Building on a public repositories only" in [2]).

Maybe time to migrate away from travis-ci to something else, e.g. GH Actions?
Thoughts?

Vojta

[1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration
[2] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

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/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/PFRTNEBW3IFCUGPI5R3VN3LEMV7DGD4Z/

[ovirt-devel] Re: Testing image transfer and backup with OST environment

[Vojtech Juranek]

> > IMO OST should be made easy to interact with from your main development
> > machine.
> TBH I didn't see much interest in running OST on developers' machines.

as it's little bit complex to setup? Making it more easy maybe would increase 
number of people contributing to OST ... 

> People are mostly using manual OST runs to verify things and that is what
> most of the efforts focus on. It's not that I wouldn't like OST to be more
> developer-friendly, I definitely would, but we need more manpower
> and interest for that to happen.
> 

> >> I noticed that many of you run OST in a VM ending up with three layers
> >> of VMs.
> >> I know it works, but I got multiple reports of assertions' timeouts and
> >> TBH I just don't
> >> see this as a viable solution to work with OST - you need a bare metal
> >> for that.
> > 
> > Why?
> > 
> > After all, we also work on a virtualization product/project. If it's
> > not good enough for ourselves, how do we expect others to use it? :-)
> 
> I'm really cool with the engine and the hosts being VMs, but deploying
> engine and the hosts as VMs nested in other VM is what I think is
> unreasonable.

I tried this approach in past two days and works fine for me (except the fast 
it's slow)

> Maybe I'm wrong here, but I don't think our customers run whole oVirt
> clusters
> inside VMs. There's just too much overhead with all that layers of nesting
> and the performance sucks.
> 
> > Also, using bare-metal isn't always that easy/comfortable either, even
> > if you have the hardware.
> 
> I'm very happy with my servers. What makes working with bm
> hard/uncomfortable?

IMHO main issue is lack of HW. I really don't want to run it directly on my 
dev laptop (without running it inside VM). If I ssh/mount FS/tunnel ports to/
from VM or some bare metal server really doesn't matter (assuming reasonable 
connection speed to bare metal server)

> I can think of reprovisioning, but that is not needed for OST usage.
> 
> > CI also uses VMs for this, IIUC. Or did we move there to containers?
> > Perhaps we should invest in making this work well inside a container.
> 
> CI doesn't use VMs - it uses a mix of containers and bare metals.
> The solution for containers can't handle el8 and that's why we're
> stuck with running OST on el7 mostly (apart from the aforementioned
> bare metals, which use el8).
> 
> There is a 'run-ost-container.sh' script in the project. I think some people
> had luck using it, but I never even tried. Again, my personal opinion, as
> much as I find containers useful and convenient in different situations,
> this is not one of them - you should be using bare metal.
> 
> The "backend for OST" is a subject for a whole, new discussion.
> My opinion here is that we should be using oVirt as backend for OST
> (as in running oVirt cluster as VMs in oVirt). I'm a big fan of the
> dogfooding
> concept. This of course creates a set of new problems like "how can
> developers
> work with this", "where do we get the hosting oVirt cluster from" etc.
> Whooole, new discussion :)
> 
> Regards, Marcin
> 
> >> On my bare metal server OST basic run takes 30 mins to complete. This is
> >> something one
> >> can work with, but we can do even better.
> >> 
> >> Thank you for your input and I hope that we can have more people
> >> involved in OST
> >> on a regular basis and not once-per-year hackathons. This is a complex
> >> project, but it's
> >> really useful.
> > 
> > +1!
> > 
> > Thanks and best regards,
> > 
> >>> Nice.
> >>> 
> >>> Thanks and best regards,
> >> 
> >> [1]
> >> https://github.com/lago-project/lago/blob/7bf288ad53da3f1b86c08b3283ee9c5
> >> 118e7605e/lago/providers/libvirt/network.py#L162 [2]
> >> https://github.com/oVirt/ovirt-system-tests/blob/6d5c2a0f9fb3c05afc854712
> >> 60065786b5fdc729/ost_utils/ost_utils/pytest/fixtures/engine.py#L105



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/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/3HCX7ML4AASGMPEAVQBSHQ4OC6H4WFTW/

[ovirt-devel] Re: vdsm fails on Travis

[Vojtech Juranek]

On čtvrtek 22. října 2020 11:48:15 CEST Ales Musil wrote:
> On Thu, Oct 22, 2020 at 11:34 AM Vojtech Juranek 
> 
> wrote:
> > Hi,
> > some network tests fail on Travis, see e.g. [1].
> > Could someone from network team take a look?
> > My guess is it's caused by commit 3ec1ad9a9f38 [2], but I'm not sure.
> > Thanks
> > Vojta
> > 
> > [1] https://travis-ci.org/github/oVirt/vdsm/jobs/737665066
> > [2]
> > https://github.com/oVirt/vdsm/commit/3ec1ad9a9f3879bf1c1b4aef2cbed4c3eda16
> > 9f6 ___
> > 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/SKA345FPGP5B
> > P6IOYP32JP5ZHO4RDZ4M/
> Hi,
> 
> the [0] should fix it. But I am not sure how to test it.

you need to rebuild containers with this change and push it into quay.io (or 
some other docker repository), change the container in .travis.yml and run the 
test on Travis.

I'm trying to verify it, but upload speed of my link is pretty slow (to push 
centors container into quay), so it will take some time

> 
> Thanks,
> Ales
> 
> [0] https://gerrit.ovirt.org/c/111851/



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/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/DHEL2ZZETOIUABTOG2XVCHFHGDHFEX2Q/

[ovirt-devel] vdsm fails on Travis

[Vojtech Juranek]

Hi,
some network tests fail on Travis, see e.g. [1].
Could someone from network team take a look?
My guess is it's caused by commit 3ec1ad9a9f38 [2], but I'm not sure.
Thanks
Vojta

[1] https://travis-ci.org/github/oVirt/vdsm/jobs/737665066
[2] 
https://github.com/oVirt/vdsm/commit/3ec1ad9a9f3879bf1c1b4aef2cbed4c3eda169f6

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/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/SKA345FPGP5BP6IOYP32JP5ZHO4RDZ4M/

[ovirt-devel] OST fails during 002_bootstrap_pytest

[Vojtech Juranek]

Hi,
can anybody look on OST, it fails constantly with error bellow.
See e.g. [1, 2] for full logs.
Thanks
Vojta

[1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7381/
[2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7382/

13:07:16 ../basic-suite-master/test-scenarios/
002_bootstrap_pytest.py::test_verify_engine_backup [WARNING]: Invalid 
characters were found in group names but not replaced, use
13:07:22 - to see details
13:07:22 /usr/lib/python2.7/site-packages/requests/__init__.py:91: 
RequestsDependencyWarning: urllib3 (1.25.10) or chardet (3.0.4) doesn't match 
a supported version!
13:07:22   RequestsDependencyWarning)
13:07:22 lago-basic-suite-master-engine | CHANGED => {
13:07:22 "changed": true, 
13:07:22 "gid": 0, 
13:07:22 "group": "root", 
13:07:22 "mode": "0755", 
13:07:22 "owner": "root", 
13:07:22 "path": "/var/log/ost-engine-backup", 
13:07:22 "secontext": "unconfined_u:object_r:var_log_t:s0", 
13:07:22 "size": 6, 
13:07:22 "state": "directory", 
13:07:22 "uid": 0
13:07:22 }

13:07:44 [WARNING]: Invalid characters were found in group names but not 
replaced, use
13:07:44 - to see details
13:07:44 /usr/lib/python2.7/site-packages/requests/__init__.py:91: 
RequestsDependencyWarning: urllib3 (1.25.10) or chardet (3.0.4) doesn't match 
a supported version!
13:07:44   RequestsDependencyWarning)
13:07:44 lago-basic-suite-master-engine | FAILED | rc=1 >>
13:07:44 Start of engine-backup with mode 'backup'
13:07:44 scope: all
13:07:44 archive file: /var/log/ost-engine-backup/backup.tgz
13:07:44 log file: /var/log/ost-engine-backup/log.txt
13:07:44 Backing up:
13:07:44 Notifying engine
13:07:44 - Files
13:07:44 - Engine database 'engine'
13:07:44 - DWH database 'ovirt_engine_history'
13:07:44 - Grafana database '/var/lib/grafana/grafana.db'
13:07:44 Notifying engineFATAL: failed to backup /var/lib/grafana/grafana.db 
with sqlite3non-zero return code
13:17:47 FAILED

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/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/J7USSMZT3FYOAS4JMC4DKV3QS4CUIR42/

[ovirt-devel] CI cannot find ioprocess package

[Vojtech Juranek]

Hi,
CI fails quite often with

Error: Unable to find a match: python3-ioprocess-1.4.1

see e.g. [1, 2].
Can someone please take a look?
Thanks
Vojta

[1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502
[2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503

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/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/SYN66JCV4GPYS3JK6XQB6X4ZAJH3QU7E/

[ovirt-devel] Re: implementing hotplugCd/hotunplugCd in vdsm

[Vojtech Juranek]

On čtvrtek 20. srpna 2020 14:42:15 CEST Michal Skrivanek wrote:
> > On 20 Aug 2020, at 14:28, Nir Soffer  wrote:
> > 
> > On Thu, Aug 20, 2020 at 12:19 PM Vojtech Juranek 
> > wrote:
> 
> >> 
> >> Hi,
> >> as Fedor is on PTO, I was asked to take over.
> >> 
> >> I don't think new functionality is need, more detail list of proposed
> >> flows and changes is bellow,
 TL;DR: I'd suggest to
> >> 
> >>  - change in engine: send PDIV instead of CD path from engine to vdsm
> 
> 
> the biggest issue here is always with older versions not having this
> functionality yet….

yes, I was wrong, this requires new functionality. Therefore Nir proposed to 
create a feature page for it. We put together flows which should cover all the 
possible issues (including VM recovery). Please review and comment directly 
under 

https://github.com/oVirt/ovirt-site/pull/2320

(unless you think creating feature page for it is wrong way to go:-)

> 
> >>  - change in vdsm: implement counter of ISOs being used by VMs to know
> >>  when we can deactivate volume
 - change in vdsm: remove old drivespec
> >>  from VM XML when changing/removing CD (and eventually deactivate
> >>  volume)>> 
> >> 
> >> You comments are welcome.
> >> Thanks
> >> Vojta
> >> 
> >> Flows
> >> ===
> >> 
> >> VM without a CD
> >> -
> >> 
> >>  - Should not be possible to insert any CD, this option should not be
> >>  available/active in the UI.
> 
> > 
> > I don't think we have such configuration, all VMs have empty cdrom by
> > default:
 
> > 
> >
> >
> >  
> >  
> >  
> >  
> >  
> >  
> >
> >
> > 
> > 
> > But of course if we have such configuration when adding CD is not
> 
> 
> we don’t. All VMs have always at least that one implicit CD (empty or
> loaded)
 We have a case where there is additional CD for
> cloud-init/payload, that additional CD is not “changeable” nor exposed in
> UI anywhere 
> 
> > possible, the menu/button
> > should be disabled in the UI.
> > 
> > 
> >> VM without CD, changeCD inserts new ISO
> 
> 
> please update to make it really clear, there’s no “VM without CD”. VM always
> has CD, just not loaded (empty tray)
 so this case doesn’t exist…
> 
> 
> >> -
> >> 
> >>  - add new drivespec to VM metadata
> > 
> > 
> > How failure is handled?
> > 
> > 
> >>  - prepare new drivespec
> > 
> > 
> > What if vdsm is restarted at this point?
> > 
> > How VM recovery should handle this drivespec referring to inactive
> > volume?
> > 
> > 
> >>  - attach new device to VM
> >>  - if attaching to VM fails, tear down drivespec and remove drivespec
> >>  from VM metadata
> 
> > 
> > Tearing down and removing drivespec cannot be done atomically. any
> > operation may fail and
> > vdsm may be killed at any point.
> > 
> > The design should suggest how vdsm recover from all errors.
> > 
> > 
> >> VM with CD, changeCD removes current ISO
> >> ---
> >> 
> >>  - tear down previous drivespec
> >>  
> >>- if volume with ISO is inactive (as a result e.g. of failure of vdsm
> >>after inserting drivespec into VM metadata, but before activating
> >>volume), continue without error
> 
> > 
> > Sounds good, and may be already handled in lvm module. You can try to
> > deactivate
 LV twice to confirm this.
> > 
> > 
> >>- if drivespec is used by another VM, don’t deactivate volume
> > 
> > 
> > This is the tricky part, vdsm does not have a mechanism for tracking
> > usage of block devices,
> > and adding such mechanism is much bigger work than supporting CD on
> > block devices, so
> > it cannot be part of this work.
> 
> 
> We do have the list of active VMs and their xml/devices, so we do know if
> there are other users, it’s nt an expensive check. Locking it properly so
> there’s no in flight request for change cd could be a bit tricky but it
> doesn’t sound that complex
> > 
> > 
> >>  -remove drivespec from VM metadata
> > 
> > 
> > What if this fails, or vdsm is restarted before we try to do this?
> > 
> > Whe

[ovirt-devel] Re: implementing hotplugCd/hotunplugCd in vdsm

[Vojtech Juranek]

On čtvrtek 20. srpna 2020 11:19:39 CEST Vojtech Juranek wrote:
> Hi,
> as Fedor is on PTO, I was asked to take over.
> 
> I don't think new functionality is need, more detail list of proposed flows
> and changes is bellow, TL;DR: I'd suggest to
>   - change in engine: send PDIV instead of CD path from engine to vdsm
>   - change in vdsm: implement counter of ISOs being used by VMs to know when
> we can deactivate volume - change in vdsm: remove old drivespec from VM XML
> when changing/removing CD (and eventually deactivate volume)
> 
> You comments are welcome.
> Thanks
> Vojta
> 
> Flows
> ===
> 
> VM without a CD
> -
>   - Should not be possible to insert any CD, this option should not be
> available/active in the UI.
> 
> VM without CD, changeCD inserts new ISO
> -
>   - add new drivespec to VM metadata
>   - prepare new drivespec
>   - attach new device to VM
>   - if attaching to VM fails, tear down drivespec and remove drivespec from
> VM metadata
> 
> VM with CD, changeCD removes current ISO
> ---
>   - tear down previous drivespec
> - if volume with ISO is inactive (as a result e.g. of failure of vdsm
> after inserting drivespec into VM metadata, but before activating volume),
> continue without error - if drivespec is used by another VM, don’t
> deactivate volume
>   -remove drivespec from VM metadata
> 
> VM with CD, changeCD inserts new ISO and removes old
> 
> -- - tear down previous drivespec
> - if volume with ISO is inactive (as a result e.g. of failure of vdsm
> after inserting drivespec into VM metadata, but before activating volume),
> continue without error - if drivespec is used by another VM, don’t
> deactivate volume
>   - remove previous drivespec from VM metadata
>   - add new drivespec to VM metadata
>   - prepare new drivespec
>   - attach new device to VM
>   - if attaching new drivespac fails, tear down new drivespec and attach
> back previous drivespec
> 
> 
> Proposed changes
> ===
> 
> Engine
> --
>   - change ChangeDiskCommand to use PDIV (pool, domain, image, volume ID)
> instead of ISO path - modify UI not to provide an option to change CD for
> VMs without CD
> 
> vdsm
> 
>   - add volume/ISO counter which would count the number of VM using the
> given ISO. When CDROM is inserted, the counter is increased, when ejected,
> the counter is decreased. ISO volume is deactivated only when on VM uses
> it. We already have sqlite DB for managed storage, so we can add DB for ISO
> quite easily.

another option (probably better) could be to use shared sanlock resouce lock 
for it, but I need to explore this option more to be sure it can be used

> - modify Vm._changeBlockDev to reflect flows suggested above
> 
> > Hi Fedor,
> > 
> > > On 27 Jun 2020, at 14:46, Fedor Gavrilov  wrote:
> > > 
> > > 
> > > 
> > > So from what I was able to see in hotplugDisk example, for CDs I would
> > > have to do similar:
> > > 
> > > 
> > > 
> > > 1. parse disk params from stored xml metadata
> > > 2. call prepareVolumePath with these params
> > > (skip normalizeVdsmImg)
> > > 3. call updateDriveIndex
> > 
> > Why?
> > 
> > > (skip validating whether volume has leases)
> > > 4. drive.getXML() and then hooks.before_disk_hotplug with it
> > 
> > If only the storage stuff would ever finish moving to xml
> > But it’s not right to call this hook anyway, iiuc you’re not doing a
> > hotplug
> > 
> > > 5. call attachDevice with drive XML and handle possible errors
> > > 
> > > 
> > > 
> > > I am not sure, however, whether we need what "else" does in hotplugDisk
> > > (vm.py line 3468)...
> > > 
> > > 
> > > 
> > > Looking forward to hearing your opinions,
> > > Fedor
> > > 
> > > 
> > > 
> > > - Original Message -
> > > From: "Fedor Gavrilov" 
> > > To: "devel" 
> > > Sent: Monday, June 22, 2020 4:37:59 PM
> > > Subject: [ovirt-devel] implementing hotplugCd/hotunplugCd in vdsm
> > > 
> > > 
> > > 
> > > Hey,
> > > 
> > > 
> > > 
> > > So in an attempt to fix change CD functionality we discovered a few
> > > other
> > > potential
>

[ovirt-devel] Re: implementing hotplugCd/hotunplugCd in vdsm

[Vojtech Juranek]

Hi,
as Fedor is on PTO, I was asked to take over.

I don't think new functionality is need, more detail list of proposed flows and 
changes is bellow,
TL;DR: I'd suggest to 
  - change in engine: send PDIV instead of CD path from engine to vdsm
  - change in vdsm: implement counter of ISOs being used by VMs to know when we 
can deactivate volume
  - change in vdsm: remove old drivespec from VM XML when changing/removing CD 
(and eventually deactivate volume)

You comments are welcome.
Thanks
Vojta

Flows
===

VM without a CD
-
  - Should not be possible to insert any CD, this option should not be 
available/active in the UI.

VM without CD, changeCD inserts new ISO
-
  - add new drivespec to VM metadata
  - prepare new drivespec
  - attach new device to VM
  - if attaching to VM fails, tear down drivespec and remove drivespec from VM 
metadata

VM with CD, changeCD removes current ISO
---
  - tear down previous drivespec
- if volume with ISO is inactive (as a result e.g. of failure of vdsm after 
inserting drivespec into VM metadata, but before activating volume), continue 
without error
- if drivespec is used by another VM, don’t deactivate volume
  -remove drivespec from VM metadata

VM with CD, changeCD inserts new ISO and removes old
--
  - tear down previous drivespec
- if volume with ISO is inactive (as a result e.g. of failure of vdsm after 
inserting drivespec into VM metadata, but before activating volume), continue 
without error
- if drivespec is used by another VM, don’t deactivate volume
  - remove previous drivespec from VM metadata
  - add new drivespec to VM metadata
  - prepare new drivespec
  - attach new device to VM
  - if attaching new drivespac fails, tear down new drivespec and attach back 
previous drivespec


Proposed changes
===

Engine
--
  - change ChangeDiskCommand to use PDIV (pool, domain, image, volume ID) 
instead of ISO path
  - modify UI not to provide an option to change CD for VMs without CD

vdsm

  - add volume/ISO counter which would count the number of VM using the given 
ISO. When CDROM is inserted, the counter is increased, when ejected, the 
counter is decreased. ISO volume is deactivated only when on VM uses it.
We already have sqlite DB for managed storage, so we can add DB for ISO 
quite easily.
  - modify Vm._changeBlockDev to reflect flows suggested above


> Hi Fedor,
> 
> 
> > On 27 Jun 2020, at 14:46, Fedor Gavrilov  wrote:
> >
> >
> >
> > So from what I was able to see in hotplugDisk example, for CDs I would
> > have to do similar:
>
> >
> >
> > 1. parse disk params from stored xml metadata
> > 2. call prepareVolumePath with these params
> > (skip normalizeVdsmImg)
> > 3. call updateDriveIndex
> 
> 
> Why?
> 
> 
> > (skip validating whether volume has leases)
> > 4. drive.getXML() and then hooks.before_disk_hotplug with it
> 
> 
> If only the storage stuff would ever finish moving to xml
> But it’s not right to call this hook anyway, iiuc you’re not doing a
> hotplug
 
> 
> > 5. call attachDevice with drive XML and handle possible errors
> >
> >
> >
> > I am not sure, however, whether we need what "else" does in hotplugDisk
> > (vm.py line 3468)...
>
> >
> >
> > Looking forward to hearing your opinions,
> > Fedor
> >
> >
> >
> > - Original Message -
> > From: "Fedor Gavrilov" 
> > To: "devel" 
> > Sent: Monday, June 22, 2020 4:37:59 PM
> > Subject: [ovirt-devel] implementing hotplugCd/hotunplugCd in vdsm
> >
> >
> >
> > Hey,
> >
> >
> >
> > So in an attempt to fix change CD functionality we discovered a few other
> > potential
> 
> CD has a long history of issues caused by historical simplifications.
> What is the intended fix, stop using string paths?
> 
> 
> > issues and what Nir suggested was to implement two [somewhat] new
> > functions in VDSM: hotplug and hotunplug for CDs similar to how it works
> > for normal disks now.
> 
> This is conceptually different, CD is a removable media,
> hotplug/unplug is for the device itself. We never supported hotplug of
> the device though.
> 
> 
> > Existing changeCD function will be left as is for backwards
> > compatibility.
> 
> 
> Who would use the new function?
> 
> 
> > As I found out, engine already calculates iface and index before invoking
> > VDSM functions, so we will just pass these along with PDIV to the VDSM.
>
> >
> >
> > Suggested flow is, let me quote:
> >
> >
> >
> >> So the complete change CD flow should be:
> >>
> >>
> >>
> >> 1. get the previous drivespec from vm metadata
> >> 2. prepare new drivespec
> >> 3. add new drivespec to vm metadata
> >> 4. attach a new device to vm
> 
> 
> Don’t call it a new device when you just change a media
> 
> 
> >> 5. teardown the previous drivespec
> >> 6. remove 

[ovirt-devel] Re: Issue while installing ovirt-imageio-daemon

[Vojtech Juranek]

On čtvrtek 2. července 2020 8:15:59 CEST Sandro Bonazzola wrote:
> Il giorno mer 1 lug 2020 alle ore 19:03 Nir Soffer  ha
> 
> scritto:
> > On Wed, Jul 1, 2020 at 7:46 PM Sandro Bonazzola 
> > 
> > wrote:
> >> Hi, just noticed in appliance build at
> >> https://jenkins.ovirt.org/job/ovirt-appliance_standard-check-patch/286/co
> >> nsoleFull>> 
> >>  15:18:22,373 INFO anaconda:program: Installing :
> >>  ovirt-imageio-daemon-2.0.9-1.el8.x86_64 90/223
> >>  
> >>   >>  consoleFull#L8,513> 15:18:22,373 INFO anaconda:program: warning: group
> >>  Development/Debug does not exist - using root> 
> > We remove "Group:" from the spec here:
> > 
> > https://github.com/oVirt/ovirt-imageio/commit/dd570082896cc410ad28b420ca37
> > dd065ec68831
> > 
> > Is this an upgrade from an older version that included Group?
> 
> No it's a build from scratch of an ovirt engine appliance.
> I see you have %dir %attr(755, %{user}, %{group}) %{logdir}
> 
> Looking at /usr/lib/rpm/macros.d content I see:
> ./macros.perl:
>   136 : Group: Development/Debug\
> ./macros.scl:
>19 : Group: Development/Debug
> 
> which looks pretty suspicious.
> 
> I think it would be safer using a different macro name for your spec file
> changing:
> %global user ovirtimg
> %global group ovirtimg
> 
> to:
> 
> %global ovirtimg_user ovirtimg
> %global ovirtimg_group ovirtimg
> 
> and use them, avoiding to use generic names like "user" and "group" that
> may conflict with existing macros

thanks for the hint, should be fixed in 
https://gerrit.ovirt.org/110066

> 
> >>   >>  consoleFull#L8,514> 15:18:22,373 INFO anaconda:program:
> >>  
> >>   >>  consoleFull#L8,515> 15:18:22,374 INFO anaconda:program: Running
> >>  scriptlet: ovirt-imageio-daemon-2.0.9-1.el8.x86_64 90/223>> 
> >> Sounds like a bug in the spec file.
> >> 
> >> --
> >> 
> >> Sandro Bonazzola
> >> 
> >> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> >> 
> >> Red Hat EMEA 
> >> 
> >> sbona...@redhat.com
> >> 
> >> 
> >> *Red Hat respects your work life balance. Therefore there is no need to
> >> answer this email out of your office hours.
> >> *



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/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/EMV7XBANC3CA5ZH2PV2H5ITPO3ENXIPB/

[ovirt-devel] Re: Proposing Ales Musil as VDSM network maintainer

[Vojtech Juranek]

On úterý 23. června 2020 13:30:30 CEST Nir Soffer wrote:
> On Mon, Jun 22, 2020 at 1:13 PM Marcin Sobczyk  wrote:
> > On 6/22/20 11:00 AM, Edward Haas wrote:
> >
> >
> >
> > Hello to all VDSM maintainers,
> 
> 
> These discussions should be public.
> Adding devel@ovirt.org
> 
> 
> > I hope I did not miss any active maintainers.
> >
> >
> >
> > I'd like to nominate Ales Musil to formally take over the vdsm-network
> > vertical as a maintainer
 after acting as such in the last period.
> >
> >
> >
> > Would you approve adding him to the vdsm-master-maintainers
> > https://gerrit.ovirt.org/#/admin/groups/106,members list,
> > so he will not be blocked on my availability?
> >
> >
> >
> > +1
> 
> 
> I don't see any problem, so +1.

+1


> Let's wait a few days for more feedback on devel.
> 
> 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/UH3YAS67MICAL
> 34RHH6QZVC5Y3PRZ3OF/



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/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/LNP2CEOYPSGQWFRGOGCQCDISNRHIVOHL/

[ovirt-devel] Re: ssl error during host install

[Vojtech Juranek]

> Sorry, my bad. `systemctl restart ansible-runner-service.service`

this seems to fix the issue. cacert.pem now looks good (with line breaks) and 
host is successfully connected.

Thanks a lot for a quick help!

> And just to be sure please also share `cat
> /etc/ansible-runner-service/config.yaml`
> 
> On Tue, May 19, 2020 at 8:52 AM Vojtech Juranek  wrote:
> > > Does the certificate look the same?
> > 
> > yes
> > 
> > > Maybe try to `systemctl restart httpd `
> > 
> > I'm running engine in developer mode, there's no httpd running, only
> > wildfly
> > on port 8080
> > 
> > > Before the certificate looked okay. (Strange that it ends with
> > > whitespace
> > > and not new line)
> > > 
> > > On Tue, May 19, 2020 at 8:31 AM Vojtech Juranek 
> > 
> > wrote:
> > > > > I do have this patch in engine build, but checking the patch,
> > > > > ansible
> > > > 
> > > > runner
> > > > 
> > > > > on engine is not up-to-date, so maybe this is the cause? Trying to
> > > > > update
> > > > > now.
> > > > 
> > > > now I have on engine machine
> > > > 
> > > > # rpm -qa "*ansible-runner*"
> > > > python3-ansible-runner-1.4.5-1.fc30.noarch
> > > > ansible-runner-service-dev-1.0.2-1.fc30.noarch
> > > > 
> > > > but it didn't help, still same issue



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/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/UIXXVCNZZCTR3KU2S4HN7QYMUZHSZHXR/

[ovirt-devel] Re: ssl error during host install

[Vojtech Juranek]

> I do have this patch in engine build, but checking the patch, ansible runner
> on engine is not up-to-date, so maybe this is the cause? Trying to update
> now.

now I have on engine machine

# rpm -qa "*ansible-runner*"
python3-ansible-runner-1.4.5-1.fc30.noarch
ansible-runner-service-dev-1.0.2-1.fc30.noarch

but it didn't help, still same issue


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/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/G2U73PW4QMYU2XBDLOXZMMN3MZKRIZAV/

[ovirt-devel] ssl error during host install

[Vojtech Juranek]

Hi,
I'm getting following SSL error when adding new host:

engine:

[...]
2020-05-18 18:28:35,530-04 WARN  
[org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] 
(EE-ManagedThreadFactory-engine-Thread-42) [762c711c] Retry failed
2020-05-18 18:28:39,033-04 WARN  
[org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] 
(EE-ManagedThreadFactory-engine-Thread-43) [762c711c] Retry failed
2020-05-18 18:28:39,033-04 ERROR 
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] 
(EE-ManagedThreadFactory-engine-Thread-3) [762c711c] Host installation failed 
for host 'ab082e77-315c-4cfe-8188-11fbee94c2b8', 'fc30-glance': Network error 
during communication with the host

host (vdsm log):

2020-05-18 18:26:36,963-0400 ERROR (Reactor thread) [vds.dispatcher] uncaptured 
python exception, closing channel  (:[X509] no certificate or crl found (_ssl.c:4053) 
[/usr/lib64/python3.7/asyncore.py|readwrite|110] 
[/usr/lib64/python3.7/asyncore.py|handle_write_event|441] 
[/usr/lib/python3.7/site-packages/yajsonrpc/betterAsyncore.py|handle_write|75] 
[/usr/lib/python3.7/site-packages/yajsonrpc/betterAsyncore.py|_delegate_call|173]
 [/usr/lib/python3.7/site-packages/vdsm/sslutils.py|handle_write|190] 
[/usr/lib/python3.7/site-packages/vdsm/sslutils.py|_handle_io|194] 
[/usr/lib/python3.7/site-packages/vdsm/sslutils.py|_set_up_socket|154]) 
(betterAsyncore:184)

Any idea what's wrong and/or how to fix it?

Both engine and host are on FC30, host is installed from standard 
ovirt-release44-pre 
repo and engine is dev build of latest engine master with glance API v2 patches 
[1].

Thanks
Vojta

[1] https://gerrit.ovirt.org/#/q/topic:"Image+Service+API+v2;

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/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/VSM7HZN5EB27ADN6NJFQMN32Y42ZJESO/

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Vojtech Juranek]

> > I'll, but need to look more into it, replacing $(PREFIX) with
> > $(SYSCONF_DIR)
> > doesn't seem to work as SYSCONF_DIR=$(PREFIX)/etc (see https://github.com/
> > oVirt/ovirt-engine/blob/master/Makefile#L41
> > ), so we
> > will end up again with /
> > usr/etc. We will probably have to do it as VMCONSOLE_* variable - hardcode
> > config file and define new just install-dev environment (and do the proper
> > testing before merge)
> 
> No. SYSCONF_DIR=$(PREFIX)/etc allow you to set PREFIX for developer work.

isn't it overwritten here:
https://github.com/oVirt/ovirt-engine/blob/master/Makefile#L37
?

I posted https://gerrit.ovirt.org//c/108672/ which does it in the same way as 
ovirt-vmconsole, but if you prefer using SYSCONFIG_DIR and it work in all 
cases, no problem to change it this way

> But then in spec file it's overridden:
> SYSCONF_DIR=%{_sysconfdir}
> $ rpm --eval "%{_sysconfdir}"
> /etc


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/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/CXYYQNFYIST2NRARPPH345UVTB5G2UL7/

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Vojtech Juranek]

On pondělí 27. dubna 2020 16:47:56 CEST Nir Soffer wrote:
> On Mon, Apr 27, 2020 at 5:37 PM Sandro Bonazzola  
wrote:
> > Il giorno lun 27 apr 2020 alle ore 16:28 Nir Soffer  
ha scritto:
> >> On Mon, Apr 27, 2020 at 5:22 PM Vojtech Juranek  
wrote:
> >> > On pondělí 27. dubna 2020 16:10:11 CEST Nir Soffer wrote:
> >> > > On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg  
wrote:
> >> > > > On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola
> >> > > > 
> >> > > > 
> >> > > > wrote:
> >> > > >> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer
> >> > > >> 
> >> > > >> 
> >> > > >> ha scritto:
> >> > > >>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola
> >> > > >>> 
> >> > > >>> 
> >> > > >>> wrote:
> >> > > >>>> Failing job is
> >> > > >>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> >> > > >>>> 
> >> > > >>>> Here's the relevant log in engine-setup:
> >> > > >>>> 
> >> > > >>>> 
> >> > > >>>> 2020-04-27 09:25:35,457-0400 DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd
> >> > > >>>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
> >> > > >>>> 'ovirt-imageio.service'), executable='None', cwd='None',
> >> > > >>>> env=None
> >> > > >>>> 2020-04-27 09:25:35,652-0400 DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> >> > > >>>> execute-result: ('/usr/bin/systemctl', 'stop',
> >> > > >>>> 'ovirt-imageio.service'), rc=0 2020-04-27 09:25:35,653-0400
> >> > > >>>> DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd plugin.execute:921
> >> > > >>>> execute-output: ('/usr/bin/systemctl', 'stop',
> >> > > >>>> 'ovirt-imageio.service') stdout:
> >> > > >>>> 
> >> > > >>>> 
> >> > > >>>> 2020-04-27 09:25:35,653-0400 DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd
> >> > > >>>> plugin.execute:926 execute-output: ('/usr/bin/systemctl',
> >> > > >>>> 'stop',
> >> > > >>>> 'ovirt-imageio.service') stderr:
> >> > > >>>> 
> >> > > >>>> 
> >> > > >>>> 2020-04-27 09:25:35,653-0400 DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd
> >> > > >>>> systemd.state:170 starting service ovirt-imageio 2020-04-27
> >> > > >>>> 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
> >> > > >>>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start',
> >> > > >>>> 'ovirt-imageio.service'), executable='None', cwd='None',
> >> > > >>>> env=None
> >> > > >>>> 2020-04-27 09:25:36,631-0400 DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> >> > > >>>> execute-result: ('/usr/bin/systemctl', 'start',
> >> > > >>>> 'ovirt-imageio.service'), rc=1 2020-04-27 09:25:36,632-0400
> >> > > >>>> DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd plugin.execute:921
> >> > > >>>> execute-output: ('/usr/bin/systemctl', 'start',
> >> > > >>>> 'ovirt-imageio.service') stdout:
> >> > > >>>> 
> >> > > >>>> 
> >> > > >>>> 2020-04-27 09:25:36,632-0400 DEBUG
> >> > > >>>> otopi.plugins.otopi.services.systemd
> >> > > >>>> plugin.execute:926 execute-output: ('/usr/bin/systemctl',
> >> > > >>>> 'start',
> >> > > >>>> 'ovirt-imageio.service') stderr: Job for ovirt-imageio.service
> >> > > >>>> failed
> >> > > >>>> because the control process exited with error code. See
> >> > > >>>> "systemctl
> >> > > >>

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Vojtech Juranek]

37, version=2.0.5) 2020-04-27 09:25:39,944 ERROR   (MainThread)
> >>> [server] Server failed>>> 
> >>> Traceback (most recent call last):
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> >>>   line 37, in main>>>   
> >>> server = Server(cfg)
> >>>   
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> >>>   line 76, in __init__>>>   
> >>> self.remote_service = services.RemoteService(self.config, self.auth)
> >>>   
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> >>>   line 80, in __init__>>>   
> >>> self._secure_server()
> >>>   
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> >>>   line 95, in _secure_server>>>   
> >>> raise errors.TlsConfigurationError(*required_config)
> >>> 
> >>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls]
> >>> section in daemon.conf), but not configured: ca_file = , cert_file = ,
> >>> key_file =
> >>> 
> >>> This means engine-setup did not create correct configuration file.
> >>> 
> >>> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> >>> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
> >>> need update?
> >>> 
> >>> This works in real setup, so I guess this is another OST environment
> >>> issue.
> >> 
> >> looking at dnf logs:
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exp
> >> orted-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_p
> >> ytest.py/lago-basic-suite-master-engine/_var_log/dnf.rpm.log
> >> 
> >> 2020-04-27T13:16:13Z SUBDEBUG Installed:
> >> ovirt-imageio-common-2.0.5-0.202004260154.gitaf86468.el8.x86_64
> >> 2020-04-27T13:16:13Z SUBDEBUG Installed:
> >> ovirt-imageio-common-2.0.5-0.202004260154.gitaf86468.el8.x86_64
> >> 2020-04-27T13:16:13Z SUBDEBUG Installed:
> >> ovirt-imageio-daemon-2.0.5-0.202004260154.gitaf86468.el8.x86_64
> >> 2020-04-27T13:16:14Z SUBDEBUG Installed:
> >> ovirt-imageio-daemon-2.0.5-0.202004260154.gitaf86468.el8.x86_64
> >> 2020-04-27T13:16:14Z INFO warning: group Development/Debug does not
> >> exist - using root
> >> 
> >> seems like it's getting a recent enough version. What about above
> >> warning?
> > 
> > I had this problem in my local environment. I was running engine-setup
> > with an unprivileged user.
> 
> For make install-dev?
> 
> I think this was fixed here:
> 
> commit 81a5e757fd8768ace825140ca7dc701cc2e011ce
> Author: Vojtech Juranek 
> Date:   Thu Apr 23 11:44:41 2020 +0200
> 
> spec: allow imageio config in dev env
> 
> Add $PREFIX into imageio config directory to allow imageio configuration
> in development environment when config files are installed into a specified
> directory.
> Currently it fails with:
> 
> [Errno 13] Permission denied: '/etc/ovirt-imageio'
> 
> Change-Id: I9e13bba0e97f681b0b07d5a135be76113e391ddc
> Signed-off-by: Vojtech Juranek 
> 
> Maybe this OST runs old engine without this fix?

OST runs in install-dev environment? IIRC not.

Looking into the logs, imageio wasn't properly configured, it seems there's no 
certificate configuration:

ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section 
in daemon.conf), but not configured: ca_file = , cert_file = , key_file =

(from 
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log)

and as Nir wrote, /etc/ovirt-imageio is not archived

looking into otopi log 
(https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-engine/setup/ovirt-engine-setup-20200427091928-9e7d0z.log)
 it looks like the config ws installed into /usr/etc/ovirt-imageio instead of 
into /usr/etc (so far no idea why, also I guess we need to throw clear 
exception if the config file is not found):

2020-04-27 09:25:00,332-0400 DEBUG otopi.transaction transaction.commit:147 
committing 'File transaction for '/usr/etc/ovirt-imageio/daemon.conf''


> > To resolve it, I created a dir: mkdir /etc/ovirt-imageio
> > And I did chown to the user running engine-setup.
> > 
> >> --
> >> 
> >> Sandro Bonazzola
> >> 
> >> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> >> 
> >> Red Hat EMEA <https://www.redhat.com/>
> >> 
> >> sbona...@redhat.com
> >> <https://www.redhat.com/>*
> >> <https://www.redhat.com/en/summit?sc_cid=7013a02D2QxAAK>*
> >> *Red Hat respects your work life balance. Therefore there is no need to
> >> answer this email out of your office hours.*
> >> ___
> >> 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/QS4QG3OMVNZ
> >> YQRCCZNENKRZ7SB3RKIDZ/



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/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/FMSDK2BCNKVDDPAVFMUXV6GJCORSL3FA/

[ovirt-devel] Re: Changing vdsm version installed on host

[Vojtech Juranek]

On úterý 21. dubna 2020 12:50:46 CEST Milan Zamazal wrote:
> Vojtech Juranek  writes:
> 
> 
> > On úterý 21. dubna 2020 10:56:59 CEST Milan Zamazal wrote:
> > 
> >> Nir Soffer  writes:
> >> 
> >
> >
> >
> >> 
> >> 
> >> > On Mon, Apr 20, 2020 at 11:34 PM Vojtech Juranek 
> >> > wrote:
> >> 
> >> 
> >> 
> >> >>
> >> >>
> >> >>
> >> >> On pondělí 20. dubna 2020 22:20:22 CEST Nir Soffer wrote:
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >> > On Mon, Apr 20, 2020 at 11:16 PM Vojtech Juranek
> >> >> > 
> >> >> > wrote:
> >> >> > 
> >> >> > 
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > > Hi,
> >> >> > > can anybody give me a hint which component is responsible for
> >> >> > > installing
> >> >> > > host
> >> >>  
> >> >>  
> >> >>  when I add a host in engine UI? Or how to change vdsm version
> >> >>  
> >> >>  
> >> >> > > installed this way on the host?
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > > It installs vdsm-4.40.2:
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > > [root@localhost ~]# rpm -q ovirt-release44-pre
> >> >> > > ovirt-release44-pre-4.4.0-0.11.beta4.el8.noarch
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > Remove this package and follow the instructions here:
> >> >> > https://github.com/ovirt/vdsm#manual-installation
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> I know how to fix it on my env. I want to fix in appropriate ovirt
> >> >> component
> >  
> >  so that correct vdsm version is installed in next 4.4.pre
> >  
> >> >> release.>
> >> >
> >> >
> >> >
> >> >
> >> > I'm not sure about the semantics of 4.4.pre, but project version is
> >> > configured
> >  
> >  using releng-tools project:
> >  
> >> > https://gerrit.ovirt.org/#/admin/projects/releng-tools
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > This is the last patch adding vdsm:
> >> > https://gerrit.ovirt.org/#/c/108276/
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > Typically the maintainer responsible for the builds is updating
> >> > the version for every release. Looks like vdsm 3.40.13 is missing.
> >> 
> >> 
> >> 
> >> The subject of the patch above is wrong (copy & paste error), it
> >> actually adds v4.40.13.  This version is also available on ovirt.org in
> >> master and pre-4.4.
> >
> >
> >
> > correct, but installed vdsm version is 4.40.2, so any idea what's wrong?
> 
> 
> No idea.  Sandro, Dafna, do you know?


either it's relevant only for CentOS 8.1 or it was some temporal glitch, now I 
added new FC-30 in the same way and everything looks good (vdsm is 4.40.13 and 
imageio runs fine)

> 
> > (btw: it seems it already starts to cause trouble to other people, see 
> > Kaustav's question "Unable to add vdsm host to ovirt-engine" from today on
> > 
 this ML - it seems that this is exactly same issue I spotted yesterday)>
> >
> >
> >> The maintainer adds each release to releng-tools when a build is done
> >> (unless it's superseded by another build immediately) and the build team
> >> is kind enough to ping him in case he doesn't. :-)
> >> 
> >> 
> >> 
> >> > To add it you need to find the on_merge job for last tag which seems
> >> > to
> >> > be:
> >>
> >>
> >>
>

[ovirt-devel] Re: Unable to add vdsm host to ovirt-engine

[Vojtech Juranek]

On úterý 21. dubna 2020 12:38:22 CEST Kaustav Majumder wrote:
> Hi,
> Yes I did try this but
> even after updating it does not work. I see the same issue.
> 
> On Tue, 21 Apr, 2020, 4:06 PM Vojtech Juranek,  wrote:
> > On úterý 21. dubna 2020 8:49:01 CEST Kaustav Majumder wrote:
> > > Hi,
> > > While trying to add a new host to a locally deployed
> > > ovirt-engine(gluster-enabled) ansible runner fails to restart vdsm owing
> > 
> > to
> > 
> > > its dependency on ovirt-imageio.service.
> > > ```
> > > "ansible_loop_var" : "item",
> > > 
> > >   "_ansible_no_log" : false,
> > >   "item" : "vdsmd.service",
> > >   "failed" : true,
> > >   "msg" : "Unable to start service vdsmd.service: A dependency
> > 
> > job
> > 
> > > for vdsmd.service failed. See 'journalctl -xe' for details.\n",
> > > 
> > >   "changed" : false,
> > > 
> > > ```
> > > Checking less /var/log/ovirt-imageio/daemon.log
> > > ```
> > > 2020-04-21 06:46:21,539 INFO(MainThread) [server] Starting
> > 
> > (pid=25592,
> > 
> > > version=2.0.5)
> > > 2020-04-21 06:46:21,546 ERROR   (MainThread) [server] Server failed
> > > 
> > > Traceback (most recent call last):
> > >   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> > >   line
> > > 
> > > 37, in main
> > > 
> > > server = Server(cfg)
> > >   
> > >   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> > >   line
> > > 
> > > 76, in __init__
> > > 
> > > self.remote_service = services.RemoteService(self.config, self.auth)
> > >   
> > >   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> > 
> > line
> > 
> > > 79, in __init__
> > > 
> > > self._secure_server()
> > >   
> > >   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> > 
> > line
> > 
> > > 104, in _secure_server
> > > 
> > > enable_tls1_1=self._config.tls.enable_tls1_1)
> > >   
> > >   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/ssl.py", line
> > 
> > 18,
> > 
> > > in server_context
> > > 
> > > purpose=ssl.Purpose.CLIENT_AUTH, cafile=cafile)
> > >   
> > >   File "/usr/lib64/python3.6/ssl.py", line 468, in
> > >   create_default_context
> > >   
> > > context.load_verify_locations(cafile, capath, cadata)
> > > 
> > > ssl.SSLError: [X509] no certificate or crl found (_ssl.c:3771
> > > ```
> > > Is there a workaround or am I doing something wrong?
> > 
> > there's installed too old vdm version. You need to run
> > dnf update
> > and restart ovirt-imageio and vdsmd services

can you share your /etc/ovirt-imageio/daemon.conf and check that certificated 
configured there exists?


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/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/YON4VLCFHVSLHZ4KYLNQMZLEMUZPRF4S/

[ovirt-devel] Re: Changing vdsm version installed on host

[Vojtech Juranek]

On úterý 21. dubna 2020 10:56:59 CEST Milan Zamazal wrote:
> Nir Soffer  writes:
> 
> 
> > On Mon, Apr 20, 2020 at 11:34 PM Vojtech Juranek 
> > wrote:
> 
> >>
> >>
> >> On pondělí 20. dubna 2020 22:20:22 CEST Nir Soffer wrote:
> >
> >
> >
> >> > On Mon, Apr 20, 2020 at 11:16 PM Vojtech Juranek 
> >> > wrote:
> >> > 
> >> > >
> >> > >
> >> > >
> >> > > Hi,
> >> > > can anybody give me a hint which component is responsible for
> >> > > installing
> >> > > host
> >>  
> >>  when I add a host in engine UI? Or how to change vdsm version
> >>  
> >> > > installed this way on the host?
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > It installs vdsm-4.40.2:
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > [root@localhost ~]# rpm -q ovirt-release44-pre
> >> > > ovirt-release44-pre-4.4.0-0.11.beta4.el8.noarch
> >> >
> >> >
> >> >
> >> >
> >> > Remove this package and follow the instructions here:
> >> > https://github.com/ovirt/vdsm#manual-installation
> >>
> >>
> >>
> >> I know how to fix it on my env. I want to fix in appropriate ovirt
> >> component
 so that correct vdsm version is installed in next 4.4.pre
> >> release.>
> >
> >
> > I'm not sure about the semantics of 4.4.pre, but project version is
> > configured
 using releng-tools project:
> > https://gerrit.ovirt.org/#/admin/projects/releng-tools
> >
> >
> >
> > This is the last patch adding vdsm:
> > https://gerrit.ovirt.org/#/c/108276/
> >
> >
> >
> > Typically the maintainer responsible for the builds is updating
> > the version for every release. Looks like vdsm 3.40.13 is missing.
> 
> 
> The subject of the patch above is wrong (copy & paste error), it
> actually adds v4.40.13.  This version is also available on ovirt.org in
> master and pre-4.4.

correct, but installed vdsm version is 4.40.2, so any idea what's wrong?

(btw: it seems it already starts to cause trouble to other people, see 
Kaustav's question "Unable to add vdsm host to ovirt-engine" from today on 
this ML - it seems that this is exactly same issue I spotted yesterday)

> The maintainer adds each release to releng-tools when a build is done
> (unless it's superseded by another build immediately) and the build team
> is kind enough to ping him in case he doesn't. :-)
> 
> 
> > To add it you need to find the on_merge job for last tag which seems to
> > be:
>
> >
> >
> > commit 3928f7f08287885fd248af08b16379476504e5be (tag: v4.40.13)
> > Author: Milan Zamazal 
> > Date:   Tue Apr 7 14:35:03 2020 +0200
> >
> >
> >
> > New release: 4.40.13
> >
> >
> >
> > You can find it here:
> > https://gerrit.ovirt.org/c/108275/#message-473c8b04_5a25626e
> >
> >
> >
> > Based on this you can prepare a patch.
> >
> >
> >
> > It would be nice if we can automate this process to avoid the manual
> > steps.
>
> >
> >
> >> > > [root@localhost ~]# rpm -q vdsm
> >> > > vdsm-4.40.2-1.el8.x86_64
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > We need newer version of vdsm (at least 4.40.11) to work properly
> >> > > with
> >> > > imageio
> >>  
> >>  2.0.
> >>  
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > vdsm 4.40.13 can be pushed by running dnf update, but it's not very
> >> > > user
> >> > > friendly (moreover imageio service needs to be restarted after update
> >> > > and
> >> > > it's
> >>  
> >>  not obvious for the user t do so), so I'd like to change it to
> >>  
> >> > > install 4.40.13 automatically when installing all other ovirt stuff.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > Thanks
> >> > > Vojta
> >> >
> >> >
> >> >
> >> > ___
> >> > 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/XP6RHEKW4
> >> > 36PX
 43BHCT4WYL4ZNULYR3N/
> >>
> >>
> 
> ___
> 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/YMK4AGVFV3JG6
> FBAQTHWFRLWNKDEHF55/



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/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/I6B3TEBPBDWXXOM4L2JEQYR2H2Y2EQJE/

[ovirt-devel] Re: Unable to add vdsm host to ovirt-engine

[Vojtech Juranek]

On úterý 21. dubna 2020 8:49:01 CEST Kaustav Majumder wrote:
> Hi,
> While trying to add a new host to a locally deployed
> ovirt-engine(gluster-enabled) ansible runner fails to restart vdsm owing to
> its dependency on ovirt-imageio.service.
> ```
> "ansible_loop_var" : "item",
>   "_ansible_no_log" : false,
>   "item" : "vdsmd.service",
>   "failed" : true,
>   "msg" : "Unable to start service vdsmd.service: A dependency job
> for vdsmd.service failed. See 'journalctl -xe' for details.\n",
>   "changed" : false,
> ```
> Checking less /var/log/ovirt-imageio/daemon.log
> ```
> 2020-04-21 06:46:21,539 INFO(MainThread) [server] Starting (pid=25592,
> version=2.0.5)
> 2020-04-21 06:46:21,546 ERROR   (MainThread) [server] Server failed
> Traceback (most recent call last):
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line
> 37, in main
> server = Server(cfg)
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line
> 76, in __init__
> self.remote_service = services.RemoteService(self.config, self.auth)
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line
> 79, in __init__
> self._secure_server()
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line
> 104, in _secure_server
> enable_tls1_1=self._config.tls.enable_tls1_1)
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/ssl.py", line 18,
> in server_context
> purpose=ssl.Purpose.CLIENT_AUTH, cafile=cafile)
>   File "/usr/lib64/python3.6/ssl.py", line 468, in create_default_context
> context.load_verify_locations(cafile, capath, cadata)
> ssl.SSLError: [X509] no certificate or crl found (_ssl.c:3771
> ```
> Is there a workaround or am I doing something wrong?

there's installed too old vdm version. You need to run
dnf update
and restart ovirt-imageio and vdsmd services



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/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/Z7M4UGBH3YCGNWXLOMMSZTFOEI6LZ5TO/

[ovirt-devel] Re: Changing vdsm version installed on host

[Vojtech Juranek]

On pondělí 20. dubna 2020 22:20:22 CEST Nir Soffer wrote:
> On Mon, Apr 20, 2020 at 11:16 PM Vojtech Juranek 
> wrote:
> >
> >
> > Hi,
> > can anybody give me a hint which component is responsible for installing
> > host
 when I add a host in engine UI? Or how to change vdsm version
> > installed this way on the host?
> >
> >
> >
> > It installs vdsm-4.40.2:
> >
> >
> >
> > [root@localhost ~]# rpm -q ovirt-release44-pre
> > ovirt-release44-pre-4.4.0-0.11.beta4.el8.noarch
> 
> 
> Remove this package and follow the instructions here:
> https://github.com/ovirt/vdsm#manual-installation

I know how to fix it on my env. I want to fix in appropriate ovirt component 
so that correct vdsm version is installed in next 4.4.pre release.

> 
> 
> >
> >
> > [root@localhost ~]# rpm -q vdsm
> > vdsm-4.40.2-1.el8.x86_64
> >
> >
> >
> > We need newer version of vdsm (at least 4.40.11) to work properly with
> > imageio
 2.0.
> >
> >
> >
> > vdsm 4.40.13 can be pushed by running dnf update, but it's not very user
> > friendly (moreover imageio service needs to be restarted after update and
> > it's
 not obvious for the user t do so), so I'd like to change it to
> > install 4.40.13 automatically when installing all other ovirt stuff.
> >
> >
> >
> > Thanks
> > Vojta
> 
> ___
> 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/XP6RHEKW436PX
> 43BHCT4WYL4ZNULYR3N/



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/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/PLJ3OIKZYCQG565YLJDT6Y5W4GHHQJ6O/

[ovirt-devel] Changing vdsm version installed on host

[Vojtech Juranek]

Hi,
can anybody give me a hint which component is responsible for installing host 
when I add a host in engine UI? Or how to change vdsm version installed this 
way on the host?

It installs vdsm-4.40.2:

[root@localhost ~]# rpm -q ovirt-release44-pre
ovirt-release44-pre-4.4.0-0.11.beta4.el8.noarch

[root@localhost ~]# rpm -q vdsm
vdsm-4.40.2-1.el8.x86_64

We need newer version of vdsm (at least 4.40.11) to work properly with imageio 
2.0. 

vdsm 4.40.13 can be pushed by running dnf update, but it's not very user 
friendly (moreover imageio service needs to be restarted after update and it's 
not obvious for the user t do so), so I'd like to change it to install 4.40.13 
automatically when installing all other ovirt stuff.

Thanks
Vojta

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/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/M5QYFCM4GAPWYVYMUGF67AFD5EJC2ZJL/

[ovirt-devel] Re: Cannot upload disk image

[Vojtech Juranek]

> Hi all,
> I'm trying to upload disk image to ovirt
> from Events I see next -
> "Transfer was stopped by system. Reason: failed to add image ticket to
> ovirt-imageio-proxy."

imageio is still WIP and currently doesn't work in 4.4.0, this is expected 
result as imageio-proxy was removed
 
> From engine.log
> 2020-04-10 10:40:39,419-04 INFO
>  [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-9)
> [9e43f14b-58a3-429d-a573-0bd8749cb8d8] Transfer was paused by system.
> Upload disk 'cirros' (disk id: 'bc2e150f-6050-4cb1-9b88-54b077a4df8b',
> image id: 'bc855d6a-b046-4b93-b78b-7bc44b64987f')
> 
> I'm new in ovirt world. Can anyone help me with this?
> Ovirt-engine logs from /var/log/ovirt-engine attached
> 
> 
> ovirt-Version - 4.4.0-0.5.beta3.20200408120550.gitf94f968ca81.el8



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/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/EYWRCTL2BGVLT3SVR3HZSHT5BQOHBOI6/

[ovirt-devel] Re: How to install ovirt-engine 4.4? Missing apache-commons-jxpath

[Vojtech Juranek]

> Hi,
> how do I install ovirt-engine 4.4, either pre or master? On CentOS 8 it
> fails with
> 
> oVirt 4.4 Pre-Release   
>
> 218 kB/s | 706 kB
> 00:03 Error:
>  Problem: package
> ovirt-engine-4.4.0-0.5.beta3.20200408120550.gitf94f968ca81.el8.noarch
> requires apache-commons-jxpath, but none of the providers can be installed
> - cannot install the best candidate for the job
>   - package apache-commons-jxpath-1.3-29.module_el8.0.0+30+832da3a1.noarch
> is excluded
> 
> On FC30 there is even more broken packages.
> Any hints how to fix it?

I think Sandro's email announcing 4.4. Beta answers my questions,
dnf module enable -y javapackages-tools pki-deps 389-ds fixes the issue. Now 
have too old postgres, but downloding CentOS 8.1 now and it will probably fix 
it.

Sorry for the rush.

 
> Thanks
> Vojta



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/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/DBPYVJEPTYXZYMWWLYOJCCNJ5BZOIGSV/

[ovirt-devel] How to install ovirt-engine 4.4? Missing apache-commons-jxpath

[Vojtech Juranek]

Hi,
how do I install ovirt-engine 4.4, either pre or master? On CentOS 8 it fails 
with 

oVirt 4.4 Pre-Release   

 218 kB/s | 706 kB 00:03
Error: 
 Problem: package 
ovirt-engine-4.4.0-0.5.beta3.20200408120550.gitf94f968ca81.el8.noarch requires 
apache-commons-jxpath, but none of the providers can be installed
  - cannot install the best candidate for the job
  - package apache-commons-jxpath-1.3-29.module_el8.0.0+30+832da3a1.noarch is 
excluded

On FC30 there is even more broken packages.
Any hints how to fix it?

Thanks
Vojta

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/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/5YZ2AFGP6U7LC2ZTRVV3VKMKXYRLIOL6/

[ovirt-devel] How to add imageio configuration into engine?

[Vojtech Juranek]

Hi,
I'd like to add imageio configuration into engine. Previously, it was done by 
dedicated setup code in imageio-proxy [1], but in new imageio we remove the 
proxy package and to configure imageio for engine we need just to place 
firewalld and imageio config files into proper place.

Initial idea was to do it directly in engine spec file, but it seems to me 
that configuration of the engine is done by dedicated packages and custom 
code. Ansible roles in packaging/ansible-runner-service-project seem to be 
only for host configuration. 

What is a proper way how to configure imageio?

Thanks
Vojta

[1] https://github.com/oVirt/ovirt-imageio/tree/master/proxy/setup

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/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/B37AHP52UKPHLXHKO6X6QHEOWRQTV5AB/

[ovirt-devel] Re: Proposing Benny Zlotnik as an Engine Storage maintainer

[Vojtech Juranek]

> +1
> well deserved!

+1
 
> On Sun, Feb 23, 2020 at 6:49 PM Roy Golan  wrote:
> > On Sun, 23 Feb 2020 at 12:30, Fred Rolland  wrote:
> >> +1
> >> 
> >> On Fri, Feb 21, 2020 at 8:53 PM Tal Nisan  wrote:
> >>> Hi everyone,
> >>> Benny joined the Storage team in November 2016 and since then played a
> >>> key role in investigating very complex customer bugs around oVirt engine
> >>> as
> >>> well as contributing to features such as DR, Cinberlib, new
> >>> export/import
> >>> mechanism and also rewrote and still maintains the LSM mechanism.
> >>> Given his big contribution and knowledge around the engine I'd like to
> >>> nominate Benny as an engine storage maintainer.
> >>> 
> >>> Your thoughts please.
> >>> Tal.
> > 
> > +2 :)
> > 
> > ___
> > 
> >>> 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/G52XI2QDSJ
> >>> NAOMZURGAFQJH2RZIHJBRX/>> 
> >> ___
> >> 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/GRZXZEA3MQK
> >> OVCILNQZZVAZ64HMPYQOQ/> 
> > ___
> > 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/TRNHBAOMERUW
> > GUFFFSWDP323BVB3D4R3/



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/JIR4PZXR2ATGMCPV3BNMRMTFWAK2TYD7/

[ovirt-devel] Re: Promotion of Eyal Shenitzky to RHV Storage team lead

[Vojtech Juranek]

On pondělí 20. ledna 2020 13:59:48 CET Tal Nisan wrote:
> Hello,
> Today I have the pleasure of announcing Eyal Shenitzky's promotion to team
> lead in the RHV Storage team.
> Eyal joined our team in August 2017 and since then became an integral part
> of the team and had a key role in features such as DR, Cinberlib,
> Incremental Backup, LSM and among others.
> For the last months Eyal also took the role of the team's scrum master and
> maintaining of our team's Kanban board and tasks.
> 
> Please join me in congratulating Eyal!

congrats, very well deserved!


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/HLMRIFTDWPGY3NHR2CEFYRZARFNXYIVC/

[ovirt-devel] Re: OST manual suite fails for more than a month

[Vojtech Juranek]

> Ran it myself now on master just to have a baseline [1], it fails with:
> 
> *17:34:58* # verify_add_all_hosts: ERROR (in 0:20:07)
> 
>   ts_manual/6329/console#L2,456>*17:34:58* @ Run test: 002_bootstrap.py: ERROR
> (in 0:27:56)
> 
>   ts_manual/6329/console#L2,457>*17:34:58* Error occured, aborting
> 
> 
> Who can have a look?
> 

in this case it's an issue with certificates [2]:

Caused by: javax.net.ssl.SSLPeerUnverifiedException: Certificate for  doesn't match any of the subject alternative names: 
[lago-basic-suite-master-host-1]

However, there are more issues. Some runs fail probably due to BZ #1776843 [3] 
(possible workaround for it is [4]), however, in some cases it works (run on a 
different machine with RHEL7?) and eventually fails in 098_ovirt_provider_ovn 
test as storage become unavailable [5] - this issue was discussed here (thread 
"OST fails, nothing provides nmstate") with no clear resolution IIRC.

SO IMHO number of OST issues seems to cumulate (just saying ... I know I can 
sit down, debug and send patches:-)

> 
> [1]
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests
> _manual/6329/console

[2] 
https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6329/artifact/exported-artifacts/test_logs/basic-suite-master/
post-002_bootstrap.py/lago-basic-suite-master-engine/_var_log/ovirt-engine/
engine.log
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1776843
[4] https://gerrit.ovirt.org/106120/
[5] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6317/artifact/
exported-artifacts/test_logs/basic-suite-master/
post-098_ovirt_provider_ovn.py/lago-basic-suite-master-host-1/_var_log/vdsm/
vdsm.log

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/FQRFQL7UUMHMEDEGFOYRRXCATIEPD5ZZ/

[ovirt-devel] Re: Proposing Vojtech Juranek as VDSM Storage maintainer

[Vojtech Juranek]

> On Tue, Nov 26, 2019 at 4:57 PM Tal Nisan  wrote:
> > Hi everyone,
> > Vojtech joined the Storage team 15 months ago and was quickly thrown by us
> > into the deep and stormy waters of VDSM
> > This past year and a bit Vojtech managed to dive quickly into VDSM and
> > played a key part in the 4K blocks feature, Python3 transformation, RHEL8
> > host support and numerous tests addition, code review and refactors.
> > Vojtech has managed to have more than 200 VDSM patches merged this year
> > and if you're a VDSM developer you probably know this is nothing trivial
> > :)
> > Given the deep knowledge Vojtech acquired and the responsibility he showed
> > in the reviews, tests and verification I'd like to nominate Vojtech as a
> > VDSM Storage maintainer.
> > 
> > Your thoughts please.
> 
> Vojtech did awesome work since he joined. I often use his work as an example
> for other contributors and I trust him to take care of vdsm storage.
> 
> Since we have enough support from other contributors, I have added Vojtech
> to
> vdsm-master maintainers group:
> https://gerrit.ovirt.org/#/admin/groups/106,members

thanks all for your trust and nice words!
 
> Vojtech, use your new powers with care!

will do


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/X6SLSAWA4OYV4VRJMMW3VJXFAQZ22MG6/

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

[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] OST fails, nothing provides nmstate

[Vojtech Juranek]

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 
[...]

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

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/4K5N3VQN26BL73K7D45A2IR7R3UMMM23/

[ovirt-devel] Re: Proposing Marcin Sobczyk as VDSM infra maintainer

[Vojtech Juranek]

+1 

> +1
> 
> On Fri, Nov 8, 2019 at 2:01 AM Amit Bawer  wrote:
> > +1
> > 
> > On Thursday, November 7, 2019, Francesco Romani 
> > 
> > wrote:
> >> On 11/7/19 3:13 PM, Martin Perina wrote:
> >> 
> >> Hi,
> >> 
> >> Marcin has joined infra team more than a year ago and during this time he
> >> contributed a lot to VDSM packaging, improved automation and ported all
> >> infra team parts of VDSM (jsonrpc, ssl, vdms-client, hooks infra, ...) to
> >> Python 3. He is a very nice person to talk, is usually very responsive
> >> and
> >> takes care a lot about code quality.
> >> 
> >> So I'd like to propose Marcin as VDSM infra maintainer.
> >> 
> >> Please share your thoughts.
> >> 
> >> 
> >> +1
> >> 
> >> --
> >> Francesco Romani
> >> Senior SW Eng., Virtualization R
> >> Red Hat
> >> IRC: fromani github: @fromanirh
> >> 
> >> ___
> > 
> > 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/FKTSHNJ7YLZW
> > VTZJQ62HQPV3XGRWG2HU/



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/LN57UVYEFKDJLNVDNMP75MVTKE3PYFNB/

[ovirt-devel] Re: Building vdsm repo fails in CI

[Vojtech Juranek]

> Hi,
> 
> We had an issue spawning el8 mock env and while fixing it it seems that
> specific build was affected. I see all consecutive builds succeeded. Please
> let us know if you encounter any further failures.

thanks! I can confirm it works now.

> On Wed, Nov 6, 2019 at 6:08 PM Vojtech Juranek  wrote:
> > Hi,
> > when I try to build vdsm repo in Jenkins, it fails with
> > 
> >  ERROR: Command failed:
> > 16:22:41 # /usr/bin/yum --installroot /var/lib/mock/epel-8-
> > ppc64le-873106fe041e712f3fe68fbbfa530ba7-bootstrap-5067/root/ --releasever
> > 8
> > install dnf dnf-plugins-core distribution-gpg-keys
> > --setopt=tsflags=nocontexts
> > 16:22:41 Failed to set locale, defaulting to C
> > 16:22:41 Error: Package: python3-dnf-4.0.9.2-5.el8.noarch
> > (centos-base-el8)
> > 16:22:41 Requires: python3-libdnf >= 0.22.5-3
> > 
> > see e.g. [1].
> > 
> > Could someone take a look? It blocks any OST testing.
> > 
> > Thanks
> > Vojta
> > 
> > [1]
> > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/13877/consoleFull
> > ___
> > Infra mailing list -- in...@ovirt.org
> > To unsubscribe send an email to infra-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/in...@ovirt.org/message/TZ6S3OYHUQDJ
> > SJBN5F5U4CDW3YXI3TUL/



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/ZIRCC5BPZQXAT5G4KMVWLFNVJNGNUDMS/

[ovirt-devel] Building vdsm repo fails in CI

[Vojtech Juranek]

Hi,
when I try to build vdsm repo in Jenkins, it fails with 

 ERROR: Command failed:
16:22:41 # /usr/bin/yum --installroot /var/lib/mock/epel-8-
ppc64le-873106fe041e712f3fe68fbbfa530ba7-bootstrap-5067/root/ --releasever 8 
install dnf dnf-plugins-core distribution-gpg-keys --setopt=tsflags=nocontexts
16:22:41 Failed to set locale, defaulting to C
16:22:41 Error: Package: python3-dnf-4.0.9.2-5.el8.noarch (centos-base-el8)
16:22:41 Requires: python3-libdnf >= 0.22.5-3

see e.g. [1].

Could someone take a look? It blocks any OST testing.

Thanks
Vojta

[1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/13877/consoleFull

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/TZ6S3OYHUQDJSJBN5F5U4CDW3YXI3TUL/

[ovirt-devel] Re: qemu-img process stuck

[Vojtech Juranek]

> On Thu, Oct 24, 2019 at 12:53 PM Vojtech Juranek 
> wrote:
> >
> >
> > Hi,
> > I'm doing some manual storage tests on RHEL 8.1 host (kernel version
> > 4.18.0-107.el8.x86_64)
 and run into following issue: when I try to move
> > an image to block SD and RHEL 8.1 host is SPM, qemu-img gets stuck. There
> > are errors regarding blk_cloned_rq_check_limits on RHEL host and also
> > max_write_same_len on iscsi target (see bellow). iscsi target runs CentOS
> > 7.6.>
> >
> >
> > Before running qemu-img command, everything works fine (e.g. cat a file
> > from iscsi target),
 after running qemu-img, all IO on iscsi target is
> > very slow.
> >
> >
> >
> > When I try to run qemu-img command manually, it's very slow (1GB image
> > take several minutes),
 but finishes, when it's run from vdsm, it seems
> > to be hung forever.
> 
> qemu-img is using BLKZEROOUT to write zeroes quickly, and this uses
> SCSI WRITE_SAME
> in the kernel.
> 
> 
> > In similar cases I found it could be fixed by adjusting various values in
> > /sys/block/#DEVICE/queue/, but in this case, AFAICT all values are correct
> > (same as on CentOS 7.7
 host where everything work). Or it was identified
> > as a bug in the kernel and was suggested to upgrade to newer kernel.
> >
> >
> >
> > Do you know any workaround, how to make it working? Or does it sound to
> > you like a bug in kernel
 which should be reported?
> 
> 
> The issue is that the client kernel see wrong value of
> max_write_same_len. For some reason it thinks
> that the value is 65535 sectors (32MiB) but the value defined on the
> server is only 4096 sectors
> (2 MiB). When qemu-img issue WRITE_SAME with wrong payload size, the
> server reject the
> request and then the client treat this as a fatal error.
> 
> You can fix this by configuring these attributes on the server side:
> 
> $ targetcli /backstores/fileio/my-disk set attribute \
> emulate_tpu=1 \
> emulate_tpws=1 \
> max_write_same_len=65335
> 
> - emulate_tpu enables discard
> - emulate_tpws enables write_same
> - max_write_same_len matches what the client see

Thanks a lot!
I tired this at the beginning of the week and doesn't work, but had no time to 
investigate what's wrong. Today I returned back to it and works. In meantime i 
replaced one iSCSI target running on CentOS 7.6 by new one on CentOS 7.7 - but 
sure if it matter or not, though.

> You can test the settings using blkdiscard like this:
> 
> 1. Set max_write_same_len attribute on a backstore
> 2. login to the iscsi server
> 3. zero the LUN with that you modified on the server
> 
> blkdiscard -z /dev/mapper/xxxyyy
> 
> I think this is a kernel bug, but not sure if this on the initiator or
> target
 side.
> 
> Nir
> 
> 
> 
> Nir
> ___
> 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/ZJNDB7LABRW2X
> DYMKPXSHEIMWT23NBZM/



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/WK4LX4YGVQ4FC265G6MMKBLQ6PDSUOY5/

[ovirt-devel] [vdsm] Standard patch check broken by Black formatter for network stuff

[Vojtech Juranek]

Hi,
standard patch check tests for vdsm are broken due to Black formatter check 
failure (see e.g. [1]): 

Oh no! 
10:16:24  6 files would be reformatted, 164 files would be left unchanged.
10:16:24  ERROR: InvocationError for command /home/jenkins/workspace/
vdsm_standard-check-patch/vdsm/.tox/black/bin/black -l 79 -S --check ./lib/
vdsm/network/ ./tests/network (exited with code 1)

Can someone take a look and fix it? I did a quick check and wasn't able to 
find any recent commit which should cause this failure:-(

Thanks
Vojta

[1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/13396

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/VD6LJ5A7Q3MX6TCRSWKPN6SRJJXOP55Q/

[ovirt-devel] qemu-img process stuck

[Vojtech Juranek]

Hi,
I'm doing some manual storage tests on RHEL 8.1 host (kernel version 
4.18.0-107.el8.x86_64)
and run into following issue: when I try to move an image to block SD and RHEL 
8.1 host is SPM,
qemu-img gets stuck. There are errors regarding blk_cloned_rq_check_limits on 
RHEL host 
and also max_write_same_len on iscsi target (see bellow). iscsi target runs 
CentOS 7.6.

Before running qemu-img command, everything works fine (e.g. cat a file from 
iscsi target),
after running qemu-img, all IO on iscsi target is very slow. 

When I try to run qemu-img command manually, it's very slow (1GB image take 
several minutes),
but finishes, when it's run from vdsm, it seems to be hung forever.

In similar cases I found it could be fixed by adjusting various values in 
/sys/block/#DEVICE/queue/, but in this case, AFAICT all values are correct 
(same as on CentOS 7.7
host where everything work). Or it was identified as a bug in the kernel and 
was suggested to 
upgrade to newer kernel.

Do you know any workaround, how to make it working? Or does it sound to you 
like a bug in kernel
which should be reported?

Thanks
Vojta

Example of qemu-img command:

[root@localhost ~]#/usr/bin/qemu-img convert -p -t none -T none -f raw 
/rhev/data-center/mnt/blockSD/ceba76d5-9d5d-4b04-9226-dffc7e77d4be/images/9aafce3d-53a6-41d7-b0d5-0e1db8aa59fc/7b7c7800-4837-4c3f-967c-c942b9c54e1b
 -O raw -W 
/rhev/data-center/mnt/blockSD/a17d7695-50fc-412e-abc7-008ebb6cdf23/images/9aafce3d-53a6-41d7-b0d5-0e1db8aa59fc/7b7c7800-4837-4c3f-967c-c942b9c54e1b
(100.00/100%)


Errors on RHEL 8.1 host:

[  356.658973] print_req_error: critical target error, dev dm-8, sector 
31203328 flags 9
[  356.658982] print_req_error: critical target error, dev dm-8, sector 
31268863 flags 9
[  356.658984] print_req_error: critical target error, dev dm-8, sector 
31334398 flags 9
[  356.658986] print_req_error: critical target error, dev dm-8, sector 
31399933 flags 9
[  356.658987] print_req_error: critical target error, dev dm-8, sector 
31465468 flags 9
[  356.658989] print_req_error: critical target error, dev dm-8, sector 
31531003 flags 9
[  356.658999] print_req_error: critical target error, dev dm-8, sector 
31596538 flags 9
[  356.659001] print_req_error: critical target error, dev dm-8, sector 
31662073 flags 9
[  356.659008] blk_cloned_rq_check_limits: over max size limit.
[  356.659044] device-mapper: multipath: Failing path 8:80.
[  356.669966] print_req_error: critical target error, dev dm-8, sector 
31727608 flags 9
[  356.669987] print_req_error: critical target error, dev dm-8, sector 
31793143 flags 9
[  358.923614] device-mapper: multipath: Reinstating path 8:80.
[  358.933888] sd 6:0:0:4: alua: port group 00 state A non-preferred supports 
TOlUSNA
[  358.933980] blk_cloned_rq_check_limits: over max size limit.
[  358.934008] device-mapper: multipath: Failing path 8:80.
[  364.927647] device-mapper: multipath: Reinstating path 8:80.
[  364.956799] sd 6:0:0:4: alua: port group 00 state A non-preferred supports 
TOlUSNA
[  364.956890] blk_cloned_rq_check_limits: over max size limit.

[...]

[  475.001255] blk_cloned_rq_check_limits: over max size limit.
[  475.001271] device-mapper: multipath: Failing path 8:80.
[  479.995729] device-mapper: multipath: Reinstating path 8:80.
[  480.006078] sd 6:0:0:4: alua: port group 00 state A non-preferred supports 
TOlUSNA
[  480.006114] blk_cloned_rq_check_limits: over max size limit.
[  480.006134] device-mapper: multipath: Failing path 8:80.
[  484.997257] device-mapper: multipath: Reinstating path 8:80.
[  485.006868] sd 6:0:0:4: alua: port group 00 state A non-preferred supports 
TOlUSNA
[  485.006908] blk_cloned_rq_check_limits: over max size limit.
[  485.006960] device-mapper: multipath: Failing path 8:80.
[  489.998641] device-mapper: multipath: Reinstating path 8:80.
[  490.010288] sd 6:0:0:4: alua: port group 00 state A non-preferred supports 
TOlUSNA
[  490.010430] blk_cloned_rq_check_limits: over max size limit.
[  490.010455] device-mapper: multipath: Failing path 8:80.
[  492.922671] INFO: task qemu-img:9509 blocked for more than 120 seconds.
[  492.922675]   Tainted: G - -t - 
4.18.0-107.el8.x86_64 #1
[  492.922676] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  492.922677] qemu-imgD0  9509   7416 0x0080
[  492.922679] Call Trace:
[  492.922703]  ? __schedule+0x253/0x830
[  492.922704]  schedule+0x28/0x70
[  492.922705]  schedule_timeout+0x26d/0x390
[  492.922711]  ? blk_flush_plug_list+0xd7/0x100
[  492.922713]  io_schedule_timeout+0x19/0x40
[  492.922714]  wait_for_completion_io+0x11f/0x190
[  492.922717]  ? wake_up_q+0x70/0x70
[  492.922719]  submit_bio_wait+0x5b/0x80
[  492.922728]  blkdev_issue_zeroout+0x142/0x220
[  492.922737]  blkdev_fallocate+0x11e/0x190
[  492.922745]  vfs_fallocate+0x13f/0x280
[  492.922753]  ksys_fallocate+0x3c/0x80
[  492.922754]  __x64_sys_fallocate+0x1a/0x20
[  492.922756]  

[ovirt-devel] Re: workaround for the lack of native el8 slaves in the CI

[Vojtech Juranek]

On středa 16. října 2019 10:53:45 CEST Marcin Sobczyk wrote:
> Hi all,
> 
> we're trying to move vdsm tests to el8.
> 
> AFAIK we don't have native el8 slaves in the CI yet, so our el8 stages run
> on el7 with el8 mocked.
> There are some issues with scripts setting up the env for storage tests -
> they are refusing to work on older
> kernel versions.
> 
> I have an idea for a workaround - until now we were using 'host-distro:
> same' in our
> 'stdci.yaml'. I can see that this option can also take a value of
> 'better/newer' [1], but that won't work
> for el8. Could we possibly implement something like [2] ? That would allow
> us to i.e. define an el8
> mocked env with 'host-distro: fc30' enforcing native fc30 host. I assume
> this would be a temporary
> workaround only, until we have native el8 slaves.

if it works, it would be great


> Regards, Marcin
> 
> [1]
> https://github.com/oVirt/jenkins/blob/a796094bfd15f1a85b9f630aaeb25ce6e0dab3
> 5d/pipelines/libs/stdci_runner.groovy#L127 [2]
> https://gerrit.ovirt.org/#/c/104091/



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/V765YTTZLZV4O7QOCTGUXAOJLKECDFTB/

[ovirt-devel] Re: Problem with vdsm 'make check'

[Vojtech Juranek]

> Thanks for pointing that out. Right now the only isssue is upgrading tox
> I guess.

yes. Fedora provides only 3.5, so you need to upgrade it via pip (and make 
sure you use one installed via pip and not from package if you previously 
installed it)

> ```
> [kmajumde:~/work/git/vdsm] master+* 2 ± make check
> Makefile:1029: warning: overriding recipe for target 'check-recursive'
> Makefile:548: warning: ignoring old recipe for target 'check-recursive'
> Checking that .in files are ignored...
> ! git --no-pager grep execCmd `git ls-files | grep -v -F -f
> execcmd-blacklist.txt`
> out=`tox --version`; \
> if [ $? -ne 0 ]; then \
> echo "Error: cannot run tox, please install tox \
> 3.14 or later"; \
> exit 1; \
> fi; \
> version=`echo $out | cut -d' ' -f1`; \
> if python2.7 build-aux/vercmp $version 3.14; then \
> echo "Error: tox is too old, please install tox \
> 3.14 or later"; \
> exit 1; \
> fi
> Error: tox is too old, please install tox   3.14 or later
> make: *** [Makefile:1012: tox] Error 1
> ```
> 
> On Mon, Oct 14, 2019 at 10:42 PM Benny Zlotnik  wrote:
> > did you run autogen.sh?
> > 
> > On Mon, Oct 14, 2019 at 7:12 PM Kaustav Majumder 
> > 
> > wrote:
> > > Yes i did but same issue.
> > > 
> > > On Mon, Oct 14, 2019 at 7:55 PM Marcin Sobczyk 
> > 
> > wrote:
> > >> Hi,
> > >> 
> > >> On 10/14/19 3:06 PM, Kaustav Majumder wrote:
> > >> 
> > >> 
> > >> Hi,
> > >> I am having an issue running make check on vdsm master.
> > >> 
> > >> `
> > >> if [ -n "$NOSE_WITH_COVERAGE" ]; then \
> > >> 
> > >> mv .coverage .coverage-nose-py27; \
> > >> 
> > >> fi
> > >> 
> > >> Traceback (most recent call last):
> > >>   File "../tests/testrunner.py", line 70, in 
> > >>   
> > >> from vdsm import constants
> > >>   
> > >>   File "/home/kmajumde/work/git/vdsm/lib/vdsm/constants.py", line 29,
> > 
> > in 
> > 
> > >> from vdsm.common.constants import *  # NOQA: F401, F403
> > >> 
> > >> `
> > >> Am I missing something? Do I need to run tests differently?
> > >> 
> > >> did you run plane 'make' before 'make check'?
> > >> 
> > >> --
> > >> 
> > >> Thanks,
> > >> 
> > >> Kaustav Majumder
> > >> 
> > >> 
> > >> ___
> > >> 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/MTWRVTRJ5DLD
> > VOWHW6RZWBLMETZ3NYCM/> 
> > > --
> > > 
> > > Thanks,
> > > 
> > > Kaustav Majumder
> > > 
> > > ___
> > > 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/7R35UEDCP4WE
> > LAQT5EHG6U72LWQFUGSK/



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/433TI2GA37QFFA4G4NB53JXENH2OZOEF/

[ovirt-devel] Re: OST fails

[Vojtech Juranek]

> I've stumbled upon similar problem on my local ost run,

should be already fixed, thanks to Galit.

> although I have even more unsatisfied rpm dependencies [1]
> 
> Andrej
> 
> [1] http://pastebin.test.redhat.com/798792
> 
> On Tue, Sep 17, 2019 at 4:46 PM Vojtech Juranek  wrote:
> > Hi,
> > OST has started to fail during today, fails with unsatisfied rpm
> > dependencies,
> > e.g.
> > 
> > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp
> > ovirt-engine
> > ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins
> > cronie
> > Error: Package: rsyslog-mmjsonparse-8.24.0-38.el7.x86_64 (alocalsync)
> > 
> > Requires: rsyslog = 8.24.0-38.el7
> > Installed: rsyslog-8.24.0-34.el7.x86_64 (installed)
> > 
> > rsyslog = 8.24.0-34.el7
> > 
> > and many more, see [1] for more details.
> > 
> > Any idea what's wrong?
> > 
> > Thanks
> > Vojta
> > 
> > 
> > [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5601/console
> > ___
> > 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/AY6D4RVQWSAQ
> > ORJHWGW2ZY3OPW2ZDY4H/



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/O7FT7IUHPDCWULFQIP5UAYYFWXW6RDFP/

[ovirt-devel] OST fails

[Vojtech Juranek]

Hi,
OST has started to fail during today, fails with unsatisfied rpm dependencies, 
e.g.

+ yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine 
ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins 
cronie
Error: Package: rsyslog-mmjsonparse-8.24.0-38.el7.x86_64 (alocalsync)
Requires: rsyslog = 8.24.0-38.el7
Installed: rsyslog-8.24.0-34.el7.x86_64 (installed)
rsyslog = 8.24.0-34.el7

and many more, see [1] for more details.

Any idea what's wrong?

Thanks
Vojta


[1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5601/console

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/AY6D4RVQWSAQORJHWGW2ZY3OPW2ZDY4H/

[ovirt-devel] Re: CI: vdsm-standard-check-patch fails

[Vojtech Juranek]

On čtvrtek 8. srpna 2019 14:57:12 CEST Amit Bawer wrote:
> its not always applicable. for example like in poc where we need to get
> same branch working in different envs and not wanting to deal with lots of
> cherry-picks from different branches.

as a workaround you can run tests in Travis which runs tests only for the 
latest commit. The flow can be (and I use it) - submit smaller batch of 
patches which are ready into gerrit and poke people to review them and merge, 
in meantime work on your current branch and push changes for testing into 
Travis.

> On Thu, Aug 8, 2019 at 3:16 PM Milan Zamazal  wrote:
> > Amit Bawer  writes:
> > > On Thu, Aug 8, 2019 at 2:50 PM Marcin Sobczyk 
> > 
> > wrote:
> > >> On 8/8/19 1:44 PM, Amit Bawer wrote:
> > >> 
> > >> 
> > >> 
> > >> On Thu, Aug 8, 2019 at 12:48 PM Milan Zamazal 
> > 
> > wrote:
> > >>> Amit Bawer  writes:
> > >>> > On Wed, Aug 7, 2019 at 3:14 PM Nir Soffer 
> > 
> > wrote:
> > >>> >> On Wed, Aug 7, 2019 at 3:06 PM Amit Bawer 
> > 
> > wrote:
> > >>> >>> On Wed, Aug 7, 2019 at 2:53 PM Nir Soffer 
> > 
> > wrote:
> > >>>  On Wed, Aug 7, 2019 at 1:23 PM Amit Bawer 
> > 
> > wrote:
> > >>> > On Wed, Aug 7, 2019 at 11:19 AM Amit Bawer 
> > >>> 
> > >>> wrote:
> > >>> >> On Tue, Aug 6, 2019 at 5:07 PM Nir Soffer 
> > >>> 
> > >>> wrote:
> > >>> >>> On Tue, Aug 6, 2019 at 5:01 PM Amit Bawer 
> > >>> 
> > >>> wrote:
> > >>>  On Tue, Aug 6, 2019 at 4:58 PM Nir Soffer  > >>>  
> > >>>  wrote:
> > >>> > On Tue, Aug 6, 2019 at 11:27 AM Amit Bawer <
> > 
> > aba...@redhat.com>
> > 
> > >>> > wrote:
> > >>> >> I have seen some improvement: when I re-trigger the CI per
> > >>> 
> > >>> patch I
> > >>> 
> > >>> >> am able to pass or get the actual test errors if any (if
> > >>> >> not
> > >>> 
> > >>> on first try,
> > >>> 
> > >>> >> then on second one).
> > >>> >> Probably not a very useful information, but I have noticed
> > 
> > that
> > 
> > >>> >> when I push 30+ patches at the same
> > >>> > 
> > >>> > Do not do that, jenkins cannot handle 30 concurrent builds,
> > 
> > and
> > 
> > >>> is
> > >>> 
> > >>> > it also bad for reviewers,
> > >>> > getting several mails about every patch in your chain, for
> > 
> > every
> > 
> > >>> > rebase.
> > >>>  
> > >>>  Is there is a way to prevent CI from running per gerrit push
> > >>>  (without working on 30 different branches) ?
> > >>> >>> 
> > >>> >>> I don't know about such way.
> > >>> >> 
> > >>> >> A legit option could be adding the Skip CI plugin to jenkins
> > >>> 
> > >>> plugins
> > >>> 
> > >>> >> [1]; with that devs can add "[skip ci]" to their commit
> > >>> >> messages
> > >>> 
> > >>> to prevent
> > >>> 
> > >>> >> jenkins from automatically launching CI upon push.
> > >>>  
> > >>>  Do you want to modify the commit message for every patch to
> > >>>  decide
> > >>> 
> > >>> if ci
> > >>> 
> > >>>  should run or not?
> > >>> >>> 
> > >>> >>> I think that having the option to knowingly disable automated CI
> > >>> >>> in
> > >>> 
> > >>> some
> > >>> 
> > >>> >>> cases is useful. We could always re-trigger when time is right
> > >>> >>> [3].
> > >>> >>> [3]
> > 
> > https://jenkins.ovirt.org/login?from=%2Fgerrit_manual_trigger%2F
> > 
> > >>> >> This is too much work, but I think today we can add a comment to
> > 
> > gerrit
> > 
> > >>> >> like
> > >>> >> 
> > >>> >> ci please test
> > >>> >> 
> > >>> >> That will trigger a build of this patch.
> > >>> > 
> > >>> > Indeed, but it leaves the "Continuous-Integration" mark untouched in
> > >>> > gerrit, giving the wrong impression this patch is still CI failed.
> > >>> 
> > >>> No, it updates CI score.  I use it routinely with falsely failed
> > >>> tests.
> > >>> 
> > >>> In my experience, CI score may not get updated if there are concurrent
> > >>> builds, such as when you upload a new version of a patch while CI is
> > >>> still running on the previous version.
> > >> 
> > >> I may have missed something, but i tried "ci build" gerrit comment on
> > 
> > one
> > 
> > >> of the CI failed patches https://gerrit.ovirt.org/#/c/101357/
> > >> the CI build passed, but CI indicator is still -1. AFAICT I had no
> > >> other
> > >> CI jobs running at the time.
> > >> 
> > >> "ci build" runs only the "build-artifacts" stage. To affect the score
> > 
> > (and
> > 
> > >> run the tests as a matter of fact) you should use "ci test".
> > > 
> > > Thanks for the clarification, good to know.
> > > So that only leaves the "how do disable automated CI upon gerrit push"
> > > issue.
> > 
> > One solution of the problem might be to have smaller batches of unmerged
> > patches.  If we could review and merge patches faster, it would be less
> > burden for everybody, including CI infrastructure.
> > 
> > >>> > The re-trigger UI takes care for that as well.
> > 

[ovirt-devel] Jenkins build fails to clone gerrit repo

[Vojtech Juranek]

Hi,
lots of Jenkin jobs fail as they cannot fetch git repo from gerrit:

17:35:32  Fetching upstream changes from https://gerrit.ovirt.org/vdsm
17:35:32   > git --version # timeout=10
17:35:32   > git fetch --tags --progress https://gerrit.ovirt.org/vdsm 
+refs/heads/*:refs/remotes/origin/*
17:36:38  ERROR: Error cloning remote repo 'origin'
17:36:38  hudson.plugins.git.GitException: Command "git fetch --tags --progress 
https://gerrit.ovirt.org/vdsm +refs/heads/*:refs/remotes/origin/*" returned 
status code 128:
17:36:38  stdout: 
17:36:38  stderr: error: RPC failed; result=22, HTTP code = 502
17:36:38  fatal: The remote end hung up unexpectedly

see e.g. [1, 2, 3] for more details, to name couple of examples.

Can someone take a look?
Thanks
Vojta

[1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8277/console
[2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8285/console
[3] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8291/console

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/KMTRVLFWG344Q5ULEOR3CXI777WFFEWR/

[ovirt-devel] Re: OST fails, cannot connect to repo

[Vojtech Juranek]

> it seems like you are downloading from external mirror.
> please use local mirrors (this fix should be done in you project)

can you explain what actually I should fix? It fails to download gluster-
ansible. I work on vdsm and it has no dependency on gluster-ansible AFAICT, so 
I have no idea what I should fix in "my" project.

Thanks
 
> 
> On Thu, Jul 18, 2019 at 10:42 AM Vojtech Juranek 
> 
> wrote:
> > Hi,
> > OST fails with
> > 
> > 09:47:03
> > https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/
> > epel-7-x86_64/repodata/repomd.xml
> > <https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-> 
> > > 7-x86_64/repodata/repomd.xml>: [Errno 14] curl#7 - "Failed connect to
> > copr-be.cloud.fedoraproject.org:443; Connection refused"
> > 
> > see e.g. [1] for full log. Stared to fail this morning.
> > Can anyone take a look and fix it?
> > 
> > Thanks in advance.
> > Vojta
> > 
> > [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5132/console
> > ___
> > Infra mailing list -- in...@ovirt.org
> > To unsubscribe send an email to infra-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/in...@ovirt.org/message/DXDNFFNWE3DC
> > 2IJTOH7CMXN7FD4PO4HU/



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/FXEMF6WA2GG457IFKFZEH422HZBE2YDA/

[ovirt-devel] OST fails, cannot connect to repo

[Vojtech Juranek]

Hi,
OST fails with

09:47:03 https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/
epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to 
copr-be.cloud.fedoraproject.org:443; Connection refused"

see e.g. [1] for full log. Stared to fail this morning.
Can anyone take a look and fix it?

Thanks in advance.
Vojta

[1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5132/console

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/DXDNFFNWE3DC2IJTOH7CMXN7FD4PO4HU/

[ovirt-devel] CI fails to download rpms

[Vojtech Juranek]

Hi,
quite a lot of Ci runs fail because Ci fails to download
mom-0.5.14-0.0.master.fc29.noarch.rpm, fails with:

Downloading Packages:
12:36:34  [MIRROR] mom-0.5.14-0.0.master.fc29.noarch.rpm: Interrupted by header 
callback: Server reports Content-Length: 133628 but expected size is: 133676
12:36:34  [FAILED] mom-0.5.14-0.0.master.fc29.noarch.rpm: No more mirrors to 
try - All mirrors were already tried without success
12:36:34  Error: Error downloading packages:
12:36:34Cannot download noarch/mom-0.5.14-0.0.master.fc29.noarch.rpm: All 
mirrors were tried

for full log, see e.g. [1].

Any idea how to fix it?
Thanks
Vojta

[1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/7809/console

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/QO67FVNAQADLYWFLJF2LOZSSSRONNLRR/

[ovirt-devel] Re: sanlock 3.7.3-1 is available for testing

[Vojtech Juranek]

On čtvrtek 23. května 2019 16:02:32 CEST Nir Soffer wrote:
> Enable this repo:
> http://buildlogs.centos.org/centos/$releasever/virt/$basearch/ovirt-4.3/

just FIY (I didn't know that): as Sandro pointed out in comment to my patch 
[1], this is a combination of centos-ovirt-common-testing-x86_64 and centos-
ovirt43-testing.

> Sandro, shouldn't it be in:
> https://cbs.centos.org/repos/virt7-ovirt-43-testing/$basearch/os/

it's in 
https://cbs.centos.org/repos/virt7-ovirt-common-testing/x86_64/os/

[1] https://gerrit.ovirt.org/#/c/99606/2/automation/check-patch.repos.el7@9

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/MSCXEMPHU3LKXUTYRAZOLM6LYT56PSQ7/

[ovirt-devel] [vdsm] Flaky IPAddressTest

[Vojtech Juranek]

Hi,
FIY, IPAddressTest seems to randomly failing, e.g. in [1] with

FAIL: test_add_delete_ipv4 (network.ip_address_test.IPAddressTest)
--
Traceback (most recent call last):
  File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/
ip_address_test.py", line 222, in test_add_delete_ipv4
self._test_add_delete(IPV4_A_WITH_PREFIXLEN, IPV4_B_WITH_PREFIXLEN)
  File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/
ip_address_test.py", line 247, in _test_add_delete
self._assert_has_no_address(nic, ip_b)
  File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/
ip_address_test.py", line 344, in _assert_has_no_address
self._assert_address_not_in(address_with_prefixlen, addresses)
  File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/
ip_address_test.py", line 352, in _assert_address_not_in
self.assertNotIn(address_with_prefixlen, addresses_list)
AssertionError: '192.168.98.1/29' unexpectedly found in ['192.168.99.1/29', 
'192.168.98.1/29', 'fe80::1442:7bff:fea7:7775/64']

Thanks
Vojta

[1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/2141//artifact/
check-patch.tests-py27.el7.x86_64/mock_logs/script/stdout_stderr.log

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/N2KRADCHZ2OMN2FSUQYMM676WZKFBWEE/

[ovirt-devel] Re: [VDSM] running tests locally

[Vojtech Juranek]

> This works only for legacy test using nose.
> 
> Storage tests use tox. tests/README explains how to run them.

thanks for the pointers, works for me now.

FIY: I've sent a PR [1] which updates instructions how to run VDSM tests

[1] https://github.com/oVirt/ovirt-site/pull/1779


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/W4GC7DZNH4IEXCQMIVRCNSG4SNJ4UTW7/

[ovirt-devel] [VDSM] running tests locally

[Vojtech Juranek]

Hi,
beginner question: I'm trying to run some VDSM tests locally (e.g. 
blocksd_test.py), using

PYTHON_EXE=python3 ./run_tests_local.sh storage/blocksd_test.py

but I'm getting quite a lot of test failures. Most of the tests fail because 
of mokeypatch fixture is not injected (see error bellow).

What I'm doing wrong and how I can run selected tests locally?
Thanks in advance
Vojta

ERROR: storage.blocksd_test.test_meta_size_max_val
--
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
TypeError: test_meta_size_max_val() missing 1 required positional argument: 
'monkeypatch'

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/I3PK3WSDFRNXM6HKUYK7ENMJAL6MS5RL/