** Also affects: taskflow
Importance: Undecided
Status: New
** Changed in: taskflow
Assignee: (unassigned) => Takashi Kajinami (kajinamit)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
** Also affects: mistral
Importance: Undecided
Status: New
** Also affects: manila
Importance: Undecided
Status: New
** Also affects: zaqar
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
Description
===
nova-mange placement audit command always fails because the target resource
provider is not found
~~~
# nova-manage placement audit --resource_provider
dbba1bf7-6e97-4dcb-8d4c-37fe36633358 --verbose
Resource provider with UUID
Public bug reported:
Currently when adding an interface to a router, Horizon shows subnets
with gateway ip.
On the other hand, Horizon supports attaching a subnet to a router with fixed
interface ip.
In this case gateway ip is not required but a new port is created with a given
ip in the
Public bug reported:
Currently neutron accepts the following parameters to set up identity
for connecting to designate in admin context, but the list doesn't
include domain parameters and it seems these parameters are based on
keystone v2 indentity instead of keystone v3 identity.
-
Closing this because our expectation here is that neutron and libvirt should
detect the same hostname.
I've reported another bug to fix current incompatibility.
https://bugs.launchpad.net/neutron/+bug/1926693
** Changed in: neutron
Status: Confirmed => Invalid
--
You received this bug
Public bug reported:
Currently we use socket.getshostname() to determine the heyervisor
hostname assuming that is what is used in libvirt.
However libvirt actually ues the following steps to generate hypervisor
hostname and socket.gethostname() doesn't match in some cases.
/* Who knew getting a
Public bug reported:
We have observed that the following Traceback is logged in metadata-
agent.log when metadata-agent encounters MessagingTimeout.
~~~
Traceback (most recent call last):
File
"/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line
397, in get
Public bug reported:
Currently horizon stops loading policy rules when it detects any file in a
wrong format.
This results in a situation where horizon works with very incomplete policy
rules because of only one invalid policy file.
For example when horizon susceeds to load the keystone policy
Public bug reported:
In some deployments, hostnames can be different between hosts and resource
provider records. For example in deployment managed by TripleO we use short
host name (without domain name) in host, while we use FQDN for resource
provider records (this comes from the FQDN set to
I think this is not an issue with nova but the one with puppet-nova.
Actually we fixed the configration related to libvirt on CentOS while we
fixed that mentioned bug, but we still need the same fix for Ubuntu
which has libvirt 6.0 recently.
We already have a proposed fix for the issue
Public bug reported:
Description
===
When we use nfs backend in cinder and attach a cinder volume to an instance,
the instance access to the file in nfs share, which is named like
volume-.
When the volume is attached to an instance and we take snapshot with
"openstack volume snapshot
to these define parameters, Otherwise it can break existing deployment
which requires extra parameters configured.
** Affects: nova
Importance: Undecided
Assignee: Takashi Kajinami (kajinamit)
Status: In Progress
--
You received this bug notification because you are a member
101 - 113 of 113 matches
Mail list logo
