[Yahoo-eng-team] [Bug 1791178] Re: pep8 tests failing on "./tools/coding-checks.sh --pylint"
Reviewed: https://review.openstack.org/602097 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=db7e19d2ba3fcde0510be0094a4851178fae578b Submitter: Zuul Branch:master commit db7e19d2ba3fcde0510be0094a4851178fae578b Author: Brian Haley Date: Wed Sep 12 10:54:47 2018 -0600 Fix pylint warning with eventlet > 0.22.0 When eventlet was bumped up to 0.24.1 in upper-constraints [1] it started generating a pylint warning, since neutron has support for older versions such as 0.22.0 that take a different number of arguments. Just silence the warning. Also, in order to get this through the gate, the neutron-grenade-dvr-multinode check job is being temporarily set to non-voting and removed from the gate. That change should be reverted as soon as we fix bug 1791989. [1] https://review.openstack.org/#/c/589382/ Change-Id: I169ecb6f33b670c5469919214a32645cd9eda206 Closes-Bug: #1791178 Related-Bug: #1791989 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1791178 Title: pep8 tests failing on "./tools/coding-checks.sh --pylint" Status in neutron: Fix Released Bug description: Example of failure: http://logs.openstack.org/37/382037/73/gate /openstack-tox-pep8/7f200e6/job- output.txt.gz#_2018-09-06_17_48_34_700485 Paste version of the above error message: http://paste.openstack.org/show/729981/ It is probably because of new eventlet = 0.24.0 used now. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1791178/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1792047] Re: keystone rbacenforcer not populating policy dict with view args
Reviewed: https://review.openstack.org/601875 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=4975b79e8174587f7639347939cf679460d4896b Submitter: Zuul Branch:master commit 4975b79e8174587f7639347939cf679460d4896b Author: morgan fainberg Date: Tue Sep 11 16:03:54 2018 -0700 Ensure view args is in policy dict The policy_dict (in enforcement) was not populating the view args in a similar manner to the old style @protected decorator. This change ensures that we mirror the old behavior (required for proper use of v3cloud policy). Change-Id: Ida9009a95a874be9cc60c3152d4e3225726562eb Partial-Bug: #1776504 Closes-Bug: #1792047 ** Changed in: keystone Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1792047 Title: keystone rbacenforcer not populating policy dict with view args Status in OpenStack Identity (keystone): Fix Released Status in OpenStack Identity (keystone) rocky series: In Progress Status in OpenStack Identity (keystone) stein series: Fix Released Bug description: The old @protected decorator pushed the view arguments into the policy_dict for enforcement purposes[0]. This was missed in the new RBACEnforcer. [0] https://github.com/openstack/keystone/blob/294ca38554bb229f66a772e7dba35a5b08a36b20/keystone/common/authorization.py#L152 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1792047/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1784006] Re: Instances miss neutron QoS on their ports after unrescue and soft reboot
** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1784006 Title: Instances miss neutron QoS on their ports after unrescue and soft reboot Status in neutron: Confirmed Bug description: Instances lose neutron QoS on their ports after unrescue and soft reboot Description === After some operations with instance: such as unrescue and soft reboot libvirt domains are created, but neutron doesn't set QoS on ports for VM. So user can avoid QoS per-port limitation and utilise all hosts bandwidth. This doesn't happen after live migration, migration, hard reboot, rescue, shutdown with start. This problem doesn't happen for operations which ends up calling _create_domain_and_network(): https://github.com/openstack/nova/blob/stable/pike/nova/virt/libvirt/driver.py#L5392 In unrescue and soft reboot libvirt driver calls _create_domain() directly and don't execute plug_vifs(): https://github.com/openstack/nova/blob/stable/pike/nova/virt/libvirt/driver.py#L2547 Steps to reproduce == 1. Create instance with port in neutron network 2. Create QoS in neutron: $ neutron qos-policy-create limited_1000mbps $ neutron qos-bandwidth-limit-rule-create limited_1000mbps --max-kbps 100 --max-burst-kbps 16 3. Update port of the instance, assign policy: $ neutron port-update --qos-policy limited_1000mbps PORT_UUID 4. Ensure, that QoS rule is applied to the port: $ /sbin/tc -s qdisc show dev tap47eaf544-39 qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 383621004 bytes 262469 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 qdisc ingress : parent :fff1 Sent 173850 bytes 1515 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 5. 1) Execute nova rescue and then nova unrescue for the instance or 2) Execute nova reboot (without parameter --hard) 6. See, that after tap interface recreation during libvirt domain start QoS are gone: $ /sbin/tc -s qdisc show dev tap47eaf544-39 qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 1537 bytes 19 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 Expected result === QoS rules are applied to the port, like in step 4. Actual result = QoS rules are gone, tap interface is not limited: $ /sbin/tc -s qdisc show dev tap47eaf544-39 qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 1537 bytes 19 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 Environment === 1. Exact version of OpenStack: OpenStack Pike nova 16.1.4 neutron 11.0.5 2. Which networking type did you use? Neutron with Open vSwitch To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1784006/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1784713] Re: cloud-init profile.d files use bash-specific builtin "local"
** Changed in: cloud-init (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1784713 Title: cloud-init profile.d files use bash-specific builtin "local" Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Bug description: /etc/profile, which is read by the Bourne-like shells (including ksh), runs the scripts in /etc/profile.d. The scripts from the cloud-init package Z99-cloudinit-warnings.sh and Z99-cloud-locale-test.sh use the bash-builtin "local" which is not recognized by ksh resulting in these errors at login: /etc/profile[23]: .[141]: local: not found [No such file or directory] /etc/profile[23]: .[142]: local: not found [No such file or directory] /etc/profile[23]: .[143]: local: not found [No such file or directory] /etc/profile[23]: .[178]: local: not found [No such file or directory] /etc/profile[23]: .[179]: local: not found [No such file or directory] $ grep -n local\ Z99* Z99-cloudinit-warnings.sh:7:local warning="" idir="/var/lib/cloud/instance" n=0 Z99-cloudinit-warnings.sh:8:local warndir="$idir/warnings" Z99-cloudinit-warnings.sh:9:local ufile="$HOME/.cloud-warnings.skip" sfile="$warndir/.skip" Z99-cloud-locale-test.sh:14:local bad_names="" bad_lcs="" key="" val="" var="" vars="" bad_kv="" Z99-cloud-locale-test.sh:15:local w1 w2 w3 w4 remain Z99-cloud-locale-test.sh:56:local bad invalid="" to_gen="" sfile="/usr/share/i18n/SUPPORTED" Z99-cloud-locale-test.sh:57:local pkgs="" Z99-cloud-locale-test.sh:70:local pkgs="" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cloud-init 18.2-27-g6ef92c98-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CloudName: Other Date: Tue Jul 31 20:04:30 2018 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/ksh SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1784713/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1766401] Re: full config file wiped after apt-upgrade issued
** Changed in: cloud-init (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1766401 Title: full config file wiped after apt-upgrade issued Status in cloud-images: New Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Artful: Fix Released Status in cloud-init source package in Bionic: Fix Released Status in cloud-init source package in Cosmic: Fix Released Bug description: === Begin SRU Template === [Impact] Upgrades of cloud-init on official Ubuntu 16.04 and 17.10 images running on IBM public cloud will be unreachable after a reboot. This is because cloud-init incorrectly recognizes the newly added 'IBMCloud' as the datasource to use and skips use of the previously used ConfigDrive or NoCloud datasource. This is because a.) Official 16.04 and 17.10 images of Ubuntu have seeded data in their /var/lib/cloud/seed/ directory that was used on first boot and should be continued to be used. b.) IBMCloud's datasource in some scenarios appears looks similar to that of Config Drive. The version of cloud-init in xenial and artful checks to disable config-drive in order to identify the IBMCloud datasource. That should not happen unless the IBMCloud datasource is enabled, which is configured off in those images. The fix is to continue using the existing datasource on those images. [Test Case] * Launch an image on IBM public cloud. * add -proposed * apt-get update && apt-get install cloud-init * reboot * ssh back in If you are able to ssh back in, then this bug has been fixed. [Regression Potential] This specific fix is tightly contained down the path involved in IBM cloud. The most likely failure scenario would be failure in 18.04 images which do not have the additional datasources built into the images. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11172924 === End SRU Template === file: 50-cloud-init.cfg wiped of it's initial (working) configuration after a standard apt-upgrade was issued. Cloud provider is SoftLayer. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1766401/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1767131] Re: Pre-seeded snaps are not necessarily available for use in cloud-init user-data
** Changed in: cloud-init (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: cloud-init (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1767131 Title: Pre-seeded snaps are not necessarily available for use in cloud-init user-data Status in cloud-images: New Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Fix Released Bug description: With some cloud software being moved to snaps, cloud-init needs to ensure that snaps have been preseeded before user scripts are run, as those user scripts may rely on the software within the snap being available for use. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1767131/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1792157] Re: cloud-init uses openstack latest version due to decoding bug
** Changed in: cloud-init (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Status: Confirmed => Fix Committed ** Changed in: cloud-init (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1792157 Title: cloud-init uses openstack latest version due to decoding bug Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: In Progress Bug description: Line like this in the log shows the issue: 2018-09-12 10:36:25,462 - openstack.py[DEBUG]: Selected version 'latest' from [b'2012-08-10', b'2013-04-04', b'2013-10-17', b'2015-10-15', b'2016-06-30', b'2016-10-06', b'latest'] we're looking for a string in a list of bytes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cloud-init 18.3-38-gd47d404e-0ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CloudName: OpenStack Date: Wed Sep 12 14:15:16 2018 Ec2AMI: ami-0131 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1792157/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1771198] Re: Support disable_root-esque behaviour for other users
** Changed in: cloud-init Status: Triaged => Fix Released ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu Cosmic) Assignee: (unassigned) => Chad Smith (chad.smith) ** Changed in: cloud-init (Ubuntu Bionic) Status: New => Triaged ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Triaged ** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/354496 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1771198 Title: Support disable_root-esque behaviour for other users Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Triaged Status in cloud-init source package in Bionic: Triaged Status in cloud-init source package in Cosmic: Fix Released Bug description: When building Ubuntu cloud images, we prefer to name the default user "ubuntu" where possible, to maintain a consistent user experience between substrates. Some clouds, however, like to have a consistent user name across all of their various image offerings. This is an inherent conflict. One way in which we have agreed to resolve this is to use the messaging that the disable_root behaviour currently provides on the cloud-specific user, to point to the ubuntu user. This means, at least, that users are given some direction (rather than being left wondering if their instance has provisioned correctly, or if their SSH keys are invalid, or ) I propose a new cloud.cfg key named "ssh_disable_users" which defines a list of users. For each of these users, cloud-init will ensure they exist, and configure the system so that users SSH'ing to that user will be redirected to the default user (a la disable_root behaviour currently). (`disable_root: True` would translate as `ssh_disable_users: ["root"]`.) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1771198/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1779801] Re: L3 AttributeError in doc job
The issue happens due to the confusion around zuul v3 migration. The situation has changed since then according to the mailing list discussion. python packages are installed based on requirements.txt of the project now, so appropriate dependencies of your project should be declared in requirements.txt in your project. For example, neutron-vpnaas declares neutron 13.0.0.0b2 (rocky-2) [1]. Considering the above, there is nothing to do in the neutron side. I am marking this bug as Invalid (in neutron). [1] https://github.com/openstack/neutron- vpnaas/blob/1e98d017adf3d559c8b4d27770fa97a2db48a78a/requirements.txt#L23 ** Changed in: neutron Status: Triaged => Invalid ** Changed in: neutron Assignee: (unassigned) => Akihiro Motoki (amotoki) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1779801 Title: L3 AttributeError in doc job Status in networking-cisco: Triaged Status in networking-midonet: In Progress Status in networking-odl: Confirmed Status in neutron: Invalid Bug description: e.g http://logs.openstack.org/87/199387/116/check/build-openstack- sphinx-docs/a509328/job-output.txt.gz 2018-07-03 01:03:26.111244 | ubuntu-xenial | Warning, treated as error: 2018-07-03 01:03:26.111548 | ubuntu-xenial | autodoc: failed to import module u'midonet.neutron.db.bgp_db_midonet'; the following exception was raised: 2018-07-03 01:03:26.111691 | ubuntu-xenial | Traceback (most recent call last): 2018-07-03 01:03:26.112024 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/sphinx/ext/autodoc/importer.py", line 152, in import_module 2018-07-03 01:03:26.112140 | ubuntu-xenial | __import__(modname) 2018-07-03 01:03:26.112514 | ubuntu-xenial | File "/home/zuul/src/git.openstack.org/openstack/networking-midonet/midonet/neutron/db/bgp_db_midonet.py", line 22, in 2018-07-03 01:03:26.112701 | ubuntu-xenial | from neutron_dynamic_routing.db import bgp_db 2018-07-03 01:03:26.113035 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron_dynamic_routing/db/bgp_db.py", line 21, in 2018-07-03 01:03:26.113165 | ubuntu-xenial | from neutron.db import l3_dvr_db 2018-07-03 01:03:26.113413 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py", line 41, in 2018-07-03 01:03:26.113524 | ubuntu-xenial | from neutron.db import l3_db 2018-07-03 01:03:26.113819 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron/db/l3_db.py", line 51, in 2018-07-03 01:03:26.113955 | ubuntu-xenial | from neutron.extensions import l3 2018-07-03 01:03:26.114260 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron/extensions/l3.py", line 23, in 2018-07-03 01:03:26.114405 | ubuntu-xenial | from neutron.api.v2 import resource_helper 2018-07-03 01:03:26.114730 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron/api/v2/resource_helper.py", line 20, in 2018-07-03 01:03:26.114877 | ubuntu-xenial | from neutron.api import extensions 2018-07-03 01:03:26.115169 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron/api/extensions.py", line 32, in 2018-07-03 01:03:26.115336 | ubuntu-xenial | from neutron.plugins.common import constants as const 2018-07-03 01:03:26.115669 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron/plugins/common/constants.py", line 28, in 2018-07-03 01:03:26.115768 | ubuntu-xenial | 'router': constants.L3, 2018-07-03 01:03:26.115894 | ubuntu-xenial | AttributeError: 'module' object has no attribute 'L3' To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1779801/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1780376] Re: Queens neutron broken with recent L3 removal from neutron-lib.constants
There is nothing to do in neutron side. If neutron-lbaas tox job pulls neutron and neutron-lib properly with upper-constraints.txt from the stable/queens branch, the issue has gone. I created a fresh neutron-lbaas tox py27 env (using stable/queens commit ed663f36b0a14202fdff8132c0dd3d353cef6aff) and confirmed the expected version of neutron and neutron-lib are installed. neutron is installed from the latest stable/queens branch and neutron-lib 1.13.0 is the latest queens version. $ .tox/py27/bin/pip freeze | grep neutron -e git+https://git.openstack.org/openstack/neutron@bffdbfe20e47d6f27cea8d26121e2c1eccba7e9f#egg=neutron -e git+https://git.openstack.org//openstack/neutron-lbaas@ed663f36b0a14202fdff8132c0dd3d353cef6aff#egg=neutron_lbaas neutron-lib==1.13.0 python-neutronclient==6.7.0 ** Changed in: neutron Status: Confirmed => Invalid ** Changed in: neutron Importance: Medium => Undecided -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1780376 Title: Queens neutron broken with recent L3 removal from neutron- lib.constants Status in neutron: Invalid Status in OpenStack Global Requirements: Fix Released Bug description: This patch: https://github.com/openstack/neutron- lib/commit/ec829f9384547864aebb56390da8e17df7051aac breaks neutron in the current global requirements setup. Current GR with the new versioning pulls queens neutron and the 1.17.0 neutron-lib. Since L3 was removed from neutron-lib.constants, queens neutron fails on the reference neutron/plugins/common/constants.py I'm not sure if L3 should be put back, queens neutron patched, or the global requirements setup where it's pulling different versions of neutron and neutron-lib needs to be fixed. Steps to reproduce: Checkout neutron-lbaas and run tox -e py27 Zuul seems to be pulling the right versions, local does not due to the GR constraints. Failed to import test module: neutron_lbaas.tests.unit.agent.test_agent Traceback (most recent call last): File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/unittest2/loader.py", line 456, in _find_test_path module = self._get_module_from_name(name) File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/unittest2/loader.py", line 395, in _get_module_from_name __import__(name) File "neutron_lbaas/tests/unit/agent/test_agent.py", line 19, in from neutron_lbaas.agent import agent File "neutron_lbaas/agent/agent.py", line 26, in from neutron_lbaas.agent import agent_manager as manager File "neutron_lbaas/agent/agent_manager.py", line 17, in from neutron.agent import rpc as agent_rpc File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/agent/rpc.py", line 27, in from neutron.agent import resource_cache File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/agent/resource_cache.py", line 20, in from neutron.api.rpc.callbacks.consumer import registry as registry_rpc File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/api/rpc/callbacks/consumer/registry.py", line 15, in from neutron.api.rpc.callbacks import resource_manager File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/api/rpc/callbacks/resource_manager.py", line 21, in from neutron.api.rpc.callbacks import resources File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/api/rpc/callbacks/resources.py", line 15, in from neutron.objects import network File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/objects/network.py", line 21, in from neutron.db.models import segment as segment_model File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/db/models/segment.py", line 24, in from neutron.extensions import segment File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/extensions/segment.py", line 26, in from neutron.api import extensions File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/api/extensions.py", line 32, in from neutron.plugins.common import constants as const File "/home/michjohn/projects/migration/neutron-lbaas/.tox/py27/local/lib/python2.7/site-packages/neutron/plugins/common/constants.py", line 28, in 'router': constants.L3, AttributeError: 'module' object has no attribute 'L3' To manage notifications about this bug go to:
[Yahoo-eng-team] [Bug 1792532] [NEW] can't update image metadata
Public bug reported: Horizon 14.0.0 Glance 17.0.0 Through openstack client everything is fine - i can change properties, but not in Horizon. Here is error from httpd/horizon log: [Fri Sep 14 10:21:53.412709 2018] [:error] [pid 1334] Traceback (most recent call last): [Fri Sep 14 10:21:53.412717 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped [Fri Sep 14 10:21:53.412723 2018] [:error] [pid 1334] data = function(self, request, *args, **kw) [Fri Sep 14 10:21:53.412730 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/glance.py", line 110, in patch [Fri Sep 14 10:21:53.412736 2018] [:error] [pid 1334] **request.DATA['updated'] [Fri Sep 14 10:21:53.412742 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/glance.py", line 564, in image_update_properties [Fri Sep 14 10:21:53.412748 2018] [:error] [pid 1334] **kwargs) [Fri Sep 14 10:21:53.412754 2018] [:error] [pid 1334] File "/usr/lib/python2.7/site-packages/glanceclient/v2/images.py", line 343, in update [Fri Sep 14 10:21:53.412776 2018] [:error] [pid 1334] raise TypeError(encodeutils.exception_to_unicode(e)) [Fri Sep 14 10:21:53.412783 2018] [:error] [pid 1334] TypeError: Unable to set 'os_hidden' to 'False' ** Affects: horizon Importance: Undecided Status: New ** Tags: glance horizon -- 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/1792532 Title: can't update image metadata Status in OpenStack Dashboard (Horizon): New Bug description: Horizon 14.0.0 Glance 17.0.0 Through openstack client everything is fine - i can change properties, but not in Horizon. Here is error from httpd/horizon log: [Fri Sep 14 10:21:53.412709 2018] [:error] [pid 1334] Traceback (most recent call last): [Fri Sep 14 10:21:53.412717 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line 127, in _wrapped [Fri Sep 14 10:21:53.412723 2018] [:error] [pid 1334] data = function(self, request, *args, **kw) [Fri Sep 14 10:21:53.412730 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/rest/glance.py", line 110, in patch [Fri Sep 14 10:21:53.412736 2018] [:error] [pid 1334] **request.DATA['updated'] [Fri Sep 14 10:21:53.412742 2018] [:error] [pid 1334] File "/usr/share/openstack-dashboard/openstack_dashboard/api/glance.py", line 564, in image_update_properties [Fri Sep 14 10:21:53.412748 2018] [:error] [pid 1334] **kwargs) [Fri Sep 14 10:21:53.412754 2018] [:error] [pid 1334] File "/usr/lib/python2.7/site-packages/glanceclient/v2/images.py", line 343, in update [Fri Sep 14 10:21:53.412776 2018] [:error] [pid 1334] raise TypeError(encodeutils.exception_to_unicode(e)) [Fri Sep 14 10:21:53.412783 2018] [:error] [pid 1334] TypeError: Unable to set 'os_hidden' to 'False' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1792532/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1792524] [NEW] Missing role assignment and group of user in the user detail view for admin
Public bug reported: The role assignments and groups of a user are not displayed directly in the user details view for an admin user. It could be interesting for administrator to display (by example as tabs) the list of role assignments of the user and the list of group of the user directly in the details view. Moreover it could be interesting to indicate role assignments that the user has got through a group. ** Affects: horizon Importance: Undecided Status: New -- 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/1792524 Title: Missing role assignment and group of user in the user detail view for admin Status in OpenStack Dashboard (Horizon): New Bug description: The role assignments and groups of a user are not displayed directly in the user details view for an admin user. It could be interesting for administrator to display (by example as tabs) the list of role assignments of the user and the list of group of the user directly in the details view. Moreover it could be interesting to indicate role assignments that the user has got through a group. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1792524/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
