On Wed, Jul 19, 2017 at 6:46 PM, Daniel Belenky <dbelenky@redhat.com> wrote:

Hi Sando,

Today we've issued a dependency issue where openvswitch-0:2.7.0-1.el7.x86_64

 requires python2-six.

No. we discussed about an issue regarding  openvswitch-2.7.1-1.1fc27.el7 requiring python2-six instead of python-six and python-six-1.10.0-3.el7 is not providing it.

I untagged the broken package and notified RDO people about the issue.

 

It seems that this dependency issue was fixed in openvswitch-1:2.7.1-1.1fc27.el7.x86_64.

No. The issue was fixed by untagging openvswitch-2.7.1-1.1fc27.el7 from Virt SIG restoring the previous 2.7.0 version.

Haïkel Guémar rebuilt python-six-1.10.0-9.el7 providing the missing python2-six package

 

But the problem is that when querying the centos-ovirt-4.2 repo with dnf I can see the new package,

This is possible only if you have not refreshed metadata. The package is not there anymore.

 

but when querying the same repo for the same package with yum from a centos host, the package can't be seen, thus our CI mirrors can't be updated.

This is correct since the 2.7.1 package is not there anymore.

 

Can you please assist to get to the root cause of this issue?

I think there's just a bit of confusion and obsolete metadata left around.

Anyway, I'm tagging openvswitch-2.7.1-1.1fc27.el7 and python-six-1.10.0-9.el7 into 4.2 candidate, this should fix the weird stuff you're seeing.

 

Thanks,

--

DANIEL BELENKY

Associate sw engineer

RHEV DEVOPS

EMEA VIRTUALIZATION R&D

Red Hat Israel

dbelenky@redhat.com    IRC: #rhev-integ, #rhev-dev

--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA

TRIED. TESTED. TRUSTED.