[ovirt-devel] Re: ioprocess-1.2.1 for ovirt 4.3.6

2019-07-23 Thread Eyal Shenitzky 
Here is the link for the brew build for rhel-7
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=22614223



On Mon, Jul 22, 2019 at 4:44 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno dom 21 lug 2019 alle ore 16:39 Nir Soffer 
> ha scritto:
>
>> On Sun, Jul 21, 2019 at 4:35 PM Nir Soffer  wrote:
>>
>>> On Sun, Jul 21, 2019 at 12:16 PM Eyal Edri  wrote:
>>>
 ioprocess is misconfigured in STDCI V1 and is missing V2 configuration
 to be fully functional.
 Currently, 4.3 is configured to come from ioprocess-1.0 branch:

  version:
   - 4.3:
   branch: ioprocess-1.0
   repoversion: 4.3

 But the last commit for that branch was 12 months ago, so I assume its
 not being used anymore? and master branch is used for all versions?
 This is why 4.3 tested repo doesn't have it and only master repo has it.

>>>
>>> Thanks for solving this issue!
>>>
>>> I think we can create 1.2 branch for 4.3, or use master, since ioprocess
>>> does not change
>>> a lot.
>>>
>>> I believe you should switch to V2, it will simplify the configuration
 dramatically ( Ehud can help you if needed ).

>>>
>>> Good idea.
>>>
>>
>> These patches should fix the issue:
>>
>> ioprocess:
>> build: Add CI V2 configuration 
>> tests: Mark expected failures on s390x
>> 
>>
>> jenkins:
>> iprocess: Move to V2 
>>
>> Please review.
>>
>>
>
> looks like the builds for ioprocess 1.2.1 have been deleted while moving
> to stdci v2.
> can you please provide a ioprocess 1.2.1 build to be released?
>
> I'm trying to get it built on CentOS CBS too but having some troubles
> there. https://cbs.centos.org/koji/buildinfo?buildID=26358
>
>
>> Thanks,
>> Nir
>>
>>
>
> --
>
> 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.
> *
>


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

[ovirt-devel] Re: ioprocess-1.2.1 for ovirt 4.3.6

2019-07-22 Thread Sandro Bonazzola 
Il giorno dom 21 lug 2019 alle ore 16:39 Nir Soffer  ha
scritto:

> On Sun, Jul 21, 2019 at 4:35 PM Nir Soffer  wrote:
>
>> On Sun, Jul 21, 2019 at 12:16 PM Eyal Edri  wrote:
>>
>>> ioprocess is misconfigured in STDCI V1 and is missing V2 configuration
>>> to be fully functional.
>>> Currently, 4.3 is configured to come from ioprocess-1.0 branch:
>>>
>>>  version:
>>>   - 4.3:
>>>   branch: ioprocess-1.0
>>>   repoversion: 4.3
>>>
>>> But the last commit for that branch was 12 months ago, so I assume its
>>> not being used anymore? and master branch is used for all versions?
>>> This is why 4.3 tested repo doesn't have it and only master repo has it.
>>>
>>
>> Thanks for solving this issue!
>>
>> I think we can create 1.2 branch for 4.3, or use master, since ioprocess
>> does not change
>> a lot.
>>
>> I believe you should switch to V2, it will simplify the configuration
>>> dramatically ( Ehud can help you if needed ).
>>>
>>
>> Good idea.
>>
>
> These patches should fix the issue:
>
> ioprocess:
> build: Add CI V2 configuration 
> tests: Mark expected failures on s390x
> 
>
> jenkins:
> iprocess: Move to V2 
>
> Please review.
>
>

looks like the builds for ioprocess 1.2.1 have been deleted while moving to
stdci v2.
can you please provide a ioprocess 1.2.1 build to be released?

I'm trying to get it built on CentOS CBS too but having some troubles
there. https://cbs.centos.org/koji/buildinfo?buildID=26358


> Thanks,
> Nir
>
>

-- 

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.
*
___
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/YUKN73XQBZ2S22TJU77XTRTUMWZAQV7K/

[ovirt-devel] Re: ioprocess-1.2.1 for ovirt 4.3.6

2019-07-21 Thread Nir Soffer 
On Sun, Jul 21, 2019 at 4:35 PM Nir Soffer  wrote:

> On Sun, Jul 21, 2019 at 12:16 PM Eyal Edri  wrote:
>
>> ioprocess is misconfigured in STDCI V1 and is missing V2 configuration to
>> be fully functional.
>> Currently, 4.3 is configured to come from ioprocess-1.0 branch:
>>
>>  version:
>>   - 4.3:
>>   branch: ioprocess-1.0
>>   repoversion: 4.3
>>
>> But the last commit for that branch was 12 months ago, so I assume its
>> not being used anymore? and master branch is used for all versions?
>> This is why 4.3 tested repo doesn't have it and only master repo has it.
>>
>
> Thanks for solving this issue!
>
> I think we can create 1.2 branch for 4.3, or use master, since ioprocess
> does not change
> a lot.
>
> I believe you should switch to V2, it will simplify the configuration
>> dramatically ( Ehud can help you if needed ).
>>
>
> Good idea.
>

These patches should fix the issue:

ioprocess:
build: Add CI V2 configuration 
tests: Mark expected failures on s390x 

jenkins:
iprocess: Move to V2 

Please review.

Thanks,
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/TDDANHOJRZEJDAQUC57CDJSF5JKHVU7R/

[ovirt-devel] Re: ioprocess-1.2.1 for ovirt 4.3.6

2019-07-21 Thread Nir Soffer 
On Sun, Jul 21, 2019 at 12:16 PM Eyal Edri  wrote:

> ioprocess is misconfigured in STDCI V1 and is missing V2 configuration to
> be fully functional.
> Currently, 4.3 is configured to come from ioprocess-1.0 branch:
>
>  version:
>   - 4.3:
>   branch: ioprocess-1.0
>   repoversion: 4.3
>
> But the last commit for that branch was 12 months ago, so I assume its not
> being used anymore? and master branch is used for all versions?
> This is why 4.3 tested repo doesn't have it and only master repo has it.
>

Thanks for solving this issue!

I think we can create 1.2 branch for 4.3, or use master, since ioprocess
does not change
a lot.

I believe you should switch to V2, it will simplify the configuration
> dramatically ( Ehud can help you if needed ).
>

Good idea.

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

[ovirt-devel] Re: ioprocess-1.2.1 for ovirt 4.3.6

2019-07-21 Thread Eyal Edri 
ioprocess is misconfigured in STDCI V1 and is missing V2 configuration to
be fully functional.
Currently, 4.3 is configured to come from ioprocess-1.0 branch:

 version:
  - 4.3:
  branch: ioprocess-1.0
  repoversion: 4.3

But the last commit for that branch was 12 months ago, so I assume its not
being used anymore? and master branch is used for all versions?
This is why 4.3 tested repo doesn't have it and only master repo has it.

I believe you should switch to V2, it will simplify the configuration
dramatically ( Ehud can help you if needed ).

To solve quickly the issue in the patch you can replace the tested repo in
the check-patch.repos to master:
https://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/x86_64/

since master has it.

On Sat, Jul 20, 2019 at 9:39 PM Nir Soffer  wrote:

> This is a requirement for supporting 4k in ovirt 4.3.6.
>
> We have a build for RHEL:
> https://bugzilla.redhat.com/1728953
>
> We need build for CentOS 7 - currently providing only:
> ioprocess-1.1.2-1.el7.x86_64.rpm
>
> Vdsm requires 1.2.1 for about 2 weeks, and OST builds pass, probably
> consuming 1.2.1 from
> ovirt repositories.
> https://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/x86_64/
>
> But CI on 4.3 fails with:
>
> Error: Package: vdsm-python-4.30.24-48.gitcc1fe4e.el7.noarch (artifacts)
> Requires: python-ioprocess >= 1.2.1 Installed:
> python2-ioprocess-1.1.2-1.201903201036.gita80158c.el7.x86_64 (@tested)
> python-ioprocess = 1.1.2 Available: python-ioprocess-0.15.1-1.el7.noarch
> (epel-el7) python-ioprocess = 0.15.1-1.el7 Available:
> python-ioprocess-0.16.1-1.el7.noarch (centos-ovirt-common-candidate)
> python-ioprocess = 0.16.1-1.el7 Available:
> python2-ioprocess-1.1.2-1.el7.x86_64 (centos-ovirt42-testing-x86_64)
> python-ioprocess = 1.1.2
>
> See https://gerrit.ovirt.org/c/101951/
>
> So either CI on 4.3 is missing the repo providing this version, or this
> build needs to be elsewhere,
>

The CI (automation/check-patch.repos) is using the 4.3 repo, which is using
the ioprocess-1.0 branch and only has 1.1.2 version.
Master has the newer version.


> probably in:
> https://cbs.centos.org/repos/virt7-ovirt-43-testing/x86_64/os/Packages/
>
> 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/DYDBO2GJMKKHG5VT2OBPEYDXR4H642EY/
>


-- 

Eyal edri

He / Him / His


MANAGER

CONTINUOUS PRODUCTIZATION

SYSTEM ENGINEERING

Red Hat 

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
___
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/QY25QKLARZ3THFR67CFX2V4AQZINYCEW/