** Also affects: keystone
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/2028409
Title:
Add domain_id config option to
test_get_console_output_server_id_in_shutoff_status test was always
wrong since starting which used to get the console for the server
created in the setup method and is in active state. This test never
tried to get the console of the shutoff server.
It is still unknown how this wrong test
marking invalid for neutron as fix is in tempest
https://review.opendev.org/c/openstack/tempest/+/888590
** Changed in: tempest
Status: New => Fix Committed
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of
** Also affects: tempest
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/2027817
Title:
neutron slow jobs before xena broken with ERROR:
as fix was in devstack, i am marking rest other projects as invalid.
Thanks Dan, Rajat for working on this.
** Changed in: tempest
Status: New => Invalid
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: devstack
Status: New => Fix Committed
**
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
** Also affects: devstack-plugin-ceph
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
nova-lvm job started failing 100% on few volume detach tests. It started
failing when we move it to run on Ubuntu jammy (22.04).
Below tests are failing::
tearDownClass (tempest.api.compute.servers.test_server_rescue
ServerStableDeviceRescueTest)
Public bug reported:
I was testing the tempest with the new RBAC enabled which means in
neutron.conf enable the below options:
[oslo_policy]
enforce_scope = True
enforce_new_defaults = True
Public bug reported:
I was testing the tempest with new RBAC enabled which mean in
neutron.conf enable the below options:
[oslo_policy]
enforce_scope = True
enforce_new_defaults = True
Closing it for nova as it is fixed on the tempest side.
** Changed in: nova
Status: Triaged => 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/1960346
adding tempest for
https://review.opendev.org/q/topic:wait_until_sshable_pingable fixes and
we will see if that fixes the things. if it does then we can remove the
nova from this bug.
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: tempest
Status: New
nothing to do in devstack side, Marking as invalid.
** Changed in: devstack
Status: Incomplete => 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/1957941
Title:
Agree with Lajos, marked invalid for neutron
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: devstack
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
yeah, jobs are made voting also now and working fine
https://review.opendev.org/c/openstack/tempest/+/824962
** Changed in: neutron
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Thanks yatin.
Marking invalid for tempest as nothing to do in Tempest.
** Changed in: tempest
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/1957941
Title:
Public bug reported:
Two test_network_basic_ops tests are failing consistently (since ~ Jan
14th 01 UTC) in centos-8-stream jobs (nova side tempest-integrated-
compute-centos-8-stream and tempest tempest-full-py3-centos-8-stream
jobs)
1.
Issue is in job variant match in devstack-ceph-plugin fixing in
https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/811478
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** Also affects: devstack-plugin-ceph
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/1945358
Title:
nova-ceph-multistore job
Public bug reported:
nova-ceph-multistore is broken on stable branches:
+ lib/cinder_backends/ceph:configure_cinder_backend_ceph:56 :
is_service_enabled c-bak
+ functions-common:is_service_enabled:1966 : return 0
+ lib/cinder_backends/ceph:configure_cinder_backend_ceph:57 : sudo ceph -c
reverted the devstack change fixed this
https://review.opendev.org/c/openstack/devstack/+/804025
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: devstack
Status: New => Fix Released
--
You received this bug notification because you are a member of
#L528-L537
In xena PTG, we agreed to fix this by returning 400 in all cases and
backport the fix. L446: https://etherpad.opendev.org/p/nova-xena-ptg
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: Triaged
** Tags: api
** Changed in:
Yes, that is expected behaviour actually. Expected I mean until we
remove the legacy policy rules where the reader is nothing but the
owner.
We have not removed the legacy policy support yet and they are still
present as deprecated rule
-
** Also affects: oslo.policy
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/1913718
Title:
rally ci job is unstable - port list takes very
marking invalid from nova side as no fix needed on nova side for this.
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
There are multiple places where nova set the new default value for other
(than nova) namespace config option for example oslo lib config options.
That is done via oslo APO set_defaults, like
-
in: python-watcherclient
Status: New => Fix Released
** Changed in: watcher
Status: New => Fix Released
** Changed in: taskflow
Status: New => Fix Released
** Changed in: solum
Status: New => Fix Released
** Changed in: solum
Assignee: (unassigned) =>
** Changed in: coverage2sql
Status: New => Fix Released
** Changed in: zaqar
Status: New => Fix Released
** Changed in: tacker
Status: New => Fix Released
** Changed in: coverage2sql
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
** Change
adding devstack also as devstack needs to move to opensuse 15.2[1] which
has qemu 4.2.0 available
also move jobs to run on opensuse 15.2 will fix this.
[1]https://github.com/openstack/devstack/blob/5aa38f51b3dd0660a0622aecd65937d3c56eedc2/stack.sh#L224
** Also affects: devstack
Importance:
closing it for oslo polocy also as all required work is done under -
https://review.opendev.org/#/q/topic:migrate-to-focal-
oslo+(status:open+OR+status:merged)
** Changed in: oslo.policy
Status: New => Fix Released
** Changed in: oslo.policy
Assignee: (unassigned) => Ghanshya
atus: New => In Progress
** Changed in: manila
Status: New => Fix Committed
** Changed in: manila
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
** Also affects: tacker
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/1885825
Title:
No implicit user creation with GRANT
** Also affects: tacker
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/1886298
Title:
Few of the lower constraints are not
** Also affects: python-senlinclient
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/1886298
Title:
Few of the lower
** Also affects: solum
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/1886298
Title:
Few of the lower constraints are not
** Also affects: python-troveclient
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/1886298
Title:
Few of the lower
** Also affects: os-win
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/1886298
Title:
Few of the lower constraints are not
** Also affects: python-watcherclient
Importance: Undecided
Status: New
** Also affects: watcher
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).
** Also affects: zaqar
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/1885825
Title:
No implicit user creation with GRANT
** Also affects: masakari
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/1886298
Title:
Few of the lower constraints are not
** Also affects: futurist
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/1886298
Title:
Few of the lower constraints are not
** Also affects: oslo.policy
Importance: Undecided
Status: New
** Also affects: oslo.reports
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).
** Also affects: taskflow
Importance: Undecided
Status: New
** Changed in: python-glanceclient
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
** Changed in: castellan
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
** Changed in: ec2-api
As
** Also affects: castellan
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/1886298
Title:
Few of the lower constraints are
** Also affects: ec2-api
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/1886298
Title:
Few of the lower constraints are not
** Also affects: coverage2sql
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/1885825
Title:
No implicit user creation with
** Also affects: keystone
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/1885825
Title:
No implicit user creation with GRANT
** Also affects: python-keystoneclient
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/1886298
Title:
Few of the lower
** Also affects: python-glanceclient
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/1886298
Title:
Few of the lower
** Also affects: manila-ui
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/1886298
Title:
Few of the lower constraints are
** Description changed:
- Markupsafe 1.0 fail the lower-constraints job with
+ lower constraint are being tested with python.6 till now and jobs
+ running fine. With the migration of testing to ubuntu focal where
+ python3.8 is default, lower-constraints job started failing due to
+ multiple
Public bug reported:
Markupsafe 1.0 fail the lower-constraints job with
ImportError: cannot import name 'Feature' from 'setuptools'
-
https://zuul.opendev.org/t/openstack/build/df8ddce0a9c84397bfe3976cf955fcbb/log
/job-output.txt
Issue is fixed in Markupsafe 1.1.1
-
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
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/1885825
Title:
No implicit use
adding cinder also if something from cinder side during detachment.
** Also affects: cinder
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).
** Changed in: devstack
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/1884256
Title:
'tox' not present on devstack based jobs
Status in devstack:
** Also 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/1884256
Title:
'tox' not present on devstack based jobs
Status in
Public bug reported:
with the new release of sphinx 3.1.0, nova pdf docs build started
failing with "! Dimension too large." error. That started failing since
10th June when the OpenStack requirement added a new constraint for
sphinx.
Seems like somewhere TeX memory is exhausted during the pdf
That is correct what you wrote above. But tricky part here is generated
policy.json from 'oslopolicy-sample-generator' tool without deprecated
rules is right thing or wrong. Because it can be seen as one of the
valid usgae for deployer who want to switch to new defaults. The only
way for them till
nassigned) => Ghanshyam Mann (ghanshyammann)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1871327
Title:
stable/stein tempest-full job fails with "tempest requires Python
'>=
to access)
-
https://github.com/openstack/nova/blob/c16315165ce307c605cf4b608b2df3aa06f46982/nova/policy.py#L191
[1]
-
https://github.com/openstack/nova/blob/cd16ae25c865f25dbb313976b3d8ef9372db80af/nova/policies/servers.py#L285
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam
Public bug reported:
server tags API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/717425
This is because API does not pass the server project_id in policy target
Public bug reported:
server resume API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/717182/
This is because API does not pass the server project_id in policy
Public bug reported:
server shelve API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/717182/
This is because API does not pass the server project_id in policy
Public bug reported:
server topology index policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/717524/
This is because API does not pass the server project_id in policy
Public bug reported:
server password API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/717204
This is because API does not pass the server project_id in policy
Public bug reported:
server metadata API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/717182/
This is because API does not pass the server project_id in policy
Public bug reported:
os-security-groups restore server API policy is default to
admin_or_owner[1] but API is allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/716779/
This is because API does not pass the server
Public bug reported:
unpause server API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/716161//1
This is because API does not pass the server project_id in policy
Public bug reported:
unlock server API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/716057/
This is because API does not pass the server project_id in policy
Public bug reported:
limits API policy is allowed for everyone but policy is default to
admin_or_owner[1].
This is because API does not pass the project_id in policy target so that oslo
policy can decide the ownership.
Public bug reported:
os-ips API policy is default to admin_or_owner[1] but API is allowed for
everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/715477/
This is because API does not pass the server project_id in policy target
-
/nova/policies/flavor_access.py#L49
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: New
** Changed in: nova
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
--
You received this bug notification because you are a mem
as discussed on review, we should not change the fetal=false, instead we
can adjust the test to verify the things. In this case, we should use
the response to verify the policy enforcement not 403.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification
Public bug reported:
os-deferred-delete restore server API policy is default to
admin_or_owner[1] but API is allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/707455/
This is because API does not pass the server
Public bug reported:
os-create-backup API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/706726/
This is because API does not pass the server project_id in policy
Public bug reported:
os-console-output API policy is default to admin_or_owner[1] but API is
allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/706724/
This is because API does not pass the server project_id in policy
Public bug reported:
os-availability-zone API policy is default to admin_or_owner[1] but API
is allowed for everyone.
This is because API does not pass the project_id in policy target so that oslo
policy can decide the ownership.
Public bug reported:
os-attach-interfaces APi policy is default to admin_or_owner[1] but API
is allowed for everyone.
We can see the test trying with other project context can access the API
- https://review.opendev.org/#/c/705126/1
This is because API does not pass the server project_id in
** Changed in: devstack
Status: Confirmed => Fix Released
** Changed in: tempest
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1859988
It is not required to backport on stable/queens as such.
stable/queens has been pinned with compatible Tempest tag -
https://review.opendev.org/#/c/703679/
** Changed in: devstack
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Importance: Undecided
Status: New
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: tempest
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
** Changed in: tempest
Importance: Undecided => Critical
--
You received this bug notification b
** Also affects: devstack
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/1860033
Title:
Tempest jobs broken on stable branches due to
/nova/blob/964d7dc87989b5765fcc60d34f734963ab8e03e7/nova/api/openstack/compute/servers.py#L1161
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo
Thanks for adding the more info. That seems strange for me that username
is not kept same as it was input. case sensitive in keystone is based on
backend but it should be consistent.
I am adding keystone as an affected project in this bug to get provide
input on why returned user name is not
Public bug reported:
ceph hammer are not present in bionic and so nova-grenade-live-migration fail
to run on bionic
- https://review.openstack.org/#/c/639017/8
http://logs.openstack.org/17/639017/8/check/nova-grenade-live-
migration/735242b/ara-report/result/8816413c-7053-418f-886b-
Public bug reported:
OpenStack CI is moving to Ubuntu Bionic. All zuulv3 native jobs based on
devstack job are already running on bionic but legacy jobs are still
running on xenial.
While migrating the legacy jobs to Bionic, nova-next job start failing -
https://review.openstack.org/#/c/639017
*** This bug is a duplicate of bug 1741000 ***
https://bugs.launchpad.net/bugs/1741000
This is duplicate of https://bugs.launchpad.net/nova/+bug/1741000
It is fixed by https://review.openstack.org/#/c/530879/ and fix is
backported till stable/pike.
Marking as duplicate of 1741000
** This
*** This bug is a duplicate of bug 1741000 ***
https://bugs.launchpad.net/bugs/1741000
This is duplicate of https://bugs.launchpad.net/nova/+bug/1741000
It is fixed by https://review.openstack.org/#/c/530879/ and fix is
backported till stable/pike.
Marking as duplicate of 1741000
** This
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1791478
Title:
nova-api get 504 when keepalived restart
Status in
And releasenotes and doc has been fixed for nova-consoleauth
requirement-
https://review.openstack.org/#/q/4f01f4ff88de571218a36ba7c4e998296a7b52a4
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Yea, there are lot of other place where API status code are not
consistent and as per guidelines. As jichenjc mentioned this will be API
change and need microversion bump to maintain the backward
compatibility.
And as per Nova process, every API change needs spec, so please write
spec for this
Just updating the latest comments. This is API change and we need spec
for any API change. This is not priority for Rocky and i will check and
discuss in API meeting if we can do and it is worth to do in stein. Or
it is ok to just fix the python client.
Marking invalid for tempest as tempest is
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
https://github.com/openstack/nova/blob/e9104dbaef9bbccc6b19811125d439fdf9558428/nova/compute/api.py#L5096
..2 https://developer.openstack.org/api-ref/compute/#list-security-
groups
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: New
after discussion on patch and IRC, i agree that from api-ref perspective
this might be more confusing to mention as optional. It can be read as
start_time can be present or not as alone which is not true all other
events attributes are all together either present or not.
** Changed in: nova
' as
empty list.
https://github.com/openstack/nova/blob/0ffe7b27892fde243fc1006f800f309c10d66028/nova/api/openstack/compute/instance_actions.py#L86
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: New
--
You received this bug notification because
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
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/1702310
Title:
Unclear
the actual behavior.
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: New
** Changed in: nova
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
--
You received this bug notification because you are a member of Yahoo!
Engineer
in api doc.
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
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
Public bug reported:
'os-quota-class-sets' GET and PUT APIs response is different between v2(all
extensions) and v2.1
There is no 'server_groups' and 'server_group_members' in quota class set APIs
response where these were present in v2 (with all extension).
'os-server-group-quotas' extension
** Changed in: nova
Status: New => Won't Fix
--
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/1504641
Title:
Listing volumes respects osapi_max_limit but does not
1 - 100 of 154 matches
Mail list logo
