Public bug reported:
Hi All,
1. OpenStack Juno
2. Both nova-scheduler Nova-cert services are in stop/waiting state
after the server restart.
root@osjuno:~# service nova-cert status
nova-cert stop/waiting
root@osjuno:~# service nova-scheduler status
nova-scheduler stop/waiting
root@osjuno:~#
Public bug reported:
When create a new volume without source, the empty volume is not
bootable. then going to edit volume to change it to bootable and the
status of bootable in this volume is YES.
1. Don't we have any button to add image to this empty
volume ?
2.
Public bug reported:
1 create net and mutiple subnet
#neutron net-create net_test_1
Created a new network:
+---+--+
| Field | Value|
Public bug reported:
Running openstack stable/icehouse
Tried booting a VM after the volumes quota is full
Nova throws a 400 Bad Request.
If Nova gets a Quota error from any of the services it should throw 413
Forbidden instead of a 400 Bad Request.
** Affects: nova
Importance: Undecided
Public bug reported:
Version: Juno 2014.2.1
In nova/db/sqlalchemy/Models.py, there is a variable pci_stats in class
ComputeNode
# Note(yongli): json string PCI Stats
# '{vendor_id:8086, product_id:1234, count:3 }'
pci_stats = Column(Text)
In fact, the type of pci_stats is not
Nova is only user of oslo.log, there is nothing in Nova that can be
changed for fixing that.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
The test step:
1. Create subnet named A and B.
2. Create router named A and B.
3. Add subnet A to router A, and set gateway for router A. then do same with B.
4. Create vpn A, the vpn subnet use subnet A, peer gateway use router B's
gateway, peer subnet use subnet B.
5.
You have been subscribed to a public bug:
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_run_terminate_instance
failed with following stack trace
--
Public bug reported:
We are experiencing issues with Fuel 6.0
Every few days some user loose connectivity to there instances over the
floating IP.
When looking at Neutron logs there are lots of connection issues.
The Rabbit log is reporting errors every few seconds:
=ERROR REPORT
** Project changed: tempest = nova
--
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/1447945
Title:
check-tempest-dsvm-postgres-full fails with mismatch_error
Status in
[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).
You have been subscribed to a public bug:
In our code we invoke the code as following:
objects.InstanceList.get_all(context, ['metadata','system_metadata'])
It throw the error said:
2015-05-19 21:52:31.222 22676 TRACE nova.scheduler.ibm.ego.ego_manager
strat =
Public bug reported:
In \nova\virt\vmwareapi\vmops.py, at the end of method
get_vnc_console(self, instance), a log has been printed. In this log,
the data content of instance.name is assigned to key UUID, which is
not correct. Since instance name can be same to more than one instances,
we should
** Project changed: nova-solver-scheduler = nova
--
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/1456871
Title:
objects.InstanceList.get_all(context,
Public bug reported:
There are a couple of issues with the way our iptables rules are formed
that prevent them from being matched in the code that looks at existing
rules to preserve counters. So the counters end up getting wiped out.
** Affects: neutron
Importance: Undecided
Assignee:
Public bug reported:
Having a distributed router with interfaces for an internal network and
external network.
When Launching a instance and pinging an external network and then associating
a floating to the instance the connection is lost i.e.
the ping fails.
When running the ping command
Public bug reported:
Using the CLI it's possible to create a router for another tenant and specify
if the router should be distributed or not:.
# neutron router-create --tenant-id tenant-id --distributed True router1
The dashboard should provide the same functionality.
Version
==
Public bug reported:
From the access and security page, the keypair tab. When one tries to
create a keypair with a name that already exist, Horizon closes the
modal and returns a error.
What should happen, is to display an error in the form if the keypair
name already exists.
** Affects:
Public bug reported:
cloud-init's code that tries to determine if it is in a ec2 region is
simply unaware of the 'central' direction.
--- /usr/lib/python2.7/dist-packages/cloudinit/distros/__init__.py.dist
2015-05-19 12:47:04.956343999 +
+++
marginally related bug 1456684
** Package changed: ubuntu = cloud-init (Ubuntu)
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Confirmed
** Changed in: cloud-init
Importance: Undecided = High
--
You received this bug
1. If you want a volume to create an image, the easiest way is to do so at
volume creation type by specifying that the volume source is an image rather
than empty. But, if you want to take an empty volume and place a bootable image
on it, you can attach the volume to a VM, login to the VM, and
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
** Changed in: cloud-init
Importance: Undecided = Medium
** Changed in: cloud-init
Public bug reported:
When adding an IPSEC Site to Site connection with peer fqdn, resolving
the peer fqdn fails for strongswan. As neutron relies on ip net
namespaces, the resolv.conf from the neutron node is not used by
StrongSwan.
Usually applications that work in ip netns try to use the
Public bug reported:
Releasing Kilo in Debian, I found out that Keystone just broke with
pysaml2 2.0.0, and in fact needs 2.4.0. The unit tests just passed, but
with pysaml2 2.0.0 Keystone just crashes with a stack dump.
Out of this, 2 remarks:
- requirements.txt is wrong and should ask for
*** This bug is a duplicate of bug 1456756 ***
https://bugs.launchpad.net/bugs/1456756
Public bug reported:
There is this trace at error level in the server logs when DVR is
enabled by default:
[req-179a109e-456a-4743-8395-58b2f322afe2 None None] Could not retrieve
gateway port for subnet
Public bug reported:
There is this trace at error level in the server logs when DVR is
enabled by default:
[req-179a109e-456a-4743-8395-58b2f322afe2 None None] Could not retrieve
gateway port for subnet {'ipv6_ra_mode': None, 'allocation_pools':
[{'start': u'10.100.0.2', 'end': u'10.100.0.14'}],
Public bug reported:
On my single-node devstack setup running the latest neutron code, there
is one AgentNotFoundByTypeHost exception found for the L3-agent.
However, the AgentNotFoundByTypeHost exception is not logged for the
DHCP, OVS, or metadata agents. This fact would point to a problem
Public bug reported:
When using DVR, the fg device in a compute is needed to access VMs on a
compute node. If for any reason the fg- device is deleted. users will
not be able access the VMs on the compute node.
On a single node system where the L3-agent is running in 'dvr-snat'
mode, a VM is
After going deeper into recent network mtu feature, it appeared that it
solves this issue by allowing to configure mtu for the external network.
** Changed in: neutron
Status: New = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Similar to token_flush, we need an operation to purge old revocation
events from the database, else they'll eventually consume excessive disk
space. The operation should be very similar in implementation and usage
to token_flush.
Filing this as Medium priority because it
Public bug reported:
gate-glance-python27 of https://review.openstack.org/#/c/184304/ failed with:
ft1.1178:
glance.tests.unit.test_opts.OptsTestCase.test_list_manage_opts_StringException:
Traceback (most recent call last):
File glance/tests/unit/test_opts.py, line 301, in
Public bug reported:
This has been observed in multi-node CI runs for Neutron:
[req-de4ba471-c1d7-49f4-860d-e717c611ebbd None None] Message received
from the host: devstack-trusty-2-node-rax-
iad-2588390-4019.slave.openstack.org during the registration of Open
vSwitch agent has a timestamp:
Public bug reported:
Since May 15th 2015 I sometimes see failures in both check and gate
pipelines with Failure prepping block device in the gate and the
following common signature:
33 matches
Mail list logo
