** Changed in: python-openstackclient
Status: New => Incomplete
** Changed in: python-openstackclient
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
** Changed in: openstack-i18n
Status: Incomplete => 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/1371447
Title:
German translation is quite
Public bug reported:
Hi,
I am using OS R Juno on Linux, When creating a VM attached to internal network
there is no problem at all., when attaching the VM to the external network i
see "No valid host was found" , the int and tun bridges between neutron and
compute node are fine, the dhcp
we've been setting the default volume api version 2 since 1.7.0, we're
at 1.9.0 now. marking this as fix released for openstackclient, see
commit: https://github.com/openstack/python-
openstackclient/commit/f14251669f96d6010581702417828f4380144aa2
** Changed in: python-openstackclient
Public bug reported:
The following exception appears in Nova's compute log when booting an
instance with the config parameter max_concurrent_builds set to 0:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/queue.py", line 117, in
switch
Fix proposed to branch: master
Review: https://review.openstack.org/250869
** Changed in: horizon
Status: Won't Fix => In Progress
** Changed in: horizon
Assignee: (unassigned) => Paul Karikh (pkarikh)
--
You received this bug notification because you are a member of Yahoo!
** No longer affects: keystone
** Summary changed:
- The test_update_user_password in tempest.api.identity.admin.v3.test_users
fails with 'Object not found' error
+ [tempest] test_update_user_password in
tempest.api.identity.admin.v3.test_users fails with 'Object not found' error
** Project
** Summary changed:
- The test_rescope_token in tempest.api.identity.admin.v3.test_tokens fails
with AssertionError
+ [tempest] test_rescope_token in tempest.api.identity.admin.v3.test_tokens
fails with AssertionError
** No longer affects: keystone
** Project changed: tempest => mos
**
Public bug reported:
Release: Kilo
I have the 'new' launch instance dialog. After I clicked the launch
instance button it takes a while to get the response, during this time
it is possible to click the button again and another request will be
triggered (resulting in multiple instances being
Yes. as discussed - that is to be expected. Closing the bug for now.
Feel free to reopen if you feel it needs more looking into.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
A watchful reviewer may notice that sometimes
test_dashboard_help_redirection fails. Initially I thought that it was
caught by an increased network timeout from Jenkins worker node to
docs.openstack.org site. So I made a patch
Public bug reported:
I installed latest Devstack, but got below error when tried to open
network topology on Dashboard. Anyone met this issue? or is this a
devstack build bug?
TypeError at /project/network_topology/
Client() got multiple values for keyword argument 'api_version'
Request Method:
You have been subscribed to a public bug:
Hi,
I am using OS R Juno on Linux, When creating a VM attached to internal network
there is no problem at all., when attaching the VM to the external network i
see "No valid host was found" , the int and tun bridges between neutron and
compute node
Public bug reported:
https://review.openstack.org/204206
\Dear bug triager. This bug was created since a commit was marked with
DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1452066
Title:
neutron-db-manage fails using mariadb fresh deployment
Status
I don't understand how this bug is related to neutron, this error is
raised in Horizon and according the stacktrace the error is raised more
precisely when using manila-ui or manilaclient ... it seems you are
mixing incorrect horizon/manila-ui/manilaclient version
** Changed in: neutron
Public bug reported:
While creating user using keystone command with password option, it does
not check if user entered any character for password or not.
steps:
$ keystone user-create --name testing --pass
New Password:
Repeat New Password:
+--+--+
|
Unless there are other details, this is working as designed. If you
don't specify security groups, you get the default security group rules
(which could be empty for your tenant if not configured yet).
Are you using neutron or nova-network? There are issues when using
neutron and a neutron
Public bug reported:
neutron/tests/functional/db/test_ipam.py:41: OsloDBDeprecationWarning:
EngineFacade is deprecated; please use oslo_db.sqlalchemy.enginefacade
** Affects: neutron
Importance: Low
Status: New
** Tags: db low-hanging-fruit
** Tags added: db
** Changed in:
Public bug reported:
If you have an instance with 2 interfaces, and one of them has no IP (e.g. is
L2 only), then
list_target_id_by_instance() fails when you disassociate a floating-ip from the
first interface.
This patch resolves.
index 1478a6f..a026b15 100644
---
Public bug reported:
Commit [1] disables ipv6 on linuxbridges. On my linuxbridge vlan system,
this fix causes the code ensure_bridge() to return too early without
passing the bridge_name back.
The introduced method returns the output of the systcl -w call
+def disable_ipv6(self):
+
Public bug reported:
The subject's test fails with the trace given below:
tempest.api.identity.admin.v3.test_tokens.TokensV3TestJSON
test_rescope_token[id-565fa210-1da1-4563-999b-f7b5b67cf112]
traceback
Traceback (most recent call last):
File
Public bug reported:
The subject's test fails with the trace given below:
test_update_user_password[id-2d223a0e-e457-4a70-9fb1-febe027a0ff9]
traceback
Traceback (most recent call last):
File
"/home/developer/mos-tempest-runner/tempest/tempest/api/identity/admin/v3/test_users.py",
line 83, in
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** Changed in: python-neutronclient
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Release: Kilo
Given my token is scoped to project A
and I am project admin in project B
I go to Identity > Projects > Edit Project B
I click 'Save'
I get the error: 'Quota value(s) cannot be less than the current usage
value(s):...' for volume usages
The problem is:
Public bug reported:
While clicking sytem Information in the Horizon Dashboard, there are some tabs
like Network Agents and Orchestration Services.
We have inconsistency in the colmun Last Updated and Status in the
Orchestration Services tab.
The last column should be Last Updated and not
With keystonemiddleware 1.5.3 tagged, this will be included
automatically with the next tagged releases of OpenStack-Ansible.
Verified in Kilo with a recent build result:
http://logs.openstack.org/57/248557/2/gate/gate-openstack-ansible-dsvm-commit/de13bfd/console.html#_2015-11-26_15_30_45_573
** Also affects: openstack-ansible/liberty
Importance: Undecided
Status: New
** Also affects: openstack-ansible/kilo
Importance: Undecided
Status: New
** Also affects: openstack-ansible/trunk
Importance: High
Assignee: Jesse Pretorius (jesse-pretorius)
Status:
Public bug reported:
http://git.openstack.org/cgit/openstack/neutron/commit/?id=5d38dc5 added
the "garp_master_repeat 5" and "garp_master_refresh 10". This badly
breaks networking to the point where it is completely unsuable:
First of all, this setting causes Keepalived to constantly spam five
Hello Hirofumi, there was a change in the way DocImpact flag workflow,
see here [1]. Now the bugs generated by the DocImpact flag are assigned
to the Neutron team instead of the doc team as it was before. Since you
are the author of the patch with the DocImpact flag would you mind
taking care of
30 matches
Mail list logo
