On Sun, Jun 25, 2017 at 12:56 PM, Eyal Edri <eedri(a)redhat.com> wrote:
On Sun, Jun 25, 2017 at 10:00 AM, Eyal Edri <eedri(a)redhat.com> wrote:
>
>
> On Sun, Jun 25, 2017 at 9:41 AM, Barak Korren <bkorren(a)redhat.com> wrote:
>
>>
>>
>> On 25 June 2017 at 09:38, Eyal Edri <eedri(a)redhat.com> wrote:
>>
>>>
>>>
>>>
>>> On Sat, Jun 24, 2017 at 8:37 PM, Barak Korren <bkorren(a)redhat.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> בתאריך 23 ביוני 2017 15:56, "Sandro Bonazzola"
<sbonazzo(a)redhat.com>
>>>> כתב:
>>>>
>>>> Hi,
>>>> we dropped publishing vdsm ppc64le builds on snapshot repos due to
>>>> issues keeping aligned nvr between x86_64 and ppc64le.
>>>>
>>>> Today we're still missing ppc64le builds on
>>>>
http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/el7/ppc64le/
>>>>
>>>> Where do we stand with the support for the build of the same nvr ob
>>>> both arches?
>>>>
>>>> Can we get it re-enabled?
>>>>
>>>>
>>>> Yes. We solved the issues we had with this a while ago with the new
>>>> deploy-to-expetimental job. Are you sure the ppc64le builds are not
making
>>>> it to 'tested'? (Im assuming the builds themselves are
enabled...)
>>>>
>>>> I suppose the situation with 4.1 is a little different because it is
>>>> not taking stuff from 'tested' yet...
>>>>
>>>
>>> Sent [1], which should solve it.
>>> Barak, the fact that we still publish nightly to 4.1 in the old way can
>>> somehow still cause issues for publishing both ppc64le and x86_64?
>>> The only thing I can think of is if for a very slim chance, one of the
>>> builds of vdsm is running during the time publisher works resulting in a
>>> mismatch in the repo, right?
>>>
>>>
>> Yeah, not very probable.
>>
>> Maybe we should just clean up the publishers and move 4.1 to use
>> 'tested' too. Do we have a ticket about that?
>>
>
>
https://ovirt-jira.atlassian.net/browse/OVIRT-1477
>
> But I don't see a good reason to push it forward unless we hit a problem
> or blocker, it might cause issues like we've seen in master and also
> there is a good chance 4.1 still has old non-standard CI projects that
> will make it impossible to finish, unless we migrate them to standard CI
> (which also might not be worth the effort).
>
> Bottom line, good to have a ticket on it, we'll do if we see its needed
> at some point.
>
Verified we have ppc64le on 4.1-snapshot:
http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/el7/ppc64le/
BTW, we're still building and publishing qemu-kvm-rhev to 4.1, i'm
assuming the latest change to pick it up from kvm-common was for master
only?
Yes, there was a bug for 4.2.
>
>
>>
>>
>>
>> --
>> Barak Korren
>> RHV DevOps team , RHCE, RHCi
>> Red Hat EMEA
>>
redhat.com | TRIED. TESTED. TRUSTED. |
redhat.com/trusted
>>
>
>
>
> --
>
> Eyal edri
>
>
> ASSOCIATE MANAGER
>
> RHV DevOps
>
> EMEA VIRTUALIZATION R&D
>
>
> Red Hat EMEA <
https://www.redhat.com/>
> <
https://red.ht/sig> TRIED. TESTED. TRUSTED.
<
https://redhat.com/trusted>
> phone: +972-9-7692018 <+972%209-769-2018>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <
https://www.redhat.com/>
<
https://red.ht/sig> TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
phone: +972-9-7692018 <+972%209-769-2018>
irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <
https://www.redhat.com/>
<
https://red.ht/sig>
TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>