Public bug reported:
This is not a bug. It is a fetaure request.
LBaaS v2 healthmonitors currently perform checks against the members'
protocol port which handles normal traffic.
I would like the ability to configure a healthmonitor to perform checks
against a different port.
Use cases:
1) An
slated set 2,
code 0x0 on isa0060/serio0).
This appears to be related to recent code changes in noVNC. If I revert
noVNC to the sha 4e0c36dda708628836dc6f5d68fc40d05c7716d9, everything
works. This sha commit date is August 26, 2016.
Phil
** Affects: horizon
Importance: Undecided
Public bug reported:
Running on Ubuntu 14.04.
After installing nova from source in either the Liberty release or Mitaka, with
WebOb 1.6.0, running any nova command generated this error:
root@openstack-ubu-controller:~# nova service-list
ERROR (AttributeError): 'unicode' object has no attribute 'g
Public bug reported:
The sample data script is genterating warnings since the keystone
commands are depricated. The script needs to be updated to use the new
openstack commands.
** Affects: keystone
Importance: Undecided
Assignee: Phil Hopkins (phil-hopkins-a)
Status: In
Public bug reported:
cloud-init is incompatible with Puppet 4 (released April 15)
Notable differences:
Package name is puppet-agent (not puppet)
Installed in /opt/puppetlabs/bin/
PUPPET_CONF_PATH = '/etc/puppetlabs/puppet/puppet.conf'
PUPPET_SSL_CERT_DIR = '/etc/puppetlabs/puppet/ssl/certs/'
PUP
Thanks Darragh, that is the problem. I am closing the bug. If anyone see
this check out the bug that Darragh referenced above.
The packets coming from the DHCP server donot have a correct shecksum
and are being droped as they cross the bridge. Adding a magle rule to
add the checksum or ignore it f
Public bug reported:
I am running Ubuntu 14.04 with a source Juno install updated as of
yesterday. I have two network nodes and two compute nodes. When a VM is
booted the broadcast DHCP request goes out and is received by the
network node dnsmasq process. The unicast DHCP response is sent and is
r
Public bug reported:
https://blueprints.launchpad.net/nova/+spec/quota-instance-resource
added a number of resource managment capabilites via extra_specs foe
libvirt - but at least one of these causes VMs to fail on devstcak with
Neutron (so I'm guessing that they aren't covered in Tempest ?)
On
onic and a
virt driver.
** Affects: nova
Importance: Undecided
Assignee: Phil Day (philip-day)
Status: New
** Changed in: nova
Assignee: (unassigned) => Phil Day (philip-day)
--
You received this bug notification because you are a member of Yahoo!
Engineering T
Public bug reported:
Change https://review.openstack.org/#/c/112988/ added clean_shutdown
support for shelve(), but instances booted from volumes are shelved via
shelve_offload() - so that should also support clean_shutdown
** Affects: nova
Importance: Undecided
Assignee: Phil Day
Public bug reported:
I am running Juno on Ubuntu 14.04. OpenStack is installed from source
and updated to the latest this morning. I am trying to build HA routers
using VXLAN tunnels. When I set up my external network as a VXXLAN
network type everything works properly. If I delete the VXLAN based
I don't think this is a valid bug. Admins can already see deleted
instances by including "deleted=True" in the search options. Non
admins shouldn't be able to see deleted instances.
** Changed in: nova
Status: In Progress => Opinion
--
You received this bug notification because you
: nova
Importance: Undecided
Assignee: Phil Day (philip-day)
Status: New
** Changed in: nova
Assignee: (unassigned) => Phil Day (philip-day)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Comp
My mistake - it was the V3 client that was passing the hints in the
wrong part of the body
** 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.la
Public bug reported:
The v2.1 scheduler_hints plugin is broken, as it tries to extract the hints
from the request_body rather than the server_dict
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/plugins/v3/scheduler_hints.py#L42-L45
The hints value in the request body
The change to drive provisioning from conductor now avoids the code path
that was logging user data, so the immediate concern has gone away. Not
carrying user data in the instance object would still be a useful
optimization - but that's a different task.
** Changed in: nova
Status: In Prog
Public bug reported:
The limits API always returns the per tenant limits and not any per-user
limits that may exist.
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/limits.py#L94-95
The call to get_project_quotas should be replaced with a call to
get_user_quotas.
I susp
Public bug reported:
Entries in the instance_actions and instance_actions_events table should
be soft deleted as part of teh associated instance deletion.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
En
.
This may help wit some of the gate failures:
https://bugs.launchpad.net/nova/+bug/1300279
** Affects: nova
Importance: Undecided
Assignee: Phil Day (philip-day)
Status: New
** Changed in: nova
Assignee: (unassigned) => Phil Day (philip-day)
--
You received this
Assignee: Phil Day (philip-day)
Status: New
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Assignee: (unassigned) => Phil Day (philip-day)
** Changed in: nova
Milestone: None => juno-2
--
You received this bug notification because you are a
Marking as Invalid since this is a MySQL mis-configuration error by the
user rather than a Nova bug
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
opaque data blob as far as Nova is concerned (and hence
of no practical use for debugging).
** Affects: nova
Importance: Undecided
Assignee: Phil Day (philip-day)
Status: New
** Changed in: nova
Assignee: (unassigned) => Phil Day (philip-day)
--
You received this
;/mnt/stack/nova/nova/network/linux_net.py", line 1302, in _ovs_vsctl
2014-04-16 12:28:52.573 TRACE nova.compute.manager [instance:
3b7ac090-1ada-4beb-9e56-1ba3a6445e1f] raise
exception.AgentError(method=full_args)
2014-04-16 12:28:52.573 TRACE nova.compute.manager [instance:
3b7ac090-
Public bug reported:
I am running Icehouse r-1 on Ubuntu 12.04. Whenever I try to launch a VM
it immediately goes into error state. The log file fo rnova-compute
shows the following:
http_log_req /usr/lib/python2.7/dist-packages/neutronclient/common/utils.py:173
2014-04-07 19:15:32.888 2866 DEBU
that are using
the default value of state_path with no warning period, which goes beyond
the scope of change for UpgradeImpact
** Affects: cinder
Importance: Undecided
Status: New
** Affects: nova
Importance: High
Assignee: Phil Day (philip-day)
Status: In Progress
Public bug reported:
When an EC2 metadata request is received via the neutron metadata proxy
Nova assumes that the X-Forwarded-For item in teh header is the address
of the instance:
https://github.com/openstack/nova/blob/master/nova/api/metadata/handler.py#L149
In fact depending on the network p
** Changed in: nova
Status: Incomplete => Invalid
** Changed in: oslo.messaging
Status: Incomplete => 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/
Public bug reported:
The recent change to oslo messaging seems to have removed the ability to
specify a list of topics for notifications. This is a critical feature
for systems which provide multiple message streams for billing and
monitoring.
To reproduce:
1) Create a devstack system
2) Add
Public bug reported:
Currently we have a mix of “==0” and “<=0” being used inside periodic
tasks to decide to skip the task altogether. We also have the
“spacing=” option in the periodic_task decorator to determine how often
to call the task, but in this case: ==0 means “call at default
interva
Public bug reported:
Volume attach/detach/swap should set task_state so that conflicting
operations such as migrate can be blocked via the check_instance_state
decorator.
This would also allow users can see slow operations are still in
progress.
** Affects: nova
Importance: Undecided
ects: nova
Importance: Undecided
Assignee: Phil Day (philip-day)
Status: New
** Changed in: nova
Assignee: (unassigned) => Phil Day (philip-day)
** Changed in: nova
Milestone: None => icehouse-3
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Trying to remove a security group from an instance which is not actually
associated with the instance produces the following:
---
$nova remove-secgroup 71069945-5bea-4d53-b6ab-9026bfeebba4 phil
ERROR: [u'Security group %(security_group_name)s not assocaited wit
The associated change was reverted as it extended the duration of the
gate too much
** Changed in: nova
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://b
Public bug reported:
https://review.openstack.org/#/c/60052/1 fixed a problem with fake
libvirt driver by adding default arguments to Connection class, but the
tests still fail sometimes because the default value for uri is only
accepted if a global in the fake driver is true:
allow_default_ur
Looks like the problem is specific to our network
** Changed in: nova
Status: Incomplete => 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/1238536
Title:
Actually I'm not sure that caching the mapping would be safe in all
cases. The period would have to be so short to avoid the risk of the
port and address being re-assigned that it probably doesn't by that much
** Changed in: neutron
Status: New => Invalid
--
You received this bug notifi
I think the reason you can't reproduce this is because it looks like
Nova no longer deletes instance_system_metadata rows when it deletes the
instance record.
I assume this bug (captured as
https://bugs.launchpad.net/nova/+bug/1226049 ) was introduced as part
of the change to the object model (we
Agree this is covered by that fix - I think it was a problem in
stacktach that made me think it wasn't
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nov
** Changed in: nova
Status: Incomplete => 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/1161473
Title:
API to add instance to a SecGroup should take ID n
The example you used was passing in a security group ID (which will
always be unique), but the create call allows either a name or an ID to
be passed in. In he case of a name being used then the bug is still
valid.
** Changed in: nova
Status: Invalid => Confirmed
--
You received this bug
Thanks Bill for offering to pick this up - I agree that this should be
fixed.
** Changed in: nova
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchp
Marking this back to New because I simply don't agree with the above
analysis.
Personally I doubt if the intention of the forcehost capability was to
allow an invalid AZ name by design, - but if there really is a need to
be able to specify an invalid AZ name when forcing to a particular host
(a p
https://review.openstack.org/#/c/21529/
** This bug is no longer a duplicate of bug 1122316
Restarting nova-compute with source groups lead to traceback.
** Changed in: nova
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
E
https://review.openstack.org/#/c/20919/
** Changed in: nova
Status: In Progress => Fix Released
--
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/498
Title:
ins
44 matches
Mail list logo
