Public bug reported:
on nova master, multinodes with 2 compute nodes available. only one of
nova compute had pci devices available.
1. booting vm with pci reqested, assume it's name: pci-vm
2. nova migrate pci-vm
3. the pci-vm been schedule to a host don't have pci devices available.
we see
Public bug reported:
The current installation guide didn't present the correct way of creating a
cell1 with a correct transport url and db, it will causing the conductor unable
to connect to MQ after it switched context.
We should fix that.
** Affects: nova
Importance: Undecided
Public bug reported:
Current, if there aren't any providers that have any of the required
traits, just exit early in _get_by_one_request. But we should also
consider the forbidden traits to optimize this attempt at a quick
return.
Public bug reported:
The following (from previous versions of the documentation) should be
added to this part of the tutorial, otherwise it will not be able to
proceed smoothly afterwards.
Create `/etc/apache2/sites-available/wsgi-keystone.conf`:
'''
Listen 5000
Listen 35357
*** This bug is a duplicate of bug 1758952 ***
https://bugs.launchpad.net/bugs/1758952
** This bug has been marked a duplicate of bug 1758952
DHCP agent fails to configure routed networks due to failure generating
subnet options
--
You received this bug notification because you are a
** Changed in: python-manilaclient
Status: Fix Committed => Fix Released
** Changed in: python-manilaclient
Milestone: liberty-1 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Changed in: nova
Status: Fix Released => In Progress
** Tags added: rocky-rc-potential
--
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/1781710
Title:
Reviewed: https://review.openstack.org/577739
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=ec5cd0d1b85d56adef836bf1167287993ec35ca6
Submitter: Zuul
Branch:master
commit ec5cd0d1b85d56adef836bf1167287993ec35ca6
Author: LIU Yulong
Date: Sat Jun 23 04:52:15 2018
** Also affects: nova
Importance: Undecided
Status: New
--
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/1782604
Title:
designate-bind9-py36 gate is failing due
** Changed in: neutron
Status: Confirmed => 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/1711463
Title:
TestNetworkBasicOps.test_network_basic_ops failed with "Timed
Public bug reported:
http://logs.openstack.org/70/434870/37/check/nova-
lvm/a7cce3d/logs/testr_results.html.gz
http://logs.openstack.org/70/434870/37/check/nova-
lvm/a7cce3d/logs/screen-n-cpu.txt.gz?level=TRACE#_Jul_19_14_40_50_480759
Jul 19 14:40:50.480759 ubuntu-xenial-ovh-gra1-829690
Fix proposed to branch: master
Review: https://review.openstack.org/583967
** Changed in: neutron
Status: Invalid => In Progress
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Invalid
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Hey, this certainly isn't the most important case.
But I wanted to report it to make you aware.
For bug 1732028 I was trying different configs.
One was an empty /etc/fstab with the kernel providing the iscsi root.
In that case cloud init runs and since it does not check on
Public bug reported:
When I created log-resource with security_group, log data didn't show at
/var/log/syslog at all.
[Environment]
$ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
Reviewed: https://review.openstack.org/580173
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=886e24155358afe7ad167ba1602d3939d68c3d5f
Submitter: Zuul
Branch:master
commit 886e24155358afe7ad167ba1602d3939d68c3d5f
Author: Kailun Qin
Date: Thu Jul 5 07:17:31 2018
This has been discused several times in the last few releases.
the original spec did not mandate that we invent a numa toploygy
of 1 when we request cpu pinning however it did not forbid it.
The current behavior is specific to the libvirt dirver and while it could
legally be changed without
Public bug reported:
After the host is in the Host Aggregates (HA) where the host is modified, the
Availability Zone (az) is also changed, but the available_zone in the instances
database of the instance on the host does not change.
The recurring steps are as follows:
1. Query the az of the
18 matches
Mail list logo
