[Yahoo-eng-team] [Bug 1681989] Re: the deletion of the instance does not release the memory quota for vram
Reviewed: https://review.openstack.org/456050 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2d03bf92db3615693b62f4f3274b867f00c0967 Submitter: Jenkins Branch:master commit f2d03bf92db3615693b62f4f3274b867f00c0967 Author: falseuser Date: Wed Apr 12 03:35:33 2017 + [BugFix] Release the memory quota for video ram when deleting an instance. When creating an instance, the quota is used to contain vram, and the deletion of the instance does not release the memory quota for vram, if delete intance it need to release the memory quota for vram. Change-Id: Iee2925c585c87d9885fd4bfe38cd9b4d316f5dab Closes-Bug: #1681989 ** Changed in: nova Status: In Progress => 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/1681989 Title: the deletion of the instance does not release the memory quota for vram Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) ocata series: New Bug description: When creating an instance, the quota is used to contain vram, and the deletion of the instance does not release the memory quota for vram If a flavor defines 512MB of RAM and 64MB of video RAM, creating an instance will take up 576MB of memory quota, but after deleting the instance, it will only release 512MB of memory quotas. In this way, after multiple creation and deletion of the virtual machine, it will gradually run out of the memory quota, but in fact did not run so many instances. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1681989/+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 1688673] [NEW] cpu_realtime_mask handling is not intuitive
Public bug reported: The nova code implicitly assumes that all vCPUs are realtime in nova.virt.hardware.vcpus_realtime_topology(), and then it appends the user-specified mask. This only makes sense if the user-specified cpu_realtime_mask is an exclusion mask, but this isn't documented anywhere. It would make more sense to simply use the mask as passed-in from the end-user. In order to preserve the current behaviour we should probably special- case the scenario where the passed-in cpu_realtime_mask starts with a "^" (indicating an exclusion). ** Affects: nova Importance: Undecided Status: New ** Tags: compute ** Description changed: The nova code implicitly assumes that all vCPUs are realtime in - nova.virt.hardware.vcpus_realtime_topology(). + nova.virt.hardware.vcpus_realtime_topology(), and then it appends the + user-specified mask. - This only makes sense if the cpu_realtime_mask is an exclusion mask, but - this isn't documented anywhere. + This only makes sense if the user-specified cpu_realtime_mask is an + exclusion mask, but this isn't documented anywhere. It would make more sense to simply use the mask as passed-in from the end-user. In order to preserve the current behaviour we should probably special- case the scenario where the passed-in cpu_realtime_mask starts with a "^" (indicating an exclusion). -- 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/1688673 Title: cpu_realtime_mask handling is not intuitive Status in OpenStack Compute (nova): New Bug description: The nova code implicitly assumes that all vCPUs are realtime in nova.virt.hardware.vcpus_realtime_topology(), and then it appends the user-specified mask. This only makes sense if the user-specified cpu_realtime_mask is an exclusion mask, but this isn't documented anywhere. It would make more sense to simply use the mask as passed-in from the end-user. In order to preserve the current behaviour we should probably special- case the scenario where the passed-in cpu_realtime_mask starts with a "^" (indicating an exclusion). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1688673/+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 1544989] Re: Nova doesn't validate user/project is valid from keystone during admin operations
Reviewed: https://review.openstack.org/435432 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1f120b5649ba03aa5b2490a82c08b77c580f12d7 Submitter: Jenkins Branch:master commit 1f120b5649ba03aa5b2490a82c08b77c580f12d7 Author: Sean Dague Date: Fri Feb 17 07:55:43 2017 -0500 Verify project id for flavor access calls This includes project id verification for flavor access calls. Closes-Bug: #1544989 Implements bp:validate-project-with-keystone Change-Id: I2620c3ebc2a6dc131946602f8aa36ec0b6e782e0 ** Changed in: nova Status: In Progress => 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/1544989 Title: Nova doesn't validate user/project is valid from keystone during admin operations Status in OpenStack Compute (nova): Fix Released Bug description: For any API call to Nova which takes a tenant_id / user_id as a parameter, and inserts it into the Nova database, no validation is done of these values. This is currently by design, largely because there is no clear way to check the existence of those users/projects. Nova has no generic credentials to do that to Keystone. It's unclear if there is a way to do this from a non admin user. Many other bugs are related to this fundamental issue for which there is no infrastructure. This includes updating quotas, adding access to flavors, etc. This will be a placeholder for all those bugs until there is some way to actually address this at the root. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1544989/+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 1688548] Re: test_update_router_extra_attributes_bumps_revision failure
Reviewed: https://review.openstack.org/462930
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=ff48a5eb38e921721eef1dcf2f19382e7d70662f
Submitter: Jenkins
Branch:master
commit ff48a5eb38e921721eef1dcf2f19382e7d70662f
Author: YAMAMOTO Takashi
Date: Fri May 5 13:01:30 2017 +
Revert "Fix tempest router migration test when HA enabled"
This reverts commit 2e8e6b8395ae0f7a48c6742b7f5a8989867fba2b.
Change-Id: I43d2a58a53071a9ec48785057f8d2655a1c55255
Closes-Bug: #1688548
** 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/1688548
Title:
test_update_router_extra_attributes_bumps_revision failure
Status in neutron:
Fix Released
Bug description:
eg. http://logs.openstack.org/10/438610/21/check/gate-tempest-dsvm-
networking-midonet-ml2-ubuntu-
xenial/a35d516/logs/testr_results.html.gz
ft1.14:
neutron.tests.tempest.api.test_revisions.TestRevisions.test_update_router_extra_attributes_bumps_revision[id-afb6486c-41b5-483e-a500-3c506f4deb49]_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2017-05-05 02:54:32,317 15758 INFO [tempest.lib.common.rest_client]
Request (TestRevisions:test_update_router_extra_attributes_bumps_revision): 400
POST http://10.37.33.223:9696/v2.0/routers 0.071s
2017-05-05 02:54:32,317 15758 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'Content-Type': 'application/json', 'Accept':
'application/json', 'X-Auth-Token': ''}
Body: {"router": {"name": "r1", "admin_state_up": true, "tenant_id":
"5b8c1ab78ec849ff8c66db67fef80206", "ha": false}}
Response - Headers: {u'x-openstack-request-id':
'req-4daea7f8-2c7e-48a6-9d34-30538c101e45', u'date': 'Fri, 05 May 2017 02:54:32
GMT', u'connection': 'close', u'content-length': '103', 'content-location':
'http://10.37.33.223:9696/v2.0/routers', u'content-type': 'application/json',
'status': '400'}
Body: {"NeutronError": {"message": "Unrecognized attribute(s) 'ha'",
"type": "HTTPBadRequest", "detail": ""}}
}}}
Traceback (most recent call last):
File "tempest/test.py", line 115, in wrapper
return func(*func_args, **func_kwargs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_revisions.py",
line 322, in test_update_router_extra_attributes_bumps_revision
**router_args)['router']
File
"/opt/stack/new/neutron/neutron/tests/tempest/services/network/json/network_client.py",
line 340, in create_router
resp, body = self.post(uri, body)
File "tempest/lib/common/rest_client.py", line 270, in post
return self.request('POST', url, extra_headers, headers, body, chunked)
File "tempest/lib/common/rest_client.py", line 659, in request
self._error_checker(resp, resp_body)
File "tempest/lib/common/rest_client.py", line 770, in _error_checker
raise exceptions.BadRequest(resp_body, resp=resp)
tempest.lib.exceptions.BadRequest: Bad request
Details: {u'type': u'HTTPBadRequest', u'detail': u'', u'message':
u"Unrecognized attribute(s) 'ha'"}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1688548/+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 1688645] [NEW] Networks panel action names not consistent with modal names
Public bug reported: In both Project > Networks and Admin > Networks panels, the table row action uses "Edit xxx" but the corresponding modal name is "Update xxx". The action name should be consistent with the modal name. For example in the Networks table, the action is "Edit Network" but the modal name is "Update network" and the Ports table, the action is "Edit Port" while the modal name is "Update Port". ** Affects: horizon Importance: Undecided Assignee: Julie Gravel (julie-gravel) Status: New ** Changed in: horizon Assignee: (unassigned) => Julie Gravel (julie-gravel) ** Summary changed: - Network panel action names not consistent with modal names + Networks panel action names not consistent with modal names -- 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/1688645 Title: Networks panel action names not consistent with modal names Status in OpenStack Dashboard (Horizon): New Bug description: In both Project > Networks and Admin > Networks panels, the table row action uses "Edit xxx" but the corresponding modal name is "Update xxx". The action name should be consistent with the modal name. For example in the Networks table, the action is "Edit Network" but the modal name is "Update network" and the Ports table, the action is "Edit Port" while the modal name is "Update Port". To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688645/+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 1688366] Re: KeyError: u'overs' in unit test runs
Reviewed: https://review.openstack.org/462764 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=df91955cffd0bca61b032ba2b3420c7eb030a5e3 Submitter: Jenkins Branch:master commit df91955cffd0bca61b032ba2b3420c7eb030a5e3 Author: melanie witt Date: Fri May 5 00:02:33 2017 + Fix unit test exception KeyErrors There are several places in the unit tests where exceptions are being used as side_effects without providing the kwargs they require for their messages. This adds the required kwargs. Closes-Bug: #1688366 Change-Id: Ie13e1b6fd4e75fce0a6b7225c4bd294889cf07c7 ** Changed in: nova Status: In Progress => 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/1688366 Title: KeyError: u'overs' in unit test runs Status in OpenStack Compute (nova): Fix Released Bug description: This was just introduced in this change: https://review.openstack.org/#/c/460305/6/nova/tests/unit/compute/test_compute.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1688366/+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 1688333] Re: Angular table footer missing the 'table_count' class
Superseded by changes made to fix https://bugs.launchpad.net/horizon/+bug/1688590 ** Changed in: horizon Status: In Progress => Invalid ** Changed in: horizon Milestone: pike-2 => None ** Changed in: horizon Assignee: Rob Cresswell (robcresswell) => (unassigned) -- 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/1688333 Title: Angular table footer missing the 'table_count' class Status in OpenStack Dashboard (Horizon): Invalid Bug description: The Python tables have a 'table_count' class on the content that shows how many items are currently being displayed. This is missing from the angular tables, making it difficult to theme. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688333/+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 1686917] Re: api-ref: unnecessary description in servers-admin-action.inc
Reviewed: https://review.openstack.org/460866 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9d6913d9f07e96b493c15be04174b4f4656dee1f Submitter: Jenkins Branch:master commit 9d6913d9f07e96b493c15be04174b4f4656dee1f Author: Takashi NATSUME Date: Fri Apr 28 16:17:28 2017 +0900 api-ref: Fix unnecessary description in servers-admin-action The action to change the administrative password is not included in servers-admin-action.inc. So the description related to the action is removed. Change-Id: I942aaea755375822e9f5ac9e29287de0c08dc573 Implements: blueprint api-ref-in-rst-pike Closes-Bug: #1686917 ** Changed in: nova Status: In Progress => 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/1686917 Title: api-ref: unnecessary description in servers-admin-action.inc Status in OpenStack Compute (nova): Fix Released Bug description: https://developer.openstack.org/api-ref/compute/#servers-run-an- administrative-action-servers-action There is the following description, but the action to change the administrative password for a server is not included in servers-admin-action.inc. So it should be removed. > You can change the administrative password for a server and inject network information into a server. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1686917/+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 1687401] Re: Horizon 403 Forbidden
** Changed in: horizon Status: Incomplete => Invalid -- 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/1687401 Title: Horizon 403 Forbidden Status in OpenStack Dashboard (Horizon): Invalid Bug description: Hello there, I have been struggling a bit with moving the horizon page from domain.com/horizon to domain.com/ + setting up HTTPS, here's what I have tied: - [General 403 debugging](https://askubuntu.com/questions/292968/apache2-forbidden-you-dont-have-permission-to-access-dir-on-this-server) - [General 403 debugging](https://unix.stackexchange.com/questions/169513/403-forbidden-you-dont-have-permission-to-access-on-this-server-apache2) - [403 fix for Horizon](https://fosshelp.blogspot.co.uk/2014/02/openstack-horizon-you-dont-have.html) - [General 403 debugging](https://stackoverflow.com/questions/10873295/error-message-forbidden-you-dont-have-permission-to-access-on-this-server) - [Launchpad 403 knwon (and fixed) bug ](https://bugs.launchpad.net/devstack/+bug/1243075) - [HTTPS config guide (from Juno)](https://docs.openstack.org/juno/config-reference/content/configure-dashboard.html#after-example) ### Environment - Followed the latest installation guide (Ocata) - Apache2 version: Apache/2.4.18 (Ubuntu) - Ubuntu 16.04.2 LTS AMD64 ### Configuration **local_settings.py** https://paste.debian.net/930199/ **openstack-dashboard.conf** https://paste.debian.net/930200/ **error.log** https://paste.debian.net/930201/ This leaves me with some funny results, the login page loads but is missing CSS, only plain HTML. When I log in, everything else gives me a `403`. Any help would be appreciated. Thank you, Tiago Ferreira m...@tiferrei.com To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1687401/+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 1688599] [NEW] resource audit races against evacuating instance
Public bug reported: We recently hit an issue where an evacuating instance with dedicated cpu_policy being pinned to same host CPUs as other instances with dedicated cpu_policy. During subsequent resource audits we would see cpu pinning errors. The root cause appears to be the fact that the resource audit skips the evacuating instance during migration phase of audit while instance was rebuilding on new host. It appears that _instance_in_resize_state() returned "false" because the vm_state was vm_states.ERROR. We allow rebuilding from the ERROR state though, so we should consider it. ** Affects: nova Importance: Undecided Status: New ** Tags: compute -- 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/1688599 Title: resource audit races against evacuating instance Status in OpenStack Compute (nova): New Bug description: We recently hit an issue where an evacuating instance with dedicated cpu_policy being pinned to same host CPUs as other instances with dedicated cpu_policy. During subsequent resource audits we would see cpu pinning errors. The root cause appears to be the fact that the resource audit skips the evacuating instance during migration phase of audit while instance was rebuilding on new host. It appears that _instance_in_resize_state() returned "false" because the vm_state was vm_states.ERROR. We allow rebuilding from the ERROR state though, so we should consider it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1688599/+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 1636531] Re: unittests blkid command fails on slave s390x
** Changed in: cloud-init Status: Invalid => Fix Committed ** Changed in: cloud-init Importance: Undecided => Medium -- 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/1636531 Title: unittests blkid command fails on slave s390x Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] Unit test updates to avoid leaking blkid calls from tests/unittests/test_datasource/test_altcloud.py. [Test Case] wget https://git.launchpad.net/~smoser/cloud-init/+git/sru- info/plain/bin/lxc-proposed-snapshot chmod 755 lxc-proposed-snapshot # Create fake-blkid.sh cat fake-blkid.sh #!/bin/bash echo "LEAKED BLKID CALL" name=proposed-test for release in xenial yakkety zesty; do \ ref=$release-proposed; ./lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref $name; lxc start $name; sleep 10; lxc exec $name mv /sbin/blkid /sbin/blkid.orig; lxc file push fake-flkid.sh $name/sbin/blkid lxc exec $name git clone -b ubuntu/xenial https://git.launchpad.net/cloud-init tox -e py27 tests/unittests/test_datasource/test_altcloud.py | grep 'LEAKED BLKID'; done [Regression Potential] None. Unit test changes only [Other Info] === End SRU Template === Running the unittests on our slave s390x system, the blkid command fails. Running it manually returns the following: jenkins@s1lp04:~$ blkid -tLABEL=CDROM -odevice jenkins@s1lp04:~$ echo $? 2 jenkins@s1lp04:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT dasda 94:00 20.6G 0 disk |-dasda1 94:10 19.7G 0 part / `-dasda2 94:20 953.5M 0 part [SWAP] Full run output: https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1636531/+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 1673637] Re: cloud-init - Hosts in softlayer receiving warning
** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Artful) Status: Fix Committed => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Artful) Importance: Undecided => Medium -- 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/1673637 Title: cloud-init - Hosts in softlayer receiving warning Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin cloud-init SRU Template === [Impact] Softlayer user datasource is undetected when only openstack/latest config-drive directory is provided (due to softlayer user-data being provided). [Test Case] For cloud-init, the easiest way to demonstrate this is to create a lxc container and populate it with a '/config-drive' that only contains a openstack/latest path. wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot chmod 755 lxc-proposed-snapshot wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/tools/make-configdrive-dir chmod 755 make-configdrive-dir name=test-proposed for release in xenial yaketty zesty; do ref=$release-proposed; ./lxc-proposed-snapshot --proposed --publish $release $ref; ./lxc init $ref $name; ## populate a /config-drive with attached 'make-configdrive-dir' ## and push it to the container d=$(mktemp -d) ./make-configdrive-dir "$d" "$name" rm -Rf "$d" lxc file pull $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg - | sed 's/NoCloud, //' | lxc file push - $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg; lxc start $name; sleep 10; lxc exec $name cp -r /config-drive /var/lib/cloud/seed/config_drive; lxc exec $name rm -rf /var/lib/cloud/seed/config_drive/openstack/2015-10-15; lxc exec $name sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep latest ; # should produce config drive seeded directory had only 'latest' done [Regression Potential] Minimal as this code is exercised for soft [Other Info] === End cloud-init SRU Template === To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1673637/+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 1688590] [NEW] The table pager is difficult to theme
Public bug reported: The table pager lacks default bootstrap styling as well as contextual classes, making it difficult to theme ** Affects: horizon Importance: Low Assignee: Rob Cresswell (robcresswell) Status: New ** Changed in: horizon Milestone: None => pike-2 ** Changed in: horizon Assignee: (unassigned) => Rob Cresswell (robcresswell) ** Changed in: horizon Importance: Undecided => Low -- 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/1688590 Title: The table pager is difficult to theme Status in OpenStack Dashboard (Horizon): New Bug description: The table pager lacks default bootstrap styling as well as contextual classes, making it difficult to theme To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688590/+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 1671693] Re: Rebuild instance panel does not show project images when using Glance V2
Reviewed: https://review.openstack.org/444091 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=445117eb1fa1cd67e21e69243fbbe12c453192fa Submitter: Jenkins Branch:master commit 445117eb1fa1cd67e21e69243fbbe12c453192fa Author: Mark Mielke Date: Thu Mar 9 23:16:51 2017 -0500 Image list function should normalize owner filter The api.glance.image_list_detailed() function accepts a list of filters which it then translates into a form that is acceptable for Glance v1 or Glance v2. These translations included support for mapping 'is_public' to 'visibility', but did not include support for mapping 'property-owner_id' to 'owner'. This changes adds support for mapping 'property-owner_id' to 'owner' for Glance v2, and mapping 'owner' to 'property-owner_id' for Glance v1. Before this fix, "rebuild instance" from the instances page did not properly list project-specific images as options. After this fix, "rebuild instance" is working as expected. Change-Id: Ica750f8b36bdbadd02a81aed41fd250864a49a66 Closes-Bug: 1671693 ** Changed in: horizon Status: In Progress => 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/1671693 Title: Rebuild instance panel does not show project images when using Glance V2 Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When using Glance v2, the "rebuild instance" panel shows public images, but does not show project images. Steps to reproduce: * Configure Horizon to use Glance v2 * Create a private image in project A * Rebuild an instance in project A from the instances dashboard * The image list will show public images, but not project images Upon more detailed investigation, the "rebuild instance" function calls code that searches for images based upon "property-owner_id", which only works in Glance v1. In Glance v2, it should use "owner". To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1671693/+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 1685810] Re: nova-lxd needs to read 'product_name' in environment, not 'platform'
** Also affects: cloud-init (Ubuntu Artful) Importance: Medium Status: 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/1685810 Title: nova-lxd needs to read 'product_name' in environment, not 'platform' Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] Warning message for nova-lxd images in openstack clouds due to no valid datasource found. [Test Case] # It downloads a cloud image of a given release, and then creates a -proposed image with cloud-init upgraded. wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot chmod 755 get-proposed-image source novarc for release in xenial yakkety zesty do; ref=$release-proposed; lxc-proposed-snapshot --proposed --publish $release $ref; lxc image export $ref .; imagefile=`ls -tr *gz | tail -n 1` mkdir $ref; cd $ref; tar -zxvf ../$imagefile; cd rootfs; tar zcvf $ref.tar.gz *; #upload raw image to your cloud openstack image create --disk-format raw --container-format bare --file $ref.tar.gz testing/$ref.tar.gz; openstack server create --image testing/$ref.tar.gz --flavor=m1.tiny lxd-$release --key-name ; nova floating-ip-create; nova foating-ip-associate ; ssh ubuntu@ 'sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep Found'; # single datasource: OpenStack done [Regression Potential] Low as this only addresses the warning by correctly identifying the OpenStack cloud datasource. [Other Info] === End SRU Template === It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs: * bug 1661797: identify lxd-nova platform to enable Openstack datasource To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1685810/+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 1688577] [NEW] Unable to update default quotas
Public bug reported: "Error: Unable to update default quotas" raised when tried update quotas in Horizon. Dialog "Update Default Quotas" appears with empty fields "Key Pairs" and "Length of Injected File Path". Even you type default quotas such as "100" and "255" you will get 2 messages: 1st - successful update and 2nd - error (see attached screenshot) Warning raised in horizon.log file "2017-02-21 18:32:42,221 1004737 WARNING horizon.exceptions Recoverable error: 'key_pairs'" CLI works w/o errors. ** 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/1688577 Title: Unable to update default quotas Status in OpenStack Dashboard (Horizon): New Bug description: "Error: Unable to update default quotas" raised when tried update quotas in Horizon. Dialog "Update Default Quotas" appears with empty fields "Key Pairs" and "Length of Injected File Path". Even you type default quotas such as "100" and "255" you will get 2 messages: 1st - successful update and 2nd - error (see attached screenshot) Warning raised in horizon.log file "2017-02-21 18:32:42,221 1004737 WARNING horizon.exceptions Recoverable error: 'key_pairs'" CLI works w/o errors. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688577/+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 1367899] Re: cloud-init rsyslog config uses deprecated syntax
** Also affects: cloud-init (Ubuntu Artful) Importance: Low Status: 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/1367899 Title: cloud-init rsyslog config uses deprecated syntax Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Status in cloud-init package in Debian: Fix Released Bug description: === Begin SRU Template === [Impact] Warning messages in /var/log/syslog on startup: warning: ~ action is deprecated, consider using the 'stop' statement instead [Test Case] Startup proposed lxcs and confirm warning message no longer present $ name=proposed-test $ for release in xenial yakkety zesty; do $ ref=$release-proposed $ lxc-proposed-snapshot --proposed --publish $release $ref $ lxc init $ref $name $ lxc start $name $ sleep 10 $ lxc exec $name grep "warning: ~ action is deprecated, consider using the 'stop' statemen" /var/log/syslog # validate cloud-init messages are making it into syslog still $ lxc exec $name grep cloud-init /var/log/syslog $ lxc stop $name $ lxc delete $name [Regression Potential] Low. oneliner rsyslog change [Other Info] Upstream commit: https://git.launchpad.net/~powersj/cloud-init/commit/?id=87dcf5769df4e5ce370be753b7d39f5a65cee2f2 === End SRU Template === To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1367899/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New -- 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/1682871 Title: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4 Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in linux source package in Xenial: Triaged Status in cloud-init source package in Yakkety: New Status in linux source package in Yakkety: New Status in cloud-init source package in Zesty: New Status in linux source package in Zesty: New Bug description: [Impact] * When vlan interfaces are created, their mac address is copied from the underlying interface, but it is not marked by kernel as stolen. * When underlying interface MAC address is changed, it does not propagate to the vlan interfaces. [Test Case] * Create vlan interface, check the addr_assign_type sysfs attribute, it should be 2, not 0. * Update the base interface mac address, the mac address of the vlan interface should change too. * cloud-init test case wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg; chmod 755 get-proposed-cloudimg; for release in xenial yakkety zesty; do ./get-proposed-cloudimg $release; MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img ; # ubuntu/passw0rd python3 -c 'from cloudinit.net import get_interfaces_by_mac; print(get_interfaces_by_mac())'; # results in no runtime error and doesn't report vlan interface name done [Regression Potential] * Userspace may rely on non-propagating MAC addresses, and the fact that vlan mac address type is wrongly stated as non-stolen; however this behaviour will be consistent with 4.7+ kernels. [Other Info] * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 kernels commit 308453aa9156a3b8ee382c0949befb507a32b0c1 Author: Mike Manning Date: Fri May 27 17:45:07 2016 +0100 vlan: Propagate MAC address to VLANs The MAC address of the physical interface is only copied to the VLAN when it is first created, resulting in an inconsistency after MAC address changes of only newly created VLANs having an up-to-date MAC. The VLANs should continue inheriting the MAC address of the physical interface until the VLAN MAC address is explicitly set to any value. This allows IPv6 EUI64 addresses for the VLAN to reflect any changes to the MAC of the physical interface and thus for DAD to behave as expected. Signed-off-by: Mike Manning Signed-off-by: David S. Miller * Original bug report When attempting to verify sru for bug 1669860, I found that vlans are not properly filtered out by 'get_interfaces_by_mac'. That means that the bug is still present with vlans. The reason for this is that /sys/class/net//addr_assign_type shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8. See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net for doc on addr_assign_type. Related bugs: * bug 1669860: cloud-init attempts to rename bonds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1684869] Re: growing root partition does not always work with root=PARTUUID=
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Artful)
Importance: Medium
Status: Fix Released
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
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/1684869
Title:
growing root partition does not always work with root=PARTUUID=
Status in cloud-init:
Confirmed
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
New
Status in cloud-init source package in Yakkety:
New
Status in cloud-init source package in Zesty:
New
Status in cloud-init source package in Artful:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
Growing the root partition would fail in either of two cases:
a.) if the device /dev/root existed
b.) the kernel command line had upper case letters in PARTUUID=
[Test Case]
get-proposed-image is
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/get-proposed-image
It downloads a cloud image of a given release, and then creates a -proposed
image with cloud-init upgraded.
1.) get a (proposed) disk image image.
and convert it to raw so you can read the partuuid with sfdisk
(get-proposed-image does this, if not,
'qemu-img convert -O raw orig.img orig.raw')
./get-proposed-image
2.) get the partition uuid of the first partition
$ raw=yakkety-server-cloudimg-amd64-proposed.raw
$ ptuuid=$(sfdisk --part-uuid $raw 1)
3.) create a nocloud seed
$ printf "%s\n%s\n%s\n%s\n" "#cloud-config" "password: passw0rd" \
"chpasswd: {expire: False}" "ssh_pwauth: True" > my-user-data
$ echo "instance-id: $(uuidgen || echo i-abcdefg)" > my-meta-data
$ cloud-localds my-seed.img my-user-data my-meta-data
4.) extract kernel from inside the image
$ sudo mount-image-callback $raw -- mchroot sh -xc 'cat /boot/vmlinu?-*' >
kernel
5.) boot instance with disk backed by the raw disk above.
$ qemu-img create -f qcow2 -b $raw disk.img 10G
$ qemu-system-x86_64 -enable-kvm \
-drive file=disk.img,if=ide,index=0 -drive file=my-seed.img,if=ide \
-net nic -net user,hostfwd=tcp::-:22 \
-snapshot -m 768 -nographic -echr 0x05 \
-kernel kernel \
-append "root=PARTUUID=${ptuuid} ro console=tty1 console=ttyS0"
6.) log in, verify / has been resized.
log in with 'ubuntu' and password 'passw0rd'
$ df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/root 9.6G 1009M 8.6G 11% /
[Regression Potential]
The regression path is really the case where devent2dev finds /dev/root
and /dev/root exists. In that case, we now possibly return a /dev/
path when previously it would have returned /dev/root.
[Other Info]
The qemu-system-x86 command above uses ide devices. This is because
the ide device emulated by qemu is built into the -generic kernel,
whilei the more common virtio-block or virtio-scsi are not. If you
attach those device types, it will fail with 'cant find root'.
=== End SRU Template ===
When trying to verify I found a couple cases where this still does not
work.
Related bugs:
* bug 1677376: growing partitions does not work when booted without initramfs
* bug 1685291: RFC: virtio and virtio-scsi should be built in
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1684869/+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 1644064] Re: sshd_config file permission changed to 644 if ssh_pwauth value is true or false
** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Artful) Importance: Undecided => Medium -- 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/1644064 Title: sshd_config file permission changed to 644 if ssh_pwauth value is true or false Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] Existing security permissions on /etc/ssh/sshd_config file are not honored. [Test Case] wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot chmod 755 lxc-proposed-snapshot # create config.yaml cat config.yaml #cloud-config ssh_pwauth: true name=proposed-test for release in xenial yakkety zesty; do \ ref=$release-proposed; lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref $name; lxc start $name; sleep 10; lxc file pull $name/etc/ssh/sshd_config .; chmod 600 sshd_config; lxc file push sshd_config $name/etc/ssh/sshd_config; lxc config set $name user.user-data - < config.yml; lxc start; sleep 10; lxc exec $name ls -ltr /etc/ssh/sshd_config; # should remain 600 lxc stop $name; lxc delete $name; done [Regression Potential] Minimal as we are now honoring file permissions if an sshd_config file exists. [Other Info] === End SRU Template === In my deploy image, the default permission of sshd_config file is 600. It always be changed to 644 after cloud-init run. After debug, it is caused by cloud-config item: ssh_pwauth: true The related code is: lines = [str(l) for l in new_lines] util.write_file(ssh_util.DEF_SSHD_CFG, "\n".join(lines)) of file cc_set_passwords.py. write_file function use default mask 644 to write sshd_config. So my file permission changed. It shall be enhanced to read old sshd_config permission and write new sshd_config with old permission to avoid security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1644064/+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 1636531] Re: unittests blkid command fails on slave s390x
** Also affects: cloud-init (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Artful) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Artful) Importance: Undecided => Medium -- 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/1636531 Title: unittests blkid command fails on slave s390x Status in cloud-init: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] Unit test updates to avoid leaking blkid calls from tests/unittests/test_datasource/test_altcloud.py. [Test Case] wget https://git.launchpad.net/~smoser/cloud-init/+git/sru- info/plain/bin/lxc-proposed-snapshot chmod 755 lxc-proposed-snapshot # Create fake-blkid.sh cat fake-blkid.sh #!/bin/bash echo "LEAKED BLKID CALL" name=proposed-test for release in xenial yakkety zesty; do \ ref=$release-proposed; ./lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref $name; lxc start $name; sleep 10; lxc exec $name mv /sbin/blkid /sbin/blkid.orig; lxc file push fake-flkid.sh $name/sbin/blkid lxc exec $name git clone -b ubuntu/xenial https://git.launchpad.net/cloud-init tox -e py27 tests/unittests/test_datasource/test_altcloud.py | grep 'LEAKED BLKID'; done [Regression Potential] None. Unit test changes only [Other Info] === End SRU Template === Running the unittests on our slave s390x system, the blkid command fails. Running it manually returns the following: jenkins@s1lp04:~$ blkid -tLABEL=CDROM -odevice jenkins@s1lp04:~$ echo $? 2 jenkins@s1lp04:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT dasda 94:00 20.6G 0 disk |-dasda1 94:10 19.7G 0 part / `-dasda2 94:20 953.5M 0 part [SWAP] Full run output: https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1636531/+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 1673637] Re: cloud-init - Hosts in softlayer receiving warning
** Also affects: cloud-init (Ubuntu Artful) Importance: Undecided Status: Fix Committed ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1673637 Title: cloud-init - Hosts in softlayer receiving warning Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Fix Committed Status in cloud-init source package in Xenial: New Status in cloud-init source package in Yakkety: New Status in cloud-init source package in Zesty: New Status in cloud-init source package in Artful: Fix Committed Bug description: === Begin cloud-init SRU Template === [Impact] Softlayer user datasource is undetected when only openstack/latest config-drive directory is provided (due to softlayer user-data being provided). [Test Case] For cloud-init, the easiest way to demonstrate this is to create a lxc container and populate it with a '/config-drive' that only contains a openstack/latest path. wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot chmod 755 lxc-proposed-snapshot wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/tools/make-configdrive-dir chmod 755 make-configdrive-dir name=test-proposed for release in xenial yaketty zesty; do ref=$release-proposed; ./lxc-proposed-snapshot --proposed --publish $release $ref; ./lxc init $ref $name; ## populate a /config-drive with attached 'make-configdrive-dir' ## and push it to the container d=$(mktemp -d) ./make-configdrive-dir "$d" "$name" rm -Rf "$d" lxc file pull $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg - | sed 's/NoCloud, //' | lxc file push - $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg; lxc start $name; sleep 10; lxc exec $name cp -r /config-drive /var/lib/cloud/seed/config_drive; lxc exec $name rm -rf /var/lib/cloud/seed/config_drive/openstack/2015-10-15; lxc exec $name sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep latest ; # should produce config drive seeded directory had only 'latest' done [Regression Potential] Minimal as this code is exercised for soft [Other Info] === End cloud-init SRU Template === To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1673637/+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 1688556] Re: devstack breaks on neutron setup
reinstalled ubuntu (brand new VM) and problem disappeared. No idea what
was wrong but I'm past this now.
** 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/1688556
Title:
devstack breaks on neutron setup
Status in neutron:
Invalid
Bug description:
Brand new tree, 2017-05-05, devstack breaks with a dependency
inconsistency in python-neutronclient.
See file attached for devstack output.
Obtaining file:///opt/stack/python-neutronclient
Exception:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/pip/basecommand.py", line 215,
in main
status = self.run(options, args)
File "/usr/local/lib/python2.7/dist-packages/pip/commands/install.py", line
335, in run
wb.build(autobuilding=True)
File "/usr/local/lib/python2.7/dist-packages/pip/wheel.py", line 749, in
build
self.requirement_set.prepare_files(self.finder)
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 380,
in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 521,
in _prepare_file
req_to_install.check_if_exists()
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_install.py", line
1036, in check_if_exists
self.req.name
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 558, in get_distribution
dist = get_provider(dist)
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 432, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 968, in require
needed = self.resolve(parse_requirements(requirements))
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 859, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
ContextualVersionConflict: (keystoneauth1 2.19.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('keystoneauth1>=2.20.0'), set(['python-neutronclient']))
+inc/python:pip_install:1 exit_trap
+./stack.sh:exit_trap:492 local r=2
++./stack.sh:exit_trap:493 jobs -p
+./stack.sh:exit_trap:493 jobs=
+./stack.sh:exit_trap:496 [[ -n '' ]]
+./stack.sh:exit_trap:502 kill_spinner
+./stack.sh:kill_spinner:388 '[' '!' -z '' ']'
+./stack.sh:exit_trap:504 [[ 2 -ne 0 ]]
+./stack.sh:exit_trap:505 echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:506 generate-subunit 1493989949 89 fail
+./stack.sh:exit_trap:507 [[ -z /opt/stack/logs ]]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1688556/+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 1688573] [NEW] neutron-fwaas iptables driver performs awful
Public bug reported: Details === >From Liberty onwards the neutron iptables_manager started using difflib.ndiff >to check for changes to iptables rules. This function does way more than it >needs to and takes exponential time, so by the time you have enough rules the >l3-agent eats 100% CPU and suffers from RPC timeouts effectively taking the >agent down. There are a couple elements in play here. First the generation of iptables rules in neutron-fwass is utterly wrong guaranteeing that every line diffed will be different. My first patch addresses this issue ensuring fields are correctly ordered, sub-fields within lines are correctly ordered, source and destination prefixes are normalized. As an experiment I increased firewall rules from 1 -> 1024 (2^N progression) to measure the damage in devstack. The time complexity was roughly 0.0045 x N^2. At 512 (~120s) we started getting timeouts and had the l3 agent spinning constantly broken unable to apply the configuration. Applying the fixes to the formatting reduced this to 0.004521s for 512 entries. I suspect looking at the code for ndiff this will equate to roughly 65536 firewall rules before the system keels over again. The second issue is with ndiff itself. If we end up in this situation again where all lines are different it correctly discovers this in O(N^2) time, however it also tries to diff pairs of lines that look alike. This is utterly superfluous to the algorithm in neutron and basically causes a huge performance penalty. Given we've been throwing away the whole ruleset and reinstalling it each time for 2 years you may as well replace it with an O(N) list compare ;D The other thing would be to parse iptables output into an internal representation and compare those which are not at the whimsical mercy of a 3rd party. Version === Liberty -> Present Severity High - we have customers with over 1500 rules, and having them able to DoS our L3 network service is not great ** Affects: neutron Importance: Undecided Assignee: Simon Murray (simon-murray-q) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1688573 Title: neutron-fwaas iptables driver performs awful Status in neutron: In Progress Bug description: Details === From Liberty onwards the neutron iptables_manager started using difflib.ndiff to check for changes to iptables rules. This function does way more than it needs to and takes exponential time, so by the time you have enough rules the l3-agent eats 100% CPU and suffers from RPC timeouts effectively taking the agent down. There are a couple elements in play here. First the generation of iptables rules in neutron-fwass is utterly wrong guaranteeing that every line diffed will be different. My first patch addresses this issue ensuring fields are correctly ordered, sub-fields within lines are correctly ordered, source and destination prefixes are normalized. As an experiment I increased firewall rules from 1 -> 1024 (2^N progression) to measure the damage in devstack. The time complexity was roughly 0.0045 x N^2. At 512 (~120s) we started getting timeouts and had the l3 agent spinning constantly broken unable to apply the configuration. Applying the fixes to the formatting reduced this to 0.004521s for 512 entries. I suspect looking at the code for ndiff this will equate to roughly 65536 firewall rules before the system keels over again. The second issue is with ndiff itself. If we end up in this situation again where all lines are different it correctly discovers this in O(N^2) time, however it also tries to diff pairs of lines that look alike. This is utterly superfluous to the algorithm in neutron and basically causes a huge performance penalty. Given we've been throwing away the whole ruleset and reinstalling it each time for 2 years you may as well replace it with an O(N) list compare ;D The other thing would be to parse iptables output into an internal representation and compare those which are not at the whimsical mercy of a 3rd party. Version === Liberty -> Present Severity High - we have customers with over 1500 rules, and having them able to DoS our L3 network service is not great To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1688573/+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 1681989] Re: the deletion of the instance does not release the memory quota for vram
** Also affects: nova/ocata Importance: Undecided Status: New ** Changed in: nova Assignee: Matt Riedemann (mriedem) => 赵明俊 (falseuser) -- 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/1681989 Title: the deletion of the instance does not release the memory quota for vram Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) ocata series: New Bug description: When creating an instance, the quota is used to contain vram, and the deletion of the instance does not release the memory quota for vram If a flavor defines 512MB of RAM and 64MB of video RAM, creating an instance will take up 576MB of memory quota, but after deleting the instance, it will only release 512MB of memory quotas. In this way, after multiple creation and deletion of the virtual machine, it will gradually run out of the memory quota, but in fact did not run so many instances. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1681989/+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 1688556] [NEW] devstack breaks on neutron setup
Public bug reported:
Brand new tree, 2017-05-05, devstack breaks with a dependency
inconsistency in python-neutronclient.
See file attached for devstack output.
Obtaining file:///opt/stack/python-neutronclient
Exception:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/pip/basecommand.py", line 215,
in main
status = self.run(options, args)
File "/usr/local/lib/python2.7/dist-packages/pip/commands/install.py", line
335, in run
wb.build(autobuilding=True)
File "/usr/local/lib/python2.7/dist-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 380,
in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 521,
in _prepare_file
req_to_install.check_if_exists()
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_install.py", line
1036, in check_if_exists
self.req.name
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 558, in get_distribution
dist = get_provider(dist)
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 432, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 968, in require
needed = self.resolve(parse_requirements(requirements))
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 859, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
ContextualVersionConflict: (keystoneauth1 2.19.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('keystoneauth1>=2.20.0'), set(['python-neutronclient']))
+inc/python:pip_install:1 exit_trap
+./stack.sh:exit_trap:492 local r=2
++./stack.sh:exit_trap:493 jobs -p
+./stack.sh:exit_trap:493 jobs=
+./stack.sh:exit_trap:496 [[ -n '' ]]
+./stack.sh:exit_trap:502 kill_spinner
+./stack.sh:kill_spinner:388 '[' '!' -z '' ']'
+./stack.sh:exit_trap:504 [[ 2 -ne 0 ]]
+./stack.sh:exit_trap:505 echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:506 generate-subunit 1493989949 89 fail
+./stack.sh:exit_trap:507 [[ -z /opt/stack/logs ]]
** Affects: neutron
Importance: Undecided
Status: New
** Attachment added: "neutron.txt"
https://bugs.launchpad.net/bugs/1688556/+attachment/4872295/+files/neutron.txt
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1688556
Title:
devstack breaks on neutron setup
Status in neutron:
New
Bug description:
Brand new tree, 2017-05-05, devstack breaks with a dependency
inconsistency in python-neutronclient.
See file attached for devstack output.
Obtaining file:///opt/stack/python-neutronclient
Exception:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/pip/basecommand.py", line 215,
in main
status = self.run(options, args)
File "/usr/local/lib/python2.7/dist-packages/pip/commands/install.py", line
335, in run
wb.build(autobuilding=True)
File "/usr/local/lib/python2.7/dist-packages/pip/wheel.py", line 749, in
build
self.requirement_set.prepare_files(self.finder)
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 380,
in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 521,
in _prepare_file
req_to_install.check_if_exists()
File "/usr/local/lib/python2.7/dist-packages/pip/req/req_install.py", line
1036, in check_if_exists
self.req.name
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 558, in get_distribution
dist = get_provider(dist)
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 432, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 968, in require
needed = self.resolve(parse_requirements(requirements))
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 859, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
ContextualVersionConflict: (keystoneauth1 2.19.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('keystoneauth1>=2.20.0'), set(['python-neutronclient']))
+inc/python:pip_install:1 exit_trap
+./stack.sh:exit_trap:492
[Yahoo-eng-team] [Bug 1688548] Re: test_update_router_extra_attributes_bumps_revision failure
seems like a bug in the test (I8caf86817a5cd8e4d0cf05d7beef850756e84bab)
** Changed in: networking-midonet
Importance: Undecided => Critical
** Project changed: networking-midonet => 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/1688548
Title:
test_update_router_extra_attributes_bumps_revision failure
Status in neutron:
In Progress
Bug description:
eg. http://logs.openstack.org/10/438610/21/check/gate-tempest-dsvm-
networking-midonet-ml2-ubuntu-
xenial/a35d516/logs/testr_results.html.gz
ft1.14:
neutron.tests.tempest.api.test_revisions.TestRevisions.test_update_router_extra_attributes_bumps_revision[id-afb6486c-41b5-483e-a500-3c506f4deb49]_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2017-05-05 02:54:32,317 15758 INFO [tempest.lib.common.rest_client]
Request (TestRevisions:test_update_router_extra_attributes_bumps_revision): 400
POST http://10.37.33.223:9696/v2.0/routers 0.071s
2017-05-05 02:54:32,317 15758 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'Content-Type': 'application/json', 'Accept':
'application/json', 'X-Auth-Token': ''}
Body: {"router": {"name": "r1", "admin_state_up": true, "tenant_id":
"5b8c1ab78ec849ff8c66db67fef80206", "ha": false}}
Response - Headers: {u'x-openstack-request-id':
'req-4daea7f8-2c7e-48a6-9d34-30538c101e45', u'date': 'Fri, 05 May 2017 02:54:32
GMT', u'connection': 'close', u'content-length': '103', 'content-location':
'http://10.37.33.223:9696/v2.0/routers', u'content-type': 'application/json',
'status': '400'}
Body: {"NeutronError": {"message": "Unrecognized attribute(s) 'ha'",
"type": "HTTPBadRequest", "detail": ""}}
}}}
Traceback (most recent call last):
File "tempest/test.py", line 115, in wrapper
return func(*func_args, **func_kwargs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_revisions.py",
line 322, in test_update_router_extra_attributes_bumps_revision
**router_args)['router']
File
"/opt/stack/new/neutron/neutron/tests/tempest/services/network/json/network_client.py",
line 340, in create_router
resp, body = self.post(uri, body)
File "tempest/lib/common/rest_client.py", line 270, in post
return self.request('POST', url, extra_headers, headers, body, chunked)
File "tempest/lib/common/rest_client.py", line 659, in request
self._error_checker(resp, resp_body)
File "tempest/lib/common/rest_client.py", line 770, in _error_checker
raise exceptions.BadRequest(resp_body, resp=resp)
tempest.lib.exceptions.BadRequest: Bad request
Details: {u'type': u'HTTPBadRequest', u'detail': u'', u'message':
u"Unrecognized attribute(s) 'ha'"}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1688548/+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 1688548] [NEW] test_update_router_extra_attributes_bumps_revision failure
You have been subscribed to a public bug:
eg. http://logs.openstack.org/10/438610/21/check/gate-tempest-dsvm-
networking-midonet-ml2-ubuntu-xenial/a35d516/logs/testr_results.html.gz
ft1.14:
neutron.tests.tempest.api.test_revisions.TestRevisions.test_update_router_extra_attributes_bumps_revision[id-afb6486c-41b5-483e-a500-3c506f4deb49]_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2017-05-05 02:54:32,317 15758 INFO [tempest.lib.common.rest_client] Request
(TestRevisions:test_update_router_extra_attributes_bumps_revision): 400 POST
http://10.37.33.223:9696/v2.0/routers 0.071s
2017-05-05 02:54:32,317 15758 DEBUG[tempest.lib.common.rest_client] Request
- Headers: {'Content-Type': 'application/json', 'Accept': 'application/json',
'X-Auth-Token': ''}
Body: {"router": {"name": "r1", "admin_state_up": true, "tenant_id":
"5b8c1ab78ec849ff8c66db67fef80206", "ha": false}}
Response - Headers: {u'x-openstack-request-id':
'req-4daea7f8-2c7e-48a6-9d34-30538c101e45', u'date': 'Fri, 05 May 2017 02:54:32
GMT', u'connection': 'close', u'content-length': '103', 'content-location':
'http://10.37.33.223:9696/v2.0/routers', u'content-type': 'application/json',
'status': '400'}
Body: {"NeutronError": {"message": "Unrecognized attribute(s) 'ha'",
"type": "HTTPBadRequest", "detail": ""}}
}}}
Traceback (most recent call last):
File "tempest/test.py", line 115, in wrapper
return func(*func_args, **func_kwargs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_revisions.py",
line 322, in test_update_router_extra_attributes_bumps_revision
**router_args)['router']
File
"/opt/stack/new/neutron/neutron/tests/tempest/services/network/json/network_client.py",
line 340, in create_router
resp, body = self.post(uri, body)
File "tempest/lib/common/rest_client.py", line 270, in post
return self.request('POST', url, extra_headers, headers, body, chunked)
File "tempest/lib/common/rest_client.py", line 659, in request
self._error_checker(resp, resp_body)
File "tempest/lib/common/rest_client.py", line 770, in _error_checker
raise exceptions.BadRequest(resp_body, resp=resp)
tempest.lib.exceptions.BadRequest: Bad request
Details: {u'type': u'HTTPBadRequest', u'detail': u'', u'message':
u"Unrecognized attribute(s) 'ha'"}
** Affects: neutron
Importance: Critical
Status: New
** Tags: gate-failure
--
test_update_router_extra_attributes_bumps_revision failure
https://bugs.launchpad.net/bugs/1688548
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
--
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 1686627] Re: Remove QoS rule check in agent
There could be older systems with qos policies and incompatible rules. This check must remain there. ** 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/1686627 Title: Remove QoS rule check in agent Status in neutron: Invalid Bug description: Now https://bugs.launchpad.net/neutron/+bug/1586056 is implemented and merged, the check made in QoS agent extension when handling the QoS rules is not needed. In [1] and [2], a check was made to test if the set of rules in the QoS policy was supported by the backend. Now this check is not needed because during the assignment of a QoS policy to a port, this check is made. The agent will handle only rules supported by the driver. [1] https://github.com/openstack/neutron/blob/master/neutron/agent/l2/extensions/qos.py#L93 [2] https://github.com/openstack/neutron/blob/master/neutron/agent/l2/extensions/qos.py#L114 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1686627/+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 1688540] [NEW] When operation log enabled, logout returns "something went wrong"
Public bug reported: When operation log enabled, logout returns "something went wrong" with the following stacktrace: 2017-05-05 14:25:11,882 16560 ERROR django.request Internal Server Error: /auth/logout/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 223, in get_response response = middleware_method(request, response) File "/usr/lib/python2.7/site-packages/horizon/middleware/operation_log.py", line 78, in process_response log_format = self._get_log_format(request) File "/usr/lib/python2.7/site-packages/horizon/middleware/operation_log.py", line 113, in _get_log_format request.user.is_authenticated()): AttributeError: 'NoneType' object has no attribute 'is_authenticated' ** 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/1688540 Title: When operation log enabled, logout returns "something went wrong" Status in OpenStack Dashboard (Horizon): New Bug description: When operation log enabled, logout returns "something went wrong" with the following stacktrace: 2017-05-05 14:25:11,882 16560 ERROR django.request Internal Server Error: /auth/logout/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 223, in get_response response = middleware_method(request, response) File "/usr/lib/python2.7/site-packages/horizon/middleware/operation_log.py", line 78, in process_response log_format = self._get_log_format(request) File "/usr/lib/python2.7/site-packages/horizon/middleware/operation_log.py", line 113, in _get_log_format request.user.is_authenticated()): AttributeError: 'NoneType' object has no attribute 'is_authenticated' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688540/+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 1688538] [NEW] [SR-IOV] --no-qos-policy for network does not clean applied limits for ports
Public bug reported: When remove qos-policy from network limits on SR-IOV ports are not cleared - http://paste.openstack.org/show/608964/ . There are no errors in logs. If we launch another new port in this network no qos rule will apply to it, but existing one can be cleared only manually. If the same qos policy applied for the port directly with --no-qos-policy it is cleared. Reproduced on the stable/newton. Ubuntu 16.04. Ethernet controller: Intel Corporation 82599ES 10-Gigabit Kernel driver in use: ixgbe ** Affects: neutron Importance: Undecided Status: New ** Tags: qos sriov-pci-pt -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1688538 Title: [SR-IOV] --no-qos-policy for network does not clean applied limits for ports Status in neutron: New Bug description: When remove qos-policy from network limits on SR-IOV ports are not cleared - http://paste.openstack.org/show/608964/ . There are no errors in logs. If we launch another new port in this network no qos rule will apply to it, but existing one can be cleared only manually. If the same qos policy applied for the port directly with --no-qos-policy it is cleared. Reproduced on the stable/newton. Ubuntu 16.04. Ethernet controller: Intel Corporation 82599ES 10-Gigabit Kernel driver in use: ixgbe To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1688538/+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 1688536] [NEW] Backspace and enter not working in Instance Console
Public bug reported: Hi, Instance Console won't accept backspace, arrow, delete or enter keystrokes. Latest Openstack, Tested on IE, Chrome and FF. PS I am totally new to OpenStack so just starting out learning it. Thanks OpenStack release v16.0.0 IOnstalled using https://docs.openstack.org/developer/devstack/ ** Affects: nova Importance: Undecided Status: New -- 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/1688536 Title: Backspace and enter not working in Instance Console Status in OpenStack Compute (nova): New Bug description: Hi, Instance Console won't accept backspace, arrow, delete or enter keystrokes. Latest Openstack, Tested on IE, Chrome and FF. PS I am totally new to OpenStack so just starting out learning it. Thanks OpenStack release v16.0.0 IOnstalled using https://docs.openstack.org/developer/devstack/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1688536/+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 1688484] [NEW] Operations log does not contain IP address of the client
Public bug reported: For having a full audit picture available, operations log should be able to trace IP address of the client. As this data is already available from in the request, it's just a matter of exposing access to request.META['REMOTE_ADDR'] ** Affects: horizon Importance: Undecided Assignee: Mateusz Kowalski (makowals) Status: In Progress -- 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/1688484 Title: Operations log does not contain IP address of the client Status in OpenStack Dashboard (Horizon): In Progress Bug description: For having a full audit picture available, operations log should be able to trace IP address of the client. As this data is already available from in the request, it's just a matter of exposing access to request.META['REMOTE_ADDR'] To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688484/+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 1688220] Re: Operational error thrown by nova-api while serving the request
@jichenjc .
Can you please tell me what configuration in mysql needed to solve this issue.
** Changed in: nova
Status: Incomplete => Opinion
--
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/1688220
Title:
Operational error thrown by nova-api while serving the request
Status in OpenStack Compute (nova):
Opinion
Bug description:
Request to be served by nova fails with operational error:
For reference adding floating ip to the server
Input task :
Rally:
"NovaServers.bootvm_userdata_test_snat": [
{
"runner": {
"type": "constant",
"concurrency": 7,
"times": 22
},
Below traces can be found: req-d5bc233e-d1de-45d8-a353-c17ced17cd63
2017-04-28 11:20:50.598 21334 DEBUG nova.api.openstack.wsgi
[req-d5bc233e-d1de-45d8-a353-c17ced17cd63 c_rally_46c61b3d_hnwpef3T
c_rally_46c61b3d_aYPvYjVl] Action: 'action', calling method: >, body: {"addFloatingIp": {"fixed_address": "1.2.44.3",
"address": "61.26.96.145"}} _process_stack
/opt/stack/nova/nova/api/openstack/wsgi.py:623
2017-04-28 11:20:50.601 21334 DEBUG nova.compute.api
[req-d5bc233e-d1de-45d8-a353-c17ced17cd63 c_rally_46c61b3d_hnwpef3T
c_rally_46c61b3d_aYPvYjVl] [instance: c57cddc2-3aed-4c47-99b0-6f3ac16015b2]
Fetching instance by UUID get /opt/stack/nova/nova/compute/api.py:2352
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
[req-d5bc233e-d1de-45d8-a353-c17ced17cd63 c_rally_46c61b3d_hnwpef3T
c_rally_46c61b3d_aYPvYjVl] Unexpected exception in API method
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions Traceback
(most recent call last):
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/extensions.py", line 338, in wrapped
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
f(*args, **kwargs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/validation/__init__.py", line 108, in wrapper
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
func(*args, **kwargs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/compute/floating_ips.py", line 223, in
_add_floating_ip
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
expected_attrs=['flavor'])
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/common.py", line 481, in get_instance
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
expected_attrs=expected_attrs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 2355, in get
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
expected_attrs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 2315, in _get_instance
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
context, instance_uuid, expected_attrs=expected_attrs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line
184, in wrapper
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions result
= fn(cls, context, *args, **kwargs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/objects/instance.py", line 463, in get_by_uuid
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
use_slave=use_slave)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/db/sqlalchemy/api.py", line 235, in wrapper
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions with
reader_mode.using(context):
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/contextlib.py", line 17, in __enter__
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
self.gen.next()
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py",
line 944, in _transaction_scope
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
allow_async=self._allow_async) as resource:
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/contextlib.py", line 17, in __enter__
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
self.gen.next()
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py",
line 558, in _session
2017-04-2
