Public bug reported:
Several APIs in glance use a pattern where an image is fetched from the
backend before performing an operation, updating an image for example.
The API code for updating an image calls the image repository, which
ultimately enforces the policy for get_image [0][1]. This can
Public bug reported:
Glance is translating "Not Found" errors from the DB layer into "Not
Authorized" errors in policy, which it should not be doing. In general,
we should always return 404 when something either does not exist, or
when permissions do not allow you to know if that thing exists.
Further discussion with Jeff indicated that replacing the { and } with (
and ) resolved the issue.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
https://review.opendev.org/c/openstack/tempest/+/774764 got merged
** Changed in: tempest
Status: Triaged => 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/1914037
Public bug reported:
When keystone implemented support for default personas (system-admin,
system-member, system-reader, domain-admin, domain-member, domain-
reader, project-admin, project-member, project-reader), we took the
stance that HTTP 403s should be returned for non-existent resources
Thanks, I've switched this to a normal public bug and set our security
advisory task to Won't Fix indicating there shouldn't be any advisory
publication required. The OpenStack VMT is treating this as a class E
report (neither a vulnerability nor hardening opportunity) per our
taxonomy:
Public bug reported:
How to reproduce the issue:
1. use neutron-ovs-agent with openvswitch firewall driver,
2. spawn vm with SG which has some rule to allow some kind of traffic (can be
e.g. ssh to the instance)
3. establish connection according to the rule(s) in SG (e.g. connect through
ssh
Public bug reported:
I have multiple regions ( e.g. R1, R2) in my setup and I am providing
those via "AVAILABLE_REGIONS" param in `local_settings` file. I have set
"DEFAULT_SERVICE_REGIONS" param too with correct endpoints ( e.g. R2).
Now while logging in I select `R2` from the Region dropdown,
>From libvirt package POV this is fixed in >=Focal (20.04) and the only
release left affected is Bionic (18.04, libvirt 4.0).
Fixing it in Bionic is IMHO worth to consider but low prio (if users can
influence, they can set an address to 8-16 and it works, only the
default-no-address use case is
** Also affects: cloud-archive
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/1864279
Title:
Unable to attach more than 6
** Project changed: cloud-archive => libvirt (Ubuntu)
--
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/1864279
Title:
Unable to attach more than 6 scsi volumes
Status in
11 matches
Mail list logo
