This bug goes deep down the rabbit-hole. All the way deep inside heat,
as it turns out, where the actual bug is. Will move this activity over
there.
** Changed in: horizon
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
*** This bug is a duplicate of bug 1285504 ***
https://bugs.launchpad.net/bugs/1285504
** This bug has been marked a duplicate of bug 1285504
lbaas add vip should allow vip from a different subnet
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Marking invalid since this is already being tracked via the above
blueprint
** 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).
Public bug reported:
The logic of _modify_rules() seems not correct. For instance, assuming
that we have a in-memory table like this:
:bn-chain001 - [0:0]
:chain002 - [0:0]
[0:0] -A bn-chain001 rule001
[0:0] -A chain002 rule002
and iptables-save output like this:
# Generated by zhaoqin on mars
Public bug reported:
I am creating a VM snapshot using nova CLI -
Set of operations and error are as below -
1. nova cli help ===
[raies@localhost cli_services]$ nova help image-create
usage: nova image-create [--show] [--poll] server name
Create a new image by taking a snapshot of a running
Public bug reported:
In the services.l3_router.L3RouterPlugin.create_floatingip(), we have
some comments (docstring) to help us to know this function, but there
are some nits inside them:
:param floatingip: data fo the floating IP being created
:returns: A floating IP object on success
AS
Public bug reported:
Missing call to function unicode for some update status messages in the object
storage pages.
This prevents some messages from being translated.
** Affects: horizon
Importance: Undecided
Assignee: Ambroise CHRISTEA (ambroise-christea)
Status: New
**
Public bug reported:
From VCenter driver, with compute node configured to be cluster01. And
VCenter IP is 10.9.1.43
But with hypervisor show command, it will display the host IP for the
controller node. It should be pointing to
the really VCenter IP.
[root@dhcp-10-9-3-83 ~]# nova
Public bug reported:
I am using devstack development environment.
my localrc file is as -
ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta
DEST=/opt/stack
disable_service n-net
enable_service tempest
API_RATE_LIMIT=False
VOLUME_BACKING_FILE_SIZE=4G
VIRT_DRIVER=libvirt
SWIFT_REPLICAS=1
export
There is a problem with version of alembic. With alembic=0.6.4 for all
plugins heal script worked normal. I tested locally and I got such error
only with alembic versions 0.6.2 and older. Global requirements already
updated with alembic=0.6.4. So the problem should get fixed with
alembic version
The bug is not invalid, it will be fixed by the blueprint but it's still
valid
** Changed in: horizon
Status: Invalid = New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
** Project changed: nova = openstack-api-site
** Description changed:
when I give a specified tenant access to the specified private flavor, I
use it like this :
POST /v2/{tenant_id}/flavors/{flavor_id}/action
{
addTenantAccess: {
tenant: fake_tenant
}
}
Public bug reported:
When the user have to see the floating IP association they can view it
under Access and Security - Floating IPs tab.
But when a floating IP is associated with virtual IP of the load
balancer, under Floating IPs tab - Instance column , only '-' is
displayed. If we click on
I can't seem to run nova --all flavor-list or nova --extra-specs
flavor-list either
** Changed in: nova
Status: New = Confirmed
** Changed in: nova
Importance: Undecided = High
** Also affects: python-novaclient
Importance: Undecided
Status: New
** Changed in:
Public bug reported:
When listing role assignments, we have the option to filter them by actor,
target and role.
As Henry Nash pointed out at [1] , the current implementation uses the standard
filtering the V3.wrap_collection. Given the large number of individual
assignments, this is pretty
Public bug reported:
Hello dear OpenStack dashboard folk:
Pagination info at top and bottom of any horizon table. For instance, by
default, you typically limit table size to 20 but only display that
there are more than 20 returned entities at the bottom of a page. GOOD
UX DESIGN PRINCIPLES
Public bug reported:
The default returned search order in the Admin panel for Users and
Projects return them in id order, not name order. The ID order is, by
design, opaque and useless so it is tantamount to idiocy to use that as
the default sort order. (It's like saying, Return things in random
Public bug reported:
Based on conversation in IRC 20 Aug 2014 our browser support is:
latest firefox, latest chrome, IE 9+ with some lower priority support for
latest safari, and latest opera.
Maybe this could be restated as
Horizon is primarily tested and supported on the latest version of
** Changed in: ossa
Status: Fix Committed = Fix Released
--
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/1349491
Title:
[OSSA 2014-027] Persistent XSS in the
*** This bug is a duplicate of bug 1291489 ***
https://bugs.launchpad.net/bugs/1291489
It was originally reported against Havana. I would agree that the patch
and the backport should fix the issue, so I'll close this BZ. Thanks,
cyeoh for spotting this (and lcostantino for fixing :)).
**
Public bug reported:
DVR routers have specific rules regarding when and where the placement
of the namespaces (SNAT and IR namespaces) occur, therefore auto-placing
based routers should be avoided as it may conflict with these.
We should also document inline what these rules are.
** Affects:
Public bug reported:
Hit the following exception:
2014-07-23 04:31:08.206 4449 ERROR keystone.common.wsgi [-] 'group_id'
2014-07-23 04:31:08.206 4449 TRACE keystone.common.wsgi Traceback (most recent
call last):
2014-07-23 04:31:08.206 4449 TRACE keystone.common.wsgi File
Public bug reported:
We are getting common JShint errors. Example link below:
http://logs.openstack.org/88/115588/1/check/gate-horizon-jshint/760a733/console.html
http://logs.openstack.org/78/109278/18/check/gate-horizon-jshint/9883c1a/console.html
Public bug reported:
This is regarding a tempest run on a Keystone change, here's the log:
http://logs.openstack.org/73/111573/3/check/check-tempest-dsvm-full/f4e3313/console.html
All the tempest tests ran successfully. Then it runs the log checker and
there are several errors in the logs.
-
Public bug reported:
When the Arista ML2 driver registers itself with Arista EOS, it sends
the admin credentials to EOS. But it does not send the admin tenant name
which causes keystone authentication to fail.
** Affects: neutron
Importance: Undecided
Status: New
--
You received
Public bug reported:
RPC is versioned per feature, but all of callback classes are implemented as
mixin classes
and they are inherited into a single class.
This prevents RPC callback class from versioning properly.
This kind of chaos leads to bugs like bug 1353309.
This bug focuses on fixes of
Public bug reported:
In the compute manager's 'retry' logic (i.e., handling
RescheduledException) in _build_and_run_instance, it has a catch-all
case for all exceptions and sets reason=str(e). This works well in most
cases, but for cases in which lower level code may generate locale-
specific
Public bug reported:
This commit added some new default flags for migration in the libvirt
driver:
https://github.com/openstack/nova/commit/26504d71ceaecf22f135d8321769db801290c405
However those new flags weren't added to
nova.tests.virt.libvirt.fakelibvirt, so if you're not running with a
real
Public bug reported:
yaguang@yaguang-ThinkPad-X230:~$ keystone --os-token beyond630 --os-endpoint
http://localhost:35357/v2.0 role-delete 1c8551ebd5e341d7888fa2b31ce592eb
An unexpected error prevented the server from fulfilling your request: 'utf8'
codec can't decode byte 0xfb in position 2:
Public bug reported:
There is a race condition in linux_net.get_dhcp_opts when
use_single_default_gateway is set. Because it makes multiple queries, if
an instance is deleted while iterating through the list of fixed ips, it
can cause an exception like the following:
2014-08-20 19:44:31.371
** Changed in: python-neutronclient
Status: Fix Committed = Fix Released
--
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/1296148
Title:
neutronclient should
** Changed in: python-neutronclient
Status: Fix Committed = 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/1297309
Title:
Unauthorized: Unknown auth
** Changed in: python-neutronclient
Status: Fix Committed = 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/1335733
Title:
Failed to boot instance
** Changed in: python-neutronclient
Status: Fix Committed = 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/1241275
Title:
Nova / Neutron Client
The update link is actually: http://docs.openstack.org/trunk/config-
reference/content/vmware.html#VMwareVCDriver_details
** 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
I tried this case in the latest Juno master, I find it's ok now
linux:˜/source glance image-create
Public bug reported:
The following steps happen in the same host machine.
1. tenant1 create vm1 with network net1 and ip 199.168.1.2
2. tenant1 create vm2 with network net1 and ip 199.168.1.4
3. configure security group of vm1 and vm2 so they can communicate with tcp
connetion
4. tenant2 create
37 matches
Mail list logo
