Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

The Placement service has been extracted from Nova [1] during
the Stein development cycle [2]. This change extracts the required
plugin logic from the original Nova plugin into a new Placement plugin
ahead of this extraction.

[1] https://docs.openstack.org/placement/latest/
[2] https://releases.openstack.org/stein/schedule.html

Piotr or Lee,
once the fix is available in downstream (probably 8.2), would you be able to verify it?

(In reply to Pavel Moravec from comment #1)
> Piotr or Lee,
> once the fix is available in downstream (probably 8.2), would you be able to
> verify it?

Hi Pavel,
Yes, I'll do the verification.

Hi Piotr,
could you pls. verify the BZ fix against below package? Thanks in advance.


A yum repository for the build of sos-3.7-3.el8 (task 22839522) is available at:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/3.el8/

You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/3.el8/sos-3.7-3.el8.repo

RPMs and build logs can be found in the following locations:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/3.el8/noarch/

The full list of available rpms is:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/3.el8/noarch/sos-3.7-3.el8.src.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/3.el8/noarch/sos-audit-3.7-3.el8.noarch.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/3.el8/noarch/sos-3.7-3.el8.noarch.rpm

Build output will be available for the next 21 days.

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/RHEA-2019:3640