Public bug reported:
post jobs cannot use zuul-cloner and have no access currently to upper-
constraints. See how nova or neutron itself handle this.
Right now the sync with translations fails:
https://jenkins.openstack.org/job/neutron-fwaas-propose-translation-
update/119/console
Please fix ve
Similar failures in other repos:
Networking-ovn:
https://jenkins.openstack.org/job/networking-ovn-propose-translation-update/130/console
neutron-vpnaas:
https://jenkins.openstack.org/job/neutron-vpnaas-propose-translation-update/119/console
neutron-lbaas:
https://jenkins.openstack.org/job/neutro
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
Public bug reported:
We've seen an effect where setting the dfefault token handler to Fenet,
and depending on Revocation events breaks several tests. These tests
are supposed to track that a tokne comes back as invalid. However, what
actually happens is the admin users token is invalid, returnin
Nope. Not going to expose this just for testing. Use direct database
access if you want.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https:
Reviewed: https://review.openstack.org/292612
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=181cab5dc4ae8a00ac2125e455f12bdd2a62d357
Submitter: Jenkins
Branch:master
commit 181cab5dc4ae8a00ac2125e455f12bdd2a62d357
Author: jichenjc
Date: Thu Feb 25 20:51:06 2016 +0800
Reviewed: https://review.openstack.org/299715
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=f738483e843fc27379b85c5401859ccc854adc5e
Submitter: Jenkins
Branch:master
commit f738483e843fc27379b85c5401859ccc854adc5e
Author: Matt Riedemann
Date: Wed Mar 30 22:07:47 2016
Public bug reported:
Docs state this is a feature for customization:
https://github.com/openstack/horizon/blob/master/doc/source/topics/settings.rst#create_instance_flavor_sort
It looks like new launch instance has removed the usage of this sort function?
Perhaps this would be easy to add bac
Public bug reported:
when i removed the symlink in the maas ephemeral image from
/etc/network/interfaces
the iscsi root boot fails, and maas deployment would also fail.
** Affects: cloud-init
Importance: Undecided
Status: New
** Affects: maas-images
Importance: Undecided
** Project changed: python-neutronclient => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1567271
Title:
The error log has appeared, but the status of the agent is displayed
You have been subscribed to a public bug:
* High level description:
I suggest that updating the status of the agent upon detecting error
logs.
I understand that "neutron agent-list " output means only whether the agent is
running.
However, by changing the display if the agent is not working pro
** Changed in: fuel/mitaka
Importance: Undecided => Low
** Changed in: fuel/mitaka
Status: New => In Progress
** Changed in: fuel/mitaka
Milestone: None => 9.0
** Changed in: fuel/mitaka
Assignee: (unassigned) => LiuNanke (nanke-liu)
** Changed in: fuel/newton
Milestone:
** Project changed: openstack-manuals => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1568332
Title:
Release Notes for Mitaka release of Neutron has incomplete text on
get-me
You have been subscribed to a public bug:
Bug is written on current content of
http://docs.openstack.org/releasenotes/neutron/mitaka.html
Following is stated (replacing bullets with hyphens:
"-An L3 agent is assigned to an availability zone; the router will be hosted by
the L3 agent with availab
Reviewed: https://review.openstack.org/294395
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=9399680106b4448c975b87a8b93f2188157a42ce
Submitter: Jenkins
Branch:master
commit 9399680106b4448c975b87a8b93f2188157a42ce
Author: Kenji Ishii
Date: Fri Mar 18 14:37:13 2016
** No longer affects: ironic-python-agent
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to anvil.
https://bugs.launchpad.net/bugs/1268480
Title:
assertTrue(isinstance()) in tests should be replace with
assertIsInstance()
Statu
Reviewed: https://review.openstack.org/295964
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=ac78a486d91dc9053c375ca681279c46d0d2b676
Submitter: Jenkins
Branch:master
commit ac78a486d91dc9053c375ca681279c46d0d2b676
Author: Luis Daniel Castellanos
Date: Tue Mar 22 1
Reviewed: https://review.openstack.org/300214
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=f65ff0fe912ba04f052aeff70eb26a6bdede5838
Submitter: Jenkins
Branch:master
commit f65ff0fe912ba04f052aeff70eb26a6bdede5838
Author: Ying Zuo
Date: Thu Mar 31 13:58:56 2016 -0
This bug tracker is just for upstream Horizon development; packaged
versions should have bugs raised in their own trackers or with the
packager directly.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
** Changed in: neutron
Status: New => 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/1568461
Title:
Failure in q-sriov-agt => Version 1.1 of QosBandwidthLimitRule is not
Public bug reported:
I tried to create Qos-Policy and BW-Rule-Limit with the following:
1) Create Qos Policy
# neutron qos-policy-create Rate_Limit_Policy_1
# neutron qos-policy-create Rate_Limit_Policy_2
2) Create Qos Rule (BW Limit Type) and Attach to Qos Policy
# neutron qos-bandwidth-limit
22 matches
Mail list logo
