Tuesday, 2017-09-05

*** baojg has quit IRC00:20
*** portdirect has joined #openstack-swift00:25
*** SkyRocknRoll has quit IRC00:28
*** kiennt has joined #openstack-swift00:47
*** mat128 has joined #openstack-swift01:27
*** bkopilov has quit IRC01:28
*** StevenK_ is now known as StevenK01:30
*** gkadam has joined #openstack-swift02:15
*** gkadam has quit IRC02:17
*** gkadam has joined #openstack-swift02:18
*** vint_bra has joined #openstack-swift02:33
mattoliverauWow its quiet in here when the US folk are on holidays.02:38
*** mat128 has quit IRC02:39
*** bkopilov has joined #openstack-swift02:46
*** kiennt_ has joined #openstack-swift03:33
*** kiennt has quit IRC03:36
*** cshastri has joined #openstack-swift03:37
openstackgerritPete Zaitcev proposed openstack/swift master: PUT+POST and its development test  https://review.openstack.org/42791103:37
*** kiennt_ is now known as kiennt03:38
*** kiennt_ has joined #openstack-swift03:44
*** kiennt has quit IRC03:47
*** links has joined #openstack-swift03:51
*** vint_bra has quit IRC03:56
*** kei_yama has quit IRC03:59
*** kei_yama has joined #openstack-swift04:01
mahaticgood morning04:13
mahaticmattoliverau: o/04:13
*** kiennt_ is now known as kiennt_AWAY04:16
*** psachin has joined #openstack-swift04:21
*** klrmn has quit IRC04:21
*** pcaruana has joined #openstack-swift04:52
kota_mahatic, mattoliverau: o/05:07
mattoliveraumahatic, kota_ o/05:07
mahatickota_: hello05:07
kota_it's too quiet since yesterday so that i can find my voice on yesterday easily in the log05:08
*** silor has joined #openstack-swift05:20
mattoliveraukota_: seems we know what country makes the most noise :P05:28
*** silor has quit IRC05:30
*** silor has joined #openstack-swift05:31
mahatic:D05:36
*** hoonetorg has quit IRC06:05
*** hseipp has joined #openstack-swift06:17
*** hoonetorg has joined #openstack-swift06:22
*** rcernin has joined #openstack-swift06:46
*** tesseract has joined #openstack-swift07:13
*** cschwede_ has joined #openstack-swift07:23
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Update Container-Sync Docs for internal_client.conf  https://review.openstack.org/50070307:24
*** geaaru has joined #openstack-swift07:29
*** m_kazuhiro has joined #openstack-swift07:40
kota_mattoliverau: lol07:43
*** m_kazuhiro has quit IRC08:12
*** cbartz has joined #openstack-swift08:23
*** ChubYann has quit IRC08:26
*** ChubYann has joined #openstack-swift08:40
*** kallenp has joined #openstack-swift08:49
kallenpHi all. Please, can I ask for a help howto copy swift storage node from production server (prod.domain.com) to devel server (devel.domain.com) ? What's the easyest way howto do it ? I google for it, but i don't find any usefuly howto. Thanks for a help. Petr08:51
kallenpAny idea howto do it ? Please ?09:08
*** bkopilov has quit IRC10:31
*** kallenp has quit IRC10:39
*** kallenp has joined #openstack-swift10:40
*** gkadam has quit IRC10:57
*** kallenp has left #openstack-swift11:01
openstackgerritjunbo.li proposed openstack/swift master: doc migration: update the doc link address  https://review.openstack.org/50077511:19
openstackgerritjunbo.li proposed openstack/swift master: doc migration: update the doc link address[2/3]  https://review.openstack.org/50077611:20
openstackgerritjunbo.li proposed openstack/swift master: doc migration: update the doc link address[1/3]  https://review.openstack.org/50077511:22
openstackgerritjunbo.li proposed openstack/swift master: doc migration: update the doc link address[3/3]  https://review.openstack.org/50077711:25
*** skudlik has joined #openstack-swift11:26
*** skudlik has left #openstack-swift11:27
*** rcernin has quit IRC11:36
*** rcernin has joined #openstack-swift11:36
*** kei_yama has quit IRC11:44
*** kiennt_AWAY has quit IRC11:46
*** mat128 has joined #openstack-swift12:06
*** SkyRocknRoll has joined #openstack-swift12:17
*** mat128 has quit IRC12:33
*** mat128 has joined #openstack-swift12:34
*** cshastri has quit IRC12:45
*** skudlik has joined #openstack-swift12:50
*** juzuluag has joined #openstack-swift12:53
*** catintheroof has joined #openstack-swift12:55
*** catintheroof has quit IRC12:55
*** catintheroof has joined #openstack-swift12:55
*** zhurong has joined #openstack-swift12:56
*** bkopilov has joined #openstack-swift13:07
*** zhurong has quit IRC13:10
*** juzuluag has quit IRC13:34
*** SkyRocknRoll has quit IRC14:07
*** SkyRocknRoll has joined #openstack-swift14:09
*** amarao has joined #openstack-swift14:10
amaraoHow to disable tempest tests which are marked as '@utils.requires_ext(extension='container_quotas', service='object')'. I've tried to use "[object-storage-feature-enabled] container_quotas=False", but it's ignored.14:12
*** therve has joined #openstack-swift14:37
*** links has quit IRC14:37
*** vint_bra has joined #openstack-swift14:40
*** geaaru has quit IRC14:42
therveHi all. I opened https://bugs.launchpad.net/swift/+bug/1715177 , if anyone would like to chat about it14:43
openstackLaunchpad bug 1715177 in OpenStack Object Storage (swift) "Container cache management is racy" [Undecided,New]14:43
thervecschwede_,  ^^14:43
*** cbartz has quit IRC15:04
openstackgerritDaniel Čech proposed openstack/python-swiftclient master: Fixed capability discovery endpoint hardcode  https://review.openstack.org/50087515:08
openstackgerritDaniel Čech proposed openstack/python-swiftclient master: Fixed capability discovery endpoint hardcode  https://review.openstack.org/50087515:09
openstackgerritDaniel Čech proposed openstack/python-swiftclient master: Fixed capability discovery endpoint hardcode  https://review.openstack.org/50087515:15
*** lucasxu has joined #openstack-swift15:17
openstackgerritDaniel Čech proposed openstack/python-swiftclient master: Fixed capability discovery endpoint hardcode  https://review.openstack.org/50088315:17
*** gyee has joined #openstack-swift15:32
*** b4rti has quit IRC15:33
notmynamegood morning15:37
notmynameamarao: that is really interesting15:38
notmynamenot in a good way ;-)15:38
*** amarao has quit IRC15:48
*** skudlik has quit IRC15:53
*** psachin has quit IRC15:55
notmynameacoles: I think the X-Backend-Recheck-Container-Existence is a red herring. yes, it's set, but yes, it's filtered by gateway16:21
*** itlinux has joined #openstack-swift16:29
timburkegood morning16:37
notmynameso far I'm not able to repro the bug16:37
timburkeeh? my bouncer seems to have lost some messages...16:39
notmynamehttps://bugs.launchpad.net/swift/+bug/171517716:39
openstackLaunchpad bug 1715177 in OpenStack Object Storage (swift) "Container cache management is racy" [Undecided,New]16:39
notmynamefrom the 7 o'clock hour this morning16:39
timburkeah. try doing a delete to the container first16:39
timburke(i'm assuming. haven't actually tried it myself)16:39
notmynameI'm using the provided repro script which claims to break against devstack16:39
notmynameI'm not using devstack16:40
notmynameso it's entirely possible that my machine is too fast to see the bug16:40
notmynameI've definitely seen issues come to light on overburdened VMs before16:40
timburkei could be wrong, but i don't think that it actually requires concurrent requests. i think a container DELETE, followed by a container HEAD, followed by a container PUT, followed by an object PUT may have the PUT fail16:44
timburkelet's find out!16:44
timburkenope, i stand corrected. unless there's something funny with the cache lifetimes...16:49
notmynameyeah, I think a slow VM may turn the repro script into concurrent actions, and it's not on my dev box ;-)16:49
timburkewhere *is* the cache time determined?16:50
rcerninkota_: timburke: do you knwo guys of IBM development progress on swift3? aparently this works in Red Hat provided openstack-swift-plugin-swift3. Do you know any background on swift3 with IBM?16:51
notmynametimburke: I think the trick is to follow that x-backend header value. it's ignored of course, but where it's actually used in the proxy is where it's setting the memcache ttl16:52
timburkercernin: i know that IBM has expressed various levels of interest in swift3 development over time, but i don't know anything about how they use, deploy, or even package it16:58
timburkei know cbartz proposed https://review.openstack.org/#/c/475873/ not too long ago...16:58
patchbotpatch 475873 - swift3 - Introduce auth middleware using account metadata.16:58
*** tesseract has quit IRC17:25
*** rcernin has quit IRC17:25
*** hseipp has quit IRC17:29
*** alenavolk has joined #openstack-swift17:37
*** klrmn has joined #openstack-swift18:00
*** alenavolk has quit IRC18:01
*** alenavolk has joined #openstack-swift18:05
*** alenavol_ has joined #openstack-swift18:11
*** alenavolk has quit IRC18:11
*** alenavolk has joined #openstack-swift18:15
*** cschwede_ has quit IRC18:16
*** alenavol_ has quit IRC18:45
*** alenavolk has quit IRC18:45
*** pcaruana has quit IRC18:49
*** alenavolk has joined #openstack-swift18:49
*** alenavol_ has joined #openstack-swift18:49
openstackgerritTim Burke proposed openstack/swift master: doc migration: update the doc link address[1/3]  https://review.openstack.org/50077519:14
*** chsc has joined #openstack-swift19:17
*** itlinux has quit IRC19:35
*** alenavol_ has quit IRC19:36
*** alenavolk has quit IRC19:36
*** alenavolk has joined #openstack-swift19:41
*** alenavol_ has joined #openstack-swift19:41
*** alenavol_ has quit IRC19:45
*** alenavolk has quit IRC19:45
*** mat128 has quit IRC19:51
*** mat128 has joined #openstack-swift19:51
*** mat128 has quit IRC19:52
*** mat128 has joined #openstack-swift19:54
therveclayg, Hi!20:05
claygheyoh!20:05
therveHere to chat about https://bugs.launchpad.net/swift/+bug/1715177 if you have a few minutes20:05
openstackLaunchpad bug 1715177 in OpenStack Object Storage (swift) "Container cache management is racy" [Undecided,Opinion]20:05
claygoh wow!  thanks for jumpin on!20:06
claygDo you have more than one proxy node (sometimes called "the controller"???)20:06
therveclayg, Yeah it's a single node devstack20:08
therveSo no in fact20:08
claygoh... well then how the heck do you get a 404 after a container PUT!?  regardless of what's going on in that other thread... i could spin up a devstack and try to duplicate there... pretty strange!  doesn't match my experience!20:09
therveWell, from what I can tell, there is nothing that protect cache setting20:09
claygdo you have a request log maybe?  i'm not in a good spot to break off what I have up and start up a devstack node and play around with it more today than I have already... but if you're stumped I could try to look again w/i 24 hours20:09
therveSo the put_container sets the cache, but the get_container overrides it with the wrong answer, IIUC20:10
therveSure I have it running, I can paste you whatever you need20:10
clayg"protect" - we cache non-existance for sure - so if you 404 a GET well set the non-existence for I think ... idk 1/10 the existence check?  But that code I pointed to (container PUT) will reset the cache - so a object PUT after container PUT should find the memcache entry for the container empty and refresh it and find the container.20:11
claygyeah if you have the request LOG, ts1 container put, ts2 container get (with 404, *after* the PUT!?), ts3 object 40420:12
claygdoes it happen *every* time?  I only ran it like maybe a half-a-dozen - if it's 1/1k maybe it would be reproducible and I just missed it?20:12
timburkei'm thinking if you do something like DELETE container, concurrently HEAD / PUT container, PUT object, there's a window where the GET gets a 404 but hasn't woken up yet, PUT goes through and invalidates the (not actually set) cache, GET wakes up and records the 40420:14
therveclayg, No it happens about 3 out of 5?20:14
therveclayg, http://paste.openstack.org/show/620436/20:14
claygtimburke: yeah that's what I thought initially, but the example script provided didn't include any DELETE20:14
thervetimburke, Yeah no delete involved20:15
claygtherve: definitely not the same for me in my test - very strange - thanks for providing more information!20:15
therveclayg, FTR removing the time.sleep was important20:15
therveOtherwise you don't see the issue20:16
therveclayg, http://paste.openstack.org/show/620437/ cleaned up with just the requests20:19
*** mat128 has quit IRC20:22
notmynameFYI https://www.openstack.org/summit/berlin-201820:22
*** mat128 has joined #openstack-swift20:23
therveNice20:23
claygthis sequence is somewhat damning... https://gist.github.com/clayg/ecaa44089599cfb7ace34ee758f467a520:23
claygGET 404, PUT 201, PUT 40420:24
claygthe interesting bit is that by my reading the PUT started before, but finished *after* - the GET20:25
claygthen the object PUT 404's20:25
claygtherve: I think it's it's not nothing!20:25
therveclayg, Yeah I try not to cry wolf :)20:26
therveIt's possible the answer is "please don't do that" though. I think I can find some kind of workaround20:27
tdasilvatherve, clayg: fwiw, i'm not able to reproduce it on my own dev SAIO, but it was easy to reproduce with tripleo20:27
thervetdasilva, With the script on the undercloud?20:27
tdasilvayes20:27
tdasilvai'm using clayg's script20:27
therveAh thanks for trying20:27
claygtdasilva: i'm noticing a huge part of the request time is spent negotiating with keystone in this log snippet - so that's one commonality between different environments where we *can* and *can not* reproduce20:28
thervetdasilva, Do you have memcache in your saio?20:28
tdasilvatherve: yes20:28
tdasilvatherve: i use this for my saio: https://github.com/thiagodasilva/ansible-saio20:28
clayganyway - my guess now is that container put should do it's cache invalidation as close as possible to the end of the request...  (instead of *before* make_request)20:29
tdasilvaclayg: and yeah, some of the differences between tripleo (especially undercloud) and a typical saio is keystone and also 1 replica vs 3 replicas20:29
claygtherve: are you in a situation you could hack that up in swift.proxy.controllers.container around L184?20:29
claygjust move clear_info_cache after make_requests and restart your proxies20:30
therveclayg, Sure20:30
timburkeclayg: so with the randomly-generated container name, the DELETE isn't necessary. i can reproduce on my vsaio using curl like http://paste.openstack.org/show/620439/20:31
claygcool - GL - be sure to post results to the bug report (either positive or negative results would be helpful I think, diffs always help)20:31
timburkegets me output like http://paste.openstack.org/show/620438/20:31
therveclayg, Seems to do the trick!20:31
claygsudo apt install uuid20:33
* therve spent days on that issue, excited to see a fix with a 2 lines diff :D20:35
claygtimburke: is your saio running keystone?  your script doesn't result in 404 for me?20:35
timburkenope. try it repeatedly. first time i got a 201, very next run (iirc) got the doubled-up 404s20:35
claygthe HEAD (even in the background) is just too quick?  maybe my vm forks faster than yours?20:35
claygtimburke: lol - i'd been running it then - *finally* it 404'd - KUDOS!20:36
claygnext 50 all 201'd20:37
* clayg shrugs20:37
timburkenature of race conditions, man20:37
clayganyway - PUT invaliding before the HEAD returns (and caches non-existance) seems to make sense to me!20:37
therveYeah it probably helps I have a small VM on my laptop20:38
clayganyway - from my mind this is ... sort of well understood - i mean it's a cache over an eventually consistent system for goodness sake - but I like the idea of doing the PUT cache invalidation at the last second better than the wider race window - so I'm totally down.20:39
therveGreat20:39
therveDo you want me to post the patch?20:39
claygthe more of that we can capture that lp bug #1715177 the better20:40
openstackLaunchpad bug 1715177 in OpenStack Object Storage (swift) "Container cache management is racy" [Medium,Confirmed] https://launchpad.net/bugs/171517720:40
claygtherve: well ... i mean we're gunna wanna a test to demonstrate the race20:40
therveclayg, Yeah that one is going to be fun to write :)20:40
claygbut you can get the ball rolling with a patch on the bug report or in gerrit20:40
therveOK I'll do that now, and see if I can find a way to test tomorrow20:40
claygit's a big help just demonstrating the issue!  thanks again for sticking with it!20:40
timburkemoving the invalidation should narrow the window, but it'll still exist. in general, though, containers are pretty long-lived -- if a client gets a 404 during an object put, it should wait a bit, try again, and if it *still* fails, get noisy, as something's misconfigured20:41
clayggreat GL!  I'm sure if you get something up on gerrit timburke or mattoliverau would help you with a test - they love that racy concurrency stuff!20:41
thervetimburke, yeah that was one of my questions as well. I can certainly make the client code more robust20:41
claygtimburke: If possible in the ideal the recovery code for errors on object PUT would grow container create logic to deal with 40420:42
claygtherve: thanks again - you too timburke!20:43
timburkeclayg: maybe, but not necessarily -- whoever's in charge of putting objects into the container may not have permission to create one20:43
*** rcernin has joined #openstack-swift20:44
openstackgerritThomas Herve proposed openstack/swift master: Delay cache invalidation during container creation  https://review.openstack.org/50097820:44
therveThanks for your help!20:44
* therve off for now20:45
*** lucasxu has quit IRC20:48
*** silor has quit IRC20:50
*** mat128 has quit IRC21:01
*** itlinux has joined #openstack-swift21:13
*** catintheroof has quit IRC21:43
*** rcernin has quit IRC21:53
*** itlinux has quit IRC22:55
notmynamemattoliverau: are you still on for the 0700 meeting?22:57
mattoliveraunotmyname: oh yeah, it's wednesday. Sure, I'll have a look at what I can add/remove from the adjenda23:06
notmynameok, thanks23:07
notmynameIMO it's really just prep for next week23:07
mattoliverauyup +123:07
mattoliverauoh and morning :)23:08
acolesmattoliverau: I won't make the 0700 this week, just arrived in SF so will definitely be asleep at that time23:21
mattoliverauacoles: wheres the dedication man :P Yeah that's fine, enjoy your sleep, being jetlagged means you probably looking forward to it ;)23:23
mattoliverauif it ends up being just me, I'll talk to myself again :P23:23
acolesmattoliverau: the dedication is somewhere over greenland ;)23:23
mattoliveraulol23:24
*** kei_yama has joined #openstack-swift23:25
*** catintheroof has joined #openstack-swift23:26
zaitcevI dunno, I don't think I can make a 1 a.m. meeting23:28
zaitcevAnyway, I was making a great progress with cleaning up PUT+POST. I assumed that we actually want it merged, so it needed proper error catches and such.23:29
zaitcevThere's not much to discuss about it short of actually reviewing.23:29
*** catintheroof has quit IRC23:31
mattoliverauzaitcev: 1am it too much, but that's why we also have the original meeting in your timezone where we can discuss PUT+POST. But I can tell people to go review it in the 0700 meeting if you want :)23:31
*** chsc has quit IRC23:32

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