Public bug reported:
When instance is migrated to another compute node, it's dhcp lease is not
removed from the first compute node even after instance termination.
If a new instance got the same IP which was present in the previous instance
created on the the first compute node where dhcp lease
The log file is not available anymore and the bug report mentioned by
Eddie which fixes the
`test_add_copy_from_image_authorized_upload_image_authorized` has been
released for Kilo RC1.
@Thomas: Feel free to reopen the bug if the problem still occurs and set
the bug status back to ''New''.
**
Public bug reported:
As of Icehouse, at least, keystone doesn't ever clean up expired tokens.
After a few years, my keystone ridiculously huge, causing query timeouts
and such.
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because
** Changed in: cinder
Status: In Progress = Invalid
** Changed in: python-cinderclient
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).
Public bug reported:
2015-04-13 21:25:51.437 7852 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py, line 1278, in
_resize_create_ephemerals
2015-04-13 21:25:51.437 7852 TRACE oslo.messaging.rpc.dispatcher ds_ref =
Public bug reported:
After a failure of the resize and a deletion of the instance. I am
unable to restart the nova compute due to the exception below. The
instance was deleted via nova api.
The DB is as follows:
mysql select * from migrations;
Public bug reported:
Some types of requests to ceilometer in metering dashboard is not
optimized. So we have a performance leak in environments with huge
amount of ceilometer data.
Main bottlenecks which I see:
* Using a meter-list for getting a unit for metric. Meter list get all
available
Public bug reported:
There are a few deprecated templatetags that we are still using in
Horizon. These can be seen in the logs:
WARNING:py.warnings:RemovedInDjango18Warning: 'The `cycle` template tag is
changing to escape its arguments; the non-autoescaping version is deprecated.
Load it from
The internal URL is not intended to be obscured from users, but rather
is intended to provide a public API interface on a faster / more
efficient network interface (depending on the deployment). If users can
reach the internal endpoint (such as for glance), then they can likely
save bandwidth
Public bug reported:
In Juno release (ubuntu packages), when you start nova-scheduler but
database is down, the service never reconnects, the stacktrace is as
follow :
AUDIT nova.service [-] Starting scheduler node (version 2014.2.2)
ERROR nova.openstack.common.threadgroup [-]
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Ben Howard (utlemming)
** Package changed: cloud-init (Ubuntu) = walinuxagent (Ubuntu)
** Changed in: walinuxagent (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Yahoo!
Docs:
http://docs.openstack.org/admin-guide-cloud/content/flushing-expired-
tokens-from-token-database-table.html
In addition, Fernet tokens, introduced in Kilo, do not need to be
persisted to the database, and will leave your token table completely
empty:
Public bug reported:
in v2.1 API, when create a volume through os-volumes
if the snapshot ID is invalid, we should report 404 , but now
exception.SnapshotNotFound is not correctly handled
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
**
Public bug reported:
Ignoring jshint on legacy JS code
Once undef and unused are enabled, legacy code will throw over 365
errors. Remember that undef check for undefined variables while unused
checks for unused variables, both are good for quality control.
We have two options going forward:
1.
Public bug reported:
If you try to rebuild a volume-backed instance, it fails.
malor@ubuntu:~/devstack$ nova image-list
+--+-+++
| ID | Name|
Status
Public bug reported:
we can get exception.OverQuota from cinder layer
but we didn't handle it in API layer when we create volume
this may lead to a 500 error
** Affects: nova
Importance: Undecided
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee:
Public bug reported:
This is a follow on to bug 1293480 and related to bug 1408176 and bug
1443186.
There can be a race when rebooting a compute host where libvirt is
shutting down guest VMs and sending STOPPED lifecycle events up to nova
compute which then tries to stop them via the stop API,
Public bug reported:
When a VM is in a bad status, there's no effective way to delete it from
CLI/API even after reset-state. The only known option is to delete it
from MySql tables. in Kilo release following Nova tables will need to be
touched which is inconvenient and could post a risk. Would
You have been subscribed to a public bug:
Based on the description in the following link
https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0#Create_a_Health_Monitor
tenant_id: only required if the caller has an admin role and wants to
create a Health Monitor for another tenant.
while in the
** Also affects: os-brick
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/1370226
Title:
LibvirtISCSIVolumeDriver cannot find
Public bug reported:
There are couple of policy rule that are unused for trust, even if the
user updates the rule it won't impact the policy check.
we should clean this up to avoid confusion.
This is step #1 as for fixing the policy rule for trust. See :
Public bug reported:
There is some javascript which hard codes the logout url to be
/auth/logout at:
https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/angular/horizon.js#L29
This is incorrect in number of distributions / deployments where horizon
resides in a path such
** Also affects: 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/1444532
Title:
nova-scheduler doesnt reconnect to
Public bug reported:
The rpc version alias need to be updated for conductor and scheduler.
Those alias is needed for rolling upgrade
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Tags: kilo-rc-potential
** Summary changed:
- Add RPC version
Public bug reported:
There isn't rpc alias for compute task api. If there is any change for
the compute task api, we need provide version cap for it to enable
rolling upgrade
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Changed in: nova
** Also affects: os-brick
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/1367189
Title:
multipath not working with Storwize
This bug was fixed in the package walinuxagent - 2.0.12-0ubuntu2
---
walinuxagent (2.0.12-0ubuntu2) vivid; urgency=medium
* Fixed systemd unit file which caused SharedConfig.xml to be deleted by
Cloud-init (LP: #1444086).
-- Ben Howard ben.how...@ubuntu.com Wed, 15 Apr 2015
*** This bug is a duplicate of bug 1437479 ***
https://bugs.launchpad.net/bugs/1437479
** This bug has been marked a duplicate of bug 1437479
Groups create has a bad request url
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
The scrubber can leave orphaned objects and db records in error / edge
cases. This is because the order in which it updates the DB and object
store. Recommended solution:
For each image that has status pending_delete:
For each image location that has status
Public bug reported:
** No longer affects: cloud-init
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1444086
Title:
cloud-init removes SharedConfig.XML on new instances of Azure
Status in walinuxagent
Public bug reported:
Based on the description in the following link
https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0#Create_a_Health_Monitor
tenant_id: only required if the caller has an admin role and wants to
create a Health Monitor for another tenant.
while in the tempest Admin API
I happened to have some investigate about this kind of issues. From the
bug history, this issue will be close as invalid. tenant_id can only be
passed in by admin. Neutron would think admin knows what he is doing,
and would allow admin to do anything.
Pls see the following bugs as reference.
You have been subscribed to a public bug:
Here is the following scenario:
This is happening only WITH tempest tests by inheriting the necessary
class from 'tempest/api/neutron':
(a) When creating a loadbalancer for non_admin user, I could see the
'tenant_id' is equal to
Public bug reported:
VPNaaS has already could support strongswan as its driver. But it is only for
ubuntu, and can not support rhel or fedora.
Compared with ubuntu, Rhel using different CLI command and strongswan
configuration directory.
** Affects: neutron
Importance: Undecided
** Package changed: ifupdown (Ubuntu) = neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1444765
Title:
admin's tenant_id is not the same with load_balancer's tenant_id in
Public bug reported:
After activating the multiple domains option in Horizon kilo-3 environment,
Create Group dialog is not working properly.
Problems:
1. No input field verification
2. Fail to create a group
Note: please see attached local_settings.py for configuraiton details.
Performt the
This will be implemented inside OVN project, setting to invalid for now
** Changed in: neutron
Status: In Progress = 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/1443259
Public bug reported:
If instance is resizing and user tries to delete the instance, in that
case instance gets deleted successfully. After instance deletion, greenthread
which was resizing the instance raises InstanceNotFound error, which caught in
errors_out_migration and raises KeyError:
Public bug reported:
keystone token responses contains both the InternalURL and adminURL for
non admin user (demo).
This information should not be exposed to a non-admin user.
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
Currently the transaction timeout is taken from a context object that has a
vsctl_timeout attribute
this method is confusing for other users of this class (like OVN) and should be
configurable in a different way
** Affects: neutron
Importance: Undecided
Assignee:
This is not valid bug now as we do not have downgrades in migrations.
** Changed in: neutron
Status: In Progress = Invalid
** Changed in: neutron
Assignee: Ann Kamyshnikova (akamyshnikova) = (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Nova security groups are supposedly name-unique, while Neutron security groups
are not necessarily so.
I've noticed that while it's possible to add Neutron security groups to server
by using the security group ID, it's impossible to do so for a Nova security
group (only
Public bug reported:
The hash type used by the ipsets is 'ip' which explodes a CIDR into
every member address (i.e. 10.100.0.0/16 becomes 65k entries). The
allowed address pairs extension allows CIDRs so a single allowed address
pair set can exhaust the entire IPset and break the security group
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Assignee: (unassigned) = Dan Watkins (daniel-thewatkins)
** Changed in: walinuxagent (Ubuntu)
Status: In Progress = Invalid
** Changed in: cloud-init
Status: New = In Progress
** Also affects: nova/juno
Importance: Undecided
Status: New
** Changed in: nova/juno
Status: New = In Progress
** Changed in: nova/juno
Importance: Undecided = High
** Changed in: nova/juno
Assignee: (unassigned) = Nikola Đipanov (ndipanov)
** Tags removed:
While this is Low by itself, it is required for Juno backport of bug
1415768
** Also affects: nova/juno
Importance: Undecided
Status: New
** Changed in: nova/juno
Status: New = In Progress
** Changed in: nova/juno
Importance: Undecided = High
** Changed in: nova/juno
Public bug reported:
Steps:
1. Login as admin user.
2. Navigate to Horizon page:
http://horizon_ip/horizon/project/access_and_security/
3. Click on View Credentials button.
4. Check position of eye icon.
Actual: icon above EC2 Secret Key field.
Expected: should be at the right end of field.
**
Public bug reported:
git checkout from kilo rc1:
I have deployed as system with nova network instead of neutron.
While trying to launch an instance, I'm getting:
Internal Server Error: /project/instances/launch
Traceback (most recent call last):
File
49 matches
Mail list logo
