** Changed in: neutron
Status: In Progress => 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/1758063
Title:
neutron_tempest_plugin.scenario.test_floatingip.FloatingIP
IMHO, this should also be fixed in cloud-init. If the input netplan
contains "global" routes, the renderer (or whatever can pre-process the
Netplan before renderering) should intelligently determine which
interfaces have an on-link gateway that matches the global route, and
automatically render the
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1716448
Ti
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
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/16
[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
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/17
Public bug reported:
# OS_USERNAME=user OS_USER_DOMAIN_NAME=admin_domain OS_PROJECT_NAME=admin
# OS_PROJECT_DOMAIN_NAME=admin_domain
openstack user list --domain testdomain -> users returned for testdomain
# OS_USERNAME=user OS_USER_DOMAIN_NAME=testdomain OS_DOMAIN_NAME=testdomain +
policy file
This bug was fixed in the package livecd-rootfs - 2.515
---
livecd-rootfs (2.515) bionic; urgency=medium
* Set the default locale to C.UTF-8 in all server and cloud images.
(LP: #1751051, #1759003)
-- Michael Hudson-Doyle Tue, 27 Mar 2018
09:59:02 +1300
** Changed in: livecd
Public bug reported:
The Horizon filtering is not fully thread-safe. If two users are
simultaneously filtering a resource (e.g. projects or instances), and
threading is enabled (e.g. 2 or more threads in Apache). It's possible
that the wrong filter will display in the form input.
I was able to re
These APIs have been this way it seems since they were added (a long
time ago):
https://blueprints.launchpad.net/nova/+spec/get-password
It looks like the only way you can POST a new password for the instance
via the metadata API is if you first reset the password using the DELETE
method via the
There are likely failures in the nova-compute and/or nova-conductor
logs, you would need to dig through those logs (or attach them) to help
diagnose the reason for the build failures.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member
This is the error from the nova-conductor logs:
2018-03-23 16:01:30.287 2213 ERROR oslo_messaging.rpc.server
[req-0c91a675-d8e1-4e94-86e8-953a30a082bb c327309640084a138cc26e41ec014bb8
4ab0b5b8aecf4096b32a93a5e954b8a5 - default default] Exception during message
handling: TypeError: argument of t
openstack image list is fine, so communicating with glance isn't a
problem.
nova image-list is a proxy to glance, so nova.conf would have to be
configured to communicate with glance, but nova image-list is also
deprecated.
What version of python-novaclient are you using?
And you're running mitak
This likely means you have:
[service_user]
send_service_user_token = True
configured in nova.conf, but you don't have valid credentials configured
in that group for the service user, see:
https://docs.openstack.org/nova/latest/configuration/config.html
#service-user
** No longer affects: cinder
Reviewed: https://review.openstack.org/553463
Committed:
https://git.openstack.org/cgit/openstack/cyborg/commit/?id=ac6b70dc6a9c440250b739c9fed9a1b74d7642be
Submitter: Zuul
Branch:master
commit ac6b70dc6a9c440250b739c9fed9a1b74d7642be
Author: Nguyen Van Trung
Date: Thu Mar 15 23:20:29 201
Public bug reported:
Hi,
Get an error message when I run the command: "openstack compute service list -
nova-compute service" command referring to the openstack documentation. the
error output message : Erreur d'API inattendue. Signalez-la sur
http://bugs.launchpad.net/nova/ et joignez-y le jo
Public bug reported:
Throughout OpenStack, the eventlet library is used heavily
for threading. In most cases, we use spawn_n() from
eventlet which does not return whether the method that was
wrapped with it raised an exception. Exceptions are instead
just printed to stderr. Many deployers are usin
The problem is this code is not cell-aware:
https://github.com/openstack/nova/blob/2ecb99939ec15057904d1b86c4478def29e193db/nova/api/openstack/wsgi_app.py#L48
It should lookup the cell0 mapping and then use that context for finding
the service record entry and creating it in the cell0 DB.
** Cha
Public bug reported:
In a routed networks environment, after the merge of
https://review.openstack.org/#/c/468744, the dhcp agent attempts to
generate subnet options for both local and non local subnets. If one of
the non-local subnets is classified as isolated from the point of view
of the metada
Public bug reported:
When the image_import call is made the taskflow is created and
responsible handling the rest of the request. It does not do any
prechecks if the import conditions are met (like verifying that the
image status transition would be possible. This will create lots of
tasks that wi
@Henry, if you need to cleanup placement, there is the osc-placement CLI
plugin available for some of this:
https://docs.openstack.org/osc-placement/latest/index.html
i.e. you can remove allocations for a given consumer (deleted instance)
if nova failed to cleanup allocations for that instance wh
Hi,
Curtin is no longer involved in rendering of Ubuntu network config,
so I've marked its task as Invalid.
Please attach the network configuration that MAAS sent.
Without this we are not able to do much in cloud-init.
In order to further investigate this bug we'll need to get some information
Public bug reported:
Hi there,
I notice that using the latest version of cloud-init on ubuntu xenial running
on AWS the cloud-init isn't changing the 50-cloud-init.cfg file on boot, that
behavior can turn the instance unreachable in some cases.
A particular case is when you change the instance
23 matches
Mail list logo
