Reviewed: https://review.openstack.org/569062
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=fda48219a378d09a9a363078ba161d7f54e32c0a
Submitter: Zuul
Branch:master
commit fda48219a378d09a9a363078ba161d7f54e32c0a
Author: Lee Yarwood
Date: Thu May 17 09:47:58 2018 +0100
Discussion with roaksoax about this and it seems likely this is a cloud-
int / netplan problem. I have added cloud-init and maas just to be
thorough.
When bionic is deployed using MAAS 2.3.0 using a static network config
the DNS search domain is missing from the netplan configuration and or
system
Reviewed: https://review.openstack.org/567878
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=6b4c38c04177ff194d05368cd4aff69958075167
Submitter: Zuul
Branch:master
commit 6b4c38c04177ff194d05368cd4aff69958075167
Author: Surya Seetharaman
Date: Fri May 11 17:12:34 2018
Reviewed: https://review.openstack.org/568271
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=64e76de43dc55e584c15fa60da50dd06d352
Submitter: Zuul
Branch:master
commit 64e76de43dc55e584c15fa60da50dd06d352
Author: Surya Seetharaman
Date: Mon May 14 13:50:12 2018
Reviewed: https://review.openstack.org/560178
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=88f86e24e121ba545012051b6587d7475bfc5cec
Submitter: Zuul
Branch:master
commit 88f86e24e121ba545012051b6587d7475bfc5cec
Author: Matt Riedemann
Date: Tue Apr 10 19:30:51 2018 -0
This bug was already fixed on the master branch by
https://review.openstack.org/#/c/566491/ so please just cherry-pick that
to stable/queens. I'm closing this bug as it's one of many duplicates.
** Changed in: neutron
Status: Confirmed => Invalid
--
You received this bug notification bec
Re-opened since bug 1774019 seems to be a duplicate. In that case a
user was able to add a router to a shared external network and it got
the .1 address. Looks like there is an edge case here we need to cover.
** Changed in: neutron
Status: Expired => Confirmed
** Changed in: neutron
Public bug reported:
In neutron-openvswitch-agent.log I see lot of timeout message.
RuntimeError: Switch connection timeout
This timeout prevents sometime neutron-openvswitch-agent to be UP.
We are running Pike and we have ~1000 ports in Open vSwitch.
I'm able to run ovs-vsctl, ovs-ofctl, etc
Public bug reported:
Originally reported in RH bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1584315
Reproduced on OSP12 (Pike).
After resizing an instance but before confirm, update_available_resource
will fail on the source compute due to bug 1774249. If nova compute is
restarted at th
Public bug reported:
Original reported in RH Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1584315
Tested on OSP12 (Pike), but appears to be still present on master.
Should only occur if nova compute is configured to use local file
instance storage.
Create instance A on compute X
Resize
Public bug reported:
The API reference for the server 'migrate' (cold migrate) action doesn't
mention any asynchronous post conditions, like that the server goes to
VERIFY_RESIZE status after a successful cold migration and then must be
confirmed or reverted.
https://developer.openstack.org/api-r
Public bug reported:
This came about from a discussion in IRC:
http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-
dev.2018-05-30.log.html#t2018-05-30T16:13:41
The API reference here doesn't mention that for a system-scoped token,
the response body can have a 'system' attribute
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Triaged
--
You received this b
Public bug reported:
There are notes from this operators mailing list thread about how the
neutron agent needed to be configured for rootwrap daemon mode to hit
scale targets otherwise servers would fail to create due to vif plugging
timeouts:
http://lists.openstack.org/pipermail/openstack-
opera
Public bug reported:
Looking at the nova configuration reference and sample:
https://docs.openstack.org/nova/latest/configuration/config.html
The osprofiler options aren't included:
https://github.com/openstack/osprofiler/blob/master/osprofiler/opts.py
osprofiler is optional but if available w
Public bug reported:
The details are in this mailing list thread:
http://lists.openstack.org/pipermail/openstack-
operators/2018-May/015347.html
But essentially the case is:
* There are 3 compute hosts.
* compute1 and compute2 are in a host aggregate and a given tenant is
restricted to that ag
Public bug reported:
When I try to delete a stack I retrieve this error:
DELETE failed: ClientException: resources.server1: Unexpected API Error.
Please report this at http://bugs.launchpad.net/nova/ and attach the
Nova API log if possible. (HTTP 500)
(Request-ID: req-25b0407d-f31a-4ec1-a6ce-3b2
** Changed in: keystone
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1768980
Title:
Wrong Port in "Create OpenStack client
Public bug reported:
when creating a vmware instance from a volume is failed, vm goes to
error state, the volume is in "in use" state, and after deleting the
vm, the state of the volume is still in "in use" so it can't been
deleted.
** Affects: nova
Importance: Undecided
Status: Ne
19 matches
Mail list logo
