Bug 2179806

Summary: 17.1/8 Container build is failing with deps issue: nothing provides network-scripts-openvswitch3.1 needed by rhosp-network-scripts-openvswitch-3.1-1.el8osttrunk.noarch
Product: Red Hat OpenStack Reporter: Sandeep Yadav <sandyada>
Component: distributionAssignee: OSP Team <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Lon Hohberger <lhh>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 17.1 (Wallaby)CC: apevec, jjoyce, jschluet, mandreou, mburns, mgarciac, rhos-maint, shrjoshi, svyas
Target Milestone: ---Keywords: Triaged
Target Release: ---Flags: ifrangs: needinfo? (rhos-maint)
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-29 11:03:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sandeep Yadav 2023-03-20 07:17:53 UTC
Description of problem:

17.1/8 Container build in CI is failing with deps issue: nothing provides network-scripts-openvswitch3.1 needed by rhosp-network-scripts-openvswitch-3.1-1.el8osttrunk.noarch


Version-Release number of selected component (if applicable):
17.1 on rhel-8

How reproducible:
Everytime in CI


Error Snippet:

~~~
2023-03-19 12:27:55.938809 | TASK [multi-node-bridge : Install openvswitch]
2023-03-19 12:27:59.466789 | primary | ERROR
2023-03-19 12:27:59.467657 | primary | {
2023-03-19 12:27:59.467738 | primary |   "failures": [],
2023-03-19 12:27:59.467765 | primary |   "msg": "Depsolve Error occurred: \n Problem: package rhosp-openvswitch-3.1-1.el8osttrunk.noarch requires rhosp-network-scripts-openvswitch = 3.1-1.el8osttrunk, but none of the providers can be installed\n  - conflicting requests\n  - nothing provides network-scripts-openvswitch3.1 needed by rhosp-network-scripts-openvswitch-3.1-1.el8osttrunk.noarch",
2023-03-19 12:27:59.467791 | primary |   "rc": 1,
2023-03-19 12:27:59.467812 | primary |   "results": []
2023-03-19 12:27:59.467832 | primary | }
~~~

Issue started on 17th March as per build history.