[Yahoo-eng-team] [Bug 1931683] Re: Old root volume status is incorrect after rebuilding instance
** Changed in: nova 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/1931683 Title: Old root volume status is incorrect after rebuilding instance Status in OpenStack Compute (nova): Invalid Bug description: When rebuild volume backed instance, the old root volume status change to reserved. The reason is nova create new attachment for each bdm when rebuilding instance. For old root volume, it is unnecessary to create new attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1931683/+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 1931683] [NEW] Old root volume status is incorrect after rebuilding instance
Public bug reported: When rebuild volume backed instance, the old root volume status change to reserved. The reason is nova create new attachment for each bdm when rebuilding instance. For old root volume, it is unnecessary to create new attachment. ** Affects: nova Importance: Undecided Status: 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/1931683 Title: Old root volume status is incorrect after rebuilding instance Status in OpenStack Compute (nova): In Progress Bug description: When rebuild volume backed instance, the old root volume status change to reserved. The reason is nova create new attachment for each bdm when rebuilding instance. For old root volume, it is unnecessary to create new attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1931683/+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 1715451] Re: Castellan 0.13.0 doesn't work with ConfKeyManager due to missing list() abstract method
** Changed in: nova 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/1715451 Title: Castellan 0.13.0 doesn't work with ConfKeyManager due to missing list() abstract method Status in castellan: Fix Released Status in Cinder: Fix Released Status in OpenStack Compute (nova): Invalid Status in OpenStack Global Requirements: New Bug description: Seen here: https://review.openstack.org/#/c/500770/ http://logs.openstack.org/70/500770/7/check/gate-tempest-dsvm-neutron- full-ubuntu- xenial/b813494/logs/screen-c-api.txt.gz?level=TRACE#_Sep_06_17_25_08_182255 This change in castellan 0.13.0 breaks cinder's ConfKeyManager: https://github.com/openstack/castellan/commit/1a13c2b2030390e3c0a5d498da486d92ddd1152c Because the Cinder ConfKeyManager extends the abstract KeyManager class in castellan but doesn't implement the list() method. To manage notifications about this bug go to: https://bugs.launchpad.net/castellan/+bug/1715451/+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 1715451] Re: Castellan 0.13.0 doesn't work with ConfKeyManager due to missing list() abstract method
This bug should affect nova similarly. ** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1715451 Title: Castellan 0.13.0 doesn't work with ConfKeyManager due to missing list() abstract method Status in castellan: New Status in Cinder: In Progress Status in OpenStack Compute (nova): New Status in OpenStack Global Requirements: New Bug description: Seen here: https://review.openstack.org/#/c/500770/ http://logs.openstack.org/70/500770/7/check/gate-tempest-dsvm-neutron- full-ubuntu- xenial/b813494/logs/screen-c-api.txt.gz?level=TRACE#_Sep_06_17_25_08_182255 This change in castellan 0.13.0 breaks cinder's ConfKeyManager: https://github.com/openstack/castellan/commit/1a13c2b2030390e3c0a5d498da486d92ddd1152c Because the Cinder ConfKeyManager extends the abstract KeyManager class in castellan but doesn't implement the list() method. To manage notifications about this bug go to: https://bugs.launchpad.net/castellan/+bug/1715451/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** Changed in: python-barbicanclient Status: Fix Committed => Fix Released ** Changed in: bandit Status: Fix Committed => Fix Released ** Changed in: barbican Status: Fix Committed => Fix Released -- 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/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Astara: Fix Released Status in Bandit: Fix Released Status in Barbican: Fix Released Status in Blazar: New Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in congress: Fix Released Status in daisycloud-core: New Status in Designate: Fix Released Status in Freezer: In Progress Status in Glance: Fix Released Status in glance_store: Fix Released Status in Higgins: New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Murano: Fix Released Status in networking-calico: Fix Released Status in networking-infoblox: In Progress Status in networking-l2gw: In Progress Status in networking-sfc: Fix Released Status in OpenStack Compute (nova): Won't Fix Status in os-brick: Fix Released Status in PBR: Fix Released Status in pycadf: Fix Released Status in python-barbicanclient: Fix Released Status in python-ceilometerclient: Invalid Status in python-cinderclient: Fix Released Status in python-designateclient: Fix Committed Status in Glance Client: Fix Released Status in python-mistralclient: Fix Released Status in python-solumclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in Rally: New Status in Sahara: Fix Released Status in Solum: Fix Released Status in sqlalchemy-migrate: New Status in SWIFT: In Progress Status in tacker: In Progress Status in tempest: Invalid Status in zaqar: Fix Released Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/astara/+bug/1259292/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
** Changed in: anvil Status: In Progress => 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/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in anvil: Invalid Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: In Progress Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Confirmed Status in octavia: Fix Released Status in os-vif: In Progress Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Swift Authentication: In Progress Status in OpenStack Object Storage (swift): In Progress Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1608980/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
** Also affects: keystoneauth Importance: Undecided Status: New ** Changed in: keystoneauth Assignee: (unassigned) => Jeremy Liu (liujiong) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: In Progress Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Confirmed Status in octavia: Fix Released Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Swift Authentication: In Progress Status in OpenStack Object Storage (swift): In Progress Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/craton/+bug/1608980/+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 1590608] Re: Services should use http_proxy_to_wsgi middleware
** Also affects: sahara Importance: Undecided Status: New ** Changed in: sahara Assignee: (unassigned) => Jeremy Liu (liujiong) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1590608 Title: Services should use http_proxy_to_wsgi middleware Status in Aodh: Fix Released Status in Barbican: In Progress Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in cloudkitty: In Progress Status in congress: New Status in Freezer: In Progress Status in Glance: Fix Released Status in Gnocchi: Fix Committed Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Magnum: New Status in neutron: Fix Released Status in Panko: Fix Released Status in Sahara: In Progress Status in OpenStack Search (Searchlight): In Progress Status in senlin: In Progress Status in OpenStack DBaaS (Trove): In Progress Bug description: It's a common problem when putting a service behind a load balancer to need to forward the Protocol and hosts of the original request so that the receiving service can construct URLs to the loadbalancer and not the private worker node. Most services have implemented some form of secure_proxy_ssl_header = HTTP_X_FORWARDED_PROTO handling however exactly how this is done is dependent on the service. oslo.middleware provides the http_proxy_to_wsgi middleware that handles these headers and the newer RFC7239 forwarding header and completely hides the problem from the service. This middleware should be adopted by all services in preference to their own HTTP_X_FORWARDED_PROTO handling. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1590608/+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 1590608] Re: Services should use http_proxy_to_wsgi middleware
** Also affects: freezer Importance: Undecided Status: New ** Changed in: freezer Assignee: (unassigned) => Jeremy Liu (liujiong) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1590608 Title: Services should use http_proxy_to_wsgi middleware Status in Aodh: Fix Released Status in Barbican: In Progress Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in cloudkitty: In Progress Status in congress: New Status in Freezer: In Progress Status in Glance: Fix Released Status in Gnocchi: Fix Committed Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Magnum: New Status in neutron: In Progress Status in Panko: Fix Released Status in OpenStack Search (Searchlight): In Progress Status in senlin: In Progress Status in OpenStack DBaaS (Trove): In Progress Bug description: It's a common problem when putting a service behind a load balancer to need to forward the Protocol and hosts of the original request so that the receiving service can construct URLs to the loadbalancer and not the private worker node. Most services have implemented some form of secure_proxy_ssl_header = HTTP_X_FORWARDED_PROTO handling however exactly how this is done is dependent on the service. oslo.middleware provides the http_proxy_to_wsgi middleware that handles these headers and the newer RFC7239 forwarding header and completely hides the problem from the service. This middleware should be adopted by all services in preference to their own HTTP_X_FORWARDED_PROTO handling. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1590608/+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: castellan Importance: Undecided Status: New ** Changed in: castellan Assignee: (unassigned) => Jeremy Liu (liujiong) ** Also affects: python-barbicanclient Importance: Undecided Status: New ** Changed in: python-barbicanclient Assignee: (unassigned) => Jeremy Liu (liujiong) ** Also affects: freezer Importance: Undecided Status: New ** Changed in: freezer Assignee: (unassigned) => Jeremy Liu (liujiong) -- 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: In Progress Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in Designate: Fix Released Status in Freezer: In Progress 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 networking-ovn: Invalid Status in octavia: Fix Released Status in python-barbicanclient: In Progress Status in python-mistralclient: In Progress 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 1323975] Re: do not use default=None for config options
** Also affects: castellan Importance: Undecided Status: New ** Also affects: freezer Importance: Undecided Status: New ** Changed in: freezer Assignee: (unassigned) => Jeremy Liu (liujiong) ** Changed in: castellan Assignee: (unassigned) => Jeremy Liu (liujiong) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1323975 Title: do not use default=None for config options Status in Aodh: Fix Released Status in Barbican: Fix Released Status in castellan: In Progress Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in Freezer: In Progress Status in Glance: Fix Released Status in glance_store: Fix Released Status in Gnocchi: Fix Released Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Murano: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in oslo-incubator: Fix Released Status in oslo.messaging: Fix Released Status in Rally: Fix Released Status in Sahara: Fix Released Status in OpenStack DBaaS (Trove): In Progress Status in zaqar: Fix Released Bug description: In the cfg module default=None is set as the default value. It's not necessary to set it again when defining config options. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1323975/+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
