Thursday, 2017-01-12

*** FL1SK has joined #openstack-mistral00:10
*** dprince has quit IRC00:22
*** rbrady has quit IRC00:43
*** jamielennox is now known as jamielennox|away00:50
*** jamielennox|away is now known as jamielennox01:21
kongping rakhmerov01:28
kongrakhmerov: a question for named lock implementation. according to https://github.com/openstack/mistral/blob/master/mistral/db/v2/sqlalchemy/api.py#L1538, what if two threads are trying to create lock using the same name?01:30
*** hparekh has joined #openstack-mistral04:25
*** ist has joined #openstack-mistral06:06
rakhmerovkong: I'm here06:59
rakhmerovthe second thread will block until the lock is released (1st TX is finished)07:00
rakhmerovand please what you mean by threads07:00
rakhmerovplease clarify..07:00
istDo you have any idea why tripleo buildbot fail in following review: https://review.openstack.org/#/c/41731407:46
istit seems some host is unreachable, I just do not know what could be the root cause...07:47
d0ugalist: looking08:17
istthanks!08:17
openstackgerritDougal Matthews proposed openstack/mistral: Insecure flag added to openstack context  https://review.openstack.org/41731408:18
d0ugalI just rechecked it once more and I'll track this build, I see it failed a few times in a row08:18
*** jpich has joined #openstack-mistral08:31
*** jpich has quit IRC08:37
*** jpich has joined #openstack-mistral08:38
*** ist has quit IRC08:58
*** ist has joined #openstack-mistral09:08
d0ugalIt failed again :(09:10
d0ugalI am trying to get help in #tripleo09:11
openstackgerritRenat Akhmerov proposed openstack/python-mistralclient: Add user and project domain name parameters for target cloud  https://review.openstack.org/41933209:16
ddejad0ugal, I've just read your discussion with thrash09:18
d0ugalddeja: Morning :)09:18
d0ugalYeah, we got a bit confused.09:18
ddejasome bad assumptions09:18
ddejaI was thinking that 'fake' is only used for testing purpose09:19
d0ugalYeah09:19
ddejaand therefore all of the flags are in mistral.conf09:19
ddejaso I don't have to treat the 'fake' driver any special way09:19
ddejasince the rpc_utils are only about preparing the config options for rpc layer09:20
rakhmerovist: hi09:20
ddejad0ugal: I'll send a patch in a minute09:20
d0ugalddeja: thanks!09:20
ddejad0ugal: is there a bug for that?09:20
d0ugalddeja: no, I don't think so09:20
rakhmerovist: on https://review.openstack.org/#/c/417314/ not only tripleO gate fails, do you think the other failure is related with your changes?09:20
d0ugalddeja: I think we were unsure if the problem was with us or the code :)09:21
ddejad0ugal: OK, so I'll submit one09:21
d0ugalddeja: thanks09:21
d0ugalrakhmerov, ist: I can confirm the TripleO failure is unrelated. I am still looking into it (or still trying to find somebody that can help me!)09:22
rakhmerovd0ugal, ddeja: hi guys, sorry being late for your discussion09:22
rakhmerovwhat's wrong with 'fake'?09:22
rakhmerovif you can tell with a couple of words..09:22
d0ugalrakhmerov: I think the issue is that it still attempts to connect to rabbit09:22
d0ugalbut my understanding could be wrong.09:23
rakhmerovyou mean even if we have 'fake' in config?09:23
ddejad0ugal, rakhmerov, it's not trying to connect to rabbit09:23
d0ugalrakhmerov: yes09:23
d0ugaloh :)09:24
ddejabut there is an assumption that some flags in config would be provided09:24
ddejalike 'rabbit_host', 'rabbit_port' and so on09:24
rakhmerovaah, yeah09:24
*** shardy has joined #openstack-mistral09:25
rakhmerovI think I even made a comment when doing some refactoring in RPC a couple of months ago09:25
rakhmerovtrue09:25
ddejaI'll fix it in a minute09:25
rakhmerovbecause in any case we call that method get_oslo_config or something..09:25
rakhmerovor get_rabbit_config09:25
ddejahm, it may not be this easy to fix it09:26
rakhmerov:))09:26
ddejait may brake some unit tests09:26
ddejaI have to check09:26
rakhmerovddeja: this is important, please try to fix it. As a matter of fact, now what we have in terms of flexible RPC layer is not 100% flexible09:27
rakhmerovin this aspect09:27
rakhmerovwe always expect rabbit09:27
rakhmerovok, thanks for clarification..09:28
ddejarakhmerov: sure09:28
ddejarakhmerov: BTW, I've looked onto kombu failure in ist's patch09:28
rakhmerovok09:28
ddejabut I have never seen this test fail befora09:28
ddejaso it *may* be related to the patch itself09:28
rakhmerovok09:30
rakhmerovist: here? Can you have a look at this?09:31
istI just looking into it and it seems following testcase fails:09:32
istmistral_tempest_tests.tests.api.v2.test_executions.ExecutionTestsV2.test_update_nonexistent_execution09:32
isti think so it is not related to my patch09:33
kongrakhmerov: i was trying to understand the named lock. suppose there are 2 threads(or green threads, whatever) are both creating named lock record using same name, they will both succeed? in sequence?09:37
rakhmerovist: ok09:37
openstackgerritOpenStack Proposal Bot proposed openstack/mistral: Updated from global requirements  https://review.openstack.org/41934409:37
rakhmerovkong: nope, not both09:37
kongthe 2nd will fail?09:38
rakhmerovsec, I'll find an article09:38
rakhmerovno, it will hang09:38
kongrakhmerov: appriciate09:38
ddejad0ugal, thrash: https://bugs.launchpad.net/mistral/+bug/165589509:38
openstackLaunchpad bug 1655895 in Mistral "Rabbit related flags need to be set when using fake driver" [Undecided,New]09:38
rakhmerovkong: http://blog.udby.com/archives/1409:40
* kong is reading09:40
kongrakhmerov: thanks!09:40
rakhmerovplease read it, after that it'll be clear to you how it works09:40
rakhmerovjust one thing in addition: with green threads there are problems, they are not even related to these locks, I can tell in details too09:41
kongrakhmerov: will get back to you if i have further questions after reading09:42
kongthanks again09:42
rakhmerovso that's why we handle RPC messages in engine w/o using green threads09:42
rakhmerovok09:42
rakhmerovkong: these locks are fully tested, they work09:42
kongcool09:42
openstackgerritJeremy Liu proposed openstack/python-mistralclient: Update .gitignore  https://review.openstack.org/41937509:55
openstackgerritDawid Deja proposed openstack/mistral: Stop excpecting to have rabbit flags set when using fake driver  https://review.openstack.org/41938810:10
ddejathrash: Hi, could you please check if this fixes your problem with fake driver? https://review.openstack.org/#/c/41938810:12
ddeja@CC d0ugal ^^ ;)10:12
d0ugalddeja: yay, thanks!10:13
d0ugalfwiw, I don't think thrash will be around for a few hours yet :)10:13
d0ugalbut I'll try it in a bit, just in the middle of something else.10:13
ddejad0ugal: OK, hope he'll check it once he's around10:13
d0ugalyup, sure he will - I've added him as a reviewer.10:14
ddejad0ugal: also timeout or exchange in this: https://github.com/openstack/mistral/blob/master/mistral/utils/rpc_utils.py#L107-L11010:14
ddejamay caouse a problem when using fake10:15
ddejacause*10:15
ddejaso if the patch itself won't work, they can be safely deleted as long as fake is used10:16
ddejaand I'll make adjustements in my patch10:16
*** AlexeyAbashkin has joined #openstack-mistral10:17
*** shardy has quit IRC10:51
*** shardy has joined #openstack-mistral11:14
rakhmerovkong: sorry for making https://review.openstack.org/#/c/414508 a long discussion, I just find it very important and want to make sure we discuss it within a bigger crowd11:21
rakhmerovddeja, d0ugal: btw, please also take a look at https://review.openstack.org/#/c/41450811:21
rakhmerovd0ugal: it's also a little bit related to our actions refactoring11:22
d0ugalSure11:23
d0ugalLots of -111:23
rakhmerovyeah, -1s are not so important11:23
rakhmerovI guess we're just trying to find the best design11:23
rakhmerovddeja: can you please explain your changes in https://review.openstack.org/#/c/419388/1/mistral/utils/rpc_utils.py ?11:24
rakhmerovwhy do we still need to try to call _get_rabbit_info_from_oslo in case of "fake"?11:24
rakhmerovseems weird to me11:24
openstackgerritRenat Akhmerov proposed openstack/python-mistralclient: Add user and project domain name parameters for target cloud  https://review.openstack.org/41933211:36
*** shardy has quit IRC11:55
*** shardy has joined #openstack-mistral11:56
rakhmerovd0ugal, hparekh, kong: guys, can you please review and approve https://review.openstack.org/#/c/414533/ ?12:05
rakhmerovit fixes the gate12:05
rakhmerovsharatss: seems like it doesn't make to recheck patches for now (you just did for https://review.openstack.org/#/c/419388/ ), I guess we need help from tripleO to fix the gate12:14
rakhmerovd0ugal: do you know if that's being investigated?12:14
sharatssrakhmerov: yes got it12:15
sharatssrakhmerov: just found debugging-tripleo-gate-failures-in-mistral doc written by d0ugal12:15
d0ugalsharatss: :-D12:15
d0ugalrakhmerov, sharatss: there are people working on it12:16
d0ugalhttps://bugs.launchpad.net/tripleo/+bug/165591912:16
openstackLaunchpad bug 1655919 in tripleo "CI: Openvswitch agent fails because can't import tinyrpc.server module" [Critical,Triaged]12:16
d0ugalThat is the bug FWIW12:16
sharatssd0ugal: thanks :)12:17
thrashddeja: sure... I'll check it out right away. :)12:22
rakhmerovd0ugal: ok, thanks :)12:24
*** dprince has joined #openstack-mistral12:35
ddejarakhmerov: I was out for 1.5hour, I'll lok in 15 minutes12:43
rakhmerovok12:43
ddejarakhmerov: about still calling _get_rabbit_info_from_oslo12:43
thrashddeja: wfm12:44
ddejathrash: great, thanks :)12:44
thrashnow... when I run 'run_functional_test.sh' it's complaining about credentials. :(12:44
ddejarakhmerov: If I remember correctly, some tests rely on info gathered inside this function12:45
ddejabut I'm not sure, I can check12:45
ddejathrash: after applaying the patch?12:45
thrashddeja: yes12:45
thrashto be fair, I was getting that before. :D12:45
ddejaufff12:46
ddejaI was terrified that some functional tests rely on rpc_utils12:46
thrashhaha12:46
thrashno, sorry to get your heart racing.12:46
ddejathrash: I remember that I have trouble with running functional tests on anything but devstack12:47
rakhmerovddeja: ok, I see12:47
rakhmerovdo you remember what tests?12:47
ddejathrash: and I've run them using tempest, not calling directly run_functional_tests12:47
ddejarakhmerov: that was some tests regarding the kombu driver12:48
ddejabut I may mixed something12:48
ddejaand I wanted to have this patch ASAP, so I went the 'safe' way12:48
ddejaI'll check in a minute if we can delete it completetly in case of fake12:48
thrashddeja: interesting...12:49
thrashddeja: that seems to be working... Calling tempest directly.12:49
thrashddeja: hold on that... it's running unit tests atm12:49
*** gongysh has joined #openstack-mistral12:52
ddejathrash: I'm glad I could help, a little12:53
thrashddeja: definitely a start. :)12:54
thrashddeja: this: nosetests -v mistral_tempest_tests/tests/api/v2/12:57
thrashgets me this: InvalidCredentials: Invalid Credentials12:57
thrashDetails: Credentials are: {'username': None, 'project_name': None, 'user_id': None, 'tenant_name': None, 'tenant_id': None, 'project_id': None} Password is not defined.12:57
ddejathrash: I have one idea13:00
ddejawhy you got this, give mi a second to confirm13:00
ddejathrash: well, it works on my devstack13:03
ddejathrash: do you run it from the tempest directory?\13:03
thrashddeja: no... Just running it from mistral dir with tempest installed in venv13:06
*** gongysh has quit IRC13:07
*** rbrady has joined #openstack-mistral13:07
*** rbrady has quit IRC13:07
*** rbrady has joined #openstack-mistral13:07
ddejathrash: I remember that running tempest tests driectly from tempest dir was importnat13:10
thrashddeja: let me try that.13:10
thrashddeja: let me just ask this... is it possible to run the functional tests outside of an openstack environment?13:12
ddejathrash: I got this when I run tests outside of tempest dir Details: Credentials are: {'username': None, 'project_name': None, 'user_id': None, 'tenant_name': None, 'tenant_id': None, 'project_id': None} Password is not defined.13:12
ddejathrash: I don't know13:12
thrashddeja: :D13:12
ddejaI just know how to run them when I need to13:13
ddeja:D13:13
thrashddeja: fair enough13:13
thrashddeja: I don't think I'll pursue this further. I'll just stick to devstack.13:13
ddejaOK13:14
openstackgerritDawid Deja proposed openstack/mistral: Stop excpecting to have rabbit flags set when using fake driver  https://review.openstack.org/41938813:24
ddejarakhmerov: It looks like I was wrong13:24
ddejaall tests passes if i simply return empty dict for 'fake' driver13:25
*** gongysh has joined #openstack-mistral13:36
*** hparekh has quit IRC13:39
*** AlexeyAbashkin has quit IRC13:59
*** AlexeyAbashkin has joined #openstack-mistral14:02
*** shardy has quit IRC14:05
*** shardy has joined #openstack-mistral14:06
ddejafolks, we still don't know why 3-O gate is failing, do we?14:25
*** bobh has joined #openstack-mistral14:30
*** AlexeyAbashkin has quit IRC14:45
*** gongysh has quit IRC14:48
*** ist has quit IRC15:01
*** chlong has joined #openstack-mistral15:03
*** jaosorior has joined #openstack-mistral15:22
*** AlexeyAbashkin has joined #openstack-mistral15:28
*** bobh has quit IRC15:50
*** bobh has joined #openstack-mistral15:53
*** AlexeyAbashkin has quit IRC16:27
*** chlong has quit IRC16:52
*** thrash is now known as thrash|biab17:09
*** chlong has joined #openstack-mistral17:26
*** jpich has quit IRC17:49
*** thrash|biab is now known as thrash17:55
*** AlexeyAbashkin has joined #openstack-mistral17:59
*** weshay is now known as weshay_bbiab18:13
*** chlong has quit IRC18:19
*** chlong has joined #openstack-mistral18:32
*** openstackgerrit has quit IRC18:33
*** AlexeyAbashkin has quit IRC18:55
*** AlexeyAbashkin has joined #openstack-mistral18:59
*** AlexeyAbashkin has quit IRC19:01
*** shardy has quit IRC19:18
*** weshay_bbiab is now known as weshay19:25
*** chlong has quit IRC19:41
*** chlong has joined #openstack-mistral19:56
*** jrist has quit IRC20:33
*** chlong has quit IRC20:44
*** AlexeyAbashkin has joined #openstack-mistral20:44
*** jrist has joined #openstack-mistral20:46
*** d0ugal has quit IRC20:52
*** d0ugal has joined #openstack-mistral20:54
*** d0ugal has joined #openstack-mistral20:54
kongping rakhmerov20:56
kongjust try my luck to see if you are here20:56
*** chlong has joined #openstack-mistral20:58
*** AlexeyAbashkin has quit IRC20:59
kongafter reading the blog you sent to me and did some testing, i found this: given there are 3 threads are inserting a record to names lock table with the same name in 3 different transactions. the 1st one will insert successfully and the other 2 are both waiting.20:59
kongrakhmerov:  after 1st thread delete the record and do commit, there will be only one thread between 2nd and 3rd threads can insert record, the other one will fail with exception.21:02
kongrakhmerov: btw, i'm using mysql with 'repeatable read' isolation.21:03
*** d0ugal has quit IRC21:03
kongis that the expected behavior?21:03
*** chlong has quit IRC21:04
*** chlong has joined #openstack-mistral21:18
*** rbrady is now known as rbrady-afk21:19
*** dturner has joined #openstack-mistral21:26
*** bobh has quit IRC21:31
*** sharatss has quit IRC22:06
*** sharatss has joined #openstack-mistral22:06
*** d0ugal has joined #openstack-mistral22:07
*** chlong has quit IRC22:29
*** dprince has quit IRC22:34
*** chlong has joined #openstack-mistral22:37
*** openstackgerrit has joined #openstack-mistral22:42
openstackgerritBrad P. Crochet proposed openstack/mistral: Put useFixture in the proper place  https://review.openstack.org/41968022:42
openstackgerritBrad P. Crochet proposed openstack/mistral: Use utcnow() instead of now()  https://review.openstack.org/41968122:48
*** jaosorior has quit IRC23:22

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!