** 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/1676486
Title:
Update row in glance images doesn't work
Status
Public bug reported:
Ther'a 2 issues with authentication.
1. Consider the following code.
client = swift_api_client.Connection(
user=keystone.user.username,
preauthurl=url,
preauthtoken=keystone.user.token.id,
Public bug reported:
% neutron floatingip-create ISP_NET --floating-ip-address 31.28.168.167
But this is broadcast IP address.
% ping 31.28.168.167
Do you want to ping broadcast? Then -b
** Affects: neutron
Importance: Undecided
Assignee: Vitalii (vb-d)
Status: Invalid
Public bug reported:
Neutron allows to create floating IP 31.28.168.167, which is broadcast
address.
I think it should raise exception.
** Affects: neutron
Importance: Undecided
Status: New
** Project changed: nova = neutron
--
You received this bug notification because you are
Public bug reported:
I stopped neutron, dropped its database, created new one, created new
external network and router.
New router has different IP address.
I restarted all nova services.
I created new instance. During boot I can see that cloud-init received
old network settings from nova.
** 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).
https://bugs.launchpad.net/bugs/1470502
Title:
nova uses outdated userdata
Status in OpenStack Compute
Public bug reported:
Ther's shutdown_timeout defined in nova.conf, which implies, that all
virtuam machines in cloud should get in time to turn off, no matter what
OS they have installed. Not logical from my point of view.
You have `image_os_shutdown_timeout` property, which used instead of
Public bug reported:
The following command worked in Icehouse. It do not work in Juno
anymore.
neutron net-create --tenant-id 7f41e236d56c4e9fa074a9185528cad2
--provider:network_type=flat --provider:physical_network=default
--router:external=True GATEWAY_NET
It returns error:
neutron
Public bug reported:
I receie weird exception when I try to perform any action with nova ( nova list
for example ).
I checked, error that should have been logged is Authorization failed for token.
Logged from file auth_token.py, line 825
Traceback (most recent call last):
File
Public bug reported:
I tried to boot server from volume using API. The following
'block_device_mapping_v2' argument
{
boot_index: 0,
uuid: image_obj,
source_type: image,
volume_size: flavor_obj.disk,
destination_type: volume,
delete_on_termination: False
}
Nova raised
Public bug reported:
Steps to reproduce:
1. Create raw bare glance image
2. Create LVM volume group
3. Boot instance with nova:
nova --debug boot --flavor m1.small --block-device
source=image,id=GLANCE IMAGE
ID,dest=volume,size=10,shutdown=preserve,bootindex=0 --nic net-
id=NEUTRON NET ID test
Public bug reported:
I created instance with one NIC attached.
Then I try to attach another NIC:
nova add-fixed-ip ServerId NetworkId
Nova compute raises exception:
2014-10-24 15:40:33.925 31955 ERROR oslo.messaging.rpc.dispatcher
[req-43570a05-937a-4ddf-a0e9-e05d42660817 ] Exception during
Public bug reported:
In Juno, ther's no option policy_file in neutron.conf, which causes exception,
when I start services:
2014-10-23 12:18:25.013 32561 TRACE neutron PolicyFileNotFound: Policy
configuration policy.json could not be found
** Affects: nova
Importance: Undecided
Public bug reported:
In Juno release /rootwrap.d/l3.filters missing filter, which enables to
kill any process with -9
At least neutron-l3-agent raises exception when I restart it.
2014-10-23 15:01:47.664 11294 TRACE neutron.agent.l3_agent
self._destroy_namespace(ns)
2014-10-23 15:01:47.664
Public bug reported:
During testing and development I had to add and remove instances, routers,
ports often. Also I restarted all neutron services often ( I use supervisor ).
After about one week, I noticed that I ran out of free RAM. It turned out there
were tens of neutron-ns-metadata-proxy
Public bug reported:
Sometimes, when I start instance, nova raises exception, that
filter like nova-instance-instance-000b-52540039740a already exists.
So I have to execute `virsh nwfilter-undefine` and try to boot instance
again:
In libvirt logs I can see the following:
2014-10-22
Public bug reported:
After I added/removed routers, nets and subnets many times, for testing
purpose, I found that I have 45 interfaces:
b# ifconfig|grep encap:Ethernet
br-eth0 Link encap:Ethernet HWaddr d0:67:e5:03:18:0f
br-eth0:1 Link encap:Ethernet HWaddr d0:67:e5:03:18:0f
eth0
17 matches
Mail list logo
