Bug 1683544 - rocky services in queens ComputeOvsDpdkSriov role
Summary: rocky services in queens ComputeOvsDpdkSriov role
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: All
OS: All
medium
low
Target Milestone: z6
: 13.0 (Queens)
Assignee: Saravanan KR
QA Contact: Yariv
URL:
Whiteboard:
Depends On:
Blocks: 1634390
TreeView+ depends on / blocked
 
Reported: 2019-02-27 08:01 UTC by Christophe Fontaine
Modified: 2019-04-30 17:28 UTC (History)
4 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.2.0-11.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-30 17:27:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 639486 0 None MERGED Remove the rokcy services from queens ComputeOvsDpdkSriov role 2020-10-01 11:50:13 UTC
Red Hat Product Errata RHBA-2019:0939 0 None None None 2019-04-30 17:28:03 UTC

Description Christophe Fontaine 2019-02-27 08:01:33 UTC
Description of problem:
The roles ComputeOvsDpdkSriov and ComputeOvsDpdkSriovRT include 3 new services which have been introduced in Rocky.

When trying to deploy, the following errors appears:
StackValidationFailed: The Resource Type (OS::TripleO::Services::NovaLibvirtGuests) could not be found.

The services which should be removed for a successful deployment are:
- OS::TripleO::Services::NovaLibvirtGuests
- OS::TripleO::Services::BootParams
- OS::TripleO::Services::MetricsQdr

Comment 11 errata-xmlrpc 2019-04-30 17:27:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0939


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