[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
Reviewed: https://review.openstack.org/566405
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=2e34279ec3f4e93a7eca1e89b307fdbeb15b211e
Submitter: Zuul
Branch:master
commit 2e34279ec3f4e93a7eca1e89b307fdbeb15b211e
Author: Brian Haley
Date: Fri May 4 16:43:45 2018 -04
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1694120
Title:
routed-networks - segments subnet dhcp port bind to wrong segment
Stat
Public bug reported:
Any enabled placement request filters are processed during scheduling
here:
https://github.com/openstack/nova/blob/d78055df0e39b53fd481c53429ba77f8c1e1ab09/nova/scheduler/manager.py#L127
But then if we're doing a rebuild, we don't call placement:
https://github.com/openstac
This isn't a bug, the command is doing what it was designed to do. If
you don't specify transport_url or database_connection via the CLI
options, the values are pulled from the config file (via either the
--config-file option or the implied /etc/nova/nova.conf) and if you run
it more than once it w
The CLI options are optional because if not specified the values are
pulled from the config file, which you can provide via the --config-file
option, and so you don't have to write URLs with credentials into
scripts. The fact it fails with "The specified transport_url and/or
database_connection com
Reviewed: https://review.openstack.org/567744
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a676d2e6b22b307287a6e18046e3384b7539de98
Submitter: Zuul
Branch:master
commit a676d2e6b22b307287a6e18046e3384b7539de98
Author: Takashi NATSUME
Date: Fri May 11 14:12:56 2018 +
** Project changed: trove => nova
** Changed in: nova
Status: Invalid => Incomplete
** Changed in: nova
Status: Incomplete => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bug
You have been subscribed to a public bug:
when i do live migration,it raise the error as below:
2018-05-03 18:38:00.838 1570085 ERROR nova.virt.libvirt.driver [req-
7a3691d2-f850-4258-8c7a-54dcaa6189aa 659e4083e38046f8a23060addb53bd96
58942649d31846858f033ee805fcb5bc - default default] [instance:
Public bug reported:
There is no step to regenerate grub.cfg file. Is it OK to have changes
only in /etc/grub/default? It not reflecting for me after reboot.
openstack release: liberty
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because
*** This bug is a duplicate of bug 1762633 ***
https://bugs.launchpad.net/bugs/1762633
** This bug has been marked a duplicate of bug 1762633
Keystone Installation Tutorial for Ubuntu in keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
Public bug reported:
While creating a new cell_v2 using command "nova-manage cell_v2
create_cell", if no parameter ie. "transport-url" and
"database_connection" are given then the values of "transport-url" and
"database_connection" of default cell are picked from nova.conf which
are already mapped
12 matches
Mail list logo
