Public bug reported:
When deploying OpenStack Icehouse on Ubuntu trusty in a cells configuration
the callback from neutron to nova that notifies nova
when a port for an instance is ready to be used seems to be lost. This causes
the spawning instance to go into an ERROR state and
the following
Public bug reported:
I received the following error from the check-tempest-dsvm-neutron-full
test suite after submitting a nova patch:
2014-08-21 14:11:25.059 | Captured traceback:
2014-08-21 14:11:25.059 | ~~~
2014-08-21 14:11:25.059 | Traceback (most recent call last):
2014-
** Also affects: nova (Ubuntu)
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/1314677
Title:
nova-cells fails when using JSON
: charm-layer-ovn
Status: New => Confirmed
** Changed in: charm-layer-ovn
Importance: Undecided => High
** Changed in: charm-layer-ovn
Assignee: (unassigned) => Liam Young (gnuoy)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
Connectivity is fine with OVS 2.15 but after upgrading ovs, connectivity
is lost to remote units over ipv6. The traffic appears to be lost while
being processed by the openflow firewall associated with br-int.
The description below uses connectivity between Octavia units and
The issue seems to be in ovs, specifically this commit
https://github.com/openvswitch/ovs/commit/355fef6f2ccbcf78797b938421cb4cef9b59af13
. I have created a ppa
https://launchpad.net/~gnuoy/+archive/ubuntu/focal-xena/+packages that
has a copy of the openvswitch package from the xena-proposed UCA. T
tion.ResourceProviderRetrievalFailed: Failed to get resource provider
with UUID 4f7c6844-d3b8-4710-be2c-8691a93fb58b
2019-04-25 09:58:12.177 31793 ERROR nova.compute.manager
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Assignee: (unassigned) => Liam
in: nova
Assignee: Liam Young (gnuoy) => (unassigned)
** Changed in: charm-keystone
Assignee: (unassigned) => Liam Young (gnuoy)
** Changed in: charm-nova-cloud-controller
Assignee: (unassigned) => Liam Young (gnuoy)
** Changed in: charm-nova-compute
Status
** Also affects: ovn-octavia-provider (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1896603
Title:
ovn-octavia-provider: Cannot crea
Assignee: Liam Young (gnuoy)
Status: New
** Changed in: nova
Assignee: (unassigned) => Liam Young (gnuoy)
--
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/1785
seem to need
api_database section.
** Affects: nova
Importance: Undecided
Assignee: Liam Young (gnuoy)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Liam Young (gnuoy)
--
You received this bug notification because you are a member of Yahoo!
Engineering
I don't think this is related to the charm, it looks like a bug in
upstream nova.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nova (Ubuntu)
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notificati
Public bug reported:
- [X] This doc is inaccurate in this way: Documentation suggests nova v2 cells
do not make 'upcalls' but they do when talking to the placement api.
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example:
input and o
Public bug reported:
Description
===
map_instances seemingly hung for hours on a cloud with ~19 instance
records. I think the following fixes are valid (in order of preference):
1) nova_manage should examine the amount of instances that need mapping and
make an informed choice about
** Also affects: python-oslo.messaging (Ubuntu)
Importance: Undecided
Status: New
** Changed in: oslo.messaging
Status: Confirmed => Invalid
** Changed in: nova
Status: New => Invalid
** Changed in: python-oslo.messaging (Ubuntu)
Status: New => Confirmed
--
You r
The fix went into 2015.1.0 and 2015.1.1 is now in the cloud archive.
** Changed in: nova (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.
Public bug reported:
As recommended in http://docs.openstack.org/havana/config-
reference/content/section_compute-cells.html#cell-config-optional-json
I'm creating the nova-cells config with the cell information stored in a
json file. However, when I do this nova-cells fails to start with this
err
17 matches
Mail list logo
