| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2019-08-02 | |||
| 16:53:49 | mordred | that seems really off - and like there's something missing down deep somewhere | |
| 16:54:12 | gtema | exact | |
| 16:54:33 | gtema | and it's terrible to debug it, since no propel logging is possible | |
| 17:35:58 | gtema | that's some mistery. When I am copying all those ansible functions into unit tests to be able to reproduce - it works, under ansible it fails | |
| 17:38:32 | gtema | the iteritems (iter(d.items(**kw)) return empty values from ansible, but correct from sdk unit tests | |
| 18:16:53 | openstackgerrit | Matt Riedemann proposed openstack/openstacksdk master: Fix DeprecationWarning for using logger.warn https://review.opendev.org/674401 | |
| 18:16:58 | mriedem | easy fix for something that's now blowing up the nova functional test job logs ^ | |
| 18:17:03 | mriedem | https://logs.opendev.org/61/673961/1/gate/nova-tox-functional-py36/a4cb2af/job-output.txt.gz#_2019-08-01_17_51_24_070219 | |
| 20:02:06 | efried | mriedem: That UnsupportedServiceVersion thing - is that showing up in devstack tests or only functional? | |
| 20:02:41 | mriedem | let me ask the magic 8 ball | |
| 20:02:44 | mriedem | i mean logstash | |
| 20:04:20 | mriedem | both | |
| 20:04:27 | mriedem | http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22UnsupportedServiceVersion%3A%20Service%20placement%20has%20no%20discoverable%20version.%5C%22&from=7d | |
| 20:05:29 | efried | mordred: Can we make placement a known, supportes service type at v1.x with an empty Proxy? | |
| 20:09:11 | mordred | efried: absolutely. let me make you a patch | |
| 20:09:22 | efried | thanks! | |
| 20:09:42 | mordred | efried: does placement need to do version discovery on its root endpoint and/or microversions? | |
| 20:09:44 | efried | mordred: that'll get rid of those warnings, yah? | |
| 20:09:48 | mordred | yeah | |
| 20:10:16 | efried | mordred: There's only one major version rn. | |
| 20:10:29 | efried | By microversion discovery, you mean "I need an endpoint that can handle at least 1.XX"? | |
| 20:11:01 | mordred | well - I mean getting the min/max microversion range from the endpoint - so yeah. I guess the question is - does placement do microversions | |
| 20:11:18 | efried | Placement definitely "does" microversions, yeah. | |
| 20:11:22 | mordred | awesome. | |
| 20:11:45 | mordred | is there a placement.example.com/v1 ? | |
| 20:11:53 | mordred | you know - how about I go read the docs and then ask you follow up questions | |
| 20:12:15 | efried | mordred: And especially if you discover holes in the docs that don't answer these questions, let us know (or open stories or whatever) | |
| 20:12:50 | efried | mordred: cdent has been in charge of this kind of stuff, so I'm pretty sure we're following all the rules wrt discovery documents and endpoint construction and whatnot. | |
| 20:13:03 | mordred | cool | |
| 20:13:19 | efried | like, I'm 95% sure you won't find snowflake behavior | |
| 20:15:18 | efried | efried@canuc:~$ curl http://192.168.218.27/placement | |
| 20:15:18 | efried | {"versions": [{"status": "CURRENT", "min_version": "1.0", "max_version": "1.36", "id": "v1.0", "links": [{"href": "", "rel": "self"}]}]} | |
| 20:15:31 | efried | that href="" is suspicious | |
| 20:22:11 | efried | mordred: Poking at my devstack, it is looking like we do not have versioned endpoints for placement. | |
| 20:22:26 | efried | So forget what I said about cdent, and let's burn him at the stake. | |
| 21:54:25 | mordred | efried: that's fine - I've already got sdk provisions for this sort of thing :) | |
| #openstack-sdks - 2019-08-03 | |||
| 07:09:00 | openstackgerrit | Artem Goncharov proposed openstack/openstacksdk master: Enable ansible module test for keypair to check return data https://review.opendev.org/674333 | |
| 18:59:53 | openstackgerrit | Artem Goncharov proposed openstack/openstacksdk master: Enable ansible module test for keypair to check return data https://review.opendev.org/674333 | |
| 19:18:40 | openstackgerrit | Merged openstack/openstacksdk master: Add CloudRegion helper method for arbitrary endpoints https://review.opendev.org/674130 | |
| 19:20:05 | openstackgerrit | Merged openstack/openstacksdk master: Fix README example for cloud layer https://review.opendev.org/674041 | |
| 19:20:06 | openstackgerrit | Merged openstack/openstacksdk master: Move the history lesson into the docs https://review.opendev.org/674045 | |
| 20:22:38 | openstackgerrit | Merged openstack/os-client-config master: Add Python 3 Train unit tests https://review.opendev.org/669450 | |
| #openstack-sdks - 2019-08-04 | |||
| 12:56:44 | openstackgerrit | norman shen proposed openstack/python-openstackclient master: support create domain project https://review.opendev.org/674487 | |
| #openstack-sdks - 2019-08-05 | |||
| 07:57:13 | openstackgerrit | Merged openstack/openstacksdk master: Fix DeprecationWarning for using logger.warn https://review.opendev.org/674401 | |
| 08:58:08 | openstackgerrit | Bence Romsics proposed openstack/python-openstackclient master: Add command: router add/remove route --route https://review.opendev.org/674325 | |
| 10:18:34 | openstackgerrit | Vishakha Agarwal proposed openstack/openstacksdk master: Add application credential CRUD support https://review.opendev.org/669331 | |
| 12:10:25 | gtema | dtantsur, mordred, Shrews: https://review.opendev.org/#/c/674333/ is really important (event as a hotfix), since without it Ansible can't get/create keypairs | |
| 12:10:44 | gtema | dtantsur, can you please have a look, whether ironic failure in the tests is related or not | |
| 12:11:20 | gtema | this change also includes switching Ansible tests to Py3, since the problem is visible only there and more and more Platforms are delivering py3 only ansible | |
| 13:21:40 | mordred | dtantsur|afk, Shrews: yeah - I recommend looking at that patch from gtema - and when it lands let's cut a bugfix release with it | |
| 13:22:01 | mordred | being broken for ansible on python3 is a bad thing | |
| 13:22:17 | mordred | should we add a second run of the ansible tests to cover python2? | |
| 13:26:59 | efried | mordred: should I nack https://review.opendev.org/#/c/674515/ on the theory that that placement placeholder will be in place soon? | |
| 14:09:08 | gtema | mordred: yeah, adding ansible py2 would be likely good | |
| 14:15:26 | mordred | efried: yeah - I'll get you one today | |
| 14:22:17 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Add empty placement proxy https://review.opendev.org/674620 | |
| 14:22:18 | mordred | efried: there's the first stab at it | |
| 14:23:36 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Add empty placement proxy https://review.opendev.org/674620 | |
| 14:31:45 | efried | \o/ Thanks mordred | |
| 15:38:12 | Shrews | dtantsur|afk: FYI, looks like the asserts in openstack.tests.functional.baremetal.test_baremetal_node compare lists (node.traits) in unsorted order and randomly fail (see https://logs.opendev.org/33/674333/3/check/openstacksdk-functional-devstack-ironic/0e8be8d/testr_results.html.gz) | |
| 15:39:34 | Shrews | mordred: do you remember who added magnum support to sdk? | |
| 15:40:51 | mordred | Shrews: I do not | |
| 15:40:58 | Shrews | oh, maybe yolanda | |
| 15:41:03 | mordred | oh - yeah - I think so | |
| 15:55:35 | openstackgerrit | David Shrewsbury proposed openstack/openstacksdk master: Fix bm tests: sort lists being compared https://review.opendev.org/674640 | |
| 15:55:43 | Shrews | dtantsur|afk: ^^ | |
| 16:05:35 | mordred | Shrews: ++ | |
| 16:14:04 | corvus | when i use the interactive form of the cli, i get this exception: http://paste.openstack.org/show/755535/ | |
| 16:14:34 | corvus | same command works fine non-interactively | |
| 16:27:10 | mordred | dtroyer: ^^? | |
| 16:30:33 | frickler | seems related to cmd2>=0.9.0, if I install cmd==0.8.9 things work fine | |
| 16:30:44 | mordred | frickler: "neat" | |
| 16:33:20 | frickler | the newer ones also give errors when doing interactive mode with options, like "openstack --os-cloud mycloud", which also works fine with older cmd2 | |
| 16:38:50 | dtroyer | yeah, we've not kept up with cmd2… I thought we capped it somewhere? | |
| 16:38:53 | mordred | frickler: so should we be pinning cmd2 for now? | |
| 16:38:56 | mordred | dtroyer: jinx | |
| 16:39:21 | dtroyer | maybe not in stable branches, or far enough back in them? | |
| 16:40:07 | mordred | corvus: what version of osc are you using there? | |
| 16:41:12 | corvus | openstack 3.19.0 | |
| 16:43:27 | mordred | corvus: and, if you don't mind, what version of cliff is installed in that venv? | |
| 16:44:48 | corvus | cliff==2.15.0 | |
| 16:45:44 | mordred | thanks | |
| 16:47:57 | frickler | I tested some older versions of cliff with no effect, versions 0.9.x of cmd2 give varying errors, so based on that short test list, I'd advise to cap cmd2<0.9 for now | |
| 16:52:14 | mordred | frickler: I don't know why it's not capped | |
| 16:52:58 | mordred | OH | |
| 16:53:00 | mordred | it's because I can't read | |
| 16:54:06 | openstackgerrit | Monty Taylor proposed openstack/cliff master: Pin cmd2 on python3 as well https://review.opendev.org/674652 | |
| 16:54:10 | mordred | frickler, dtroyer: ^& | |
| 17:01:05 | efried | mordred: This [1] is likely because of the way we're (not) fixturing [2], which was pretty weak to begin with. I suspect I can get moving by adding a mock for get_endpoint_from_catalog, and then possibly also get_session_client... but I'm kinda not sure I should keep chasing fixtures for sdk internals like that. Thoughts? | |
| 17:01:05 | efried | [1] https://logs.opendev.org/25/674625/1/check/nova-tox-functional-py36/27b16b6/testr_results.html.gz | |
| 17:01:05 | efried | [2] https://opendev.org/openstack/nova/src/branch/master/nova/tests/fixtures.py#L2125 | |
| 17:13:26 | mordred | efried: hrm. you're making my brain do work | |
| 17:13:44 | mordred | efried: I agree - I don't think you should need to chase fixtures for internals lke that | |
| 17:14:11 | efried | I did open a story for sdk to publish fixtures for this purpose, but people are busy | |
| 17:14:22 | mordred | yeah. and I really want to publish those | |
| 17:14:46 | efried | perhaps initially it's as simple as moving the one from nova into sdk, and it can get better refined later. | |
| 17:14:51 | mordred | efried: maybe for today just adding in a get_endpoint_from_catalog mock - but let's elevate the priority of getting you a real fixture | |
| 17:15:19 | efried | okay, I'll try that on the nova test patch and see what shakes out. | |
| 17:15:55 | mordred | efried: cool. and I'll see if I can sort out something WRT workable long-term exported fixture status | |
| 17:16:45 | efried | thanks mordred | |