[Yahoo-eng-team] [Bug 1611491] Re: api-docs: make example URLs consistent
** Changed in: glance Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1611491 Title: api-docs: make example URLs consistent Status in Glance: Fix Released Bug description: This bug covers the narrative-style API docs, namely, the stuff in specs/api in the glance-specs repo. For consistency, make sure that example URLs for openstack components are in the form: project.openstack.example.org So, for example, an example image-list call to Glance would use a URL written like this: http://glance.openstack.example.org/v2/images To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1611491/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1596829] Re: String interpolation should be delayed at logging calls
** Changed in: glare
Status: New => 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/1596829
Title:
String interpolation should be delayed at logging calls
Status in congress:
Fix Released
Status in ec2-api:
Confirmed
Status in Glance:
In Progress
Status in glance_store:
In Progress
Status in Glare:
Fix Released
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in Ironic:
Fix Released
Status in OpenStack Identity (keystone):
Fix Released
Status in masakari:
Fix Released
Status in networking-vsphere:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in os-brick:
Fix Released
Status in os-vif:
Fix Released
Status in Glance Client:
Fix Released
Status in python-manilaclient:
Fix Released
Status in python-openstackclient:
Fix Released
Status in python-troveclient:
Fix Released
Status in senlin:
Invalid
Status in watcher:
In Progress
Status in Zun:
Fix Released
Bug description:
String interpolation should be delayed to be handled by the logging
code, rather than being done at the point of the logging call.
Wrong: LOG.debug('Example: %s' % 'bad')
Right: LOG.debug('Example: %s', 'good')
See the following guideline.
* http://docs.openstack.org/developer/oslo.i18n/guidelines.html
#adding-variables-to-log-messages
The rule for it should be added to hacking checks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/congress/+bug/1596829/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1614361] Re: tox.ini needs to be updated as openstack infra now supports upper constraints
** Changed in: python-mistralclient Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1614361 Title: tox.ini needs to be updated as openstack infra now supports upper constraints Status in castellan: Fix Released Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in Designate: Fix Released Status in Freezer: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic Inspector: Fix Released Status in Mistral: Fix Released Status in networking-ovn: Invalid Status in octavia: Fix Released Status in python-barbicanclient: Fix Released Status in python-mistralclient: Fix Released Status in python-muranoclient: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tacker: Fix Released Status in OpenStack DBaaS (Trove): Invalid Status in vmware-nsx: Fix Released Status in zaqar: Fix Released Status in Zaqar-ui: Fix Released Bug description: Openstack infra now supports upper constraints for releasenotes, cover, venv targets. tox.ini uses install_command for these targets, which can now be safely removed. Reference for mail that details this support: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html To manage notifications about this bug go to: https://bugs.launchpad.net/castellan/+bug/1614361/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1508442] Re: LOG.warn is deprecated
** No longer affects: freezer ** Changed in: cloud-init Assignee: Sharat Sharma (sharat-sharma) => (unassigned) ** Changed in: cloud-init Status: In Progress => New ** Changed in: anvil Status: In Progress => New ** Changed in: anvil Assignee: Sharat Sharma (sharat-sharma) => (unassigned) -- 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/1508442 Title: LOG.warn is deprecated Status in anvil: New Status in Aodh: Fix Released Status in Astara: Fix Released Status in Barbican: Fix Released Status in bilean: Fix Released Status in Ceilometer: Fix Released Status in cloud-init: New Status in cloudkitty: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in django-openstack-auth: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in Evoque: In Progress Status in gce-api: Fix Released Status in Glance: In Progress Status in Gnocchi: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in KloudBuster: Fix Released Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in masakari: Fix Released Status in Mistral: Invalid Status in Monasca: New Status in networking-arista: Fix Released Status in networking-calico: In Progress Status in networking-cisco: In Progress Status in networking-fujitsu: Fix Released Status in networking-odl: Fix Committed Status in networking-ofagent: Fix Committed Status in networking-plumgrid: In Progress Status in networking-powervm: Fix Released Status in networking-vsphere: Fix Released Status in OpenStack Compute (nova): Fix Released Status in nova-powervm: Fix Released Status in nova-solver-scheduler: In Progress Status in octavia: Fix Released Status in openstack-ansible: Fix Released Status in oslo.cache: Fix Released Status in oslo.middleware: New Status in Packstack: Fix Released Status in python-dracclient: Fix Released Status in python-magnumclient: Fix Released Status in RACK: In Progress Status in python-watcherclient: In Progress Status in Rally: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Committed Status in shaker: Fix Released Status in Solum: Fix Released Status in tacker: Fix Released Status in tempest: Fix Released Status in tripleo: Fix Released Status in trove-dashboard: Fix Released Status in Vitrage: Fix Committed Status in watcher: Fix Released Status in zaqar: Fix Released Bug description: LOG.warn is deprecated in Python 3 [1] . But it still used in a few places, non-deprecated LOG.warning should be used instead. Note: If we are using logger from oslo.log, warn is still valid [2], but I agree we can switch to LOG.warning. [1]https://docs.python.org/3/library/logging.html#logging.warning [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85 To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1508442/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1613542] Re: tempest.conf doesn't contain $project in [service_available] section
** No longer affects: vitrage
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1613542
Title:
tempest.conf doesn't contain $project in [service_available] section
Status in Aodh:
Fix Released
Status in Ceilometer:
Fix Released
Status in ec2-api:
Fix Released
Status in Gnocchi:
Fix Released
Status in Ironic:
In Progress
Status in Ironic Inspector:
Fix Released
Status in OpenStack Identity (keystone):
Invalid
Status in Magnum:
Fix Released
Status in neutron:
New
Status in OpenStack Data Processing ("Sahara") sahara-tests:
Fix Released
Status in senlin:
Invalid
Status in vmware-nsx:
Fix Released
Bug description:
When generating the tempest conf, the tempest plugins need to register the
config options.
But for the [service_available] section, ceilometer (and the other mentioned
projects) doesn't register any value so it's missng in the tempest sample
config.
Steps to reproduce:
$ tox -egenconfig
$ source .tox/genconfig/bin/activate
$ oslo-config-generator --config-file
.tox/genconfig/lib/python2.7/site-packages/tempest/cmd/config-generator.tempest.conf
--output-file tempest.conf.sample
Now check the [service_available] section from tempest.conf.sample
To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1613542/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1475722] Re: Never use MagicMock
** Also affects: python-heatclient Importance: Undecided Status: New ** Changed in: python-heatclient Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Also affects: swift Importance: Undecided Status: New ** Changed in: swift Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Also affects: python-swiftclient Importance: Undecided Status: New ** Changed in: python-swiftclient Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Also affects: horizon Importance: Undecided Status: New ** Changed in: horizon Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Also affects: rally Importance: Undecided Status: New ** Changed in: rally Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1475722 Title: Never use MagicMock Status in Ceilometer: New Status in Cinder: New Status in heat: New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): New Status in Mistral: In Progress Status in Murano: In Progress Status in python-ceilometerclient: New Status in python-heatclient: New Status in python-mistralclient: New Status in python-muranoclient: In Progress Status in python-neutronclient: In Progress Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Committed Status in python-swiftclient: New Status in python-troveclient: In Progress Status in Rally: New Status in OpenStack Object Storage (swift): New Status in OpenStack DBaaS (Trove): New Bug description: They magically allow things to pass. This is bad. Any usage should be replaced with the Mock class and explicit attributes should be set on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1475722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1475722] Re: Never use MagicMock
** Also affects: barbican Importance: Undecided Status: New ** Changed in: barbican Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1475722 Title: Never use MagicMock Status in Barbican: New Status in Ceilometer: New Status in Cinder: New Status in Designate: New Status in Glance: New Status in heat: New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): New Status in Mistral: In Progress Status in Murano: In Progress Status in Panko: New Status in python-ceilometerclient: New Status in python-heatclient: In Progress Status in python-mistralclient: In Progress Status in python-muranoclient: In Progress Status in python-neutronclient: In Progress Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Committed Status in python-swiftclient: In Progress Status in python-troveclient: In Progress Status in Rally: New Status in OpenStack Object Storage (swift): New Status in OpenStack DBaaS (Trove): New Bug description: They magically allow things to pass. This is bad. Any usage should be replaced with the Mock class and explicit attributes should be set on it. To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1475722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1475722] Re: Never use MagicMock
** Also affects: python-barbicanclient Importance: Undecided Status: New ** Changed in: python-barbicanclient Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1475722 Title: Never use MagicMock Status in Aodh: New Status in Barbican: In Progress Status in Ceilometer: New Status in Cinder: New Status in Designate: New Status in Glance: New Status in heat: New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): New Status in Mistral: In Progress Status in Murano: In Progress Status in Panko: New Status in python-barbicanclient: In Progress Status in python-ceilometerclient: New Status in python-heatclient: In Progress Status in python-mistralclient: In Progress Status in python-muranoclient: In Progress Status in python-neutronclient: In Progress Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Committed Status in python-swiftclient: In Progress Status in python-troveclient: In Progress Status in Rally: New Status in OpenStack Object Storage (swift): New Status in tempest: New Status in OpenStack DBaaS (Trove): New Bug description: They magically allow things to pass. This is bad. Any usage should be replaced with the Mock class and explicit attributes should be set on it. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1475722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1475722] Re: Never use MagicMock
** Also affects: tempest Importance: Undecided Status: New ** Changed in: tempest Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1475722 Title: Never use MagicMock Status in Aodh: New Status in Barbican: In Progress Status in Ceilometer: New Status in Cinder: New Status in Designate: New Status in Glance: New Status in heat: New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): New Status in Mistral: In Progress Status in Murano: In Progress Status in Panko: New Status in python-barbicanclient: In Progress Status in python-ceilometerclient: New Status in python-heatclient: In Progress Status in python-mistralclient: In Progress Status in python-muranoclient: In Progress Status in python-neutronclient: In Progress Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Committed Status in python-swiftclient: In Progress Status in python-troveclient: In Progress Status in Rally: New Status in OpenStack Object Storage (swift): New Status in tempest: New Status in OpenStack DBaaS (Trove): New Bug description: They magically allow things to pass. This is bad. Any usage should be replaced with the Mock class and explicit attributes should be set on it. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1475722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1475722] Re: Never use MagicMock
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1475722 Title: Never use MagicMock Status in Aodh: New Status in Barbican: In Progress Status in Ceilometer: New Status in Cinder: New Status in Designate: New Status in Glance: New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): In Progress Status in keystonemiddleware: New Status in Mistral: In Progress Status in Murano: In Progress Status in OpenStack Compute (nova): New Status in Panko: New Status in python-barbicanclient: In Progress Status in python-ceilometerclient: New Status in python-heatclient: In Progress Status in python-mistralclient: In Progress Status in python-muranoclient: In Progress Status in python-neutronclient: In Progress Status in python-novaclient: New Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Committed Status in python-swiftclient: In Progress Status in python-troveclient: In Progress Status in Rally: New Status in OpenStack Object Storage (swift): New Status in tempest: New Status in OpenStack DBaaS (Trove): New Bug description: They magically allow things to pass. This is bad. Any usage should be replaced with the Mock class and explicit attributes should be set on it. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1475722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1475722] Re: Never use MagicMock
** 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 Identity (keystone). https://bugs.launchpad.net/bugs/1475722 Title: Never use MagicMock Status in Aodh: New Status in Barbican: In Progress Status in Ceilometer: New Status in Cinder: New Status in Designate: New Status in Glance: New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): In Progress Status in keystonemiddleware: New Status in Mistral: In Progress Status in Murano: In Progress Status in OpenStack Compute (nova): New Status in Panko: New Status in python-barbicanclient: In Progress Status in python-ceilometerclient: New Status in python-heatclient: In Progress Status in python-mistralclient: In Progress Status in python-muranoclient: In Progress Status in python-neutronclient: In Progress Status in python-novaclient: New Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Committed Status in python-swiftclient: In Progress Status in python-troveclient: In Progress Status in Rally: New Status in OpenStack Object Storage (swift): New Status in tempest: New Status in OpenStack DBaaS (Trove): New Bug description: They magically allow things to pass. This is bad. Any usage should be replaced with the Mock class and explicit attributes should be set on it. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1475722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1475722] Re: Never use MagicMock
** Also affects: ironic Importance: Undecided Status: New ** Changed in: ironic Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1475722 Title: Never use MagicMock Status in Aodh: In Progress Status in Barbican: In Progress Status in Ceilometer: New Status in Cinder: New Status in Designate: In Progress Status in Glance: New Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic: New Status in OpenStack Identity (keystone): In Progress Status in keystonemiddleware: In Progress Status in Mistral: In Progress Status in Murano: In Progress Status in neutron: In Progress Status in OpenStack Compute (nova): In Progress Status in oslo.log: New Status in oslo.messaging: New Status in oslo.service: New Status in Panko: In Progress Status in python-barbicanclient: In Progress Status in python-ceilometerclient: New Status in python-designateclient: New Status in python-glanceclient: In Progress Status in python-heatclient: In Progress Status in python-mistralclient: In Progress Status in python-muranoclient: In Progress Status in python-neutronclient: In Progress Status in python-novaclient: In Progress Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Committed Status in python-senlinclient: New Status in python-swiftclient: In Progress Status in python-troveclient: In Progress Status in Rally: New Status in senlin: New Status in OpenStack Object Storage (swift): New Status in tacker: New Status in tempest: New Status in OpenStack DBaaS (Trove): New Bug description: They magically allow things to pass. This is bad. Any usage should be replaced with the Mock class and explicit attributes should be set on it. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1475722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1508442] Re: LOG.warn is deprecated
** Changed in: mistral Assignee: Sharat Sharma (sharat-sharma) => (unassigned) ** Changed in: mistral Status: In Progress => Invalid -- 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/1508442 Title: LOG.warn is deprecated Status in anvil: In Progress Status in Aodh: Fix Released Status in Astara: Fix Released Status in Barbican: Fix Released Status in bilean: Fix Released Status in Ceilometer: Fix Released Status in cloud-init: In Progress Status in cloudkitty: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in django-openstack-auth: Fix Released Status in django-openstack-auth-kerberos: In Progress Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in Evoque: In Progress Status in Freezer: In Progress Status in gce-api: Fix Released Status in Glance: In Progress Status in Gnocchi: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in KloudBuster: Fix Released Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in masakari: Fix Released Status in Mistral: Invalid Status in Monasca: New Status in networking-arista: Fix Released Status in networking-calico: In Progress Status in networking-cisco: In Progress Status in networking-fujitsu: Fix Released Status in networking-odl: Fix Committed Status in networking-ofagent: In Progress Status in networking-plumgrid: In Progress Status in networking-powervm: Fix Released Status in networking-vsphere: Fix Released Status in OpenStack Compute (nova): Fix Released Status in nova-powervm: Fix Released Status in nova-solver-scheduler: In Progress Status in octavia: Fix Released Status in openstack-ansible: Fix Released Status in oslo.cache: Fix Released Status in oslo.middleware: New Status in Packstack: Fix Released Status in python-dracclient: Fix Released Status in python-magnumclient: Fix Released Status in RACK: In Progress Status in python-watcherclient: In Progress Status in Rally: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Committed Status in shaker: Fix Released Status in Solum: Fix Released Status in tacker: Fix Released Status in tempest: Fix Released Status in tripleo: Fix Released Status in trove-dashboard: Fix Released Status in Vitrage: Fix Committed Status in watcher: Fix Released Status in zaqar: Fix Released Bug description: LOG.warn is deprecated in Python 3 [1] . But it still used in a few places, non-deprecated LOG.warning should be used instead. Note: If we are using logger from oslo.log, warn is still valid [2], but I agree we can switch to LOG.warning. [1]https://docs.python.org/3/library/logging.html#logging.warning [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85 To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1508442/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1648442] [NEW] [api-ref] The maximum number of characters for a tag not mentioned anywhere
Public bug reported: The maximum number of characters allowed in a tag are 60. The user comes to know the limit only after he exceeds the limit and faces error like this: "Invalid input for operation: 'tooo lng tag 1234567890' exceeds maximum length of 60." The limit must be documented in the api-ref here: http://developer.openstack.org/api-ref/networking/v2/?expanded=add-a -tag-detail,replace-all-tags-detail,remove-all-tags-detail,confirm-a -tag-detail ** Affects: neutron Importance: Undecided Status: New ** Tags: api-ref low-hanging-fruit ** Tags added: api-ref low-hanging-fruit ** Description changed: The maximum number of characters allowed in a tag are 60. The user comes to know the limit only after he exceeds the limit and faces error like this: "Invalid input for operation: 'tooo lng tag 1234567890' exceeds maximum length of 60." - This must be documented in the api-ref here: + The limit must be documented in the api-ref here: http://developer.openstack.org/api-ref/networking/v2/?expanded=add-a -tag-detail,replace-all-tags-detail,remove-all-tags-detail,confirm-a -tag-detail -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1648442 Title: [api-ref] The maximum number of characters for a tag not mentioned anywhere Status in neutron: New Bug description: The maximum number of characters allowed in a tag are 60. The user comes to know the limit only after he exceeds the limit and faces error like this: "Invalid input for operation: 'tooo lng tag 1234567890' exceeds maximum length of 60." The limit must be documented in the api-ref here: http://developer.openstack.org/api-ref/networking/v2/?expanded=add-a -tag-detail,replace-all-tags-detail,remove-all-tags-detail,confirm-a -tag-detail To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1648442/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1599718] [NEW] json formatter is of no use
Public bug reported: When the output is retrieved in the json format using command "neutron net-ip-availability-show -f json", the output is displayed without any indentation. There is a json formatter "--noindent" to display the output without indentation in json format. Though the --noindent option is not used, the output is displayed without indentation. Note: net-ip-availability-show is a sample usecase. This bug applies across all the usecases. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1599718 Title: json formatter is of no use Status in neutron: New Bug description: When the output is retrieved in the json format using command "neutron net-ip-availability-show -f json", the output is displayed without any indentation. There is a json formatter "--noindent" to display the output without indentation in json format. Though the --noindent option is not used, the output is displayed without indentation. Note: net-ip-availability-show is a sample usecase. This bug applies across all the usecases. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1599718/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1614361] Re: tox.ini needs to be updated as openstack infra now supports upper constraints
** Also affects: python-mistralclient Importance: Undecided Status: New ** Changed in: python-mistralclient Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1614361 Title: tox.ini needs to be updated as openstack infra now supports upper constraints Status in Cinder: In Progress Status in Designate: Fix Released Status in Glance: In Progress Status in heat: In Progress Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic Inspector: Fix Released Status in Mistral: Fix Released Status in Murano: Fix Released Status in networking-ovn: Invalid Status in octavia: Fix Released Status in python-mistralclient: New Status in python-muranoclient: Fix Released Status in tacker: In Progress Status in OpenStack DBaaS (Trove): Invalid Status in vmware-nsx: Fix Released Status in zaqar: Fix Released Status in Zaqar-ui: Fix Released Bug description: Openstack infra now supports upper constraints for releasenotes, cover, venv targets. tox.ini uses install_command for these targets, which can now be safely removed. Reference for mail that details this support: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1614361/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1613542] Re: tempest.conf doesn't contain $project in [service_available] section
** Also affects: vitrage
Importance: Undecided
Status: New
** Changed in: vitrage
Assignee: (unassigned) => Sharat Sharma (sharat-sharma)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1613542
Title:
tempest.conf doesn't contain $project in [service_available] section
Status in Aodh:
Fix Released
Status in Ceilometer:
Fix Released
Status in ec2-api:
In Progress
Status in Gnocchi:
Fix Committed
Status in Ironic:
In Progress
Status in Ironic Inspector:
Fix Released
Status in OpenStack Identity (keystone):
Invalid
Status in Magnum:
Fix Released
Status in neutron:
New
Status in OpenStack Data Processing ("Sahara") sahara-tests:
Fix Released
Status in senlin:
In Progress
Status in Vitrage:
New
Status in vmware-nsx:
Fix Released
Bug description:
When generating the tempest conf, the tempest plugins need to register the
config options.
But for the [service_available] section, ceilometer (and the other mentioned
projects) doesn't register any value so it's missng in the tempest sample
config.
Steps to reproduce:
$ tox -egenconfig
$ source .tox/genconfig/bin/activate
$ oslo-config-generator --config-file
.tox/genconfig/lib/python2.7/site-packages/tempest/cmd/config-generator.tempest.conf
--output-file tempest.conf.sample
Now check the [service_available] section from tempest.conf.sample
To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1613542/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1572164] [NEW] Missing response parameter in Identity admin API
Public bug reported: http://developer.openstack.org/api-ref-identity-admin-v2.html#admin- createUser tenant_id parameter is missing from the response parameter table. It is shown in the json example. So, it must be listed. ** Affects: openstack-api-site Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: New ** Tags: keystone ** Changed in: glance Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Project changed: glance => openstack-api-site -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1572164 Title: Missing response parameter in Identity admin API Status in openstack-api-site: New Bug description: http://developer.openstack.org/api-ref-identity-admin-v2.html#admin- createUser tenant_id parameter is missing from the response parameter table. It is shown in the json example. So, it must be listed. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-api-site/+bug/1572164/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1327035] Re: error occurred when swift Pseudo-folder include "="
*** This bug is a duplicate of bug 1347734 *** https://bugs.launchpad.net/bugs/1347734 ** This bug has been marked a duplicate of bug 1347734 The container dashboard does not handle unicode url correctly -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1327035 Title: error occurred when swift Pseudo-folder include "=" Status in OpenStack Dashboard (Horizon): In Progress Bug description: when swift Pseudo-folder include "=" (this kind of usage often use in hive partition), hirizon link will transfer "=" to "%253D", for example, my Pseudo-folder name is "A=B", if I want enter "A=B", actually enter "A%253DB" through horizon To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1327035/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1566477] Re: "networks" object is not documented anywhere
** Project changed: openstack-api-site => nova -- 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/1566477 Title: "networks" object is not documented anywhere Status in OpenStack Compute (nova): In Progress Bug description: The API reference (http://developer.openstack.org/api-ref- compute-v2.1.html) for creating a new server has a request parameter of "networks". There is no example given on how to use this field, yet it is a key piece of information for a new instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1566477/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1283655] Re: Adds host_ip to hypervisor show API
Assigning to myself since there is no activity from a long time. if any one have issues please tell me. ** Changed in: openstack-api-site Assignee: Lucky samadhiya (lucky-samadhiya) => Sharat Sharma (sharat-sharma) ** Changed in: openstack-api-site Status: Triaged => In Progress ** Project changed: openstack-api-site => nova -- 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/1283655 Title: Adds host_ip to hypervisor show API Status in OpenStack Compute (nova): In Progress Status in openstack-manuals: Invalid Bug description: https://review.openstack.org/52733 commit e05566de71f39acad3566fc31ba1053d84130c03 Author: Jay Lau Date: Wed Feb 5 22:44:15 2014 +0800 Adds host_ip to hypervisor show API After no-compute-fanout-to-scheduler, host_ip was stored in the table of compute_nodes. Host ip address should be considered as the hypervisor attribute similar to the hypervisor_type, hypervisor_version etc, and now those attributes such as hypervisor_type, hypervisor_version etc are all listed as the hypervisor attribute when calling "nova hypervisor-show host", so we can also set "host_ip" as a new attribute output for this command. DocImpact 1) Only administrators can view hypervisor detail in nova. 2) It can help improve debug capabilities for nova. For example, if admin using SimpleCIDRAffinityFilter, then after VM is deployed, admin can check if the VM was deployed successfully to the desired host by checking ip address of the host via "nova hypervisor-show host". 3) Add host_ip to the output for "nova hypervisor-show" Implement bp hypervisor-show-ip Change-Id: I006a504d030be1f47beb68a844647026a6daf0ce To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1283655/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1543169] Re: Nova os-volume-types endpoint doesn't exist
Nova api has moved to nova code base.
** Changed in: nova
Status: Invalid => Confirmed
** Changed in: openstack-api-site
Status: Confirmed => Invalid
** Changed in: nova
Assignee: (unassigned) => Sharat Sharma (sharat-sharma)
--
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/1543169
Title:
Nova os-volume-types endpoint doesn't exist
Status in OpenStack Compute (nova):
Confirmed
Status in openstack-api-site:
Invalid
Bug description:
The Nova v2.1 documentation shows an endpoint "os-volume-types" which
lists the available volume types. http://developer.openstack.org/api-
ref-compute-v2.1.html#listVolumeTypes
I am using OpenStack Liberty and that endpoint doesn't appear to exist
anymore. GET requests sent to /v2.1/{tenant_id}/os-volume-types
return 404 not found. When I searched the Nova codebase on GitHub, I
could only find a reference to volume types in the policy.json but not
implemented anywhere.
Does this endpoint still exist, and if so what is the appropriate
documentation?
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1543169/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1515841] Re: Link rot in identity-api-v3-os-inherit-ext
** Changed in: openstack-api-site Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1515841 Title: Link rot in identity-api-v3-os-inherit-ext Status in OpenStack Identity (keystone): Fix Released Status in openstack-api-site: Invalid Bug description: When I visit http://specs.openstack.org/openstack/keystone- specs/api/v3/identity-api-v3-os-inherit-ext.html, I find almost all the links are dead. e.g. Relationship: http://docs.openstack.org/api /openstack-identity/3/ext/OS- INHERIT/1.0/rel/project_user_role_inherited_to_projects To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1515841/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1369140] Re: Add quotas for Server Groups (quota checks)
** Project changed: openstack-api-site => nova -- 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/1369140 Title: Add quotas for Server Groups (quota checks) Status in OpenStack Compute (nova): Confirmed Bug description: https://review.openstack.org/116079 commit 0e9093c30f53d6d44c8290b669b238c21e17a772 Author: Phil Day Date: Thu Aug 21 19:38:28 2014 + Add quotas for Server Groups (quota checks) This third change in a sequence that adds new quota values for server groups, which implements the quota checks. Co-authored-by: Cyril Roelandt Implements: blueprint server-group-quotas DocImpact Change-Id: I535c4ac2475d0b0ca6e14081f92e1c7d111792bd To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1369140/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1490531] Re: api: deprecate the concept of extensions in v2.1
** Changed in: openstack-api-site Status: Confirmed => In Progress ** Project changed: openstack-api-site => nova -- 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/1490531 Title: api: deprecate the concept of extensions in v2.1 Status in OpenStack Compute (nova): In Progress Bug description: https://review.openstack.org/214592 commit 11507eeceb2c56e50e9fe030a70470a02f577f2a Author: John Garbutt Date: Wed Aug 19 13:46:52 2015 +0100 api: deprecate the concept of extensions in v2.1 We want to remove the extension infrastructure in the v2.1 API during the next release. To make that possible, we must deprecate the configuration now. Also deprecating the osapi_v3 group, and moving to osapi_v21. UpgradeImpact DocImpact Part of blueprint nova-api-deprecate-extensions Change-Id: I08b11dceda7cf8f88c157aa67d36490fce49 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1490531/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1521791] Re: Nova client incorrectly lists block storage size units in GB
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- 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/1521791 Title: Nova client incorrectly lists block storage size units in GB Status in OpenStack Compute (nova): New Status in openstack-api-site: In Progress Status in python-novaclient: In Progress Bug description: Both Horizon and the nova client documents the block storage size parameters in gigabytes(GB), when it should be in gibibytes (GiB). Both the cinder and manila clients and associated Horizon panels have been changed to address this issue. Nova should follow suit for consistency. Related bugs: https://bugs.launchpad.net/horizon/+bug/1511167 https://bugs.launchpad.net/python-manilaclient/+bug/1516841 https://bugs.launchpad.net/horizon/+bug/1516848 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1521791/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1543791] Re: Nova API doc for listing servers is missing metadata filter
** Project changed: openstack-api-site => nova
--
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/1543791
Title:
Nova API doc for listing servers is missing metadata filter
Status in OpenStack Compute (nova):
In Progress
Bug description:
I am using Nova v2.1 (Liberty). The documentation for listing servers
only covers a portion of the supported filter options. I don't know
what they all should be but I've found that 'metadata' is one of them.
:-)
List Servers Doc: http://developer.openstack.org/api-ref-
compute-v2.1.html#listServers
Here is the filter method for listing servers where you can see the supported
filters:
https://github.com/openstack/nova/blob/098d4ad487f8431b82d776629f15d13142d42789/nova/compute/api.py#L2027
The query below searches for servers with the metadata "foo=bar", and
is URL encoded:
curl -X "GET"
"http://api.openstacknetsdk.org:8774/v2.1/cae3d055dc5e4828adc4fdfe341168f7/servers/detail?metadata=%7B%22foo%22:%22bar%22%7D";
Without the encoding the query looks like this:
servers/detail?metadata={"foo":"bar"}
I haven't tried any other filters found in that method but they may be
ip (fixed_ip) and system_metadata.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1543791/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1545972] Re: Missing API doc for fault server field
Confirmed in the api-site, so pushing a patch. ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Changed in: nova Status: New => In Progress -- 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/1545972 Title: Missing API doc for fault server field Status in OpenStack Compute (nova): In Progress Status in openstack-api-site: Confirmed Bug description: In API reference[1], optional response field `fault` is not mentioned under `GET /v2/XXX/servers/YYY`. [1] http://developer.openstack.org/api-ref-compute-v2.1.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1545972/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1545972] Re: Missing API doc for fault server field
** Changed in: openstack-api-site Status: Confirmed => Invalid -- 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/1545972 Title: Missing API doc for fault server field Status in OpenStack Compute (nova): In Progress Status in openstack-api-site: Invalid Bug description: In API reference[1], optional response field `fault` is not mentioned under `GET /v2/XXX/servers/YYY`. [1] http://developer.openstack.org/api-ref-compute-v2.1.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1545972/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1542149] Re: Enable volume operations for shelved instances
Hi Bathri, The nova api has moved into nova code base. So, removing the api-site and adding nova. ** Project changed: openstack-api-site => nova -- 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/1542149 Title: Enable volume operations for shelved instances Status in OpenStack Compute (nova): Confirmed Status in openstack-manuals: Opinion Bug description: https://review.openstack.org/265898 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit cf34a32820cc21dd9b9075d5476e050ecd8b34ac Author: Andrea Rosa Date: Mon Jan 11 15:50:09 2016 + Enable volume operations for shelved instances This change enables the attach and detach volume operations for instances which are in shelve and shelved_offloaded state. The code to manage the actual attach and detach is implemented by this change: https://review.openstack.org/259528 New tempest tests are going to be written for testing the new feature. APIImpact DocImpact by this change we are allowing operations which were not allowed before, we need to track this change in the documentation. Partially implements blueprint: volume-ops-when-shelved Change-Id: I43b67a50d998d43a6ff78c917093c513231b6ff2 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1542149/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1550525] Re: Abort an ongoing live migration
** Changed in: openstack-api-site Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Changed in: openstack-api-site Status: Confirmed => In Progress ** Project changed: openstack-api-site => nova -- 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/1550525 Title: Abort an ongoing live migration Status in OpenStack Compute (nova): In Progress Bug description: https://review.openstack.org/277971 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/nova" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit fa002925460e70d988d1b4dd1ea594c680a43740 Author: Andrea Rosa Date: Fri Feb 5 08:31:06 2016 + Abort an ongoing live migration This change adds a DELETE call on the server-migrations object to cancel a running live migration of a specific instance. TO perform the cancellation the virtualization driver needs to support it, in case that the feature is not supported we return an error. We allow a cancellation of a migration only if the migration is running at the moment of the request and if the migration type is equal to 'live-migration'. In this change we implement this feature for the libvirt driver. When the cancellation of a live migration succeeded we rollback the live migration and we set the state of the Migration object equals to 'cancelled'. The implementation of this change is based on the work done by the implementation of the feature called 'force live migration': https://review.openstack.org/245921 DocImpact ApiImpact Implements blueprint: abort-live-migration Change-Id: I1ff861e54997a069894b542bd764ac3ef1b3dbb2 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1550525/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1521791] Re: Nova client incorrectly lists block storage size units in GB
nova api does not exist in api-site anymore. So, moving to invalid. ** Changed in: openstack-api-site Status: In Progress => Invalid -- 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/1521791 Title: Nova client incorrectly lists block storage size units in GB Status in OpenStack Compute (nova): In Progress Status in openstack-api-site: Invalid Status in python-novaclient: In Progress Bug description: Both Horizon and the nova client documents the block storage size parameters in gigabytes(GB), when it should be in gibibytes (GiB). Both the cinder and manila clients and associated Horizon panels have been changed to address this issue. Nova should follow suit for consistency. Related bugs: https://bugs.launchpad.net/horizon/+bug/1511167 https://bugs.launchpad.net/python-manilaclient/+bug/1516841 https://bugs.launchpad.net/horizon/+bug/1516848 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1521791/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1563314] Re: Add microversion changes desription con compute introduction section
** Project changed: openstack-api-site => nova -- 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/1563314 Title: Add microversion changes desription con compute introduction section Status in OpenStack Compute (nova): In Progress Bug description: Add microversion changes description on compute introduction. https://github.com/openstack/nova/blob/4c18867424f09332cf5f7f5678e1f3a984b03618/nova/api/openstack/api_version_request.py#L72 Currently microversion history is not documented. http://developer.openstack.org/api-ref-compute-v2.1.html Ref. see following review comments https://review.openstack.org/#/c/291270/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1563314/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1569555] Re: Request is wrong for compute v2.1 os-flavor-access list
** Project changed: openstack-api-site => nova -- 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/1569555 Title: Request is wrong for compute v2.1 os-flavor-access list Status in OpenStack Compute (nova): In Progress Bug description: The docs say that it takes a tenant_id parameter for listing flavor- access: http://developer.openstack.org/api-ref- compute-v2.1.html#listFlavorAccess But the code doesn't take a tenant_id, only a flavor_id: https://github.com/openstack/nova/blob/2002120c459561d995eac4273befb42b3809d5bb/nova/api/openstack/compute/flavor_access.py#L51 The response in the docs is correct, only the request is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1569555/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1501116] Re: "Image Registry" window contains a text box which overlaps with buttons (Japanese and German)
** Changed in: sahara Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1501116 Title: "Image Registry" window contains a text box which overlaps with buttons (Japanese and German) Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Fix Released Bug description: Project > Data Processing > Image Registry > Register Image The "Register Image" window, "Image Registry tool" text box becomes larger when it contains translated text (only confirmed in German and Japanese, but could be affecting more languages). It overlaps with buttons and other text. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1501116/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1572164] Re: Missing response parameter in Identity admin API
** Project changed: openstack-api-site => keystone -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1572164 Title: Missing response parameter in Identity admin API Status in OpenStack Identity (keystone): In Progress Bug description: http://developer.openstack.org/api-ref-identity-admin-v2.html#admin- createUser tenant_id parameter is missing from the response parameter table. It is shown in the json example. So, it must be listed. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1572164/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1580536] [NEW] Typo in api doc
Public bug reported:
In the
http://developer.openstack.org/api-ref-compute-v2.1.html#os-server-actions-v2.1
section, the sentence is "Enables all users to performs an action on a server.
Specify the action
in the request body.". It must be "Enables all users to perform an action on a
server. Specify the action
in the request body."
** Affects: nova
Importance: Wishlist
Assignee: Sharat Sharma (sharat-sharma)
Status: In Progress
** Tags: low-hanging-fruit
** Changed in: nova
Assignee: (unassigned) => Sharat Sharma (sharat-sharma)
** Changed in: nova
Status: New => In Progress
--
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/1580536
Title:
Typo in api doc
Status in OpenStack Compute (nova):
In Progress
Bug description:
In the
http://developer.openstack.org/api-ref-compute-v2.1.html#os-server-actions-v2.1
section, the sentence is "Enables all users to performs an action on a server.
Specify the action
in the request body.". It must be "Enables all users to perform an action on
a server. Specify the action
in the request body."
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1580536/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1580552] [NEW] Developer Guide: Nova API v2 is deprecated
Public bug reported: Compute API v2 is deprecated but http://docs.openstack.org/developer/nova/#welcome-to-nova-s-developer- documentation still says that v2 API is supported. Both v2 API and v2 extensions are deprecated. ** Affects: nova Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: New ** Tags: low low-hanging-fruit ** Changed in: nova Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Tags added: low low-hanging-fruit -- 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/1580552 Title: Developer Guide: Nova API v2 is deprecated Status in OpenStack Compute (nova): New Bug description: Compute API v2 is deprecated but http://docs.openstack.org/developer/nova/#welcome-to-nova-s-developer- documentation still says that v2 API is supported. Both v2 API and v2 extensions are deprecated. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1580552/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
https://review.openstack.org/#/c/315397/ fix proposed to vitrage ** Also affects: vitrage Importance: Undecided Status: New ** Changed in: vitrage Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Changed in: vitrage Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in anvil: Fix Committed Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in CloudRoast: In Progress Status in congress: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Committed Status in python-keystoneclient: Fix Released Status in python-manilaclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Fix Committed Status in OpenStack SDK: Fix Released Status in python-rackclient: Fix Committed Status in Rally: In Progress Status in Sahara: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: In Progress Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1268480/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
there are no such occurances. ** Changed in: anvil Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in anvil: Invalid Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in CloudRoast: In Progress Status in congress: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Committed Status in python-keystoneclient: Fix Released Status in python-manilaclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Fix Committed Status in OpenStack SDK: Fix Released Status in python-rackclient: Fix Committed Status in Rally: In Progress Status in Sahara: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: In Progress Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1268480/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
No such occurances ** Changed in: python-heatclient Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in anvil: Invalid Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in CloudRoast: In Progress Status in congress: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Invalid Status in python-keystoneclient: Fix Released Status in python-manilaclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Fix Committed Status in OpenStack SDK: Fix Released Status in python-rackclient: Fix Committed Status in Rally: In Progress Status in Sahara: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: In Progress Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1268480/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
** Also affects: zaqar Importance: Undecided Status: New ** Changed in: zaqar Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in anvil: Invalid Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in CloudRoast: In Progress Status in congress: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Invalid Status in python-keystoneclient: Fix Released Status in python-manilaclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Fix Committed Status in OpenStack SDK: Fix Released Status in python-rackclient: Fix Committed Status in Rally: In Progress Status in Sahara: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: In Progress Status in zaqar: In Progress Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1268480/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1564742] Re: [Rules for default security group] miss "security_group_default_rules" parameter
** Changed in: openstack-api-site Assignee: Nam (namnh) => Sharat Sharma (sharat-sharma) ** Project changed: openstack-api-site => nova -- 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/1564742 Title: [Rules for default security group] miss "security_group_default_rules" parameter Status in OpenStack Compute (nova): In Progress Bug description: Request/Response parameters in List default security group rules [1], Create default security group rule [2], Show default security group rule details [3] miss "security_group_default_rule" parameter. [1] http://developer.openstack.org/api-ref-compute-v2.1.html#listSecGroupDefaultRules [2] http://developer.openstack.org/api-ref-compute-v2.1.html#createSecGroupDefaultRule [3] http://developer.openstack.org/api-ref-compute-v2.1.html#showSecGroupDefaultRule To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1564742/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582099] [NEW] Need to create the sample file for Add Floating IP request action.
Public bug reported: Currently, the floating-ips-create-resp.json is used as the request sample for Add (Associate) Floating Ip (Addfloatingip Action) in the servers-actions.inc file. According to TODO, a new request sample file must be created for this action. ** Affects: nova Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: New ** Changed in: nova Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- 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/1582099 Title: Need to create the sample file for Add Floating IP request action. Status in OpenStack Compute (nova): New Bug description: Currently, the floating-ips-create-resp.json is used as the request sample for Add (Associate) Floating Ip (Addfloatingip Action) in the servers-actions.inc file. According to TODO, a new request sample file must be created for this action. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1582099/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1570946] Re: Improve Help Text of Configuration Options in Glance and Glance Store
** Changed in: glance-store Assignee: Sharat Sharma (sharat-sharma) => (unassigned) ** Changed in: glance Status: New => Fix Released ** Changed in: glance-store Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1570946 Title: Improve Help Text of Configuration Options in Glance and Glance Store Status in Glance: Fix Released Status in glance_store: Fix Released Bug description: The overall aim is operators should not need to read and understand the code to know how to configure the system. This lite-spec is focusing on making sure oslo.config has all the information required to generate good sample configuration files and generating good documentation for the configuration options. This spec is not focusing on how the documentation is generated from the option definitions. Most importantly, we need a good description for each of the configuration options, set in the help text of the option. This means developers reviewing each configuration option descriptions and adding any missing details. Nova has found standardizing around a template has helped build some consistency in what is described in the help text for each option. This template, shown below, probably works well for Glance too. # A short description about what it does. If it is a unit (e.g. timeout) # describe the unit which is used (seconds, megabyte, mebibyte, ...) # A long description what the impact and scope is. The operators should # know the expected change in the behavior of Glance if they tweak this. Services which consume this: # A list of services which consume this option. Operators should not be # required to read code to know which one of the services will change its # behavior. Nor should they set this in every configuration file to be # sure. This can really help deployers understand how the option is used. Possible values: # Description of possible values. Especially if this is an option # with numeric values (int, float), describe the edge cases (like the # min value, max value, 0, -1). Further, for choices which are not # obviously named, please describe the affect of each choice. # Note: this does not replace the need for StrOpt.choices, StrOpt.regex, # IntOpt.min, etc. Related options: # Which other config options have to be considered when I change this # one? If it stands solely on its own, use "None" # Note: this does not replace the proposed Opt.related_options, it's used # when extra details are required. When reviewing the description of the configuration, it's worth reviewing the other parameters passed to ``oslo.config``. There have been features added to make the opt definition more precise, but some of the options have not been updated since those new features were added. We must pay particular attention to: * Option type: make sure you are using the best type, and in some cases making better use of custom option types. * Check if there is any extra options that could be used for that type of option to help improve the documentation, such as StrOpt.choices, IntOpt.min * Deprecated: look at deprecating options that are best removed rather than having the documentation improved. Look at removing options that have been deprecated for several releases, but not yet removed. Be sure to set the deprecated_reason setting. * Look out for bad defaults that force install guides to tell users to set configuration value because the default would never work. Always optimize the default for operators rather than the test environment. (NOTE: This is mostly taken from the cross-project spec [0] and adapted to Glance) [0] https://review.openstack.org/#/c/295543/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1570946/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
** Changed in: python-openstackclient Status: Fix Committed => Invalid ** Changed in: python-rackclient Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in anvil: Invalid Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in CloudRoast: In Progress Status in congress: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Invalid Status in python-keystoneclient: Fix Released Status in python-manilaclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Invalid Status in OpenStack SDK: Fix Released Status in python-rackclient: Invalid Status in Rally: In Progress Status in Sahara: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: Fix Released Status in zaqar: In Progress Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1268480/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582706] [NEW] Help message for --request-format is confusing
Public bug reported:
--request-format {json}
DEPRECATED! Only JSON request format is supported.
This is confusing. It is more helpful if it was "XML DEPRECATED! Only
JSON request format is supported."
** Affects: neutron
Importance: Undecided
Assignee: Sharat Sharma (sharat-sharma)
Status: New
** Changed in: nova
Assignee: (unassigned) => Sharat Sharma (sharat-sharma)
--
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/1582706
Title:
Help message for --request-format is confusing
Status in neutron:
New
Bug description:
--request-format {json}
DEPRECATED! Only JSON request format is supported.
This is confusing. It is more helpful if it was "XML DEPRECATED! Only
JSON request format is supported."
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1582706/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582706] Re: Help message for --request-format is confusing
** Project changed: nova => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1582706
Title:
Help message for --request-format is confusing
Status in neutron:
New
Bug description:
--request-format {json}
DEPRECATED! Only JSON request format is supported.
This is confusing. It is more helpful if it was "XML DEPRECATED! Only
JSON request format is supported."
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1582706/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1558939] Re: Truncated hint text due to the limited length set in the field
** Changed in: horizon Status: In Progress => Fix Released ** Changed in: magnum-ui Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1558939 Title: Truncated hint text due to the limited length set in the field Status in OpenStack Dashboard (Horizon): Fix Released Status in Magnum UI: Invalid Bug description: Project > Instances > Launch Instance > Source Japanese version of input hint text "Click here for filters" is truncated and it seems that there is a limit on the length of the text to be visible in the field. English text fits in perfectly but there should be a number of languages in which translation is longer than the English text. It is better if it is not restricated to such short length, so that the entire message can be shown to the users. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1558939/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1508442] Re: LOG.warn is deprecated
** Also affects: freezer Importance: Undecided Status: New ** Changed in: freezer Status: New => In Progress ** Changed in: freezer Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1508442 Title: LOG.warn is deprecated Status in anvil: In Progress Status in Aodh: Fix Released Status in Astara: Fix Released Status in Barbican: Fix Released Status in bilean: Fix Released Status in Blazar: In Progress Status in Ceilometer: Fix Released Status in cloud-init: In Progress Status in cloudkitty: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in django-openstack-auth: Fix Released Status in django-openstack-auth-kerberos: In Progress Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in Evoque: In Progress Status in Freezer: In Progress Status in gce-api: Fix Released Status in Gnocchi: Fix Released Status in heat: Fix Released Status in heat-cfntools: In Progress Status in OpenStack Identity (keystone): Fix Released Status in KloudBuster: Fix Released Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: In Progress Status in networking-arista: In Progress Status in networking-calico: In Progress Status in networking-cisco: In Progress Status in networking-fujitsu: Fix Released Status in networking-odl: In Progress Status in networking-ofagent: In Progress Status in networking-plumgrid: In Progress Status in networking-powervm: Fix Released Status in networking-vsphere: Fix Released Status in neutron: In Progress Status in OpenStack Compute (nova): In Progress Status in nova-powervm: Fix Released Status in nova-solver-scheduler: In Progress Status in octavia: Fix Released Status in openstack-ansible: Fix Released Status in oslo.cache: Fix Released Status in Packstack: Fix Released Status in python-dracclient: Fix Released Status in python-magnumclient: Fix Released Status in RACK: In Progress Status in python-watcherclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in shaker: Fix Released Status in Solum: Fix Released Status in tempest: In Progress Status in tripleo: In Progress Status in trove-dashboard: Fix Released Status in watcher: Fix Released Status in zaqar: In Progress Bug description: LOG.warn is deprecated in Python 3 [1] . But it still used in a few places, non-deprecated LOG.warning should be used instead. Note: If we are using logger from oslo.log, warn is still valid [2], but I agree we can switch to LOG.warning. [1]https://docs.python.org/3/library/logging.html#logging.warning [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85 To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1508442/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1583919] [NEW] --no-ssl-compression is deprecated
Public bug reported: The glance --help gives the following in optional arguments: --no-ssl-compression DEPRECATED! This option is deprecated and not used anymore. SSL compression should be disabled by default by the system SSL library. The deprecated option must not be shown in the help message to avoid confusion. ** Affects: glance Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: New ** Changed in: glance Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1583919 Title: --no-ssl-compression is deprecated Status in Glance: New Bug description: The glance --help gives the following in optional arguments: --no-ssl-compression DEPRECATED! This option is deprecated and not used anymore. SSL compression should be disabled by default by the system SSL library. The deprecated option must not be shown in the help message to avoid confusion. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1583919/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1583923] [NEW] deprecated arguments in the help message
Public bug reported: The help message of glance gives: --key-file OS_KEY DEPRECATED! Use --os-key. --ca-file OS_CACERT DEPRECATED! Use --os-cacert. --cert-file OS_CERT DEPRECATED! Use --os-cert. Instead of showing the correct usage in the help text, the correct arguments only can be displayed as the optional arguments. For example: --os-key instead of --key-file ** Affects: glance Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: New ** Changed in: glance Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1583923 Title: deprecated arguments in the help message Status in Glance: New Bug description: The help message of glance gives: --key-file OS_KEY DEPRECATED! Use --os-key. --ca-file OS_CACERT DEPRECATED! Use --os-cacert. --cert-file OS_CERT DEPRECATED! Use --os-cert. Instead of showing the correct usage in the help text, the correct arguments only can be displayed as the optional arguments. For example: --os-key instead of --key-file To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1583923/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1583923] Re: deprecated arguments in the help message
** Project changed: glance => python-glanceclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1583923 Title: deprecated arguments in the help message Status in python-glanceclient: Confirmed Bug description: The help message of glance gives: --key-file OS_KEY DEPRECATED! Use --os-key. --ca-file OS_CACERT DEPRECATED! Use --os-cacert. --cert-file OS_CERT DEPRECATED! Use --os-cert. Instead of showing the correct usage in the help text, the correct arguments only can be displayed as the optional arguments. For example: --os-key instead of --key-file To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1583923/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1583919] Re: --no-ssl-compression is deprecated
** Project changed: glance => python-glanceclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1583919 Title: --no-ssl-compression is deprecated Status in python-glanceclient: New Bug description: The glance --help gives the following in optional arguments: --no-ssl-compression DEPRECATED! This option is deprecated and not used anymore. SSL compression should be disabled by default by the system SSL library. The deprecated option must not be shown in the help message to avoid confusion. To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1583919/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1424970] Re: VMware: Router Type Extension Support
** Project changed: openstack-api-site => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1424970 Title: VMware: Router Type Extension Support Status in neutron: Incomplete Bug description: https://review.openstack.org/157377 commit a8ed4ad3d345187bb314c7c574a1476de1a16584 Author: Gary Kotton Date: Thu Feb 19 05:55:14 2015 -0800 VMware: Router Type Extension Support Provide a router type extension. This will enable defining the type of edge appliance. That is, an exclusive edge or a shared edge for routing services. DocImpact Change-Id: I1464d0390c0b3ee7658e7955e6433f2ac078a5fe To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1424970/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1174499] Re: Keystone token hashing is MD5
** Changed in: openstack-api-site Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1174499 Title: Keystone token hashing is MD5 Status in django-openstack-auth: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in openstack-api-site: Invalid Status in python-keystoneclient: Fix Released Bug description: https://github.com/openstack/python- keystoneclient/blob/master/keystoneclient/common/cms.py def cms_hash_token(token_id): """ return: for ans1_token, returns the hash of the passed in token otherwise, returns what it was passed in. """ if token_id is None: return None if is_ans1_token(token_id): hasher = hashlib.md5() hasher.update(token_id) return hasher.hexdigest() else: return token_id MD5 is a deprecated mechanism, it should be replaces with at least SHA1, if not SHA256. Keystone should be able to support multiple Hash types, and the auth_token middleware should query Keystone to find out which type is in use. To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1174499/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: designate Importance: Undecided Status: New ** Changed in: designate Status: New => In Progress ** Changed in: designate Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: Fix Released Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: Fix Released Status in Designate: In Progress Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in octavia: Fix Released Status in ooi: Fix Released Status in os-client-config: Fix Released Status in python-barbicanclient: Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in Sahara: Fix Released Status in Solum: Fix Released Status in Stackalytics: In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Status in designate package in Ubuntu: Fix Released Status in python-tuskarclient package in Ubuntu: Fix Committed Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: watcher Importance: Undecided Status: New ** Changed in: watcher Status: New => In Progress ** Changed in: watcher Assignee: (unassigned) => Sharat Sharma (sharat-sharma) ** Changed in: python-openstackclient Status: In Progress => 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: Fix Released Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: Fix Released Status in Designate: In Progress Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in octavia: Fix Released Status in ooi: Fix Released Status in os-client-config: Fix Released Status in python-barbicanclient: Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: Fix Released Status in OpenStack SDK: In Progress Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in Sahara: Fix Released Status in Solum: Fix Released Status in Stackalytics: In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in tuskar: Fix Released Status in watcher: In Progress Status in zaqar: Fix Released Status in designate package in Ubuntu: Fix Released Status in python-tuskarclient package in Ubuntu: Fix Committed Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1585025] Re: Normalize the options use singele quotes
*** This bug is a duplicate of bug 1584558 *** https://bugs.launchpad.net/bugs/1584558 ** This bug has been marked a duplicate of bug 1584558 Some config options in codes use double quotes but most of the options use single quotes and that need to be normalized -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1585025 Title: Normalize the options use singele quotes Status in Glance: New Bug description: https://review.openstack.org/319720 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/glance" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 208c96ab1438e643eb274aaf0c07883c556cd635 Author: liangjingtao Date: Mon May 23 11:29:41 2016 +0800 Normalize the options use singele quotes Some config options in codes use double quotes but most of the options use single quotes and that need to be normalized DocImpact Closes-Bug: #1584558 Change-Id: I828326d9bb22b6cb98885255ebc0dfcc1efc0497 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1585025/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1587418] [NEW] router-create takes first parameter as name
Public bug reported: While creating a router the following situation occurred: [root@Mitaka5 ~(keystone_admin)]# neutron router-create --description "This is a bug" router_one Created a new router: +-+--+ | Field | Value| +-+--+ | admin_state_up | True | | availability_zone_hints | | | availability_zones | | | description | router_one | | distributed | False| | external_gateway_info | | | ha | False| | id | 7aecee37-b665-4ab2-aad0-1ce58b388004 | | name| This is a bug| | routes | | | status | ACTIVE | | tenant_id | 9d56bfe003a341fea149442236760e0f | +-+--+ Here the description is considered as name and name is considered as description. Summary: The first field is always taken to be name. ** Affects: neutron Importance: Undecided Assignee: Pallavi (pallavi-s) Status: Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1587418 Title: router-create takes first parameter as name Status in neutron: Confirmed Bug description: While creating a router the following situation occurred: [root@Mitaka5 ~(keystone_admin)]# neutron router-create --description "This is a bug" router_one Created a new router: +-+--+ | Field | Value| +-+--+ | admin_state_up | True | | availability_zone_hints | | | availability_zones | | | description | router_one | | distributed | False| | external_gateway_info | | | ha | False| | id | 7aecee37-b665-4ab2-aad0-1ce58b388004 | | name| This is a bug| | routes | | | status | ACTIVE | | tenant_id | 9d56bfe003a341fea149442236760e0f | +-+--+ Here the description is considered as name and name is considered as description. Summary: The first field is always taken to be name. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1587418/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1587719] [NEW] no option to view the interfaces attached to router from CLI
Public bug reported: There is no way to view the interfaces attached to a router from the CLI. To know the interfaces attached to the router, we have to rely on dashboard. So an extra field has to be added to the router-show table to display the attached interfaces. ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: New ** Changed in: neutron Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1587719 Title: no option to view the interfaces attached to router from CLI Status in neutron: New Bug description: There is no way to view the interfaces attached to a router from the CLI. To know the interfaces attached to the router, we have to rely on dashboard. So an extra field has to be added to the router-show table to display the attached interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1587719/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1587723] [NEW] routers created as demo user are not listed when admin
Public bug reported: Steps to reproduce: 1. Create a router as demo user 2. From CLI, the router can be listed when you are admin user 3. From dashboard, the router is not listed when logged in as admin ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: New ** Changed in: neutron Assignee: (unassigned) => Sharat Sharma (sharat-sharma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1587723 Title: routers created as demo user are not listed when admin Status in neutron: New Bug description: Steps to reproduce: 1. Create a router as demo user 2. From CLI, the router can be listed when you are admin user 3. From dashboard, the router is not listed when logged in as admin To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1587723/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1587723] Re: routers created as demo user are not listed when admin
** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1587723 Title: routers created as demo user are not listed when admin Status in neutron: Invalid Bug description: Steps to reproduce: 1. Create a router as demo user 2. From CLI, the router can be listed when you are admin user 3. From dashboard, the router is not listed when logged in as admin To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1587723/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1588262] [NEW] yaml option displayed twice
Public bug reported:
The help message of "neutron rbac-list" displays "yaml" twice in the
output formatters option.
Steps to reproduce:
1. neutron rbac-list --help
Output:
..
output formatters:
output formatter options
-f {csv,html,json,json,table,value,yaml,yaml}, --format
{csv,html,json,json,table,value,yaml,yaml}
the output format, defaults to table
The yaml option need not be displayed twice.
** Affects: neutron
Importance: Undecided
Assignee: Sharat Sharma (sharat-sharma)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Sharat Sharma (sharat-sharma)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1588262
Title:
yaml option displayed twice
Status in neutron:
New
Bug description:
The help message of "neutron rbac-list" displays "yaml" twice in the
output formatters option.
Steps to reproduce:
1. neutron rbac-list --help
Output:
..
output formatters:
output formatter options
-f {csv,html,json,json,table,value,yaml,yaml}, --format
{csv,html,json,json,table,value,yaml,yaml}
the output format, defaults to table
The yaml option need not be displayed twice.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1588262/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1588262] Re: yaml option displayed twice
** Project changed: neutron => python-neutronclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1588262
Title:
yaml option displayed twice
Status in python-neutronclient:
Confirmed
Bug description:
The help message of "neutron rbac-list" displays "yaml" twice in the
output formatters option.
Steps to reproduce:
1. neutron rbac-list --help
Output:
..
output formatters:
output formatter options
-f {csv,html,json,json,table,value,yaml,yaml}, --format
{csv,html,json,json,table,value,yaml,yaml}
the output format, defaults to table
The yaml option need not be displayed twice.
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1588262/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1558090] [NEW] Delete multiple networks from CLI
Public bug reported: If I try to delete multiple networks through cli, only one network gets deleted at a time. We should have the option to delete multiple networks simultaneously to be in sync with dashboard. For ex: If I create 2 networks n1 and n2 from dashboard, I am able to delete both of them through dashboard if I select both the networks for delete. But if I try the same functionality in cli, I get the following output: [root@liberty2 ~(keystone_admin)]# neutron net-list +--+--+--+ | id | name | subnets | +--+--+--+ | bda0b455-a838-4004-9f7c-dceeefd47473 | n2 | 69275ced-1df0-4aa8-8fcd-54296dca1cee 30.0.0.0/24 | | cbe71faf-be6f-4e0d-b3a2-74d83b5fb1c9 | internal | 2664b3a4-d587-43cb-8985-55f2bc9433aa 120.0.0.0/24| | 3da43b68-e8f8-4aa3-bf23-420ae7cc39fc | n1 | bb622270-98df-4529-b92f-816f59e9e2c9 20.0.0.0/24 | | effb89f5-34bb-4dbe-bc50-e434614419fe | public | f2845986-7b21-46b1-a9db-8b178e739e4a 172.24.4.224/28 | +--+--+--+ [root@liberty2 ~(keystone_admin)]# neutron net-delete n1 n2 Deleted network: n1 [root@liberty2 ~(keystone_admin)]# neutron net-list +--+--+--+ | id | name | subnets | +--+--+--+ | bda0b455-a838-4004-9f7c-dceeefd47473 | n2 | 69275ced-1df0-4aa8-8fcd-54296dca1cee 30.0.0.0/24 | | cbe71faf-be6f-4e0d-b3a2-74d83b5fb1c9 | internal | 2664b3a4-d587-43cb-8985-55f2bc9433aa 120.0.0.0/24| | effb89f5-34bb-4dbe-bc50-e434614419fe | public | f2845986-7b21-46b1-a9db-8b178e739e4a 172.24.4.224/28 | +--+--+--+ Observation: The n2 networks do not get deleted and there is no notification for the same, net delete only reads the first argument that it gets. We should either have the option to delete multiple networks simultaneously and if my understanding if wrong then there should be a check for the number of arguments that have been passed for the net-delete command. ** Affects: neutron Importance: Undecided Assignee: Sharat Sharma (sharat-sharma) Status: Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1558090 Title: Delete multiple networks from CLI Status in neutron: Confirmed Bug description: If I try to delete multiple networks through cli, only one network gets deleted at a time. We should have the option to delete multiple networks simultaneously to be in sync with dashboard. For ex: If I create 2 networks n1 and n2 from dashboard, I am able to delete both of them through dashboard if I select both the networks for delete. But if I try the same functionality in cli, I get the following output: [root@liberty2 ~(keystone_admin)]# neutron net-list +--+--+--+ | id | name | subnets | +--+--+--+ | bda0b455-a838-4004-9f7c-dceeefd47473 | n2 | 69275ced-1df0-4aa8-8fcd-54296dca1cee 30.0.0.0/24 | | cbe71faf-be6f-4e0d-b3a2-74d83b5fb1c9 | internal | 2664b3a4-d587-43cb-8985-55f2bc9433aa 120.0.0.0/24| | 3da43b68-e8f8-4aa3-bf23-420ae7cc39fc | n1 | bb622270-98df-4529-b92f-816f59e9e2c9 20.0.0.0/24 | | effb89f5-34bb-4dbe-bc50-e434614419fe | public | f2845986-7b21-46b1-a9db-8b178e739e4a 172.24.4.224/28 | +--+--+--+ [root@liberty2 ~(keystone_admin)]# neutron net-delete n1 n2 Deleted network: n1 [root@liberty2 ~(keystone_admin)]# neutron net-list +--+--+--+ | id | name | subnets | +--+--+--+ | bda0b455-a838-4004-9f7c-dceeefd47473 | n2 | 69275ced-1df0-4aa8-8fcd-54296dca1cee 30.0.0.0/24 | | cbe71faf-be6f-4e0d-b3a2-74d83b5fb1c9 | internal | 2664b3a4-d587-43cb
