Posted	Nick	Remark
#openstack-sdks - 2018-02-27
21:03:41	openstackgerrit	Slawek Kaplonski proposed openstack/python-openstacksdk master: Functional test for set_tags on Neutron resources https://review.openstack.org/548405
#openstack-sdks - 2018-02-28
02:01:54	openstackgerrit	Dongcan Ye proposed openstack/python-openstacksdk master: Network: Add tag support for QoS policy https://review.openstack.org/547372
02:09:15	openstackgerrit	Dongcan Ye proposed openstack/python-openstacksdk master: Network: Add tag support for security group https://review.openstack.org/547369
02:13:17	openstackgerrit	Dongcan Ye proposed openstack/python-openstacksdk master: Network: Add tag support for floating ip https://review.openstack.org/547366
07:52:25	tobixen	I've set up a devstack, and I'm trying to run functional tests towards it. Set up a simple clouds.yaml to access devcloud, but I'm constantly getting 400s from the server, "Expecting to find domain in project"
07:52:29	tobixen	what am I missing?
07:53:14	tobixen	trying to run functional tests for shade, that is.
08:19:39	frickler	tobixen: devstack should already create a working /etc/openstack/clouds.yaml, maybe use that one? or compare to yours to see where the issue might be?
08:38:54	tobixen	frickler: thanks, that seems to help
08:39:41	tobixen	actually, already got things working by trial and error, adding "project_domain_name: default" and "domain_name: default" to my self-created clouds.yaml
09:34:24	tobixen	still 6 tests failing for me when running functional tests on shade, using the master branch
09:37:37	mordred	tobixen: hrm... I'd expect them to work, so that's not happy-making - which tests?
09:42:10	tobixen	let's see ... https://ipfs.io/ipfs/QmU86ETBVHoTaiA4CTcJmPQTFoBevytsMyf6hDDVsbprpV
09:43:48	slaweq	mordred: hi
09:44:16	slaweq	I know that You are busy this week but if You would have a minute, please take a look at https://review.openstack.org/#/c/548405/ - it's only some additional functional tests
09:44:20	slaweq	thx in advance
09:49:54	tobixen	mordred: test logs at https://ipfs.io/ipfs/QmU86ETBVHoTaiA4CTcJmPQTFoBevytsMyf6hDDVsbprpV that is. Rolled out a devstack VM on our openstack, and ran shade functional tests from the same VM
10:00:27	mordred	tobixen: awesome - I'll check that in just a few minutes ...
10:00:29	mordred	slaweq: will do
10:02:25	slaweq	mordred: thx
10:12:26	frickler	tobixen: mordred: I'm getting a similar set of failures when I run that locally, wondering what the gate sets up differently for devstack. looking at a log, "disable_service tempest" may have some effect
10:22:27	openstackgerrit	Merged openstack/python-openstacksdk master: modify typos of word password https://review.openstack.org/542635
11:12:24	tobixen	I added "disable_service tempest" and upgraded devstack to newest master, and ... tests passed
11:13:42	tobixen	frickler: mordred: ^
11:15:47	frickler	tobixen: thanks for confirming my guess :)
13:25:26	tobixen	frickler: still doing research on this one. It may seem that things aren't well-enough cleaned up when doing "unstack ; stack", perhaps the trick to get tests going is to start devstack completely from scratch.
13:40:57	dtroyer	tobixen: have you tried using clean.sh rather than unstack.sh? Clean gets more aggressive at removing things, unstack was meant for a quick(-ish) restart.
13:52:05	mordred	tobixen, frickler: oh, fun!
13:54:15	mordred	tobixen, frickler: looking at the traceback (sorry, jst got to it) I think even though there's a workaround, we could/should also fix the conflicts
14:13:25	openstackgerrit	Thomas Herve proposed openstack/python-openstacksdk master: Allow not resolving outputs on get stacks https://review.openstack.org/548595
14:46:19	openstackgerrit	Merged openstack/python-openstacksdk master: Functional test for set_tags on Neutron resources https://review.openstack.org/548405
15:15:34	openstackgerrit	Merged openstack/osc-lib master: Updated from global requirements https://review.openstack.org/538478
15:53:06	openstackgerrit	Corey Bryant proposed openstack/cliff master: Align parsed() call with cmd2 versions >= 0.7.3 https://review.openstack.org/548625
16:39:28	openstackgerrit	Matthew Treinish proposed openstack/python-openstackclient master: Cleanup error messages on failure https://review.openstack.org/548656
16:42:32	openstackgerrit	Matthew Treinish proposed openstack/python-openstackclient master: Cleanup tox.ini for functional tests https://review.openstack.org/548657
16:45:12	mtreinish	dtroyer: ^^^ still reading things, but that first patch might help
16:45:23	mtreinish	I'm having a hard time reading the giant blob of text
16:45:57	dtroyer	I think the entry point failures is the key, that they are there at all, not which ones specifically
16:46:39	dtroyer	I've narrowed it down to working fine locally without https://review.openstack.org/#/c/538478/ and failing with it, and that commit is the only difference in the venv
16:46:59	dtroyer	the dependencies that changed in there do not change between test runs
16:47:08	dtroyer	(I am removing the venv each tme so it is always refreshed)
16:48:32	dtroyer	that cleanup is certainly worth doing no matter what, thanks
16:49:31	mtreinish	yeah, parsing the giant blob in the logs I see the entrypoint failure now
16:49:39	mtreinish	and I agree that's likely the issue
16:50:41	mtreinish	I just looked at the pip freeze logs from the run and it seems like there are some weird issues there: http://logs.openstack.org/78/538478/5/check/osc-functional-devstack-tips/356323d/tox/functional-5.log
17:11:51	openstackgerrit	Merged openstack/osc-lib master: Add project lookup utils https://review.openstack.org/522861
17:27:24	openstackgerrit	OpenStack Proposal Bot proposed openstack/cliff master: Updated from global requirements https://review.openstack.org/548672
17:39:11	tobixen	dtroyer: thanks, clean.sh did the trick. Just verified that I managed getting some tests failing with a fresh devstack, and getting all tests passing by disabling tempest and doing a clean.sh
19:57:52	frickler	mordred: this one looks fun, too ;) https://launchpad.net/bugs/1751822
19:57:54	openstack	Launchpad bug 1751822 in cliff "EXCEPTION of type 'AttributeError' when using 'help' from openstack-cli" [Undecided,In progress] - Assigned to Corey Bryant (corey.bryant)
20:12:44	openstackgerrit	Corey Bryant proposed openstack/cliff master: Align parsed() call with cmd2 versions >= 0.7.3 https://review.openstack.org/548625
20:16:08	openstackgerrit	Corey Bryant proposed openstack/cliff master: Align parsed() call with cmd2 versions >= 0.7.3 https://review.openstack.org/548625
22:16:27	openstackgerrit	Tobias Brox proposed openstack-infra/shade master: Simple fix making the TestNetwork functional test cleanup more robust and a bit faster, by passing network id instead of network name. Task: 6594 Story: 2001617 https://review.openstack.org/548714
22:18:16	openstackgerrit	Tobias Brox proposed openstack-infra/shade master: Functional test robustness and performance fix. In TestNetwork._cleanup_networks, pass network id instead of network name. Task: 6594 Story: 2001617 https://review.openstack.org/548714
22:35:19	openstackgerrit	Tobias Brox proposed openstack-infra/shade master: Add subnetpool_name_or_id parameter to create_subnet https://review.openstack.org/548722
#openstack-sdks - 2018-03-01
02:12:30	mordred	mtreinish: yah - those warnings are a known issue with python installed from git repos on zuul nodes - pip parses git origin urls to find the string to use to print the version of the package - but there is no origin url on the repos there - it just produces ugly output though
02:22:57	openstackgerrit	Robin Cernin proposed openstack/python-openstackclient master: Adds missing Project information in server list https://review.openstack.org/548733
03:31:34	openstackgerrit	Robin Cernin proposed openstack/python-openstackclient master: Adds missing Project information in server list https://review.openstack.org/548733
03:40:12	openstackgerrit	Monty Taylor proposed openstack-infra/shade master: Functional test robustness and performance fix https://review.openstack.org/548714
03:40:26	openstackgerrit	Monty Taylor proposed openstack-infra/shade master: Add subnetpool_name_or_id parameter to create_subnet https://review.openstack.org/548722
03:43:33	mnaser	mordred: i see i'm not the only one who's unable to sleep :p
03:43:39	mordred	mnaser: :)
05:07:27	openstackgerrit	Merged openstack-infra/shade master: Functional test robustness and performance fix https://review.openstack.org/548714
05:20:46	openstackgerrit	Robin Cernin proposed openstack/python-openstackclient master: Adds missing Project information in server list https://review.openstack.org/548733
05:23:35	openstackgerrit	Robin Cernin proposed openstack/python-openstackclient master: Adds missing Project information in server list https://review.openstack.org/548733
05:40:28	openstackgerrit	Robin Cernin proposed openstack/python-openstackclient master: Adds missing Project information in server list https://review.openstack.org/548733
07:25:52	openstackgerrit	OpenStack Proposal Bot proposed openstack/python-openstackclient master: Imported Translations from Zanata https://review.openstack.org/548850
09:45:38	openstackgerrit	Tobias Brox proposed openstack-infra/shade master: Fix proper domain support in user role grants https://review.openstack.org/548887
10:49:26	openstackgerrit	Dean Troyer proposed openstack/osc-lib master: Revert "Updated from global requirements" https://review.openstack.org/548908
15:49:03	openstackgerrit	Dongcan Ye proposed openstack/python-openstacksdk master: DNM: osc functional check https://review.openstack.org/548977
18:05:31	frickler	mordred: shouldn't https://review.openstack.org/548702 be on master initially?
20:32:04	slaweq	mordred: hi
20:32:37	slaweq	mordred: I have a question about https://review.openstack.org/#/c/548737/ - why this revert of revert is proposed?
20:33:03	slaweq	I see that this patch wasn't even merged: https://review.openstack.org/#/q/1ef3ce7ac0ab2598a494e85b8575b0114f562296
20:33:50	slaweq	mordred: sorry if I missed something but I don't understand now if there is any issue with this preferred FIP or not :)
20:39:14	frickler	slaweq: iiuc your original patch introduced a regression. the revert is amended with a test for that regression. the revert of the revert is being edited so that it hopefully will fix both the original issue and the regression
20:39:55	slaweq	frickler: but rever wasn't merged so why "revert of revert"?
20:39:57	slaweq	:)
20:41:12	frickler	slaweq: mordred is preparing two steps at once, so that when both are ready and can be merged in one batch, things wills work fine
20:41:30	slaweq	frickler: ok, thx :)
20:41:34	frickler	without the first revert, it would not be so easy to show the test working
20:41:47	frickler	see https://storyboard.openstack.org/#!/story/2001619 for a description of the regression
20:43:01	slaweq	ok, I see now
20:43:23	slaweq	so both are necessary and we have to merge it on proper order, right?
21:14:49	frickler	slaweq: yes. might instead do two new patches, one adding the tests and one fixing the regression. but that's a matter of taste I'd say
21:15:29	slaweq	frickler: yes, now I at least undersand why there are two patches :)
21:15:37	slaweq	thx a lot for help with understanding that
22:17:05	openstackgerrit	Tobias Brox proposed openstack-infra/shade master: Fix proper domain support in user role grants https://review.openstack.org/548887
#openstack-sdks - 2018-03-02
06:22:27	openstackgerrit	Robin Cernin proposed openstack/python-openstackclient master: Adds missing Project information in server list https://review.openstack.org/548733
07:40:12	openstackgerrit	Monty Taylor proposed openstack-infra/shade master: Fix private_v4 selection related to floating ip matching https://review.openstack.org/549116
07:46:11	mordred	slaweq, frickler: I've found the actual issue ^^ so I think we'll be in a position to just land a fix ratherthan a revert and a revert ...
07:47:18	mordred	slaweq, frickler: I'm not sure I had an *actual* plan with the twopatches - as much as ansible inventory was broken for some people and that seemed like a thing that should be fixed quickly - but luckily the real problem isn't too bad
07:47:39	mordred	and also yes ... should fix it on master too :)
07:52:11	openstackgerrit	Monty Taylor proposed openstack-infra/shade master: Fix private_v4 selection related to floating ip matching https://review.openstack.org/549116
07:52:55	mordred	slaweq, frickler: ^^ and that should fix the 2 tests that the fix broke (yay for nova network!)
07:54:01	slaweq	mordred: thx, +2 already :)
07:54:25	openstackgerrit	Monty Taylor proposed openstack/python-openstacksdk master: Fix private_v4 selection related to floating ip matching https://review.openstack.org/549117
07:54:26	slaweq	please remember to cherry-pick it to openstacksdk also as it is there as well
07:54:35	mordred	slaweq: done! :)
07:54:47	mordred	slaweq: I will be happy when we no longer need to cherry-pick between the two

Earlier   Later