-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create Flavors #573
Comments
version 2.0.9 / 2.10 Additional properties are not allowed (u'OS-FLV-DISABLED:disabled', u'public' were unexpected) |
I've got the same problem in 2.0.9, could anyone tell me if openstack4j supports OpenStack Liberty? |
Same issue using 2.11 version. I'm using Openstack Liberty. |
@elikraja Are you getting the OSClient with the perspective as ADMIN?
|
Hi @vinodborole |
@elikraja Did you check if you can create the flavor using openstack CLI with the same user? |
Yep, first thing I tested was the creation from CLI. |
@elikraja i am able to create it with o4j. My openstack version is Juno My code:
INFO: 1 * Sending client request on thread main May 02, 2016 7:32:12 PM org.glassfish.jersey.filter.LoggingFilter log |
@vinodborole I'm running Liberty. That's probabily the problem My code is: Flavor flavor = os.compute().flavors().create("m1.test", 1024, 10, 10, 4, 0, 1, true);` The only way to make it works is to add a @JsonIgnore to both methods (isDisabled and isPublic) on NovaFlavor class |
@elikraja When you run the command using openstack CLI what does your flavor json look like? Can we compare this with the flavor json generated by o4j? |
@vinodborole This is what I get when I run nova flavor-create (getting json from log file)
This is the json I get when trying to create flavor from o4j
As you can see, OS-FLV-DISABLED:disabled parameter doesn't exist anymore and the public parameter now is called os-flavor-access:is_public |
@elikraja Thanks for the information. It does makes sense to ignore these parameters then. |
i used to 2.11 version, Flavor flavor = os.compute().flavors().create("deleteme",512,1,10,0,0,1.0f,true); ClientResponseException{message=Invalid input for field/attribute flavor. Value: {u'name': u'deleteme', u'ram': 512, u'OS-FLV-DISABLED:disabled': False, u'vcpus': 1, u'swap': 0, u'os-flavor-access:is_public': True, u'rxtx_factor': 1.0, u'OS-FLV-EXT-DATA:ephemeral': 0, u'disk': 10, u'public': True}. Additional properties are not allowed (u'OS-FLV-DISABLED:disabled', u'public' were unexpected), status=400, status-code=BAD_REQUEST} |
@huytt1992 |
@vinodborole I follow the instructions here and use the library as a guide. |
What openstack version are you using? |
@vinodborole |
that's the openstack4j library, that is fine..., i need to know the openstack cloud version that u are using? Is it liberty, mitaka, juno? |
@vinodborole |
It seems the following properties are not allowed for mitaka release. I do not think openstack4j supports some of the API's post kilo.. properties are not allowed (u'OS-FLV-DISABLED:disabled', u'public' were unexpected) |
@vinodborole |
I see your instructions, and I follow it, by calling the API directly through tool Insomina. INFO: 1 * Sending client request on thread main and response : { if i delete 2 line ("public" : true,"OS-FLV-DISABLED:disabled" : false,), response : Ok { thank you so much ! |
@huytt1992 Will let you know once we get this feature out. |
What's the plan on fixing this? Kind of blocked when using Mitaka. Seems like an easy fix nulling out these fields on creation. Is there a workaround we can gain access to the POJO before submission? |
I have the same problem,Openstack:mitaka.Is there any solutions to solove this problem and tell me the reason? Thank you. |
merged |
Looks like there are two properties being sent to Nova to create a Flavor which it doesn't like.
OS-FLV-DISABLED:disabled and public
Getting the following error:
Additional properties are not allowed (u'OS-FLV-DISABLED:disabled', u'public' were unexpected), status=400, status-code=BAD_REQUEST}
Using the following code.
Connecting to a v2.0 endpoint.
I can't tell if this is a version problem of API I'm connecting to or not.
The text was updated successfully, but these errors were encountered: