Friday, 2016-11-04

*** mariusv has quit IRC00:15
*** mariusv has joined #openstack-swift00:15
*** mariusv has joined #openstack-swift00:15
*** links has joined #openstack-swift00:27
*** Jeffrey4l has quit IRC00:30
*** zhugaoxiao has quit IRC00:30
*** zhugaoxiao has joined #openstack-swift00:30
*** Jeffrey4l has joined #openstack-swift00:31
*** jerrygb has joined #openstack-swift01:26
*** jerrygb_ has quit IRC01:27
*** takashi has joined #openstack-swift01:30
*** jerrygb_ has joined #openstack-swift01:32
*** jerrygb has quit IRC01:35
*** jerrygb_ has quit IRC01:39
*** dmorita has quit IRC01:41
*** jerrygb has joined #openstack-swift01:41
*** jerrygb has quit IRC01:49
*** jerrygb has joined #openstack-swift01:50
*** chlong has joined #openstack-swift02:06
*** jerrygb has quit IRC02:12
*** jerrygb has joined #openstack-swift02:13
*** jerrygb has quit IRC02:29
*** jerrygb has joined #openstack-swift02:30
kota_morning02:32
*** winggundamth has quit IRC02:37
*** jerrygb_ has joined #openstack-swift02:42
*** winggundamth has joined #openstack-swift02:43
*** jerrygb has quit IRC02:44
*** jerrygb has joined #openstack-swift02:47
*** jerrygb_ has quit IRC02:50
*** dmorita has joined #openstack-swift03:42
*** dmorita has quit IRC03:46
*** vinsh has quit IRC04:09
*** jerrygb has quit IRC04:24
*** SkyRocknRoll has joined #openstack-swift04:54
*** viktork has joined #openstack-swift05:01
*** ppai has joined #openstack-swift05:08
charz_kota_: good morning!05:13
openstackgerritChangBo Guo(gcb) proposed openstack/swift: Enable DeprecationWarning in test environments  https://review.openstack.org/38111705:13
kota_charz_: hi ;-)05:13
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: Fix error handling on gf_ivnert_matrix in isa-l backend  https://review.openstack.org/39359505:33
kota_hmmm... i wanna write a few of patches for liberasurecode but i like to depends on patch 387879 because it should land asap to prevent regressions05:35
patchbothttps://review.openstack.org/#/c/387879/ - liberasurecode - Fix liberasurecode skipping a bunch of invalid_arg...05:35
kota_so maybe working to land patch 387879 at first, then improve anything else should be a way go fast.05:36
patchbothttps://review.openstack.org/#/c/387879/ - liberasurecode - Fix liberasurecode skipping a bunch of invalid_arg...05:36
kota_thx tsg to add kmgreen to the reviewer.05:37
kota_tsg: (if you are in this channel)05:37
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: Fix error handling on gf_ivnert_matrix in isa-l backend  https://review.openstack.org/39359505:43
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: Fix error handling on gf_ivnert_matrix in isa-l backend  https://review.openstack.org/39359505:45
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: WIP: ISA-L Cauchy support  https://review.openstack.org/39326305:47
*** rcernin has joined #openstack-swift05:55
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873606:03
*** vinsh has joined #openstack-swift06:09
*** vinsh has quit IRC06:14
*** ChubYann has quit IRC06:27
zaitcevhttps://www.computerworlduk.com/cloud-computing/mark-shuttleworth-on-openstack-hpe-layoffs-prove-bs-as-service-theory-3648336/ - really, Shuttleworth? I can't wait to hear your opinion how Swift is unnecessary06:27
*** sams-gleb has joined #openstack-swift06:56
*** sams-gleb has joined #openstack-swift06:57
*** tesseract has joined #openstack-swift07:04
*** tesseract is now known as Guest1319407:04
*** klrmn has quit IRC07:24
ppaizaitcev: swift being one of the cores, I don't think he meant that about swift. But I totally get the reference to sheer number of new peripheral projects that have popped up.  Used to be just around 6 project code names.07:25
*** pcaruana has joined #openstack-swift07:33
*** chlong has quit IRC07:33
*** d0ugal has joined #openstack-swift08:07
*** hseipp has joined #openstack-swift08:10
*** rledisez has joined #openstack-swift08:18
*** d0ugal has quit IRC08:28
*** geaaru has joined #openstack-swift08:28
*** amoralej|off is now known as amoralej08:29
*** hseipp has quit IRC08:42
*** ppai has quit IRC08:51
*** cbartz has joined #openstack-swift08:55
*** hseipp has joined #openstack-swift08:55
*** hseipp has left #openstack-swift08:57
*** d0ugal_ has joined #openstack-swift08:58
*** hseipp has joined #openstack-swift09:18
openstackgerritKota Tsuyuzaki proposed openstack/pyeclib: Add greedy test for decode/reconstruct result solid  https://review.openstack.org/39365609:18
*** silor has joined #openstack-swift09:19
*** jordanP has joined #openstack-swift09:20
*** silor1 has joined #openstack-swift09:22
*** silor has quit IRC09:24
*** silor1 is now known as silor09:24
*** kei_yama has quit IRC09:27
kota_oh, notmyname already worked on the backporting for audit patch, https://review.openstack.org/#/c/38974609:37
patchbotpatch 389746 - swift (stable/mitaka) - Make ECDiskFileReader check fragment metadata (MERGED)09:37
kota_good job09:37
kota_i just was searching the patches in open reviews.09:37
openstackgerritKota Tsuyuzaki proposed openstack/pyeclib: WIP: ISA-L Cauchy support  https://review.openstack.org/39327609:38
*** acoles_ is now known as acoles09:43
*** d0ugal_ is now known as d0ugal09:51
*** d0ugal has joined #openstack-swift09:51
acolestimburke: thanks for doing the backport09:55
admin6aoles: kota_ Hi, thanks for the backport to mitaka for checking EC fragments metadata. I applied it, and it seems to work, but sometimes, I have errors on os.rename with no such file or directory : http://paste.openstack.org/show/587874/09:59
*** takashi has quit IRC10:00
openstackgerritKota Tsuyuzaki proposed openstack/liberasurecode: Fix liberasurecode skipping a bunch of invalid_args tests  https://review.openstack.org/38787910:01
kota_admin6: looking10:01
kota_acoles: oh, backporting patch is stil open?10:02
kota_still10:02
kota_hi, acoles and admin6 anyway.10:02
*** dmorita has joined #openstack-swift10:03
kota_dmorita!!??10:04
kota_admin6: it looks like to fail to move the corrupted fragments to move quarantine dir but no info appeared which one doesn't exist...10:05
kota_s/fragments/fragment/ it's single.10:05
kota_either the fragment has been quarantined or no quarantine dir.10:05
kota_lemme check the code..10:06
*** dmorita has quit IRC10:07
admin6kota_ it seems to be only on device s02z2ecd03, other devices have good quarantine Invalid EC logs10:08
kota_could you quick check if quarantine dir exists or not in the device?10:09
*** vinsh has joined #openstack-swift10:11
kota_AFAIK, the renamer can dig the directory structure if it's nested so it could happen either racing to make/delete the dir or no source file?10:12
kota_or failed to dig the dir?10:13
admin6kota_ the quarantine dir exist and has good permissions. The corrupted fragment is present in the quarantine dir : ls -al /srv/node/s02z2ecd03/quarantined/objects-1/91021a50d6c103235c1fc0a4fa0cebdd/10:16
*** vinsh has quit IRC10:16
admin6-rw------- 1 swift swift 2790878 Sep 25 14:14 1470952148.01588#3.data10:16
patchbothttps://review.openstack.org/#/c/25/ - openstack-infra/system-config - Manage apt and gems path with puppet. Add tarmac.c... (MERGED)10:16
admin6-rw-r--r-- 1 swift swift       0 Sep 25 14:14 1470952148.01588.durable10:16
patchbothttps://review.openstack.org/#/c/25/ - openstack-infra/system-config - Manage apt and gems path with puppet. Add tarmac.c... (MERGED)10:16
kota_you don't have to work, patchbot10:16
kota_admin6: the error is only in auditor? or object-server too?10:22
kota_so if the auditor detects the frag corrupted and at the same time, someone request to GET the object, both object-server and object-auditor could race to move it to quarantine dir10:23
kota_and the looser on the race might dump the error, in my current idea.10:23
kota_not sure10:23
kota_but curious, it happens only a device...10:24
acoleskota_: admin6 so the frag has been quarantined but we also get the traceback from renamer - I'm looking for path where we maybe try to quarantine the same frag twice, but can't see it yet :/10:26
admin6I don’t see error in the object-server so far. however it doesn’t happen on only one device, but it happens always on the same devices10:26
admin6kota_ some device logs fine quarantine, but some always log this error when they quarantine frags. I doubt it could be a race condition with the object-server10:29
admin6kota_ I’ve also seen anothe type of error : " line 1800, in close#012    {'exc': e, 'stack': ''.join(traceback.format_stack()),#012"   http://paste.openstack.org/show/587879/   I’m rolling back my servers to unpatched versions.10:34
*** vint_bra1 has joined #openstack-swift10:41
kota_hmmm10:42
*** blair has quit IRC10:42
*** janonymous has quit IRC10:42
*** vint_bra has quit IRC10:43
*** AndyWojo has quit IRC10:43
*** nottrobin has quit IRC10:43
*** philipw has quit IRC10:43
*** fungi has quit IRC10:44
*** tdasilva has quit IRC10:44
*** calebb has quit IRC10:44
*** tries_ has quit IRC10:44
*** philipw has joined #openstack-swift10:45
*** AndyWojo has joined #openstack-swift10:45
*** nottrobin has joined #openstack-swift10:45
acolesso, do we somehow have a race between the reader quarantining the frag while reading and also attempting to quarantine while closing (in _handle_close_quarantine)?? One or other will fail, producing one or other of admin6 logs. The frag would be quarantined so if this is the case we're looking at log noise, not failure to quarantine. BUT I can't see how that can happen yet i.e. read a chunk, check it, quarantine *and* als10:46
acoleso call _handle_close_quarantine. It would mean read_to_eof is True.10:46
acoleskota_: ^^10:46
*** openstackgerrit has quit IRC10:47
*** openstackgerrit has joined #openstack-swift10:48
kota_acoles: could be? not yet get the path.10:52
*** blair has joined #openstack-swift10:53
kota_if the bad frag appeared at the mid of the file, DiskFileQuarantined will be raised so i doesn't seem to go read_to_eof  == True10:54
kota_and if the bad frag is in the tail, no check_frag doesn't anything untill to get into the tail...10:55
acoleskota_: agree, but see line 3 of this paste ... the frag has been quarantined, but the exception raised in close() suggests that the _handle_close_quarantine got called ??10:56
admin6kota_ acoles: I checked 6 or 7 error logs on different servers and different devices, the corrupted frags always has been quarantined correctly10:56
kota_acoles: yeah, that's odd.10:56
*** tries_ has joined #openstack-swift10:57
*** tries_ has quit IRC10:57
*** tries_ has joined #openstack-swift10:57
*** janonymous has joined #openstack-swift10:57
acolesadmin6: good! I think/hope that the logger error is due to an unnecessary second attempt to quarantine. But I'd like to figure out why!10:58
*** calebb has joined #openstack-swift10:58
*** fungi has joined #openstack-swift10:58
kota_acoles: not sure if auditor calling the reader with closing context but the reader already has the final statement to close itself11:09
kota_acoles: does it trigger the duplication?11:09
*** CrackerJackMack has quit IRC11:10
kota_so, if i got true, it could happen when 1. it doesn't include corrupted fragment metdata 2. it has invalid md5sum, maybe?11:11
kota_try to make sure the tests11:11
kota_no, 1 is probably false11:11
kota_since admin6's paste11:12
kota_the duplication could be, try to make sure..11:13
*** hseipp has quit IRC11:16
acoleskota_: yeah I am looking at the same (two calls to reader.close) but not sure that explains the other traceback (renamer fails during read of a chunk)11:16
acolesline 8 of paste11:17
*** CrackerJackMack has joined #openstack-swift11:18
*** gopenshaw_ has quit IRC11:19
*** vinsh has joined #openstack-swift11:23
acoleskota_: reader.close() sets self._fp None and also uses self._fp as a guard so it won't execute twidce11:39
*** tdasilva has joined #openstack-swift11:40
*** d0ugal has quit IRC11:40
acolestwice*11:40
kota_acoles: sure11:40
acoleskota_: so i am back to wondering if somehow check_frag is called during iter and also during close->handle_close_quarantine11:41
acolesfor same data file, which would result in a duplication of renamer calls11:42
acoleskota_ should be going home ?11:42
kota_acoles: might be11:43
kota_not yet11:43
*** d0ugal has joined #openstack-swift11:45
kota_still in fog :(11:59
acoleskota_: another crazy thought...the renamer retries once if an OSError is raised...is it possible that the first rename does perform the file move but also raises an OSError (like I said, crazy thinking) so the second attempt fails. i.e. there is just one call to renamer??12:02
kota_acoles: sounds crazy but could be possible but i cannot think it happens so frequently...12:04
acoleskota_: yep. v unlikely. more likely something to do with the reader iter but I can't see it. seems like another call to the iter is needed AFTER the quarantine has occurred and the exception raised. Then, we'd see both of admin6 cases depending on whether there was more data to read (another call to check_frag) or no more data (so close calls handle_close_quarantine calls check_frag)12:10
*** chlong has joined #openstack-swift12:13
kota_acoles: probably similar thought to me but right now no idea where we catch the exception and retry the iter calls12:17
kota_acoles: one minor mistake could be found.12:22
*** jerrygb has joined #openstack-swift12:23
kota_acoles: i don't think it is related to the admin6's issue though, https://github.com/openstack/swift/blob/master/swift/obj/diskfile.py#L2648 line may be unecessary12:23
kota_acoles: it seems we can expect DiskFileQuarantined will be raised at self._quarantine with quarantine_hook12:24
kota_and it seems object-server doesn't want to raise an exception during transferring the data, maybe?12:25
kota_it calls without quarantine_hook12:25
acolesI think clayg added that and i think it is so that when detecting corrupt frag during a GET (not audit) then the GET will terminate early12:26
acolesquarantine_hook only installed by auditor12:26
openstackgerritChristian Hugo proposed openstack/swift: Raise ValueError if a config section does not exist  https://review.openstack.org/39338812:28
*** jerrygb has quit IRC12:31
*** iurygregory has quit IRC12:32
*** hseipp has joined #openstack-swift12:33
kota_acoles: on the duplication call, i'm now wondering, how we can capture the *diskfile* log message?12:33
kota_acoles: unit test looks to capture the auditor's logger and assert only error lines...12:34
kota_diskfile's logger is from manager, let me check...12:34
kota_audit worker's logger seems to be passed to the diskfile router so the router pass it to diskfile, maybe?12:36
kota_hmm...12:36
kota_oh, yeah, trying to warning level log lines, it looks like there is the diskfile's line.12:37
acolesyes the auditor creates DF manager with the same logger as auditor12:39
acolesso we see the warning from diskfile12:39
kota_acoles: moving on another idea/question, can threadpool.run_in_thread return sort of None?12:40
kota_if something fails12:40
kota_if we still have self.frag_buf and the run_in_thread failed and return None, it seems to go close with read_to_eof = True12:41
kota_and then, with closing statement also trying to close???12:42
*** jerrygb has joined #openstack-swift12:42
*** vinsh has quit IRC12:45
*** chlong has quit IRC12:46
admin6kota_ acoles: I need to leave. thanks for looking to this error. I’ve re-applied the patch and I’ll let it run for a while as long as it seems to be only a "noise" log error (I hope so). I’ll survey the IRC for your comment tonight (in about 6-8 hours) Let me know if you need more logs/infos.12:48
acoleskota_: yes, but close() will only call handle_close_quarantine once because self._fp is set to None in the finally. And the finally is executed *before* the DiskFileQuarantine exception is handled in the auditor, so the "with closing" context would find self._fp=None, I *think*??12:48
acolesadmin6: ok, thanks for flagging this up12:48
acoleskota_: I am away for lunch12:49
kota_acoles: ok, and i have to leave my office12:49
kota_will think more next week.12:49
*** hseipp has quit IRC12:52
*** jerrygb has quit IRC13:01
*** admin6 has quit IRC13:03
*** StraubTW has joined #openstack-swift13:09
*** StraubTW_ has joined #openstack-swift13:10
*** hseipp has joined #openstack-swift13:10
*** d0ugal has quit IRC13:12
*** StraubTW has quit IRC13:13
*** SkyRocknRoll has quit IRC13:13
*** links has quit IRC13:13
*** silor has quit IRC13:19
*** d0ugal has joined #openstack-swift13:21
*** silor has joined #openstack-swift13:26
*** daemontool has joined #openstack-swift13:32
*** amoralej is now known as amoralej|lunch13:32
*** d0ugal has quit IRC13:35
*** d0ugal has joined #openstack-swift13:37
*** jerrygb has joined #openstack-swift13:39
*** jerrygb has quit IRC13:39
*** jroll is now known as jrollinhatin13:40
*** jerrygb has joined #openstack-swift13:46
*** doxavore has joined #openstack-swift13:47
*** jerrygb has quit IRC13:48
*** sweeper has joined #openstack-swift13:50
*** d0ugal_ has joined #openstack-swift13:51
sweeperso13:53
*** d0ugal has quit IRC13:53
sweeperI've got this cluster that's gone through a rough week or so, with the colo deciding to turn off half of our rack one day, followed by the other half the next day13:54
sweeperthis shook out a drive or three, so we did a rebalance13:54
sweepernow we're looking at this drive that's full to 100% when it should really be around 90% tops13:55
*** sgundur has joined #openstack-swift13:58
*** Guest13194 has quit IRC13:58
acoleskota_: admin6 I filed a bug report here bug 1639244 , I have to work on some other stuff rest of today, we'll try to get some other minds to think on it14:02
openstackbug 1639244 in OpenStack Object Storage (swift) "Auditor logs "No such file" errors when renaming corrupt EC fragments" [Undecided,New] https://launchpad.net/bugs/163924414:02
sweeperis there a way to see if this is just a result of the ongoing rebalance? allocation in the ringfile looks right14:09
*** Guest13194 has joined #openstack-swift14:13
openstackgerritNandini Tata proposed openstack/swift: Multi Swift - Multiple Swift clusters on same h/w  https://review.openstack.org/39379414:17
*** donagh has quit IRC14:24
*** vinsh has joined #openstack-swift14:27
*** jistr is now known as jistr|call14:29
acolessweeper: try asking later (west coast US time), someone there may be able to answer14:29
acolesadmin6: can you double check you don't have two auditor processes running on the same node? (I'm clutching at straws, but worth asking)14:31
*** d0ugal_ has quit IRC14:39
*** d0ugal has joined #openstack-swift14:39
*** amoralej|lunch is now known as amoralej14:46
*** jerrygb_ has joined #openstack-swift14:52
*** jerrygb has joined #openstack-swift15:01
*** jistr|call is now known as jistr15:03
*** jerrygb_ has quit IRC15:04
*** zul has quit IRC15:07
*** zul has joined #openstack-swift15:08
*** jistr is now known as jistr|biab15:10
*** zul has quit IRC15:10
*** zul has joined #openstack-swift15:12
*** jistr|biab is now known as jistr15:14
*** Victor777 has joined #openstack-swift15:19
*** Victor777 has quit IRC15:24
*** sgundur has quit IRC15:24
*** sgundur has joined #openstack-swift15:25
*** rcernin has quit IRC15:25
*** chsc has joined #openstack-swift15:25
*** chsc has joined #openstack-swift15:25
notmynamegood morning15:26
notmynameacoles: west coast US time, you say?15:26
*** rcernin has joined #openstack-swift15:27
acolesnotmyname: that's now is it? I think we're only 7 hours apart this week15:28
notmynameyep. 8:30 ish here right now15:28
notmynameso, for most people we work with on the west coast, that hardly counts as "morning" ;-)15:28
sweeperdamn hippies15:29
notmynamefungi: I have a CI question. in general, if a project needed to pull in a dependency and build it from source (ie instead of pulling a distro package), how would one do that? is there anythign in infra that currently supports that?15:29
acoleslol15:29
funginotmyname: i think it would be very situationally dependent15:29
notmynamesweeper: I'm likely not exactly the right person to answer your question, but I can give it a shot. you're trying to figure out if the drive fullness is because of rebalancing? or failures? or ...?15:30
funginotmyname: i mean, technically there are plenty of jobs that do that now. if you have a python project depend on pycrypto i'll pull down sdists of numpy that build c extensions against cffi.h15:30
notmynamefungi: ah, right15:30
notmynamefungi: specifically for swift I'm thinking of the EC libraries or the future golang stuff (if the TC sticks with "not in the swift repo")15:31
fungiand we have jobs that build java-based projects with maven or similar tools15:31
fungiso those are grabbing random java deps from the 'net before compiling15:32
notmynamefungi: do they build a binary that's then available in the PATH? or are they building a distro package and then installing that?15:32
fungifor the java case they typically build a jar, war, whatever and then run that under a jvm15:32
fungii think there's an effort starting with nova wanting to test against just-in-time builds of libvirt and qemu from trunk as well15:34
fungithough i don't know if they've worked out the details on that yet15:34
notmynameah, interesting15:35
fungii know they were waffling between compiling in-job vs having a separate periodic job to build packages of those their jobs could grab15:35
notmynameregardless of where the code lives (in or out of today's swift repo), we'll have to solve the build problem for golang stuff. ie build from source and test that instead of installing some distro package version15:35
notmynameyeah, we considered that too. eg a nightly build that we use15:36
notmynameI'm not a big fan of that. seems to be the worst of both worlds15:36
fungiyep. the up-side is that it speeds up your tests because you don't have to wait for the build15:36
fungidown side, which we see with projects that do this already to create things like service images, is that if your periodic update publishes a broken artifact your jobs are all instabroken until you solve that15:37
notmynameour tests are currently slow because of devstack setup. that is, those are the longest running tests by far, so we've got a fairly generous "budget" to play with, if jobs run concurrently, before we increase the wall-time of a check15:38
*** Guest13194 is now known as tesseract-15:38
fungiyep, so as i said, highly situationally dependent15:38
fungiit comes down to what tradeoffs you're willing to make15:39
notmynameheh. our in-tree unit and functional tests each are about 5 minutes long. gate-tempest-dsvm-neutron-identity-v3-only-full-ubuntu-xenial-nv is 45 minutes15:40
notmynameby the way, what is that test?15:40
notmynamewhy does swift need to have an extra 15 minutes (next slowest is only 30 min) for testing neutron with keystone v3?15:40
fungii believe that's a devstack integration job using neutron instead of nova-net and keystone v3 api instead of v2, running the "full" set of tempest tests on ubuntu-xenial but not voting (because you're probably still relying on ubuntu-trusty and need to switch)15:41
notmynamewe're running gate-swift-dsvm-functional-identity-v3-only-ubuntu-xenial-nv (in ~15 min) and that's passing15:42
fungisure, that probably doesn't, e.g., set up glance and exercise it to make sure that changes to swift don't break glance's use of it as a storage backend15:43
notmynameanyway, it's jsut something I didn't (don't) know about. thought I'd ask. if we're all running that to make sure of something, that's good for me15:44
fungiagreed, those are questions better posed to the qa team15:44
fungifrom an infra perspective, i just want to make sure that if there are jobs you want to run, we have the support in place for you to be able to do so15:45
notmynamethanks :-)15:45
notmynamewhat I want to run is something that builds a binary from source. at some point soon, we need to figure that out together (I hope)15:46
notmynamepdardeau: you've got keystone set up against your swift dev cluster(s) right?15:47
fungisure. ultimately what our ci platform gives you is a way to run shell scripts in a vm with root access. so really it's a blank slate if you want, but there are almost certainly modular bits of prior art we can draw from so you don't have to write it from the ground up15:47
notmynamecool15:47
notmynamesounds like `./configure && make && make install` is even reasonable. we put that in a script in our repo, then call it from the gate job, and done!15:48
fungiyep15:48
notmynameoh, speaking of gate changes, I've got one other thing on my plate15:49
notmynameI need to make a new job template copied from the py27 base one that adds an XFS partition15:49
notmynamelikely will mount /tmp as XFS15:49
notmynamejust a head's up that I'm hoping to get that done...hmm, it's already friday. maybe next week then15:50
notmynamemaybe today. we'll see what comes up15:50
fungisure, i remember discussing it with you. the tox-based python unit test jobs are pretty modular already, so shouldn't be hard. just need to add a custom shell builder prior to revoke-sudo that does your mkfs and mount15:51
notmynameright15:51
notmynameI'd prefer to do that in the existing job template, but I've been told that would be unacceptable15:51
*** stradling has joined #openstack-swift15:52
fungiwell, the existing template is pretty hollow. a copy of that to be xfs-specific wouldn't be a problem15:52
fungithe main sticking point, if i recall, was making sure the xfs-requiring tests are opportunistic so you can also continue to run an xfs-less unit test to meet the consistent testing interface guidelines15:54
notmynameyeah, I'm not worried about the "difficulty" of making a new job template. that looks easy. but yeah, that15:54
*** bogdands has joined #openstack-swift15:54
notmynameit makes the existing py27 jobs skip about 1/3 of the tests and all the associated code in repo to handle that15:54
stradlingHey, guys -- newb here. Looking for guidance on puppet-swift -- has development moved from puppetforge to Github definitively, or will the changes eventually flow back to puppetforge?15:55
fungialternative being to mock those interactions in your unit tests so they don't touch an actual local fs, and then do your real xfs testing in the functional job. presumably you have good reasons to discount that solution tough15:55
notmynamestradling: I have no idea. fungi, do you know where openstack puppet devs hang out?15:55
fungistradling: https://wiki.openstack.org/wiki/IRC says they have a #openstack-uppet channel15:56
fungier, #openstack-puppet15:56
stradlingNice. Thanks!15:56
*** nikivi has joined #openstack-swift15:56
notmynamefungi: yeah, that's what we're actually replacing. we were halfway mocking a filesystem. so the option is either to write a pretty-close-to-real FS as a mock or use one that's provided to us on the test node. that second option is much preferred15:56
*** rcernin has quit IRC15:56
*** Victor777 has joined #openstack-swift15:57
notmynamepoint being that in many ways swift's job is to write a file in a filesystem. makes it *really* hard to test if you don't actually have a filesystem to write to15:57
fungisure. just also makes it hard as a local dev to run swift unit tests without knowing that you need to do extra setup15:58
notmynamebut yeah. plan right now is to add the all the skips and then make a new gate job15:58
*** pcaruana has quit IRC15:58
fungianyway, we can definitely make it work. give me a heads up once you have a first stab and i'll give it a once-over15:58
*** tesseract- has quit IRC15:59
bogdandsHi everyone. I've been struggling with something for a few days now and figured this is my last chance of figuring it out. I want to have all users of a project with the role of _member_ being able to list containers, I thought you'd have to edit the policy.json file and add something like .."identity:list_containers": "rule:member", where member is "role:_member_", but it doesn't really work and I've tried several other15:59
bogdandswould be awesome if someone has any insight on this15:59
notmynameI disagree with the level of difficulty added. but i also don't think it's too important to argue about. the path forward with the least issues is a new job template. makes our code more complex, but that's what we're paid to do as devs15:59
notmynamefungi: thanks15:59
*** Victor777 has quit IRC15:59
funginotmyname: you're welcome! always happy to help15:59
notmynameacoles: is guy fawkes day tomorrow a thing that's celebrated? or is that something that americans think is a brittish holiday because of a movie that came out a few years ago?16:00
pdardeaunotmyname: no, we don't use keystone. we've taken very brief looks into it a couple of times.16:01
notmynamepdardeau: ah. ok. I was wondering about the impact of fernet tokens16:01
notmynamepdardeau: I thought you might have had some experience there or at least something set up to easily compare16:01
*** jordanP_ has joined #openstack-swift16:02
acolesnotmyname: yes it is widely celebrated this weekend - bonfires and fireworks galore!16:02
notmynameoh, fun!16:03
acolesnot if you are a dog ;)16:03
notmynamelol16:03
*** jordanP has quit IRC16:04
*** jordan__ has joined #openstack-swift16:04
*** Victor777 has joined #openstack-swift16:04
acolesor, in the past, a cat, but that's not a pleasant tale16:05
*** 18VAABSMN has quit IRC16:06
*** jordanP_ has quit IRC16:08
*** Victor777 has quit IRC16:08
*** raginbaj- has joined #openstack-swift16:09
*** cebruns_ has quit IRC16:11
*** cebruns_ has joined #openstack-swift16:14
acolesbogdands: swift doesn't use policy.json files. Any user with an operator_role on a project as defined in proxy-server.conf can list containers. Default operator_roles are admin and swiftoperator.16:20
bogdandsthanks for the reply, but can I have a user that cannot write/create containers and still be able to list them16:21
*** diogogmt has joined #openstack-swift16:27
acolesbogdands: you cannot achieve that with roles, but you can with container ACLs - you can use a read ACL to grant read access to users which allows them to list container and read its objects. The best description is here https://review.openstack.org/#/c/374215/4/doc/source/overview_acl.rst which is a patch we have yet to merge into the docs16:28
patchbotpatch 374215 - swift - Document access control lists (ACLs)16:28
acolesbogdands: also see docs here http://docs.openstack.org/developer/swift/overview_auth.html#access-control-using-keystoneauth16:31
*** dmorita has joined #openstack-swift16:32
*** dmorita has quit IRC16:34
*** dmorita has joined #openstack-swift16:34
bogdandsacoles: thanks, but I also need the users to be able to list all available containers, which I'm afraid won't be possible if done in this manner16:41
acolesbogdands: correct, with keystone auth only users with operator_role can list all containers in a project, and those users can also modify them, so that does not achieve your goal. There is work in progress to add account level ACL support for keystone auth https://review.openstack.org/#/c/356715/16:43
patchbotpatch 356715 - swift - Supporting Account ACL in keystoneauth16:43
claygweee16:44
bogdandsok, thank you acoles. Really appreciate your answer. Cheers16:44
claygacoles used to be a cat?16:45
* acoles purrs16:46
acolesclayg: kota and I got completely stumped looking into this https://bugs.launchpad.net/swift/+bug/163924416:47
openstackLaunchpad bug 1639244 in OpenStack Object Storage (swift) "Auditor logs "No such file" errors when renaming corrupt EC fragments" [Undecided,New]16:47
acolesadmin6 applied the Mitaka backport, saw corrupt frags quarantined (good!) but also some error logs16:48
claygmaybe the file is not very long/big (i.e. < 64K)16:48
claygI would have swore I saw that once in dev when I was doing functional testing - but it was laborsome - the patch changed - and I sort of forgot about it16:49
claygacoles: neway - i'll look16:49
acolescouldn't see how that would cause duplicate attempts to quarantine16:49
acolesoh, interesting16:49
claygi was sorta looking at it already - but I'm going to spend some time with liberasurecode stuff today too - so my head should be pleanty in EC (no guarantee I'll see something you missed tho, probably the oppostite)16:49
acolesclayg: one of the culprit frags was listed by admin6, >2M http://eavesdrop.openstack.org/irclogs/%23openstack-swift/%23openstack-swift.2016-11-04.log.html#t2016-11-04T10:16:0916:51
acolesclayg: ok, I was just mentioning it cos sometimes fresh eyes produce an "aha" moment16:51
*** bogdands has quit IRC16:51
*** jamielennox is now known as jamielennox|away16:51
claygacoles: so you're saying asking clayg if he can offer anything useful is sort of a last ditch hail mary shot in the dark - but what have you got too loose?16:52
*** dmorita has quit IRC16:57
*** dmorita has joined #openstack-swift16:57
*** dmorita has quit IRC16:57
acoleslol16:59
*** dmorita has joined #openstack-swift16:59
acolesI'm admitting defeat16:59
*** nikivi has quit IRC17:01
clayggo enjoy some fireworks17:05
*** klrmn has joined #openstack-swift17:06
*** rledisez has quit IRC17:06
*** hseipp has quit IRC17:09
*** stradling has quit IRC17:20
claygntata: I really thought the few places we hard code /etc/swift/swift.conf made multi-swift impossible to do w/o some patching?  patch 39379417:21
patchbothttps://review.openstack.org/#/c/393794/ - swift - Multi Swift - Multiple Swift clusters on same h/w17:21
*** ChubYann has joined #openstack-swift17:21
claygtimburke: man it's going to be *really* hard to keep probetests running with encryption if people aren't running saio's with encryption turned on (vsaio makes it easy to swap into encryption, but I leave it off mostly)17:25
clayg... makes me wonder about our auditor ec checksum patches and encryption :'(17:25
openstackgerritClay Gerrard proposed openstack/swift: Add probetest for response with duplicate frags  https://review.openstack.org/37177117:29
clayg^ test only change - added back acoles +217:32
claygAlthough - I didn't run it with encryption turned on :\17:32
*** sgundur has quit IRC17:33
*** sgundur has joined #openstack-swift17:33
*** cbartz has left #openstack-swift17:35
*** d0ugal has quit IRC17:39
acolesI just did17:49
acolesclayg: so is this a case where I should just go ahead and approve? seems like we could do that17:50
pdardeauclayg: cschwede: i like the graphics you used in ring talk17:51
acolespdardeau: I want t-shirts with those graphics :)17:56
clayglike with the parts in buckets and arrows?  or the one with krik cursing rings?17:59
*** jordan__ has quit IRC18:01
acolesparts in buckets18:02
acolesbedlinen, towels... ;)18:03
* acoles thinks it may be time to go.18:04
*** acoles is now known as acoles_18:05
pdardeauclayg: i liked all of them! i'll probably end up having to re-watch it about 20 times to grok the content, so i'll keep better track on next viewing. ;-)18:05
*** links has joined #openstack-swift18:09
*** links has quit IRC18:10
*** daemontool has quit IRC18:19
*** klrmn has quit IRC18:34
*** sgundur has quit IRC18:36
*** sgundur has joined #openstack-swift18:37
*** klrmn has joined #openstack-swift18:37
*** klrmn has quit IRC18:38
*** klrmn has joined #openstack-swift18:38
*** jamielennox|away has quit IRC18:38
*** dmorita has quit IRC18:40
clayglol18:41
claygbedlinen, towels!?18:41
claygnow *I* have to rewatch it?!18:41
*** dmorita has joined #openstack-swift18:41
openstackgerritMerged openstack/swift: Add probetest for response with duplicate frags  https://review.openstack.org/37177118:42
openstackgerritPete Zaitcev proposed openstack/liberasurecode: Fix liberasurecode skipping a bunch of invalid_args tests  https://review.openstack.org/38787918:42
*** jerrygb has quit IRC18:45
*** jerrygb has joined #openstack-swift18:45
*** david_c_ has joined #openstack-swift18:47
*** geaaru has quit IRC18:54
*** doxavore has quit IRC18:59
claygtimburke: do you have a system to keep track of the backports for all the high/critical bugs we've been fixing?19:03
openstackgerritTim Burke proposed openstack/swift: Reduce backend requests for SLO If-Match / HEAD requests  https://review.openstack.org/34753819:03
openstackgerritTim Burke proposed openstack/swift: Confirm receipt of SLO PUT with etag  https://review.openstack.org/39090119:03
timburkeclayg: i've got https://review.openstack.org/#/dashboard/?title=Open+Backports&foreach=is:open+branch:%255Estable/.*&Swift=project:openstack/swift&Swift+Client=project:openstack/python-swiftclient but that only surfaces the backports that have already been proposed. in terms of identifying patches that should be backported but haven't yet, no, i don't have a good solution beyond "someone said maybe we should backport this -- i should19:09
timburkego propose it!"19:09
patchbotError: No closing quotation19:09
*** amoralej is now known as amoralej|off19:11
*** jamielennox|away has joined #openstack-swift19:13
*** jamielennox|away is now known as jamielennox19:13
*** jerrygb has quit IRC19:14
claygnotmyname: maybe a good friday project would be to hack up patchbot so that the only responses he can give are the patch description lines?19:16
*** jerrygb has joined #openstack-swift19:16
clayglike `if "review.openstack.org" not in response: return` or something19:18
timburkeclayg: i think it runs deeper than that, unfortunately. like, we need to rewrite some/all of supybot, which seems to have defaulted to enabling a bunch of things when notmyname changed the machine that was running patchbot19:21
pdardeauhere is what patchbot is currently thinking: https://www.youtube.com/watch?v=c8N72t7aScY19:24
zaitcevthis better not be a music video by Rick Astley20:00
*** jerrygb_ has joined #openstack-swift20:01
*** jerrygb has quit IRC20:05
*** jerrygb_ has quit IRC20:06
*** vinsh has quit IRC20:06
*** vinsh has joined #openstack-swift20:06
*** sileht has quit IRC20:21
claygtimburke: yeah totally - find the method that sucks in supy bot and monkey patch the hell out of it20:23
clayglike - there's probably only one place that acctually writes to the socket that goes out to irc - i'm saying stuff some jank in that method right there20:24
*** sileht has joined #openstack-swift20:28
timburkeclayg: this is how we get shit like https://github.com/openstack/swift/blob/2.10.0/swift/proxy/server.py#L220 and then we can't upgrade because socket._fileobject flat out *isn't a thing anymore*20:30
*** dmorita has quit IRC20:31
*** dmorita has joined #openstack-swift20:43
*** adb5a56 has joined #openstack-swift20:45
*** 7ITAAOQ37 has joined #openstack-swift20:48
*** 7ITAAOQ37 has quit IRC20:48
*** tries_ has quit IRC20:48
*** chsc has quit IRC20:52
*** chsc has joined #openstack-swift21:03
*** chsc has joined #openstack-swift21:03
*** sams-gleb has quit IRC21:06
*** sams-gleb has joined #openstack-swift21:06
*** sams-gleb has quit IRC21:11
claygtimburke: *totally*21:15
claygtimburke: where does socket keep it's fileobject now then?21:15
timburkeno gd clue21:15
*** silor has quit IRC21:19
claygtimburke: oh look how just *hands* every plugin the irc instance - it *wants* you to monkey patch takeMsg https://github.com/Supybot/Supybot/blob/159c1e7cd886cb5f8c68d1ba703b1d302a716e5d/src/drivers/Socket.py#L10221:21
*** chsc has quit IRC21:28
*** sgundur has quit IRC21:35
*** jrollinhatin is now known as jroll21:36
openstackgerritTim Burke proposed openstack/python-swiftclient: Add additional headers for HEAD/GET/DELETE requests.  https://review.openstack.org/37265621:39
*** StraubTW_ has quit IRC21:43
*** jerrygb has joined #openstack-swift21:51
*** vint_bra1 has quit IRC21:52
*** jerrygb has quit IRC21:56
ntataclayg, that's a good question. I made those changes in my personal repo that I forked. Multi Swift pulls Swift from my forked Swift repo and works :). I used the same idea of exporting SWIFT_ROOT from env variables and use it in the code.22:20
ntataI will propose upstream  the changes I made for a custom swift dir to work.22:21
*** diogogmt has quit IRC22:39
notmynameclayg: I think you hinted at this a few days ago, but yikes! https://github.com/openstack/swift/blob/master/test/functional/__init__.py#L46-L4922:39
notmynamethe rabbit hole goes deeper...22:40
*** dmorita has quit IRC22:44
claygnotmyname: cool right!22:45
notmynameneat!22:45
claygntata: yes yes yes!22:45
*** dmorita has joined #openstack-swift22:45
*** amoralej|off is now known as amoralej22:46
claygwho else was looking at the ec/ssync/auditor corrupt frag bugs?  I can't remember the easiest way to get corrupt frags on disk that match their etag metadata?22:46
openstackgerritMerged openstack/python-swiftclient: Enable code coverage report in console output  https://review.openstack.org/38866922:51
*** jerrygb has joined #openstack-swift22:52
zaitcevnotmyname: impressive22:58
*** jerrygb has quit IRC22:58
claygnew way to run into lp bug #1558754 - if you increase your replica count!  solution - let the builder do it's code instead of having stupid cli's doing stupid cli thing - workaround tell he cli to gtfo w/ -f23:11
openstackLaunchpad bug 1558754 in OpenStack Object Storage (swift) "remove devices before min-part-hours requires --force" [Undecided,Confirmed] https://launchpad.net/bugs/1558754 - Assigned to Jethro Sun (shwsun)23:11
openstackgerritNandini Tata proposed openstack/swift: Allow custom swift configuration directory  https://review.openstack.org/39395223:16
claygyay cschwede fixed it already!23:17
claygpatch 32696723:18
patchbothttps://review.openstack.org/#/c/326967/ - swift - Rebalance with min_part_seconds_left > 023:18
claygtdasilva: I ahve this vauge memory of at one time trying think about adding some sort of tag to bugs like "has a patch in gerrit"23:18
claygtdasilva: like "fixed-in-gerrit" or something?  I'm wondering if we might be able to leverage it later for finding old bugs with fixes that new reviewing23:19
claygwhat is the official bug tracker for liberasure?23:51
claygi sorta think it's still -> https://bitbucket.org/tsg-/liberasurecode/issues23:53
claygmaybe we can just use tdasilva's pyeclib project -> https://bugs.launchpad.net/pyeclib23:54
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925023:58
notmynameclayg: no, it's on openstack too23:58
notmynamehttps://bugs.launchpad.net/liberasurecode23:58
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873623:58
claygyes!23:59
*** amoralej is now known as amoralej|off23:59

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