** Changed in: neutron
Status: In Progress = Invalid
** Changed in: neutron
Status: Invalid = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1448862
Title:
Thanks for the Nova fix. I guess we can't fix anything on Ironic side,
can we?
** Changed in: ironic
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
For openstack-ansible, the bump to the latest juno release (which
includes the fix referenced in this bug) is here:
https://review.openstack.org/#/c/177388/
Once that merges, the work for openstack-ansible in this bug is
complete.
** Also affects: openstack-ansible/juno
Importance: Undecided
Public bug reported:
The OVS library now allows registering a notification hook by
subclassing the Idl class and defining a notify() function. To be able
to use this in Neutron (and networking-ovn), it must be possible for the
Connection object to use a subclassed Idl. It currently is hardcoded
Public bug reported:
Subfolder_path is None when upload object.
Step:
1. Create 50 containers. Container_1 ~ 50.
2. click Container_1 then create pseudo-folder folder1.
3. click folder1 and then upload object test1.
4. repeate to click sidebar Container to reload table.
5. repeate step 3 will
Public bug reported:
#1438226 reported that CPU pinning was broken in select versions of
libvirt. Further investigation has highlighted issues with NUMA tuning
in general on these versions. The same error messages seen with when
configuring CPU pinning are seen when configuring NUMA tuning. The
Public bug reported:
When limiting access to token-related operations, we may need references
like %(target.token.user.domain.id)s.
However possible values of target.token.* is missing while
target.user.*, target.role.* and so on are listed in
configuration.rst:
** Also affects: neutron/kilo
Importance: Undecided
Status: New
** Changed in: neutron/kilo
Milestone: None = kilo-rc3
** Changed in: neutron/kilo
Status: New = In Progress
** Changed in: neutron/kilo
Importance: Undecided = Critical
** Tags removed: kilo-rc-potential
** Also affects: neutron/kilo
Importance: Undecided
Status: New
** Changed in: neutron/kilo
Milestone: None = kilo-rc3
** Changed in: neutron/kilo
Status: New = In Progress
** Changed in: neutron/kilo
Importance: Undecided = High
--
You received this bug notification
** Also affects: neutron/kilo
Importance: Undecided
Status: New
** Changed in: neutron/kilo
Milestone: None = kilo-rc3
** Changed in: neutron
Milestone: kilo-rc3 = None
** Changed in: neutron/kilo
Status: New = In Progress
** Changed in: neutron/kilo
Importance:
** Also affects: nova/kilo
Importance: Undecided
Status: New
** Changed in: nova/kilo
Status: New = In Progress
** Changed in: nova/kilo
Importance: Undecided = Critical
** Changed in: nova/kilo
Milestone: None = kilo-rc3
** Tags removed: kilo-rc-potential
--
You
** Tags added: kilo-rc-potential
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Milestone: None = liberty-1
** Changed in: neutron
Importance: Undecided = High
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
When we associate a floatingip in an HA router setup, it is properly
associated.
However, when we check the status of the Floating ip, it is shown as empty.
$neutron floatingip-show 2675730e-6e9f-438d-be8a-0d45c641cf7a
Based on precedent set in bug 1362651, it looks like the impact of this
isn't a sufficient denial of service to warrant a security advisory for
existing stable releases.
** Changed in: ossa
Status: New = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
** Also affects: nova/kilo
Importance: Undecided
Status: New
** Changed in: nova/kilo
Milestone: None = kilo-rc3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Booting from volume does not actually boot from the volume; it boots
from a Glance image. Perform the following steps to test this:
Using the GUI steps:
1. In the Volumes tab, select Create Volume. For Volume Source, select an
image (I use CirrOS). Click Create Volume.
2.
Public bug reported:
Running base line mutli-node test shows tracebacks in q-agt.log when
deleting test networks
Test Bed:
- Kilo based
- LinuxBridge with VxLAN
- Mutli node - node1: controller/compute, node2: compute
Test details:
- Create tenant/router - attach to public network
-
Public bug reported:
when I create a loadbalancer with the following body, I could see the
'operating_status' is still showing 'ONLINE', it should be 'DISABLED'. I
also believe 'provisioning_status' should be shown as 'OFFLINE' , but I
could see as 'ONLINE'
Steps can be reproduced:
POST
Public bug reported:
1.1 Under test tenement,create network:net1,subnet:subnet1,network
address:192.168.1.0/24 and other keep default
1.2 Create rotuer:R1,R1 inner interface relate to subnet1 and set outer network
for R1
1.2 Create VM1-1,choose subnet1,security group is empty and firewall is
Public bug reported:
When the runcmd errors the power-state-change does not take effect and
the instance is not powered off.
AMI ID: ubuntu-vivid-15.04-amd64-server-20150422 (ami-2d10241d)
Instance launched on EC2 using awscli:
$ aws --region us-west-2 ec2 run-instances --image-id
[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).
** Changed in: horizon
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1447459
Title:
stable/kilo fetches master translations
Status
** Project changed: nova = python-cinderclient
** Changed in: python-cinderclient
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
arp spoofing code tries to install flows with arp_spa=ipv6_address and
ovs-ofctl correctly complains.
2015-04-26 00:17:36.844 ERROR neutron.agent.linux.utils [req-f516905e-77b4-4975-
8b8d-5b3669cdda0d None None]
Command: ['ovs-ofctl', 'add-flows', 'br-int', '-']
Exit code:
Public bug reported:
Cinder volumes can get stuck in a state of 'attaching' or 'detaching' and they
need to be cleaned up or they will be incapable of being used. This is not
possible because python-novaclient 'nova volume-detach' lacks a '--force'
option.
Nova will need to call Cinder
25 matches
Mail list logo