Wednesday, 2020-11-25

*** spatel has joined #openstack-trove01:03
sorrisonHi lxkong, I'm having a play with tempest in the gate and I'm getting build timeouts `status(current: BUILD) within the required time (196 s).`01:15
sorrisonCan't figure out why the timeout is so low01:16
sorrisonahh, of course now that I ask I figure it out01:17
*** openstackgerrit has joined #openstack-trove01:20
openstackgerritSam Morrison proposed openstack/trove-tempest-plugin master: [WIP] reinstate removed api tests  https://review.opendev.org/c/openstack/trove-tempest-plugin/+/76147201:20
*** spatel has quit IRC01:55
*** rcernin has quit IRC02:19
*** rcernin has joined #openstack-trove02:21
*** rcernin has quit IRC02:23
*** rcernin has joined #openstack-trove02:24
*** spatel has joined #openstack-trove02:33
*** spatel has quit IRC02:37
*** sapd1 has joined #openstack-trove04:17
lxkongsorrison: hi, still need help?04:54
sorrisonhey lxkong04:54
lxkongi'm preparing the trove upgrade recently so may not pay much attention to the irc04:54
sorrisonbeen trying to get the tempest tests working in the gate with that nested virt nodegroup04:55
sorrisonhttps://review.opendev.org/c/openstack/trove/+/764073 should fix the devstack issue04:55
lxkongafter jenkins +1 the other day, i can't make it work :-(04:56
sorrisonThat patch will fix your issue04:56
lxkongi will rebase mine and see if that could pass04:56
sorrisonI got a full devstack run to work ok with https://review.opendev.org/c/openstack/trove-tempest-plugin/+/761472 which depends on that04:57
openstackgerritLingxian Kong proposed openstack/trove master: Use nested virt node for trove functional test  https://review.opendev.org/c/openstack/trove/+/76363004:58
sorrisonAlthough the tempest tests fail to spin up a instance `Trove instance status: ERROR, Trove instance status description: Build error: guestagent timeout.: trove.common.exception.PollTimeOut: Polling request timed out.`04:58
sorrisonI see that in the taskmanager logs04:58
sorrisondo we get the guestagent logs in zuul somehow do you know?04:59
lxkongin tempest, no, only supported in trove-scenario-mysql-single05:00
sorrisonok, I'll look at how that is configured05:02
lxkongsorrison: may i know what are you working on when you saw this issue?05:02
sorrisonI'm trying to add back all the API tempest tests https://review.opendev.org/c/openstack/trove-tempest-plugin/+/76147205:02
lxkonghmm..i would suggest we compare what's missing with the current test cases and add those one by one, instead of restoring the previous code.05:04
lxkonge.g. we really don't need those xxx_client.py05:04
sorrisonah ok, why not?05:05
sorrisonthe separate clients in tempest are really important to ensure the api doesn't break05:06
sorrisonthat's how it's done in the other projects so be good to keep it consistent05:06
lxkongthe methods in trove_tempest_plugin/services/client.py can cover most of the api calls, no need to add extra wrapper05:06
lxkongbut i'm not against to have those, just suggestion05:07
sorrisonI just think doing it that way make it easy to introduce backwards incompatible changes05:07
lxkongalso, most of the test cases in trove_tempest_plugin/tests/api/database/instances/test_instance_actions.py have been covered in the current repo05:08
lxkongand the instance actions, user and db mgmt, backup are mixed in that file05:09
lxkongand no consideration for different datastores05:09
sorrisonYeah the API tests don't test the specific datastore, that doesn't matter05:10
lxkonge.g. we need to be able to test not only mysql, but also mariadb, and postgresql as well05:10
sorrisonit just tests the API05:10
sorrisonbut yes the API tests work on what ever backend you like05:10
sorrisonwould also be good to bring it back more inline with our tempest tests are written, makes it easier for people like me who work on lots of openstack projects05:13
lxkongyeah, if it's me, i will just add missing test cases based on the current trove tempest structure to avoid duplication05:16
lxkongsomething we could improve05:16
sorrisonok, I'll have at the scenario tests and see where the duplicates are an update this patch05:17
lxkongthe current tempest, when you run `tempest run --list-tests --regex ^trove_tempest_plugin`05:17
lxkongyou can see test cases for different datastore05:17
lxkongbut for those api tests, it'd hard coded to use `CONF.database.datastore_type`05:18
lxkongit's not ideal when you run tempest, you need to change this option frequently for different datastores05:18
lxkongalthough they are all api tests, but we still want to make sure the api does work for all the datastores that are supported.05:19
lxkongbecause same api calls could invoke the same methods of different datastores05:20
lxkongmake sense?05:20
sorrisonwe just have a tempest env for each datastore we support05:20
sorrisonit looks like you're doing that in the gate too as it is called `trove-scenario-mysql-single` ?05:21
lxkongthis one is a legacy one05:22
sorrisonso I thought you'd have a `trove-scenario-postgresql-single`05:22
sorrisonah ok05:22
lxkongthe legacy ones are maintained but shouldn't add more test cases there05:22
sorrisonit might make it less complicated if the devstack plugin and tempest were set up to assume one datastore?05:23
sorrisonit would make it faster to run too?05:23
sorrisonthen can run each datastore in parallel05:24
lxkongfor upstream CI, yes, we can set up multiple jobs to run different ds, but tempest itself should support multiple datastores in an easy way05:24
lxkongjust like how  the scenario test is implemented currently05:24
sorrisonyeah ok, it does add a lot of complication though05:25
lxkongbecause trove is kind of, special05:25
sorrisonif you go away then it is a lot of work to maintain all of this05:25
lxkongit's not that complicated, one abstract layer and different layers for different datastores05:26
lxkongno duplication at all05:26
lxkongif you want to run tests for mysql, just `tempest run --list-tests --regex ^trove_tempest_plugin | grep -i mysql`05:27
*** sapd1 has quit IRC05:27
sorrisonyeah that's all good05:27
lxkongit's also explicitly tell the developers, what datastores are supported in the upstream05:27
lxkongor tested05:28
lxkongok, i will continue with my upgrade work05:28
lxkonghopefully we could finish the upgrade in 202005:29
sorrisonwhat are you upgrading?05:29
lxkongtrove from ussuri to victoia05:29
lxkongbut there are also other services involved05:29
sorrisonyeah ok, we are going to be stuck on ussuri for a while I think until all the container stuff with upgrades is sorted out05:30
lxkongyeah, i know it's painful, but i believe we could work that out in a sensible way together.05:32
sorrisonI fear that the changes are so great that it's going to be very hard for us05:33
lxkongheh, we will see05:33
* lxkong really hopes he could travel back to 2 years ago so he could wok with sorrison together on trove, rather than by himself05:35
sorrisonyeah I feel for you :-)05:35
sorrisongood luck with the upgrade05:36
lxkongty05:36
sorrisonThe hard thing is that most deployments are a couple releases behind so we don't see these changes until it is too late05:37
lxkongyeah it's disappointed to know there were actually many other trove deployments out there but no one showed up in the community05:38
lxkongduring the hardest time of this project05:38
lxkongi know there are some other clouds have deployed trove, but have added many private changes and decided to not follow the upstream05:39
lxkongthat's totally understandable05:39
sorrisonyeah it's tricky05:39
lxkongthat's also part of open source05:40
* lxkong has to go for dinner05:40
*** sapd1 has joined #openstack-trove06:05
*** spatel has joined #openstack-trove08:25
*** spatel has quit IRC08:30
*** rcernin has quit IRC08:50
*** tosky has joined #openstack-trove08:50
*** rcernin has joined #openstack-trove09:18
*** rcernin has quit IRC09:27
*** rcernin has joined #openstack-trove09:37
*** sapd1 has quit IRC10:00
*** rcernin has quit IRC10:07
*** rcernin has joined #openstack-trove10:27
*** rcernin has quit IRC10:33
*** rcernin has joined #openstack-trove10:59
*** rcernin has quit IRC11:04
*** spatel has joined #openstack-trove11:26
*** spatel has quit IRC11:31
*** e0ne has joined #openstack-trove11:38
*** rcernin has joined #openstack-trove11:47
*** rcernin has quit IRC12:07
*** rcernin has joined #openstack-trove13:21
*** e0ne has quit IRC13:25
*** e0ne has joined #openstack-trove13:25
*** rcernin has quit IRC13:25
*** congnt96 has joined #openstack-trove14:37
*** sapd1 has joined #openstack-trove14:58
*** irclogbot_0 has quit IRC16:41
*** irclogbot_3 has joined #openstack-trove16:47
*** e0ne has quit IRC18:42
*** congnt96 has quit IRC21:03
*** sapd1 has quit IRC21:05
*** sapd1 has joined #openstack-trove21:17
*** e0ne has joined #openstack-trove21:30
*** e0ne has quit IRC21:31
*** rcernin has joined #openstack-trove21:35
*** rcernin has quit IRC21:37
*** rcernin has joined #openstack-trove21:38
*** e0ne has joined #openstack-trove21:46
*** e0ne has quit IRC21:52
openstackgerritLingxian Kong proposed openstack/trove master: Support --image-tags for trove-manager datastore_version_update command  https://review.opendev.org/c/openstack/trove/+/76424522:09
*** rcernin has quit IRC22:54
*** rcernin has joined #openstack-trove22:54
openstackgerritMerged openstack/trove master: Support --image-tags for trove-manager datastore_version_update command  https://review.opendev.org/c/openstack/trove/+/76424523:50
*** tosky has quit IRC23:51

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!