Public bug reported:
Description
===
Unshelving a VM can cause an over consumption of a project's quota. I'm not
sure if this is a bug or if it's actually intended behaviour, but in my opinion
this should not be possible since this will allow users to potentially use a
lot more resource
Public bug reported:
First of all, I'm not really sure if this is a bug, or some sort of
configuration error on our side.. But I'm having issues with the port
forwarding in neutron.
Openstack ussuri, running on Bionic
neutron-l3-agent2:16.2.0-0ubuntu1~cloud0
openvswitch-switch 2.13.1
Public bug reported:
Hi,
This seems to be a "duplicate" of #1779250 but not quite. I have trouble
launching a community image from horizon:
How to reproduce:
- Create two projects, A and B.
- In project A, create a snapshot of a VM
- Set the snapshot to community
- Switch to project B
- Try to l
Public bug reported:
I'm experiencing some weird bugs/brokenness when trying to use the
Nvidia A100 for vGPU in nova. It's a little bit involved, but I tihnk I
have an idea of what's going on.
My setup:
Dell R7525 with 2xNvidia A100
CentOS 8.2
Openstack Ussuri (openstack-nova-compute.noarch 1:21.
Public bug reported:
Description
===
In Ussuri, when a compute node providing vGPUs (Nvidia GRID in my case) is
rebooted, the mdevs for VGPUs is not recreated, and a traceback from
libvirt.libvirtError is thrown.
https://paste.ubuntu.com/p/4t4NvTHGd8/
As far as I understand, this shoul
Public bug reported:
First of all, I'm not really sure which project to "blame" for this bug,
but here's the problem:
When you reboot a compute-node with Nvidia GRID and guests running with
a VGPU attached, the guests will often have their VGPU re-created on a
different mdev than before the reboo
Public bug reported:
In our work on upgrading from Queens to Rocky, we have stumbled upon
some weird behaviour in neutron-l3-agent. After "a while" (usually
~days), the l3-agent will simply stop processing router updates. In the
debug log, we see:
Got routers updated notification :[u'1dea9d84-e5e
Public bug reported:
In rocky, FWaaS v2 fails to add the correct ip6tables rules for ICMPv6.
Steps to reproduce:
* Create rule with Protocol ICMP, IP version 6 in horizon
* Add the rule to a policy, and make sure the firewall group with that policy
is attached to a port
* Login to the neutron ne
** Changed in: horizon
Status: Incomplete => 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/1788159
Title:
AngularJS keypair panel is broken
Status
Public bug reported:
In Queens (openstack-dashboard 3:13.0.1-0ubuntu1~cloud0), when logging
into Horizon in context of a _member_ in any project, the "Add allowed
address pair" button in "Network" -> "Networks" -> ->
"Ports" -> -> "Allowed address pairs" is not visible.
When accessing the same
Public bug reported:
In queens, the AngularJS panel for key pairs is enabled by default. I
would consider it broken, because both "Create keypair" and "Import
keypair" don't work. They throw the following JS error to the console:
http://paste.openstack.org/show/728509/
If I set
ANGULAR_FEATURES
Public bug reported:
If you have configured keystone with an LDAP backend, and you have
project with a disabled AD user as a member, the "openstack role
assignment list --project --names" command will fail with a HTTP
404 response, beacause it can't resolve the name of the disabled user.
Example
12 matches
Mail list logo
