On Thu, Oct 18, 2018 at 1:27 PM, Dafna Ron <dron@redhat.com> wrote:
> I added dpdk to the 4.2 repo as well which should solve the issue in upgrade
> I do see that http://mirror.centos.org/centos/7/extras/x86_64/Packages/ has
> both dpdk-16.11.2-4.el7.x86_64.rpm and dpdk-17.11-7.el7.x86_64.rpm so hope
> it would grab the correct one.
>

I have only tested it w/ dpdk-17.11-13.el7.x86_64 - and that works.
That's also in extras, and from my understanding in should push the
latest one available.

Fingers crossed.

>
>
> On Thu, Oct 18, 2018 at 11:37 AM Miguel Duarte de Mora Barroso
> <mdbarroso@redhat.com> wrote:
>>
>> On Thu, Oct 18, 2018 at 11:56 AM, Dafna Ron <dron@redhat.com> wrote:
>> > Hi,
>> >
>> > We have a failure in upgrade suite.
>> > Issue is due to openvswitch failing to install due to dpdk deps.
>> > it seems that even after we add the missing package there are some
>> > issues
>> > with dependencies.
>> >
>> > I see that Miguel has a patch for that as well - Miguel, can you please
>> > update on the issue?
>> >
>> > full log is here;
>> >
>> >
>> > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifact/upgrade-from-release-suite.el7.x86_64/test_logs/upgrade-from-release-suite-master/post-002_bootstrap.py/
>> >
>> > My patch which continues to fail after adding the packge:
>> > https://gerrit.ovirt.org/#/c/95015/
>> >
>> > error for jobs: https://pastebin.com/CfLTRe5R
>> >
>> > Thanks,
>> > Dafna
>> >
>>
>> Hi all,
>>
>> I am quite probably the culprit of this entire ordeal.
>>
>> To use openvswitch 2.10 - [0] - , we need the latest dpdk libraries,
>> which are available on the centos *extra* repo.
>>
>> Following Alan Pevec's advice I told Sandro to untag the current
>> version of dpdk, which would - from what I understood - get us dpdk
>> from *extras*. Patch [1] does that.
>>
>> Now, thing is, that it works for openvswitch 2.10, not openvswitch 2.9
>> - which is what we're shipping in 4.2.7, and is being pulled in the
>> failed OST run. I also think it failed even after your patch because
>> it attempts to retrieve dpdk from the centos *base* repo, not the
>> *extras*.
>>
>> Build [2] is an OST execution of the basic suite, using ovs-2.10 with
>> its dpdk dependency, which passed successfully.
>>
>> Build [3] is an OST execution of the upgrade suite, using ovs-2.10
>> with its dpdk dependency. It failed, but, from the host yum.log - at
>> [4], it seems the issue you described above is fixed.
>>
>> I think that there are 2 courses of action depending on what we want to
>> deliver:
>> ovs-2.9 - re-tag the old DPDK version in the virt sig
>> ovs-2.10 - tag build [1], and get the DPDK dependencies from centos
>> extra packages
>>
>> [0] - https://cbs.centos.org/koji/buildinfo?buildID=24364
>> [1] - https://gerrit.ovirt.org/#/c/95014/
>> [2] - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/3389/
>> [3] - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/3390/
>> [4] -
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/3390/artifact/exported-artifacts/test_logs/upgrade-from-release-suite-master/post-002_bootstrap.py/lago-upgrade-from-release-suite-master-host-0/_var_log/yum.log
>>
>> >
>> >