Reviewed: https://review.openstack.org/632904
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=6489f2d2b44827d133dad9a3bb52436ee304a934
Submitter: Zuul
Branch:master
commit 6489f2d2b44827d133dad9a3bb52436ee304a934
Author: melanie witt
Date: Fri Jan 18 16:30:40 2019
Reviewed: https://review.openstack.org/631684
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=1b797f6f7e99fdef380340d6fe29e4004be48781
Submitter: Zuul
Branch:master
commit 1b797f6f7e99fdef380340d6fe29e4004be48781
Author: Hang Yang
Date: Thu Jan 17 16:57:56 2019 -0800
Sorry, I was wrong and everything is ok with documentation. I mark this bug
report as invalid.
Sorry again
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Public bug reported:
In OpenStack it is possible to configure a network setup such that the
metadata server is accessible via a "secondary" NIC, for example eth1.
In such a setup cloud-init fails to locate the proper NIC to access the
metadata server.
** Affects: cloud-init
Importance:
Public bug reported:
I am observing StaleDataError on stable/pike during live migration,
causing live migration to fail. It occurs when attempting to live-
migrate a handful of VM's (5-6 VM's is all it takes) in rapid succession
from the same source to the same target. This quick and dirty script
** Tags added: disco packaging
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
The nova-live-migration job has 2 nodes and in addition to running live
migration tests it also runs evacuate tests for image-backed and volume-
backed servers.
Seeing intermittent failures, with debug in this change:
https://review.openstack.org/#/c/571325/
It looks like
Public bug reported:
There is a race condition between nova-compute boots instance and l3-agent
processes DVR (local) router in compute node.
This issue can be seen when a large number of instances were booted to one same
host, and instances are under different DVR router.
So the l3-agent will
** Changed in: tempest
Assignee: Matt Riedemann (mriedem) => Bence Romsics (bence-romsics)
** Changed in: tempest
Importance: Undecided => High
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** Changed in: tripleo
Status: In Progress => Invalid
--
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/1715270
Title:
Remove usage of kwarg retry_on_request in API
There are lots of warnings showing up in ovs-vswitchd log
2019-01-24T18:40:59.070Z|00058|connmgr|INFO|br-ex<->tcp:127.0.0.1:6633: 2
flow_mods 10 s ago (2 adds)
2019-01-24T18:40:59.184Z|00059|connmgr|INFO|br-tun<->tcp:127.0.0.1:6633: 10
flow_mods 10 s ago (10 adds)
Public bug reported:
Hello,
our users need to know who made each OS instance, but unfortunately,
there is no clue to get this info in instance action log as there is
user-id only.
Can you please consider to add some additional info about a user here? I
mean user-name and user-group maybe?
Public bug reported:
on edit image form, do not enter the min disk and min ram, no error
message shown
** Affects: horizon
Importance: Undecided
Assignee: pengyuesheng (pengyuesheng)
Status: In Progress
** Changed in: horizon
Assignee: (unassigned) => pengyuesheng
13 matches
Mail list logo
