[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2018-04-02 Thread Takashi NATSUME
In python-novaclient, the "nova secgroup-create" command has been removed since https://review.openstack.org/#/c/437145/. So it is no longer necessary to fix it in python-novaclient. ** Changed in: python-novaclient Status: In Progress => Won't Fix -- You received this bug notification

[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2016-02-12 Thread Sean Dague
We've updated the Nova docs that this is no longer optional. ** Changed in: nova Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2015-04-30 Thread Dean Troyer
** Changed in: python-openstackclient Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1434172 Title: security group create

[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2015-03-30 Thread Sean Dague
Right, optional means you are allowed to not provide the parameter. Not that you can provide it as null. There is a python-novaclient bug here. ** Changed in: nova Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team,

[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2015-03-24 Thread Steve Martinelli
Switched it back to new, let me know if you disagree. ** Also affects: python-novaclient Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2015-03-24 Thread Steve Martinelli
@sdague, I made a change to novaclient to ensure the body does not include the description value. You can see in the log below that the body is just: {security_group: {name: tempo}} But, the result remains the same (400 with description is not a string or unicode): 2015-03-25 00:22:48.445 DEBUG

[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2015-03-24 Thread Sean Dague
description is optional, optional does not mean it can be null, it means it shouldn't be in the payload at all. ** Changed in: nova Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute

[Yahoo-eng-team] [Bug 1434172] Re: security group create errors without description

2015-03-23 Thread Steve Martinelli
AFAICT - the API says a request with no description in the body should be allowed: http://developer.openstack.org/api-ref-compute-v2-ext.html In the controller, the description value is not checked but goes to validate_property...