Public bug reported:
Due to bug #1445674, Migration object was not set to error if there is a
resize failure.
Later on, if we delete the instance, the Migration object will continue
to exist.
If we were to restart compute service, it will fail to start since
_update_usage_from_migrations
Versio
Public bug reported:
in neutron/policy.py:
def check_is_admin(context):
"""Verify context has admin rights according to policy settings."""
init()
# the target is user-self
credentials = context.to_dict()
target = credentials
# Backward compatibility: if ADMIN_CTX_POLICY i
Public bug reported:
This is similar to bug #1423952.
We need to handle that 'migration' can be in args or kwargs.
It should follow the same fix for bug 1423952.
This fixes the KeyError in the decorator by normalizing the args/kwargs
list into a single dict that we can pull the migration from.
2
Public bug reported:
In a load test where a nova environment w/ networking enabled was set up
to have ~250K instances, attempting to launch 50 instances would cause
many to time out, with the error "Timeout while waiting on RPC response
- topic: "network", RPC method: "allocate_for_instance". T
I had an approach to have a special username matching keyword for
policy.json to address this. It was wildly unpopular.
The general consensus was to add a role in the deployment and match
based on that.
** Changed in: neutron
Assignee: Kevin Benton (kevinbenton) => (unassigned)
** Changed i
Public bug reported:
I'm using a nova built from stable/kilo and trying to implement instance
IO resource quotas for disk as per
https://wiki.openstack.org/wiki/InstanceResourceQuota#IO.
While this works when building an instance from ephemeral storage, it
does not when booting from a bootable ci
This bug was fixed in the package cloud-init - 0.7.7~bzr1091-0ubuntu1
---
cloud-init (0.7.7~bzr1091-0ubuntu1) vivid; urgency=medium
* New upstream snapshot.
* fix processing of user-data in cloud-config-archive format (LP: #1445143)
-- Scott MoserFri, 17 Apr 2015 12:04:16 -
Public bug reported:
Tempest failure has been seen due to various failures in the tests.
It's failed on 'MANUAL' != 'AUTO' in an assert, and occasionally the 500
error as seen below.
2015-04-17 15:52:46.992 |
tempest.api.compute.servers.test_disk_config.ServerDiskConfigTestJSON.test_rebuild_serv
Public bug reported:
Failed Tempest due to a not yet tracked down race condition.
2015-04-17 15:52:46.984 |
tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_rebuild_server_in_stop_state[gate,id-30449a88-5aff-4f9b-9866-6ee9b17f906d]
2015-04-17 15:52:46.984 |
---
Public bug reported:
The tempest test is failing, likely due to a race condition with setting
system_metadata on instances too quickly.
2015-04-17 15:52:47.001 |
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_run_idempotent_instances[id-c881fbb7-d56e-4054-9d76-1c3a60a207b0]
2
Public bug reported:
Overview:
After deactivating an image, the image owner can no longer see the image in a
list images response.
Steps to reproduce:
1) Create an image with user A
2) Deactivate the image with an admin
3) List all images, accounting for pagination as needed, with user A via:
GE
Problem with driver loading in new repo was resolved, so this is no
longer a failure. Marked as invalid.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://
** 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/1282855
Title:
Add httmock to test-requirements.txt and update requests -> 2.1
** Changed in: django-openstack-auth
Milestone: None => 1.1.9
** Changed in: django-openstack-auth
Status: Fix Committed => Fix Released
** Changed in: horizon
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineer
Service Type Framework effort was abandoned and will be replaced in the
future by the "flavor" framework. This will not be done.
** Changed in: neutron
Status: In Progress => Invalid
** Changed in: neutron
Assignee: Paul Michali (pcm) => (unassigned)
--
You received this bug notific
Public bug reported:
On Project->Compute->Instances->Edit Instance->Security Group there is
not enough width for the Spanish translation of Instance Security Groups
to be rendered inline with the filter.
** Affects: horizon
Importance: Undecided
Status: New
** Attachment added: "ed
** 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/1444765
Title:
admin's tenant_id is not the same with load_balancer's tenant_id in
t
** Package changed: ubuntu => nova (Ubuntu)
--
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 databases when started and d
Public bug reported:
This may be related to 1290635 but I am not familiar enough with Nova's
dhcp and shelve implementations to know for sure. Also the behavior I am
seeing seems to be slightly different.
In the multinode nova-net job
(http://logs.openstack.org/88/174288/1/check/check-tempest-dsv
** Changed in: neutron
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1442524
Title:
Operation not allowed errors when execute db migration when us
In your bug description you indicate this is only a security hardening
measure, but now you've switched the bug type to indicate it's an
exploitable security vulnerability. Also this looks like a duplicate of
bug 1445475 reported against nova.
** Also affects: ossa
Importance: Undecided
You've switched this bug report to indicate an exploitable security
vulnerability. Can you describe in greater detail the exploitation
scenario you have in mind? What sort of patch to neutron do you expect
to correct this defect? Does this vulnerability appear in previous
releases of neutron as wel
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: cloud-init (Ubuntu)
Assignee: Dan Watkins (daniel-thewatkins) => (unassigned)
** Changed in: cloud-init
Stat
I think the reason the 'nova' user needs the 'admin' role is because
neutron uses it to send a network allocation event back to nova. Nova
should be configured by default to allow users with the 'service' role
to do this operation and not require the 'admin' role.
** Information type changed from
Public bug reported:
Overview:
When attempting to deactivate a queued image (one without an image file)
returns a "'403 Forbidden - Not allowed to deactivate image in status 'queued'".
Steps to reproduce:
1) Register a new image as user
2) Without uploading an image file, deactivate the image as
*** This bug is a security vulnerability ***
Public security bug reported:
The typical config has nova using the 'neutron' user in the 'service' project
to do operations against Neutron. The 'neutron' user should not require the
'admin' role on the 'service' project to do all the operations it
** Also affects: ec2-api
Importance: Undecided
Status: New
** Changed in: ec2-api
Status: New => Confirmed
--
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/
Public bug reported:
The "edp.java.adapt_for_oozie" boolean configuration value may be set on
the execution of a Java job. It causes Sahara to modify the hadoop
configuration of a Java job automatically so that configuration values
set during job launch are automatically set without having to modi
** Also affects: ec2-api
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/1370250
Title:
Can not set volume attributes at insta
Public bug reported:
There are two boolean configuration values that enable substitution of
data source objects for custom urls or uuids in configs, args, and
params when jobs are submitted:
* edp.substitute_data_source_for_name -- substitute data source objects
for urls of the form datasource:/
** Also affects: ec2-api
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/1370901
Title:
Nova EC2 doesn't create empty volume w
** Also affects: ec2-api
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/1371445
Title:
Nova EC2 doesn't assign a floating IP
** Also affects: ec2-api
Importance: Undecided
Status: New
** Changed in: ec2-api
Status: New => Confirmed
--
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/
Public bug reported:
On a single-node devstack installation, on Ubuntu LTS 14.4, with the Xen
hypervisor.
To reproduce:
nova volume-create --image-id cirros-0.3.2-x86_64-uec --display-name vol-cirros
1
nova boot --key-name `hostname` --block-device
source=volume,id=$volume_id,dest=volume,bootin
Fair enough, thanks. I'll move this bug to the client then.
** Project changed: glance => python-glanceclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1444056
Title:
v1 client may
Public bug reported:
the get_routers plugin call that the l3 agent makes is serviced by a
massive amount of SQL queries that lead the whole process to take on the
order of hundreds of milliseconds to process a request for 10 routers.
This will be a blanket bug for a series of performance improvem
** Changed in: oslo.messaging
Status: New => Invalid
--
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/1393320
Title:
Juno: Nova compute service cant connect to AMQP
IMO, this just needs to be documented.
Obviously ports that go first get their fixed IPs allocated and later port
creation may fail if some port specifies already-allocated IP.
I don't think it makes sense to arrange input port list in anyway.
** Changed in: neutron
Status: Confirmed => I
I think, this was resolved some time ago, and this tries to fix it
another time.
If you feel, like this is a missing feature, please add a blueprint
about this. Thank you.
** Changed in: horizon
Status: Opinion => Incomplete
** Changed in: horizon
Assignee: Kanagaraj Manickam (kanaga
39 matches
Mail list logo
