Public bug reported:
When SDN mechanism driver is used in Neutron (on our site we use
mlnx_sdn_assist but this issue isn’t limited just to this driver, we
hear about similar issues with at least three other SDN solutions) there
is no consistency checking applied to the fabric past the initial
Public bug reported:
Whilst building out a new set of AWS AMIs I have a need to explicitly
deny `sudo` access to a subset of users. We are using `cloud-init` for
the management of these user resources via the users and groups
module[1].
By default, `cloud-init` doesn't assign `sudo` permissions
Private bug reported:
Amazon prime customer service number +1-888-341-6651 Prime Customer
Service Phone Amazon prime customer service number +1-888-341-6651 Prime
Customer Service Phone Amazon prime customer service number
+1-888-341-6651 amazon customer service number amazon Customer support
I would like to propose re-opening this bug. We ran into it today when
upgrading Neutron from G-J. The patch provided solved the issue.
** Changed in: neutron
Status: Invalid = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
When booting instances passing in block-device and increasing the volume size ,
instances can go in to error state if the volume takes longer to create than
the hard code value set in:
nova/compute/manager.py
def _await_block_device_map_created(self, context, vol_id,
Public bug reported:
Using 2013.2.1 from Ubuntu packages.
I want prevent libvirt from injecting anything in to any image so I set:
libvirt_inject_partition = -2 in nova.conf
Then proceed to launch and instances (cirros).
I still see nova trying to mount the instances disk. Why?
sudo
Hi Mike,
Thanks for the insight. Setting my endpoint back to v1 allows the proper
info to be displayed:
+--+---+--+--+-+--+-+
| ID | Status | Display Name | Size |
7 matches
Mail list logo
