Monday, 2018-05-21

*** amandap has quit IRC00:22
*** amandap has joined #openstack-swift00:23
*** amandap has quit IRC00:31
*** germs has joined #openstack-swift00:45
*** germs has quit IRC00:50
*** germs has joined #openstack-swift00:54
*** threestrands has joined #openstack-swift01:12
*** amandap has joined #openstack-swift01:23
*** armaan has quit IRC01:30
*** armaan has joined #openstack-swift01:31
*** armaan has quit IRC02:21
*** armaan has joined #openstack-swift02:21
*** germs has quit IRC02:38
*** psachin has joined #openstack-swift03:10
*** amandap has quit IRC03:10
*** amandap has joined #openstack-swift03:17
*** germs has joined #openstack-swift04:10
*** germs has quit IRC04:15
*** threestrands has quit IRC04:18
*** threestrands has joined #openstack-swift04:22
*** threestrands has quit IRC04:22
*** threestrands has joined #openstack-swift04:22
*** threestrands has quit IRC04:23
*** threestrands has joined #openstack-swift04:23
*** amandap has quit IRC04:38
*** amandap has joined #openstack-swift04:39
*** cshastri has joined #openstack-swift04:45
*** geaaru_ has quit IRC05:36
*** armaan_ has joined #openstack-swift05:57
*** armaan has quit IRC05:57
*** links has joined #openstack-swift05:57
*** germs has joined #openstack-swift06:11
*** germs has quit IRC06:11
*** germs has joined #openstack-swift06:11
*** germs has quit IRC06:16
*** amandap has quit IRC06:20
*** itlinux has joined #openstack-swift06:33
*** saltsa has joined #openstack-swift06:47
*** pcaruana has joined #openstack-swift06:47
*** ntt has quit IRC07:00
*** ntt has joined #openstack-swift07:04
*** rcernin has quit IRC07:06
*** ccamacho has joined #openstack-swift07:10
*** tesseract has joined #openstack-swift07:10
*** ccamacho has quit IRC07:15
*** ccamacho has joined #openstack-swift07:16
*** amandap has joined #openstack-swift07:25
acolesgood morning07:32
acoleshope everyone in Vancouver has a great week07:33
*** geaaru has joined #openstack-swift07:37
openstackgerritAlistair Coles proposed openstack/swift master: Use correct policy when faking misplaced objects in probe test  https://review.openstack.org/56973707:38
acolestimburke: that's a fix for the problem you ran into with probe test failing ^^07:39
*** pcaruana has quit IRC07:40
*** pcaruana has joined #openstack-swift07:41
*** amandap has quit IRC07:48
*** amandap has joined #openstack-swift07:48
*** silor has joined #openstack-swift07:59
*** threestrands has quit IRC08:00
*** itlinux has quit IRC08:04
*** germs has joined #openstack-swift08:12
*** germs has quit IRC08:12
*** germs has joined #openstack-swift08:12
*** germs has quit IRC08:17
*** amandap has quit IRC08:22
*** amandap has joined #openstack-swift08:22
*** amandap has quit IRC08:28
*** amandap has joined #openstack-swift08:29
*** silor has quit IRC08:33
*** bkopilov has joined #openstack-swift08:34
*** amandap has quit IRC08:35
*** amandap has joined #openstack-swift08:52
*** amandap has quit IRC08:57
*** armaan_ has quit IRC09:37
*** armaan has joined #openstack-swift09:38
*** bkopilov has quit IRC10:08
*** mikecmpbll has joined #openstack-swift10:11
*** germs has joined #openstack-swift10:13
*** armaan has quit IRC10:17
*** armaan has joined #openstack-swift10:17
*** germs has quit IRC10:18
*** armaan has quit IRC10:22
*** armaan has joined #openstack-swift10:23
*** kei_yama has quit IRC10:24
openstackgerritAlistair Coles proposed openstack/swift master: Container sharding doc fixes and clarifications  https://review.openstack.org/56977310:37
*** psachin has quit IRC10:43
openstackgerritAlistair Coles proposed openstack/swift master: Container sharding doc fixes and clarifications  https://review.openstack.org/56977310:59
*** psachin has joined #openstack-swift11:04
*** armaan has quit IRC11:22
*** armaan has joined #openstack-swift11:22
*** bkopilov has joined #openstack-swift11:28
*** amandap_ has joined #openstack-swift11:53
*** NM has joined #openstack-swift12:10
remix_tjacoles: if i want to store a custom metadata on an object, which name should i use? X-Object-Systemeta-* ? or i can specify my own X-whatever?12:13
*** germs has joined #openstack-swift12:14
remix_tjor X-Meta?12:14
remix_tjX-Object-Meta-* ?12:14
*** mikecmpbll has quit IRC12:18
*** germs has quit IRC12:18
acolesremix_tj: that depends upon the context - a client can only set x-object-meta, whereas middleware can set x-object-sysmeta. Also x-object-sysmeta is not visible to clients. So x-object-sysmeta can be used for internal metadata, whereas x-object-meta is for clients.12:18
remix_tji want give user the ability to say "This file cannot be altered or deleted for X time"12:19
acolesremix_tj: https://docs.openstack.org/swift/latest/development_middleware.html#swift-metadata12:19
remix_tjso i think X-Object-Meta is the appropriate12:19
remix_tji'll take a look. I need also to find when the file has been created, so i can calculate when a file can be deleted. I've seen that X-Delete-After is converted to X-Delete-At converting the seconds to a timestamp, am i right?12:21
*** mikecmpbll has joined #openstack-swift12:23
acolesremix_tj: for that you might want to consider translating a client header e.g. 'X-do-such-and-such' to x-object-sysmeta-do-such-and-such in middleware. Otherwise you have to 'reserve' a user metadata name for internal purposes. There's examples of this pattern in other middleware e.g. https://github.com/openstack/swift/blob/097e975938befb939fa6821f50c061e2c7f42cef/swift/common/middleware/symlink.py#L417-L45412:24
remix_tjacoles: thank you12:25
acolesAlso, you should be aware of the persistence properties of various object metadata - see that doc ^^12:25
remix_tjyes, that's what i'm reading now12:26
acolesremix_tj: re x-delete-at - correct, internally x-delete-after is converted to absolute x-delete-at time12:26
remix_tjanyway in my idea if an object hasn't expired it's retention time, any altering operation is denied12:27
*** psachin has quit IRC12:29
*** cshastri has quit IRC12:31
*** psachin has joined #openstack-swift12:37
*** ndk_ has quit IRC12:45
*** ndk_ has joined #openstack-swift12:46
*** vinsh has quit IRC12:55
*** vinsh has joined #openstack-swift12:55
*** spsurya has joined #openstack-swift12:58
*** portdirect has quit IRC13:04
*** portdirect has joined #openstack-swift13:04
openstackgerritAlistair Coles proposed openstack/swift master: Improve building listings from shards  https://review.openstack.org/56979613:23
*** silor has joined #openstack-swift13:26
*** mikecmpbll has quit IRC13:26
*** silor has quit IRC13:32
*** NM has quit IRC13:36
*** cshastri has joined #openstack-swift13:38
*** NM has joined #openstack-swift13:38
*** NM has quit IRC13:39
*** mvenesio has joined #openstack-swift13:54
openstackgerritAlistair Coles proposed openstack/swift master: Maintain manage-shard-ranges docs in its module  https://review.openstack.org/56979914:01
acoleskota_: ^^ this is something you suggested during review14:01
*** armaan has quit IRC14:02
*** armaan has joined #openstack-swift14:03
*** tesseract-RH has joined #openstack-swift14:09
*** tesseract has quit IRC14:12
*** germs has joined #openstack-swift14:15
*** germs has joined #openstack-swift14:15
*** armaan has quit IRC14:17
*** armaan has joined #openstack-swift14:17
*** zhongjun_ has quit IRC14:18
*** germs has quit IRC14:20
*** amandap_ has quit IRC14:23
*** NM has joined #openstack-swift14:30
*** NM has quit IRC14:33
*** NM has joined #openstack-swift14:36
remix_tjacoles: last question for today and then i'll will not bother you for some days: is there any metadata reporting when an object has been created? I see X-Object-Meta-mtime but to me "mtime" means "modification time". I'm looking for something like "ctime"14:37
*** NM has quit IRC14:40
*** germs has joined #openstack-swift14:41
*** SkyRocknRoll has joined #openstack-swift14:41
*** NM has joined #openstack-swift14:44
*** NM has joined #openstack-swift14:45
acolesremix_tj: IIRC X-Object-Meta-mtime is actually sent by swiftclient. Internal to swift the X-Backend-Data-Timestamp is the time at which the object was PUT. X-Backend-Timestamp is the time at which the last POST or PUT occurred. The two will be equal if there has not been a POST. You should cast the string header values to a utils.Timestamp instance.14:45
*** NM has quit IRC14:47
*** SkyRocknRoll has quit IRC14:47
remix_tjacoles: in my idea is that there is a container level default retention value. So if there is no specific metadata set on the object, then  the retention time is defaulted to object_creation_time + container_default_retention_value14:49
remix_tjbut i don't want to set metadata on each object, i want to be able also to compute on the fly14:49
remix_tji'm getting the object headers with: swift.proxy.controllers.base.get_object_info14:50
*** itlinux has joined #openstack-swift14:51
*** links has quit IRC14:51
*** NM has joined #openstack-swift14:56
*** SkyRocknRoll has joined #openstack-swift14:56
*** itlinux has quit IRC14:59
*** germs has quit IRC15:13
*** tesseract-RH has quit IRC15:16
*** pcaruana has quit IRC15:18
*** cshastri has quit IRC15:20
acolesremix_tj: hmm, looks like the backend timestamps don't make it into the object info returned by get_object_info15:24
remix_tjacoles: no15:24
remix_tjbut if there is another function to get it, i can use15:24
*** armaan has quit IRC15:25
*** armaan has joined #openstack-swift15:26
acolesyou could stash a copy of x-timestamp during each PUT in object sysmeta, under your own sysmeta key, then you'd be able to access it from the get_object_info, under sysmeta. or maybe there's a way to get to it - AFAICT it comes back in the HEAD response that populated object info, just isn't copied into the cached dict15:26
remix_tjok, i'll check if i can get those infos15:31
*** tesseract has joined #openstack-swift15:31
*** gyee has joined #openstack-swift16:02
notmynamegood monring16:11
notmynameFYI, now that sharding has merged, I'm planning on waiting until the end of this week (or potentially the start of next) to do the 2.18.0 tag16:12
notmynameDHE: ^16:12
DHE:)16:13
notmynamenote for everyone, though, sharding's merged, so that means master is unfrozen. other stuff can land now16:13
*** cshastri has joined #openstack-swift16:13
notmynameI'll be going to vancouver tomorrow and be there through thursday evening16:15
notmynamekota_: mattoliverau: cschwede: mahatic: if you're available, I'd love to go to dinner with you on wednesday evening16:15
* notmyname is not sure who else is at the summit16:15
*** gyee has quit IRC16:31
*** gyee has joined #openstack-swift16:35
*** mikecmpbll has joined #openstack-swift16:51
*** silor has joined #openstack-swift16:53
*** psachin has quit IRC16:56
*** pcaruana has joined #openstack-swift17:05
*** germs has joined #openstack-swift17:13
*** germs has joined #openstack-swift17:13
*** germs has quit IRC17:17
*** armaan has quit IRC17:21
*** armaan has joined #openstack-swift17:21
*** spsurya has quit IRC17:27
*** germs has joined #openstack-swift17:27
*** tesseract has quit IRC17:28
timburkeacoles: so even with that patch, i'm still getting a failure around https://github.com/openstack/swift/blob/master/test/probe/test_sharder.py#L181717:35
timburkeall replicas are at collapsed, with two deleted shard ranges plus their own shard range17:36
acolestimburke: can you take a peek at the partitions for root and shards? using shard-info?17:38
acolestimburke: if a shard is in same partition as root then it may be that it is shrunk sooner than the test expects17:38
timburkeah, that's probably it -- i see two dbs on 197, one on 9817:38
timburkei guess we could add a --suffix option? *shrug*17:39
acolesif one on 197 is second shard then that would explain it17:39
timburkewill re-run and check that it passes17:39
openstackgerritSamuel Merritt proposed openstack/swift master: Add support for PROXY protocol v1 (only)  https://review.openstack.org/37356317:39
acolesor a --db_file option ?17:39
acolestimburke: or perhaps the test doesn't need to empty the second shard range quite so soon?17:40
acoleswhat's your EC ring part power?17:40
timburkeboth are 817:41
acoleshmm, maybe its the two shards that would need to be in same partition17:42
timburkeroot and shard index 1 had the same partition17:44
acolesah, line 1814 will be the culprit then, running sharder on shard index 1 to get updates inadvertently runs sharder on root which causes shard index 1 to shrink (assuming it runs on the root first)17:45
*** silor has quit IRC17:46
*** NM has quit IRC17:46
*** cshastri has quit IRC17:48
openstackgerritAlistair Coles proposed openstack/swift master: WIP Reclaim expired cleaving context metadata  https://review.openstack.org/56983217:49
*** amandap has joined #openstack-swift17:49
acolestimburke: I'll look tomorrow at if the object deletes can be reordered to avoid that glitch, if you don't beat me to it. I need to go now.17:50
acolestimburke: I'll look tomorrow at if the object deletes can be reordered to avoid that glitch, if you don't beat me to it. I need to go now.17:50
*** NM has joined #openstack-swift17:53
*** geaaru has quit IRC17:54
*** amandap has quit IRC17:54
*** armaan has quit IRC18:12
*** armaan has joined #openstack-swift18:13
openstackgerritTim Burke proposed openstack/swift master: Use assertRaises more  https://review.openstack.org/56793318:13
torgomaticinteresting; test/unit/common/test_utils.py:TestUtils.test_get_logger_sysloghandler_plumbing fails on python 3.5 on Ubuntu 18.04, but passes on Ubuntu 16.0418:15
openstackgerritTim Burke proposed openstack/swift master: Make the decision between primary/handoff sets more obvious  https://review.openstack.org/56794018:18
openstackgerritTim Burke proposed openstack/swift master: Fix-up signal handling  https://review.openstack.org/56983718:21
openstackgerritTim Burke proposed openstack/swift master: Handle SIGINT more like we do SIGHUP and SIGTERM  https://review.openstack.org/56983818:21
openstackgerritTim Burke proposed openstack/swift master: Remove exclude_states from get_shard_ranges  https://review.openstack.org/56984018:25
*** SkyRocknRoll has quit IRC18:29
notmynametimburke: or torgomatic: if either of you could take some time to look at https://review.openstack.org/#/c/555245/ in the next couple of days, I'd appreciate it18:29
patchbotpatch 555245 - swift - Fix versioned writes error with url-encoded object...18:29
notmynamea while back (before the feature/deep crunch), we'd said we'd like to have it for 2.18.018:29
notmynameso if it were to land this week, that would be great18:29
timburkeoh yeah, i'd started looking at it a while ago... i should at least leave my comments so far...18:30
notmynamethanks18:30
notmynamerememeber, kota_ is at the summit, so he likely won't have a lot of chance for gerrit back-and-forth18:31
*** NM has quit IRC18:31
*** NM has joined #openstack-swift18:35
*** Guest74322 is now known as mgagne18:41
*** mgagne has quit IRC18:42
*** mgagne has joined #openstack-swift18:42
openstackgerritTim Burke proposed openstack/swift master: Plumb includes down into _get_shard_range_rows  https://review.openstack.org/56984718:50
*** mikecmpbll has quit IRC19:03
*** NM has quit IRC19:06
openstackgerritTim Burke proposed openstack/swift master: container/backend: Always call transform_func when building listings  https://review.openstack.org/56985019:22
*** zaitcev has joined #openstack-swift19:28
*** ChanServ sets mode: +v zaitcev19:28
*** amandap has joined #openstack-swift19:50
*** amandap has quit IRC19:54
*** NM has joined #openstack-swift19:57
claygtimburke: ok, I see the race now in https://review.openstack.org/#/c/569837/1/swift/common/wsgi.py@94920:05
patchbotpatch 569837 - swift - Fix-up signal handling20:05
claygTHANK YOU!20:05
claygBut I'm not sure the solution is just to make it so small it's atomic - I think it'd be to design it so the context is "sigterm recieved = True" and we just never let sighup overwrite that20:06
claygthe problem is I didn't see the race the first go 'round so reusing context[1] = signal wasn't obviously wrong20:06
claygTHANKS for seeing what I could not!20:06
timburkei'm not sure it's a *bad* idea to have multiple SIGTERMs trigger multiple killpg()s though -- like, i *told you* i wanted you to go murdering processes, and i have have reason to believe that *i need to tell you again* -- just GO DO IT AGAIN20:08
clayghrm... interesting...20:09
claygtimburke: it was under sam's advice that pulled out the syscalls from the handler - it sure made sense to me - maybe we could ask his opinion?20:09
claygtorgomatic: you have AF's for patch 569837 :D20:10
patchbothttps://review.openstack.org/#/c/569837/ - swift - Fix-up signal handling20:10
torgomaticAF's?20:10
claygoh.. I was thinking "any" - i guess it's typically just "as 4$@%"20:11
timburkei always trust torgomatic on these things -- i'll defer to his judgement!20:11
claygtorgomatic: you've been nominated ruler of all signal handling :D20:12
torgomaticoh joy :)20:13
torgomaticI left a comment with my reasoning on that patch20:14
timburkehmmm... so this is weird -- when i go to run *all* probe tests, they go along fine until test_object_partpower_increase, at which point i hit an error down in resetswift: "umount: /mnt/swift-disk: target is busy"20:16
claygtorgomatic: but we already knew that logging would bork us - timburke pointed out that syscalls probably wouldn't bork us - but we're less clear if moving them back into the signal handler is "better"?  I guess it makes the race smaller.  That's probably better.20:18
torgomaticI should probably go read up on signal handlers and such again. I have a vague idea that maybe you can't get a signal while you're in a signal handler, so if you manage to infinite-loop in a signal handler then SIGKILL is your only way out, but I could easily be wrong about that20:19
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Maintain manage-shard-ranges docs in its module  https://review.openstack.org/56979920:21
*** germs has quit IRC20:21
openstackgerritMerged openstack/swift master: Use correct policy when faking misplaced objects in probe test  https://review.openstack.org/56973720:23
openstackgerritMerged openstack/swift master: Use assertRaises more  https://review.openstack.org/56793320:23
kota_notmyname: unfortunately, wednesday is only unavailable day through the summit for dinner :/20:24
kota_notmyname: today, Tuesday, Thursday can work for me.20:25
kota_and congrats container-sharding is now in the master.20:25
openstackgerritTim Burke proposed openstack/swift master: Pre-storage-policy-index tests shouldn't have shard_range tables  https://review.openstack.org/56985620:36
*** pcaruana has quit IRC20:37
timburkei'd really like to take those container db migration tests and make them much more declarative...20:37
*** mvenesio has quit IRC20:40
openstackgerritTim Burke proposed openstack/swift master: Respect auto_create_account_prefix in container PUT path  https://review.openstack.org/56986020:47
notmynamewow. 2.18.0 will be swift's 49th release!20:51
claygwhoot!  let's do 3.0.0 next!?20:54
claygbig five-oh!?20:54
openstackgerritTim Burke proposed openstack/swift master: Use sets instead of dicts when we only care about the keys  https://review.openstack.org/56986121:01
claygtimburke: what's the story with patch 569860 - can you put it in the commit message for me?21:07
patchbothttps://review.openstack.org/#/c/569860/ - swift - Respect auto_create_account_prefix in container PU...21:07
claygit's not obvious to me at all why we'd want to start doing that?  Do we HAVE to?21:08
timburkenothing much -- it just seemed weird to me that we respect that flag on GET (check up around L90) to differentiate between 401/403/404 (i guess?) but we don't look at it on PUT21:09
timburkelike -- i can do a GET on the container and get back a 404... but then i do a PUT and i get back... another 404? i guess it's telling me what needs to happen at least... it's just weird that we've got an option that says that account should get auto created, but we're not auto creating it21:12
claygI still don't get it... i thought all that dot-account stuff was for internal daemons only - you're saying some of the proxy's controllers make special accommodations for  dot-accounts and this is the only operation that doesn't?21:14
timburkeiirc we need the code in GET so we can get shards before the container-updater goes to report stats back to the .sharded_ account which pops it into existence21:18
timburkePOST and DELETE don't need it -- if the account doesn't exist, the container can't exist, so 404 is appropriate21:19
timburkei suppose there's a similar oddity in the account APIs... there, we don't look at the prefixes *at all*21:20
claygi see, so we snuck it in so internal client can get ahead of the container-updater... and I guess maybe we can't just skip the check on GET because of how account-reaping works... difference between 404 and 410 maybe?21:24
claygI mean what you're saying about POST & DELETE can't be true or we wouldn't need the hack in GET ;)21:24
claygif we can't loose the check on GET maybe internal client should just get special privledge to make whatever requests to the container layer it damn well pleases regardless of what the account layer thinks?21:25
timburkebah, you're right! need it in POST and DELETE, too.21:28
timburkethis isn't even for internal client! it's for client-facing proxy-server! as soon as a container starts responding that it's sharding and got an active range, we want to be able to go querying that shard db21:29
claygoh, gross - does container_info have this problem?  maybe the flag is "hi, I'm a client, please don't trust me" vs. "I am the $%^&ing proxy dude, back off!"21:33
claygor maybe it's the combination of 404 and config_option_1 + config_option_2 ???21:33
*** NM has quit IRC21:33
*** NM has joined #openstack-swift21:34
claygyou could factor it out to a single source of truth... IDK, i wonder if it's more "this makes my OCD itch" more than "this is technical investment to make doing other things later cheaper"21:35
timburkeclayg: probably more the former than the latter -- just something that i noticed in review that i figured i could push up a patch for... i'll see about getting it better formed (or just let it get forgotten in my long long list of open patches)21:38
clayg👍21:38
*** NM has quit IRC21:38
*** Guest83262 has joined #openstack-swift21:46
*** germs has joined #openstack-swift21:48
*** Guest83262 is now known as _alastor_21:49
*** germs has quit IRC21:50
*** ianychoi has quit IRC22:06
*** ianychoi has joined #openstack-swift22:06
*** germs has joined #openstack-swift22:13
*** germs has quit IRC22:13
*** germs has joined #openstack-swift22:13
*** rcernin has joined #openstack-swift22:16
*** germs has quit IRC22:17
openstackgerritMerged openstack/swift master: Container sharding doc fixes and clarifications  https://review.openstack.org/56977322:29
openstackgerritMerged openstack/swift master: Pre-storage-policy-index tests shouldn't have shard_range tables  https://review.openstack.org/56985622:29
*** mikecmpbll has joined #openstack-swift22:34
timburkeoh yay! someone already wrote up https://bugs.launchpad.net/openstack-gate/+bug/170870422:46
openstackLaunchpad bug 1708704 in OpenStack-Gate "yum client: [Errno 256] No more mirrors to try" [Undecided,New]22:46
timburkelooks like manila's already found a workaround!? sweet! https://review.openstack.org/#/c/569360/22:47
patchbotpatch 569360 - manila - Fix manila-tempest-*-centos-7 jobs (MERGED)22:47
openstackgerritTim Burke proposed openstack/swift master: Fix probe tests in the gate  https://review.openstack.org/56988222:52
claygtimburke: you're a mad man!  56988222:53
timburkeclayg: the commit message may be more hope than fact ;-)22:53
claygif the gate passes can we get the abridged story in the commit message?  I'll pour a glass of wine and snuggle up with my phone ..22:54
timburke...it's not super-interesting. the manila folks did all the heavy lifting and spotted the centos-devel message: https://lists.centos.org/pipermail/centos-devel/2018-March/016542.html22:57
*** amandap has joined #openstack-swift22:58
timburkebasically, we need /etc/yum/vars/contentdir to say "centos" and it either wasn't getting set, or was saying "altarch", or *something*22:58
timburkemaybe related? https://bugs.centos.org/view.php?id=1479522:59
timburkealready doing loads better: http://zuul.openstack.org/stream.html?uuid=e42544d0e627464faae31646eabd4563&logfile=console.log22:59
*** amandap has quit IRC23:02
*** threestrands has joined #openstack-swift23:05
*** amandap has joined #openstack-swift23:08
timburkeclayg: how much do you really care about the story? or is the link to someone else's write-up (which in turn includes links to how kolla and tripleo fixed it) enough?23:11
timburke'cause those probe tests look like they're gonna pass, and i'd rather not waste wall time if i'm gonna need to push up an updated commit message23:12
notmynametimburke: great work. IMO a link to someone else's writeup is find23:13
notmyname*fine23:13
notmynameah, the related-change id. got it23:14
notmynametimburke: I'm personally good with it, as-is23:14
claygprobably i'm just not good at reading playbooks!23:15
clayg... and I think I missed the related change - cause I hadn't looked at it before23:15
claygi wonder why whoever is producing these images wouldn't want contentdir to just be populated to start with?23:20
timburkeno idea. something tells me eventually this would have resolved itself, and the base images would start including it... but i want working probe tests in the gate faster than "eventually"23:28
*** armaan has quit IRC23:28
clayg👍23:28
claygwhen do we get to find out if it works!!!23:29
*** armaan has joined #openstack-swift23:29
timburkeclayg: we already know it does :-) http://zuul.openstack.org/ shows that change just waiting on the two long-running jobs -- everything else (including probe tests) passed23:36
clayg:shipit:23:37
openstackgerritTim Burke proposed openstack/swift master: Clean up direct_client's gen_headers  https://review.openstack.org/56988423:40
openstackgerritMerged openstack/swift master: Maintain manage-shard-ranges docs in its module  https://review.openstack.org/56979923:41
clayg+19, -78 <- LIKE A BOSS!23:45
*** amandap has quit IRC23:49

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