Public bug reported:
'server lock' is indented to protect instance from simple mistakes (like
removing the wrong instance, or shut-downing it). It does prevent
shutdown, destruction and port detachment.
But if port is removed via `openstack port delete` it silently get
removed from locked instanc
This problem exists in Ironic regardless of bot attempts to sweep it
under the expiration rug.
** Changed in: nova
Status: Expired => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bug
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1685237
Title:
port security does not block router advertisem
Public bug reported:
Host local IP addresses shouldn't be in source_ip for incoming packets.
No exceptions.
Current implementation of security groups, when user allow a wide range
of IP addresses to pass, allow to pass 127.0.0.0/8.
Steps to reproduce:
1. Create rule in security groups which allo
Public bug reported:
Affected version: mitaka
Issue: If port security is enabled, IPv6 router advertisements may be
send by any instance.
Network configuration: vlan, security groups disabled, port security
enabled.
subnet:
{
"description": "",
"enable_dhcp": true,
"network_id": "b71b7cc7
Public bug reported:
Current documentation states that:
http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html#version-2
... a config drive: ...Must be a un-partitioned block device (/dev/vdb,
not /dev/vdb1)...
This is not correct.
1. Cloud-init actually, works with Confi
Public bug reported:
Normally dhcp agents should not provide routable services. There is one
exception: monitoring. Checking dhcp agents availability by sending PING
requests is very easy and sits well with existing monitoring frameworks.
Outside of checking of availability of DHCP agent itself th
Public bug reported:
Hello.
File cloud-init/cloudinit/distros/rhel.py has a broken link "# See:
http://tiny.cc/6r99fw";. Can you put it content somewhere inside repo?
Thanks.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because y
Public bug reported:
Currently there is no way to change key-name associated with instance.
This has some justification as key may be downloaded only at build time
and later changes will be ignored by instance.
But this is not a case for rebuild command. If tenant want to rebuild
instance, he may
** Project changed: ironic => nova
** Tags added: ironic
** Description changed:
If nova-compute service is down at the moment of execution 'nova delete'
for instance, node with this instance will never been cleaned/turned off
after nova-compute start.
Steps to reproduce:
1. Prepare
** Also affects: nova (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/1660317
Title:
NotImplementedError for detach_i
Public bug reported:
When baremetal instance deleted there is a harmless but annoying trace
in nova-compute output.
nova.compute.manager[26553]: INFO [instance:
e265be67-9e87-44ea-95b6-641fc2dcaad8] Terminating instance
[req-5f1eba69-239a-4dd4-8677-f28542b190bc 5a08515f35d749068a6327e387ca04e2
Public bug reported:
Right now when ML2 load mechanism driver, if some of them is unavailable
(due to typo or bug in the driver, preventing it to be loaded by
stevedore), it registered only in 'info' output of neutron-server
('Configured mechanism driver names' and 'Loaded mechanism driver
names')
Public bug reported:
If ml2 have settings
[DEFAULT]
extension_drivers = port_security
[securitygroup]
enable_security_group = False
and one is trying to disable port-security on a given port, he/she will
fail:
neutron port-update fad58638-3568-4bcb-8742-d857d138056d --port-
security-enabled=Fa
Public bug reported:
Neutron 8.3 (mitaka) rejects requests to update allowed_address_pairs.
Request:
neutron --debug port-update b59bc3bb-7d34-4fbb-8e55-a9f1c5c88411
--allowed-address-pairs type=dict list=true ip_address=10.254.15.4
curl:
curl -g -i -X PUT
https://network.servers.example.com:9
Public bug reported:
We've performed upgrade juno->kilo->libery->mitaka (one by one) without
rebooting compute hosts.
After mitaka upgrage we found that some of tenant networks are not
functional. Deeper debug shows that in openvswitch tag value in 'other-
config' field in ovs port description do
We've got same issue after upgrading from liberty. It was really
painful, and we've been forced to manually patch agent on hosts.
This is a real issue, please fix it.
** Changed in: neutron
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
E
** Also affects: nova
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/1656854
Title:
Incorrect metada in ConfigDrive when usin
Public bug reported:
version: newton (2:9.0.0-0ubuntu1~cloud0)
When neutron trying to bind port for Ironic baremetall node, it sending
wrong notification to nova about port been ready. neutron send it with
'device_id' == ironic-node-id, and nova rejects it as 'not found' (there
is no nova instanc
Public bug reported:
If there is no suitable mech driver found, ML2 just make port
bind_failed and write uninformative message in the log:
2017-01-12 13:56:46.691 3889 ERROR neutron.plugins.ml2.managers [req-
d9d956d7-c9e9-4c1b-aa1b-59fb974dd980 5a08515f35d749068a6327e387ca04e2
7d450ecf00d64399ae
I found one more source of this bug (It was pointed by Marsikus at
habrahabr.ru):
https://github.com/openstack/oslo.config/compare/3.18.0...master
As you can see, oslo.config have dependency for python-rfc3986== 0.2.0
in version 3.18.0, and 0.2.2 in stable/newton.
And https://releases.openstack.o
I found source of the bug: python-rfc3986 is to blame (it is used by
oslo-config). Version 0.2.0-2 contains bug which violates RFC3986. It
was fixed in 0.2.2. Version of python-rfc3986 from zesty (0.3.1-2) fix
this problem.
I believe this bug should be fixed by bumping up version of python-
rfc39
Public bug reported:
nova version: newton
dpkg version: 2:14.0.1-0ubuntu1~cloud0
distribution: nova @ xenial with ubuntu cloud archive, amd64.
Nova fails with exception ConfigFileValueError: Value for option url is
not valid: invalid URI: if url parameter of [neutron] section or
novncproxy_base_
Public bug reported:
Right now if instance has been deleted, 'nova instance-action-list'
returns 404. Due to very specific nature of 'action list' is is very
nice to have ability to see action lists for deleted instances,
especially deletion request.
Can this feature be added to nova? Al least, f
Public bug reported:
Nova in juno ignores following settings in configuration file ([DEFAULT]
section):
logging_context_format_string
logging_default_format_string
logging_debug_format_suffix
logging_exception_prefix
when sending logs via syslog. Log entries on stderr / in log files are
fine (us
** Attachment added: "Full build log from CI"
https://bugs.launchpad.net/nova/+bug/1548724/+attachment/4579857/+files/consoleText
** Changed in: nova
Status: Incomplete => Opinion
** Changed in: nova
Status: Opinion => New
--
You received this bug notification because you are
Public bug reported:
When I've tried to set up CI build for nova package (13.0b2) but it
fails on tests:
==
FAIL:
nova.tests.unit.test_signature_utils.TestSignatureUtils.test_get_certificate
nova.tests.unit.test_signature_utils.
Public bug reported:
Steps to reproduce:
1. Create a few networks. In my case they were shared external networks
of 'vlan' type.
Example:
neutron net-create internet_192.168.16.64/27 --router:external True
--provider:physical_network internet --provider:network_type vlan
--provider:segmentati
Public bug reported:
neutron --debug port-list --binding:vif_type=binding_failed displays all
ports with all vif_type, not only with binding_failed.
vif_type=binding_failed is set when something bad happens on a compute
host during port configuration (no local vlans in ml2 conf, etc)
We had inte
Public bug reported:
Horizon: 2014.2.3
Steps to reproduce:
1. Create net
2. Create subnet with gateway
3. Open network details (click on network name) under admin section
4. Click 'edit subnet'
5. Click "Disable Gateway"
Expected behavior:
1. Field 'gateway' disabled
2. IP address in 'gateway' c
Public bug reported:
Steps to reproduce:
1. Create instance
2. Shutdown instance
3. Perform resize
4. Try to start instance.
Expected behaviour: instance starts in resize_confirm state
Actual behaviour: ERROR (Conflict): Instance
d0e9bc6b-0544-410f-ba96-b0b78ce18828 in vm_state resized. Cannot
May be. I'm not sure. Anyway, this is not nova/glance/neutron bug, but
python-eventlet, and it is mostly concerns for distributions, not for
developers.
** Also affects: python-eventlet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a m
Public bug reported:
Affected:
glance-api
glance-registry
neutron-server
nova-api
If service was configured to use rsyslog and rsyslog was restarted after
API server started, it hangs on next log line with 100% CPU. If server
have few workers, each worker will eat own 100% CPU share.
Steps to r
Public bug reported:
If neutron was configured to have more than one DHCP agent per network
(option dhcp_agents_per_network=2), it causes dnsmasq to reject leases
of others dnsmasqs, creating mess and stopping instances to boot
normally.
Symptoms:
Cirros (at the log):
Sending discover...
Sending
Public bug reported:
Horizon version:
openstack-dashboard 1:2014.2.2-0ubuntu1~cloud0
python-django-horizon 1:2014.2.2-0ubuntu1~cloud0
Steps to reproduce:
1. Disable router extension in neutron (empty service_plugins in neutron.conf)
2. Disable routers in horizon OP
Public bug reported:
doc/api_samples/all_extensions/extensions-get-resp.json in repository
contains broken links:
namespace":
"http://docs.openstack.org/compute/ext/extended_rescue_with_image/api/v2";
namespace": "http://docs.openstack.org/compute/ext/rescue/api/v1.1";
etc.
** Affects: nova
Public bug reported:
If network have no free fixed IPs, new instances failed with 'No valid
hosts found' without proper explanation.
Example:
nova boot foobar --flavor SSD.1 --image cirros --nic net-id=f3f2802a-
c2a1-4d8b-9f43-cf24d0dc8233
(There is no free IP left in network f3f2802a-c2a1-4d8b
Public bug reported:
If nova recieve 404 from neutron due lack of free fixed IPs, it traces
badly and return 500 error to user.
Steps to reproduce:
0. Setup nova & neutron, create network & subnetwork
1. Consume all IP from that network
2. Try to attach interface to that network (nova interface-a
Public bug reported:
If my_ip in nova config do not exit on any interface of the compute
host, nova-compute silently accepts it and failing cold migration.
Expected behaviour: error or warning if my_ip can not be found on any
interface.
Nova version: 1:2014.2.1-0ubuntu1~cloud0
** Affects: nova
** Description changed:
State to reproduce:
1. Boot instance from image
2. Delete image
3. Stop nova-compute
4. Remove /var/lib/nova/instances/_base/*
5. start nova-compute
6. Try to rescue instance (nova rescue image)
Nova-compute will fail with few traces (see below) and inst
Public bug reported:
State to reproduce:
1. Boot instance from image
2. Delete image
3. Stop nova-compute
4. Remove /var/lib/nova/instances/_base/*
5. start nova-compute
6. Try to rescue instance (nova rescue image)
Nova-compute will fail with few traces (see below) and instance get
strange stat
Public bug reported:
I know it sounds silly, but I just spend five hours trying to find why
glance is not working with swift and printing random erros. At the end I
had found it had ignored all debug/log settings, and later I had found
the source of the problem - small typo in my config.
If confi
Public bug reported:
When administrator misspells mappings for external flat networks, nova
fails with obscure trace during instance creation:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2231,
in _build_resources
yield resourc
Public bug reported:
If openstack installation has no cinder service in endpoint list,
horizon reports 'Error: Invalid service catalog service: volume' many
times (after login, each time dialog for new instance is opened).
** Affects: horizon
Importance: Undecided
Status: New
--
Y
Public bug reported:
We found that large amount of metering labels and rules cause memory
leak in neutron server. This problem is multiplied by amount of workers
(10 workers - 10x memory leak).
In our case we have 657 metering-lables and 122399 metering-label-rules,
If anyone query them, neutron
Public bug reported:
We've has a planned outage for whole OS installation, and after booting
back (+few reboots of hosts and instances during that process) many (may
be all) instances changed their ssh keys.
OS: havana@ubuntu
cloud-init:
cloud-init 0.7.2-3~bpo70+1
cloud-in
Public bug reported:
Installation works about few months, got this message in logstash.
Happens once, there is no surrounding activity (no requests to API).
Havanna, ubuntu-cloud-archive, 2013.2.3-0ubuntu1.1
Aug 17 21:48:59 api1 neutron.openstack.common.db.sqlalchemy.session[12400]:
ERROR DB
Public bug reported:
If instance is migrated from hypervisor by 'nova host-servers-migrate'
and it image was deleted, instance fails to start with message
{u'message': u'Image d2ab45e6-3db0-450b-b5aa-8b0646e063a2 could not be
found.', u'code': 404, u'created': u'2014-06-12T12:39:27Z'}
Steps to r
Public bug reported:
Ubuntu's source package for neutron can not be rebuild twice:
1. There is no proper clean target.
2. neutron.egg-info included in neutron_2013.2.3.orig.tar.gz (regardless of
.gitignore in original git).
That cause problem when package is build twice from same source. 1st
bu
Public bug reported:
ovs plugin floods auth.log with repeative messages:
Apr 20 06:25:20 pp3 sudo: neutron : TTY=unknown ; PWD=/ ; USER=root ;
COMMAND=/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl
--timeout=2 --format=json -- --columns=name,external_ids list Interface
Apr 20 0
Public bug reported:
If all compute nodes in some availability zone are disabled, horizon
trace at availability zones list.
Steps to reproduce:
1. Create host aggregate and availability zone (nova aggreage-create some some)
2. Add some (at least one) host to that host aggregate (nova aggreage-ad
Public bug reported:
If LBaaS functionality enabled and instances has more that one network
interfaces, horizon incorrectly choose members ports to add in the LB
pool.
Steps to reproduce:
0. nova, neutron with configured LBaaS functions, horizon.
1. Create 1st network (e.g. net1)
2. Create 2nd n
neutron-plugin-metering-agent1:2013.2.1-0ubuntu1~cloud0
** Project changed: neutron => neutron (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1286209
Title:
unhandled trace
Public bug reported:
If network node has no active routers on it l3-agent, metering-agent
tracing:
2014-02-28 17:04:51.286 1121 DEBUG
neutron.services.metering.agents.metering_agent [-] Get router traffic counters
_get_traffic_counters
/usr/lib/python2.7/dist-packages/neutron/services/meterin
Public bug reported:
If any OVS-enabled host with GRE tunnes change it IP, neutron do not
discard entry in ovs_tunnel_endpoints table and recreate gre-x
interfaces in br-tun on every boot.
Expected behavior: automaic removing of entries in ovs_tunnel_endpoints
when IP address is changed.
** Affe
Public bug reported:
If user was capable to create broken network configuration, instance
become undeletable. Reason why user can create broken networking is
under investigation (current hypothesis: if network (neutron) created in
one tennant and instance in other, and user is admin in both tenan
Public bug reported:
Steps to reproduce:
1. Create maximum amount of instances allowed by quota
2. Go to Project -> Instances.
3. Terminate any instance
Expected behavior: Button "Launch Instance (quota exceded)" become enabled and
changed to "Launch Instance"
Actual behavior: Button not change
57 matches
Mail list logo
