** Changed in: cloud-init
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1402474
Title:
Devstack install_pip.py failed the installation
Status in Init
I don't think it's necessary.
Default value of the parameter is host name and in most cases it even doesn't
make sense to specify it.
It's not necessary to have each and every conf parameter commented in
neutron.conf
** Changed in: neutron
Status: New = Opinion
--
You received this bug
Fix proposed to branch: master
Review: https://review.openstack.org/144228
** Changed in: neutron
Status: Opinion = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Summary:
when the Management IP address of a compute node differs with its my_ip
config of nova.conf, nova-conductor would prefer the my_ip config and store
it into the compute_nodes table host_ip column of nova database. Certainly,
this would lead to the failure of this
Public bug reported:
Summary:
When live-migrating a virtual machine from a compute node to another one with
the same bios uuid, libvirt would fail the migration because of the bios uuid
checking.
nova-compute.log from the source node:
2014-12-27 05:23:19.889 1923 ERROR nova.virt.libvirt.driver
Public bug reported:
It is not possible right now to run horizon selenium integration tests
concurently.
This request emerged in [0]. Because of following reasons(quoting Timur
Sufiev):
I guess the whole point of running tests as more than 2 users is the
ability to run concurrently more than 1
All Nova check jobs are failing
** 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/1405626
Title:
Public bug reported:
this issue reproduce steps:
1. nova boot vm1 base fcsan volume, this instance bdm table connection_info as
following:
{driver_volume_type: fibre_channel, serial:
63013f85-34fd-4040-a234-6ee57e1a8eeb, data: {device_path: /dev/dm-11,
target_discovered: false, devices:
Public bug reported:
Summary:
When block-migrating a vm between two compute nodes, if the destination node
lacks ssh daemon or refuses ssh connection, the block-migration would fail and
cause permanent damage to the vm, vm will be unusable and no easy way to
recover.
Scenario:
Block-migrating
Public bug reported:
The docstring says Return the provider based on ``token_format`` if
``provider`` is not set. Otherwise, ignore ``token_format`` and return
the configured ``provider`` instead., refer to:
https://github.com/openstack/keystone/blob/master/keystone/token/provider.py#L127
Public bug reported:
According to current code, to enable the glance datastore backend driver
function, the following section should be added and configured in
glance-api.conf:
[glance_store]
default_store = vsphere
stores = glance.store.vmware_datastore.Store
** Affects: glance
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: glance
Assignee: (unassigned) = ZhiQiang Fan (aji-zqfan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
12 matches
Mail list logo
