Public bug reported:
http://docs.openstack.org/contributor-guide/docs-builds.html does not
document the source of the networking guide (http://docs.openstack.org
/networking-guide/).
In fact, the contributor guide does not even document its own source ---
which is why I am opening this bug in
Public bug reported:
http://docs.openstack.org/networking-guide/scenario_legacy_ovs.html
includes a warning that
"Proper operation of this scenario requires Open vSwitch 2.1 or newer"
--- but does not explain what part of the scenario requires that.
** Affects: neutron
Importance:
Public bug reported:
The current filter scheduler handles the scheduling of a homogenous
batch of N instances with a loop that assumes that a host ruled out in
one iteration can not be desirable in a later iteration --- but that is
a false assumption.
Consider the case of a filter whose purpose
Public bug reported:
I have a Heat template with an output like this:
pool_ip_address:
value: {get_attr: [pool, vip, address]}
description: The IP address of the load balancing pool
For that output, the value shows up in command line output (`heat stack-
show`) but in the dashboard
Public bug reported:
`cat X | nova keypair-add K` produces a different result from `nova
keypair-add --pub-key X K`.
The latter takes the contents of X as the public key; the former does
not.
For example:
ubuntu@mjs-dstk-623b:~$ cat bar.pub | nova keypair-add bar_stdin
-BEGIN RSA PRIVATE
Those two commands used to produce the same result. They have diverged
only recently.
Sorry about the wrong project identification; will remove the wrong one.
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Removed DevStack and Heat from the affected projects list based on
Steve's affirmation that things outside Nova are working as expected.
** No longer affects: devstack
** No longer affects: heat
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Summary changed:
- OS::Heat::AutoScalingGroup scale up fails to find networks
+ publicly-visible nova network not always visible
** No longer affects: heat
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
** Also affects: devstack
Importance: Undecided
Status: New
** Summary changed:
- publicly-visible nova network not always visible
+ The One And Only network is variously visible
** Also affects: heat
Importance: Undecided
Status: New
--
You received this bug notification
Assuming that when a nova network's project_id field in the database is
null this means the network is public, I would think the bug is in
Nova's nova/network/api.py, where class API has the following method:
wrap_check_policy
def get_all(self, context):
Get all the networks.
Public bug reported:
The API for creating an instance does not support idempotent usage.
** Affects: nova
Importance: Undecided
Status: New
** Tags: api conductor
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
Using DevStack, with a pretty plain local.conf, to install OpenStack
into a VM made from http://cloud-images.ubuntu.com/saucy/20140326/saucy-
server-cloudimg-amd64-disk1.img - the launch of keystone fails, ending
with this complaint:
dbus.exceptions.DBusException:
Public bug reported:
While chasing down some errors I found the first one was the following,
found in the log from the Nova API process.
2014-03-06 22:17:41.713 ERROR nova.api.openstack
[req-0a2e7b6b-8ea8-48f1-b6c9-4c6a20ba27b4 admin admin] Caught error:
AmbiguousEndpoints: [{u'url':
Marking the heat side of this as invalid, as I think this is what Steve
is saying.
** Changed in: heat
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
Public bug reported:
The fix to https://bugs.launchpad.net/devstack/+bug/1203680 is useless
unless people know to set the new variable when doing a DevStack
install. The DevStack documentation should be updated to mention this,
as should the various places that describe how to do unit testing.
Public bug reported:
http://docs.openstack.org/developer/nova/devref/unit_tests.html#running-
the-tests says to use run_tests.sh;
https://github.com/openstack/nova/blob/master/HACKING.rst says to use
tox.
** Affects: nova
Importance: Undecided
Status: New
** Tags: documentation
Public bug reported:
Horizon can be configured to ask for an admin password to inject when
instantiating an image, or not. But it is not that simple. Whether
password injection will actually happen also depends on nova
configuration and the image being instantiated. The bug is that Horizon
is
.
** Affects: nova
Importance: Undecided
Assignee: Mike Spreitzer (mike-spreitzer)
Status: In Progress
** Tags: documentation low-hanging-fruit
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova
Public bug reported:
nova/doc/README.rst describes how to build the nova developer
documentation but omits mention of oslo.sphinx. The doc build requires
oslo.sphinx, but oslo.sphinx is not included in requirements.txt
(because oslo.sphinx is not needed to run nova). It suffices to pip
install
19 matches
Mail list logo
