Bug 1780275 - Missing dpdk from ovirt-release43
Summary: Missing dpdk from ovirt-release43
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-release
Classification: oVirt
Component: CentOS
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Sandro Bonazzola
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-05 15:43 UTC by Stefano Stagnaro
Modified: 2019-12-11 13:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-06 09:31:16 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)
yum repolist and yum update output (144.86 KB, text/plain)
2019-12-05 15:43 UTC, Stefano Stagnaro
no flags Details
/etc/yum.repos.d/ (4.11 KB, application/gzip)
2019-12-05 15:44 UTC, Stefano Stagnaro
no flags Details

Description Stefano Stagnaro 2019-12-05 15:43:04 UTC
Created attachment 1642413 [details]
yum repolist and yum update output

Description of problem:
When upgrading CentOS Hosts from oVirt 4.2 to 4.3, openvswitch update fails (log annexed).

Manually installing it from CentOS Extra seems to have solved the problem:

# yum localinstall http://mirror.centos.org/centos-7/7/extras/x86_64/Packages/dpdk-18.11.2-1.el7.x86_64.rpm

Version-Release number of selected component (if applicable):
ovirt-release43-4.3.7-1.el7.noarch
centos-release-7-7.1908.0.el7.centos.x86_64

I even tried to update CentOS to 7.7 first with 
# yum update --disablerepo=ovirt-4.3*

But then I got the same error.

Comment 1 Stefano Stagnaro 2019-12-05 15:44:40 UTC
Created attachment 1642414 [details]
/etc/yum.repos.d/

Comment 2 Dominik Holler 2019-12-06 07:17:22 UTC
Stefano, thanks for reporting this.
The problem is that CentOS-Base.repo is not replaced by CentOS-Base.repo.rpmnew .

The solution is to replace CentOS-Base.repo by CentOS-Base.repo.rpmnew manually or
enable the extras repo manually by 
yum-config-manager --enable extras

.

Does one of this solutions solves the problem for you?

Comment 3 Stefano Stagnaro 2019-12-06 08:06:03 UTC
Thank you Dominik, manually replacing CentOS-Base.repo with CentOS-Base.repo.rpmnew has solved the problem.

Comment 4 Dominik Holler 2019-12-06 08:26:47 UTC
(In reply to Stefano Stagnaro from comment #3)
> Thank you Dominik, manually replacing CentOS-Base.repo with
> CentOS-Base.repo.rpmnew has solved the problem.

Thanks for the feedback.

Can we close this bug?

Comment 5 Stefano Stagnaro 2019-12-06 08:58:43 UTC
Yes, please close this bug.

Thank you for your support.


Note You need to log in before you can comment on or make changes to this bug.