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

Bug 1436837

Summary:	OSP10 create flavor fails to set project
Product:	Red Hat OpenStack	Reporter:	Benjamin Schmaus <bschmaus>
Component:	python-openstackclient	Assignee:	Julie Pichon <jpichon>
Status:	CLOSED ERRATA	QA Contact:	Shai Revivo <srevivo>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	apevec, beth.white, dnavale, jpichon, jruzicka, lhh, marjones, sclewis, srevivo, svigan, tvignaud
Target Milestone:	z8	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	python-openstackclient-3.2.1-3.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, when creating a new flavor, meant to be private to a project, the flavor would be created but not assigned to the project. With this update, the code has been modified to use the new flavor's generated ID when an ID is not explicitly set. As a result, it is now possible to assign a flavour to be private to a project when creating a new flavor.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-17 15:49:28 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 Benjamin Schmaus 2017-03-28 19:32:16 UTC

Description of problem:

openstack flavor create --ram 2000 --disk 20 --vcpus 2 --private --project <project-id> RU-Test

we receive the following: 
Failed to add project <project-id> access to flavor: Flavor auto could not be found. (HTTP 404) (Request-ID: req-f7bd5faa-1dc4-4cc4-b5c7-6244fe516386)


Version-Release number of selected component (if applicable):
OSP10

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Issue is fixed upstream in python-openstackclient 3.7.0

Comment 1 Chris Fields 2017-05-23 15:43:39 UTC

Can I get an idea on when we can expected to see the upstream fix in an errata release?

Comment 2 Beth White 2017-06-14 15:14:13 UTC

This bug is triaged and aimed for current release.

Comment 4 Julie Pichon 2018-01-25 14:02:22 UTC

Adjusting status and flags as the original request is for a backport to OSP10. The upstream fix was shipped as part of OSP11 already.

Comment 16 errata-xmlrpc 2018-05-17 15:49:28 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-2018:1596