[ovirt-devel] Re: Master is broken for Fedora

2019-06-05 Thread Sandro Bonazzola 
Il giorno mer 5 giu 2019 alle ore 17:21 Nir Soffer  ha
scritto:

> On Wed, Jun 5, 2019 at 3:54 PM Nir Soffer  wrote:
>
>> On Tue, Jun 4, 2019 at 9:12 AM Nir Soffer  wrote:
>>
>>>
>>>
>>> On Tue, Jun 4, 2019, 08:57 Sandro Bonazzola  wrote:
>>>


 Il giorno mar 4 giu 2019 alle ore 06:44 Dan Kenigsberg <
 dan...@redhat.com> ha scritto:

>
>
> On Tue, 4 Jun 2019, 1:14 Nir Soffer,  wrote:
>
>>
>>
>> On Tue, Jun 4, 2019 at 12:56 AM Nir Soffer 
>> wrote:
>>
>>> On Mon, Jun 3, 2019 at 8:04 PM Nir Soffer 
>>> wrote:
>>>


 On Mon, Jun 3, 2019, 18:12 Sandro Bonazzola 
 wrote:

> Hi,
> just to let you know that vdsm jsut broke hosted engine on fedora.
> Reason is that hosted engine is still building for python2 whiile
> vdsm is now being shipped for python3 only.
>

 Thats a bug, vdsm should build for both 2 and 3 on Fedora 28. We
 should switch theses builds to Fedora 29 soon.

>>>
>>> Vdsm is built for both python 2 and 3 on Fedora 28 - here is build
>>> from master
>>> (with 2 unelated patches):
>>> https://jenkins.ovirt.org/job/standard-manual-runner/310/artifact/
>>>
>>> Maybe this is an issue in the code publishing builds to the repo?
>>>
>>
>> The issue is that we create packages with the same name for both
>> python 2.7 and 3.6.
>>
>> When we publish both packages to the repo, one of the versions
>> overwrite the other, so
>> we are left only python 2.7 or 3.6 or some random mix :-)
>>
>> We need to name all packages with python2 or python3 prefix. Until
>> this is fixed we should
>> disable the python 3.6 builds since they cannot work anyway at this
>> point.
>>
>
> Renaming is a real pain. Can we simply place the py3 rpms in a
> different directory of build artifacts?
>

 Renaming is still mandatory for Fedora inclusion of vdsm package.
 You can limit python3 build to Fedora 30 and keep python2 to older
 Fedoras

>>>
>>> We can rename only the python 3 packages to limit the pain.
>>>
>>
>> Until we find a solution, I posted a patch disabling python 3.6 builds:
>> https://gerrit.ovirt.org/c/100574/
>> Currently running "yum update" on Fedora 28 you get vdsm build fro python
>> 3 instead of python 2,
>> and this breaks developers setup.
>>
>
> Sandro, this should be fixed in master, can you confirm that hosted engine
> works now?
>

I can try to test it tomorrow, today I'm out of energy.



>
> Do we have OST job that verify this?
>

We have no job testing fedora on OST yet. Not enough resources for testing
in OST both CentOS and Fedora.



>
>
>
>>
>>
>>>
>>>

>
>
>>
>>>
>>>
 hosted engine build is currently broken on missing yajsonrpc being:
>
> $ rpm -ql
> https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc28/noarch/vdsm-yajsonrpc-4.40.0-309.git0371e7531.fc28.noarch.rpm
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.opt-1.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.opt-1.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.opt-1.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.opt-1.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.opt-1.pyc
>
> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.pyc
> /usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py
> /usr/lib/python3.6/site-packages/yajsonrpc/exception.py
> /usr/lib/python3.6/site-packages/yajsonrpc/stomp.py
> /usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py
> /usr/lib/python3.6/site-packages/yajsonrpc/stompserver.py
>
> please note that package naming for this package is not following
> Fedora guidelines. It should be prefixed with "python3-" according to
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_naming
> Rule doesn't apply to applications but yajsonrpc subpackage is a
> library package.
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA

[ovirt-devel] Re: Master is broken for Fedora

2019-06-05 Thread Nir Soffer 
On Wed, Jun 5, 2019 at 3:54 PM Nir Soffer  wrote:

> On Tue, Jun 4, 2019 at 9:12 AM Nir Soffer  wrote:
>
>>
>>
>> On Tue, Jun 4, 2019, 08:57 Sandro Bonazzola  wrote:
>>
>>>
>>>
>>> Il giorno mar 4 giu 2019 alle ore 06:44 Dan Kenigsberg <
>>> dan...@redhat.com> ha scritto:
>>>


 On Tue, 4 Jun 2019, 1:14 Nir Soffer,  wrote:

>
>
> On Tue, Jun 4, 2019 at 12:56 AM Nir Soffer  wrote:
>
>> On Mon, Jun 3, 2019 at 8:04 PM Nir Soffer  wrote:
>>
>>>
>>>
>>> On Mon, Jun 3, 2019, 18:12 Sandro Bonazzola 
>>> wrote:
>>>
 Hi,
 just to let you know that vdsm jsut broke hosted engine on fedora.
 Reason is that hosted engine is still building for python2 whiile
 vdsm is now being shipped for python3 only.

>>>
>>> Thats a bug, vdsm should build for both 2 and 3 on Fedora 28. We
>>> should switch theses builds to Fedora 29 soon.
>>>
>>
>> Vdsm is built for both python 2 and 3 on Fedora 28 - here is build
>> from master
>> (with 2 unelated patches):
>> https://jenkins.ovirt.org/job/standard-manual-runner/310/artifact/
>>
>> Maybe this is an issue in the code publishing builds to the repo?
>>
>
> The issue is that we create packages with the same name for both
> python 2.7 and 3.6.
>
> When we publish both packages to the repo, one of the versions
> overwrite the other, so
> we are left only python 2.7 or 3.6 or some random mix :-)
>
> We need to name all packages with python2 or python3 prefix. Until
> this is fixed we should
> disable the python 3.6 builds since they cannot work anyway at this
> point.
>

 Renaming is a real pain. Can we simply place the py3 rpms in a
 different directory of build artifacts?

>>>
>>> Renaming is still mandatory for Fedora inclusion of vdsm package.
>>> You can limit python3 build to Fedora 30 and keep python2 to older
>>> Fedoras
>>>
>>
>> We can rename only the python 3 packages to limit the pain.
>>
>
> Until we find a solution, I posted a patch disabling python 3.6 builds:
> https://gerrit.ovirt.org/c/100574/
> Currently running "yum update" on Fedora 28 you get vdsm build fro python
> 3 instead of python 2,
> and this breaks developers setup.
>

Sandro, this should be fixed in master, can you confirm that hosted engine
works now?

Do we have OST job that verify this?



>
>
>>
>>
>>>


>
>>
>>
>>> hosted engine build is currently broken on missing yajsonrpc being:

 $ rpm -ql
 https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc28/noarch/vdsm-yajsonrpc-4.40.0-309.git0371e7531.fc28.noarch.rpm

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.opt-1.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.opt-1.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.opt-1.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.opt-1.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.opt-1.pyc

 /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.pyc
 /usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py
 /usr/lib/python3.6/site-packages/yajsonrpc/exception.py
 /usr/lib/python3.6/site-packages/yajsonrpc/stomp.py
 /usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py
 /usr/lib/python3.6/site-packages/yajsonrpc/stompserver.py

 please note that package naming for this package is not following
 Fedora guidelines. It should be prefixed with "python3-" according to
 https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_naming
 Rule doesn't apply to applications but yajsonrpc subpackage is a
 library package.

 --

 Sandro Bonazzola

 MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

 Red Hat EMEA 

 sbona...@redhat.com
 
 
 ___
 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:

[ovirt-devel] Building python 2 and python 3 packages for Fedora

2019-06-05 Thread Nir Soffer 
In several projects (e.g. vdsm, imageio, sanlock), we have the issue of
building python 3 packages
for Fedora.

The current build process create packages with the same name for both
python 2 and python 3.
When the packages are published to oVirt repository, the python 3 packages
overwrite the python 2
packages.

We can rename the packages properly (e.g. python2-xxx, python3-xxx) but
this requires lot of work
and typically breaks later in the code publishing the packages.

There is also the difficulty of building both python 2 and python 3
packages from same spec in the same
build. This should be possible but not easy.

Since python 2 is about to die soon, should we simplify by building python
2 *or* python 3, depending
on version?

Fedora 29: python 2.7
Fedora 30: python 3.7
CentOS 7: python 2.7
CentOS 8: python 3.6

This make it possible to test and develop on python 2.7 until vdsm is fully
functional on python 3,
and it save resources in the CI.

Thoughts?

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

[ovirt-devel] Re: Master is broken for Fedora

2019-06-05 Thread Nir Soffer 
On Tue, Jun 4, 2019 at 9:12 AM Nir Soffer  wrote:

>
>
> On Tue, Jun 4, 2019, 08:57 Sandro Bonazzola  wrote:
>
>>
>>
>> Il giorno mar 4 giu 2019 alle ore 06:44 Dan Kenigsberg 
>> ha scritto:
>>
>>>
>>>
>>> On Tue, 4 Jun 2019, 1:14 Nir Soffer,  wrote:
>>>


 On Tue, Jun 4, 2019 at 12:56 AM Nir Soffer  wrote:

> On Mon, Jun 3, 2019 at 8:04 PM Nir Soffer  wrote:
>
>>
>>
>> On Mon, Jun 3, 2019, 18:12 Sandro Bonazzola 
>> wrote:
>>
>>> Hi,
>>> just to let you know that vdsm jsut broke hosted engine on fedora.
>>> Reason is that hosted engine is still building for python2 whiile
>>> vdsm is now being shipped for python3 only.
>>>
>>
>> Thats a bug, vdsm should build for both 2 and 3 on Fedora 28. We
>> should switch theses builds to Fedora 29 soon.
>>
>
> Vdsm is built for both python 2 and 3 on Fedora 28 - here is build
> from master
> (with 2 unelated patches):
> https://jenkins.ovirt.org/job/standard-manual-runner/310/artifact/
>
> Maybe this is an issue in the code publishing builds to the repo?
>

 The issue is that we create packages with the same name for both python
 2.7 and 3.6.

 When we publish both packages to the repo, one of the versions
 overwrite the other, so
 we are left only python 2.7 or 3.6 or some random mix :-)

 We need to name all packages with python2 or python3 prefix. Until this
 is fixed we should
 disable the python 3.6 builds since they cannot work anyway at this
 point.

>>>
>>> Renaming is a real pain. Can we simply place the py3 rpms in a different
>>> directory of build artifacts?
>>>
>>
>> Renaming is still mandatory for Fedora inclusion of vdsm package.
>> You can limit python3 build to Fedora 30 and keep python2 to older Fedoras
>>
>
> We can rename only the python 3 packages to limit the pain.
>

Until we find a solution, I posted a patch disabling python 3.6 builds:
https://gerrit.ovirt.org/c/100574/
Currently running "yum update" on Fedora 28 you get vdsm build fro python 3
instead of python 2,
and this breaks developers setup.


>
>
>>
>>>
>>>

>
>
>> hosted engine build is currently broken on missing yajsonrpc being:
>>>
>>> $ rpm -ql
>>> https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc28/noarch/vdsm-yajsonrpc-4.40.0-309.git0371e7531.fc28.noarch.rpm
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.opt-1.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.opt-1.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.opt-1.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.opt-1.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.opt-1.pyc
>>>
>>> /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.pyc
>>> /usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py
>>> /usr/lib/python3.6/site-packages/yajsonrpc/exception.py
>>> /usr/lib/python3.6/site-packages/yajsonrpc/stomp.py
>>> /usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py
>>> /usr/lib/python3.6/site-packages/yajsonrpc/stompserver.py
>>>
>>> please note that package naming for this package is not following
>>> Fedora guidelines. It should be prefixed with "python3-" according to
>>> https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_naming
>>> Rule doesn't apply to applications but yajsonrpc subpackage is a
>>> library package.
>>>
>>> --
>>>
>>> Sandro Bonazzola
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@redhat.com
>>> 
>>> 
>>> ___
>>> 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/334BHJFEYEODVO6D3FSYI7CPZUGS2S7I/
>>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>>

[ovirt-devel] ovirt-engine has been tagged (ovirt-engine-4.3.4.3)

2019-06-05 Thread Tal Nisan 

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

[ovirt-devel] Re: Storage test case needs to be fixed: 002_bootstrap.resize_and_refresh_storage_domain

2019-06-05 Thread Galit Rosenthal 
We didn't make any changes.
I don't think retrie will help in this case
we are trying to catch what cause this.

If you see this again please let us know.

We are still debugging it

On Wed, Jun 5, 2019 at 10:56 AM Dafna Ron  wrote:

> Hi,
>
> This is a random failure - so no, I have not.
> However, I looked at several failures and they are all the same, the
> action on engine/vdsm side succeeds and lago repots a failure but prints a
> success from logs.
> Did you add anything more to the tests to allow better debugging?
> Did you add a re-try to the test?
>
> Thanks,
> Dafna
>
>
>
> On Wed, Jun 5, 2019 at 8:21 AM Galit Rosenthal 
> wrote:
>
>> Hi Dafna
>>
>> If you see this failure again, please send us the link to the job.
>>
>> We are trying to reproduce it and find the root cause.
>>
>> Regards,
>> Galit
>>
>> On Tue, May 21, 2019 at 5:15 PM Dafna Ron  wrote:
>>
>>> sure
>>>
>>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-master/post-002_bootstrap.py/
>>>
>>>
>>> On Tue, May 21, 2019 at 3:04 PM Shani Leviim  wrote:
>>>
 Hi Dafna,
 Can you please direct me to the full test's log?


 *Regards,*

 *Shani Leviim*


 On Tue, May 21, 2019 at 11:57 AM Tal Nisan  wrote:

> Sure, Shani can you please have a look?
>
> On Mon, May 20, 2019 at 8:30 PM Dafna Ron  wrote:
>
>> Hi Tal,
>>
>> I am seeing random failures for test
>> 002_bootstrap.resize_and_refresh_storage_domain
>> It looks like this is a timing issue since by the time we print out
>> the error we actually see the resize succeeded. see example below:
>>
>>
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/testReport/junit/(root)/002_bootstrap/running_tests___basic_suite_el7_x86_64___resize_and_refresh_storage_domain/
>>
>> Can you please assign someone from the storage team to fix this test?
>>
>> Thanks,
>> Dafna
>>
>> ___
>>> 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/P4UZJ4PWELVW2AGLVIFXKM5OTMHUHKGC/
>>>
>>
>>
>> --
>>
>> GALIT ROSENTHAL
>>
>> SOFTWARE ENGINEER
>>
>> Red Hat
>>
>> 
>>
>> ga...@redhat.comT: 972-9-7692230
>> 
>>
>

-- 

GALIT ROSENTHAL

SOFTWARE ENGINEER

Red Hat



ga...@redhat.comT: 972-9-7692230

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

[ovirt-devel] Re: Storage test case needs to be fixed: 002_bootstrap.resize_and_refresh_storage_domain

2019-06-05 Thread Dafna Ron 
Hi,

This is a random failure - so no, I have not.
However, I looked at several failures and they are all the same, the action
on engine/vdsm side succeeds and lago repots a failure but prints a success
from logs.
Did you add anything more to the tests to allow better debugging?
Did you add a re-try to the test?

Thanks,
Dafna



On Wed, Jun 5, 2019 at 8:21 AM Galit Rosenthal  wrote:

> Hi Dafna
>
> If you see this failure again, please send us the link to the job.
>
> We are trying to reproduce it and find the root cause.
>
> Regards,
> Galit
>
> On Tue, May 21, 2019 at 5:15 PM Dafna Ron  wrote:
>
>> sure
>>
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-master/post-002_bootstrap.py/
>>
>>
>> On Tue, May 21, 2019 at 3:04 PM Shani Leviim  wrote:
>>
>>> Hi Dafna,
>>> Can you please direct me to the full test's log?
>>>
>>>
>>> *Regards,*
>>>
>>> *Shani Leviim*
>>>
>>>
>>> On Tue, May 21, 2019 at 11:57 AM Tal Nisan  wrote:
>>>
 Sure, Shani can you please have a look?

 On Mon, May 20, 2019 at 8:30 PM Dafna Ron  wrote:

> Hi Tal,
>
> I am seeing random failures for test
> 002_bootstrap.resize_and_refresh_storage_domain
> It looks like this is a timing issue since by the time we print out
> the error we actually see the resize succeeded. see example below:
>
>
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/testReport/junit/(root)/002_bootstrap/running_tests___basic_suite_el7_x86_64___resize_and_refresh_storage_domain/
>
> Can you please assign someone from the storage team to fix this test?
>
> Thanks,
> Dafna
>
> ___
>> 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/P4UZJ4PWELVW2AGLVIFXKM5OTMHUHKGC/
>>
>
>
> --
>
> GALIT ROSENTHAL
>
> SOFTWARE ENGINEER
>
> Red Hat
>
> 
>
> ga...@redhat.comT: 972-9-7692230
> 
>
___
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/PY5PCZWS3ED7PRC7EEHHDEMX23GW4PLE/

[ovirt-devel] Re: Dropping Fedora 28 support in oVirt development repos and jenkins

2019-06-05 Thread Sandro Bonazzola 
Il giorno mer 5 giu 2019 alle ore 09:08 Nir Soffer  ha
scritto:

> On Wed, Jun 5, 2019, 08:32 Sandro Bonazzola  wrote:
>
>> Hi,
>> while we are introducing support for fedora 29 and 30 we need to free
>> resources both on jenkins and on resources.ovirt.org.
>> Starting today I'll start pushing removal of fc28 jenkins jobs. Once
>> done, I'm going to remove the fc28 repositories from all snapshot and
>> tested repos, keeping fc28 repos only within the released repositories.
>>
>
> This is fine once we have working f29 build.
>

Not sure we can wait that much dropping fc28.
Right now it takes up to 3 days for a patch to land on snapshot repos due
to the amount of time spent by deploy_to_master_tested generating the
repositories metadata.
And we have space limitations to the amount of builds we can keep on our
systems.




>
>
>> Thanks,
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>> 
>> ___
>> 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/36OHDZDMIMKCEAG3NXZWOGQGYEV2ARR2/
>>
>

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


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

[ovirt-devel] Re: Storage test case needs to be fixed: 002_bootstrap.resize_and_refresh_storage_domain

2019-06-05 Thread Galit Rosenthal 
Hi Dafna

If you see this failure again, please send us the link to the job.

We are trying to reproduce it and find the root cause.

Regards,
Galit

On Tue, May 21, 2019 at 5:15 PM Dafna Ron  wrote:

> sure
>
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-master/post-002_bootstrap.py/
>
>
> On Tue, May 21, 2019 at 3:04 PM Shani Leviim  wrote:
>
>> Hi Dafna,
>> Can you please direct me to the full test's log?
>>
>>
>> *Regards,*
>>
>> *Shani Leviim*
>>
>>
>> On Tue, May 21, 2019 at 11:57 AM Tal Nisan  wrote:
>>
>>> Sure, Shani can you please have a look?
>>>
>>> On Mon, May 20, 2019 at 8:30 PM Dafna Ron  wrote:
>>>
 Hi Tal,

 I am seeing random failures for test
 002_bootstrap.resize_and_refresh_storage_domain
 It looks like this is a timing issue since by the time we print out the
 error we actually see the resize succeeded. see example below:


 http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/testReport/junit/(root)/002_bootstrap/running_tests___basic_suite_el7_x86_64___resize_and_refresh_storage_domain/

 Can you please assign someone from the storage team to fix this test?

 Thanks,
 Dafna

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


-- 

GALIT ROSENTHAL

SOFTWARE ENGINEER

Red Hat



ga...@redhat.comT: 972-9-7692230

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

[ovirt-devel] Re: Dropping Fedora 28 support in oVirt development repos and jenkins

2019-06-05 Thread Nir Soffer 
On Wed, Jun 5, 2019, 08:32 Sandro Bonazzola  wrote:

> Hi,
> while we are introducing support for fedora 29 and 30 we need to free
> resources both on jenkins and on resources.ovirt.org.
> Starting today I'll start pushing removal of fc28 jenkins jobs. Once done,
> I'm going to remove the fc28 repositories from all snapshot and tested
> repos, keeping fc28 repos only within the released repositories.
>

This is fine once we have working f29 build.


> Thanks,
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
> 
> ___
> 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/36OHDZDMIMKCEAG3NXZWOGQGYEV2ARR2/
>
___
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/KNGJHFUMYRMH64VDI6CNBOT4QXH44F4C/