Tuesday, 2015-09-08

*** haomaiwang has quit IRC00:01
*** haomaiwang has joined #openstack-swift00:01
*** kota_ has joined #openstack-swift00:17
*** ChanServ sets mode: +v kota_00:17
kota_good morning00:29
mattoliveraukota_: morning00:30
*** m_kazuhiro has joined #openstack-swift00:30
*** sanchitmalhotra has joined #openstack-swift00:35
*** haomaiwang has quit IRC00:36
*** sanchitmalhotra1 has quit IRC00:36
*** esker has quit IRC00:42
*** ho has joined #openstack-swift00:45
hogood morning!00:49
*** esker has joined #openstack-swift00:50
mattoliverauho: morning00:50
kota_ho, mattoliverau: morning :)00:54
*** parker7788 has left #openstack-swift00:54
*** kei_yama has quit IRC01:03
*** kei_yama has joined #openstack-swift01:04
*** baojg has joined #openstack-swift01:07
*** patchbot has quit IRC01:11
*** patchbot` has joined #openstack-swift01:11
*** ujjain has quit IRC01:12
*** patchbot` is now known as patchbot01:12
*** ujjain- has joined #openstack-swift01:12
*** esker has quit IRC01:32
*** esker has joined #openstack-swift01:33
*** haomaiwang has joined #openstack-swift01:35
*** sanchitmalhotra1 has joined #openstack-swift01:39
*** sanchitmalhotra has quit IRC01:42
*** david-ly_ has joined #openstack-swift01:51
*** david-lyle has quit IRC01:54
*** esker has quit IRC01:57
*** haomaiwang has quit IRC02:01
*** sanchitmalhotra has joined #openstack-swift02:01
*** haomaiwang has joined #openstack-swift02:01
*** sanchitmalhotra1 has quit IRC02:03
*** esker has joined #openstack-swift02:06
homattolverau, kota_: morning!02:09
*** SkyRocknRoll has joined #openstack-swift02:16
mattoliverauLooks like I'll be flying into Tokyo on the Monday... at least I don't have to worry about jetlag. :)02:21
kota_mattoliverau: definitely. when are you planning to land to Japan?02:27
kota_mattoliverau: strictly time...I mean.02:27
*** esker has quit IRC02:31
mattoliverauI land at 19:30 in Narita, so I suspect I wont get into Tokyo until quite late :(02:31
kota_exactly, it's late time :( In addition, everyone have to spend about an hour to get into downtown...02:33
kota_but that's good info, maybe I have to re-plan the date of something like party(?) I'd like to host.02:35
kota_Manday might not be good :/02:35
kota_s/Manday/Monday/02:35
*** esker has joined #openstack-swift02:38
mattoliveraukota_: well I'd love to come, but if you can only do Monday that's fine, I don't want to ruin anyone else's fun :)02:43
kota_mattoliverau: not yet dicieded anything. I'm now surveying which date is suitable for anyone.02:44
*** kei_yama has quit IRC02:47
mattoliveraukota_: oh ok :)02:47
*** kei_yama has joined #openstack-swift02:47
*** kei_yama has quit IRC02:48
*** kei_yama has joined #openstack-swift02:48
*** wbhuber has quit IRC02:49
mattoliveraukota_: also my wife is flying up on the Saturday (after summit) and we'll spend 2 weeks holidaying in your lovely country :)02:52
*** silor has joined #openstack-swift02:56
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
*** esker has quit IRC03:05
*** esker has joined #openstack-swift03:10
*** SkyRocknRoll has quit IRC03:25
*** esker has quit IRC03:26
*** baojg has quit IRC03:31
*** esker has joined #openstack-swift03:35
*** ppai has joined #openstack-swift03:42
homattoliverau: +1000003:42
kota_mattoliverau: really nice!!!03:53
*** esker has quit IRC03:54
*** jamielennox is now known as jamielennox|away03:56
*** haomaiwang has quit IRC04:01
*** esker has joined #openstack-swift04:01
*** haomaiwang has joined #openstack-swift04:01
*** baojg has joined #openstack-swift04:04
*** mahatic has joined #openstack-swift04:05
openstackgerritAlexandra Settle proposed openstack/swift: Moving DLO functionality doc to middleware  https://review.openstack.org/21999104:15
*** nadeem has joined #openstack-swift04:21
openstackgerritAlexandra Settle proposed openstack/swift: Moving DLO functionality doc to middleware  https://review.openstack.org/21999104:22
*** resker has joined #openstack-swift04:23
*** esker has quit IRC04:24
*** hrou has quit IRC04:35
*** nadeem has quit IRC04:35
*** resker has quit IRC04:44
*** esker has joined #openstack-swift04:48
*** SkyRocknRoll has joined #openstack-swift04:57
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:01
*** flwang1 has quit IRC05:07
*** mahatic has quit IRC05:13
*** esker has quit IRC05:16
*** eranrom has joined #openstack-swift05:20
*** esker has joined #openstack-swift05:22
*** nadeem has joined #openstack-swift05:33
*** mahatic has joined #openstack-swift05:40
*** nadeem has quit IRC05:41
openstackgerritKota Tsuyuzaki proposed openstack/swift: Don't send commits for quorum *BAD* requests on EC  https://review.openstack.org/22005905:44
*** esker has quit IRC05:45
*** bkopilov has joined #openstack-swift05:49
*** esker has joined #openstack-swift05:51
*** csmart has quit IRC05:59
*** haomaiwang has quit IRC06:01
*** csmart has joined #openstack-swift06:01
*** haomaiwang has joined #openstack-swift06:01
*** pksingh has quit IRC06:05
*** portante_ has quit IRC06:09
*** ndk has quit IRC06:09
*** portante has joined #openstack-swift06:09
*** trifon has quit IRC06:10
*** ndk has joined #openstack-swift06:10
*** mattoliverau has quit IRC06:13
*** mattoliverau has joined #openstack-swift06:14
*** ChanServ sets mode: +v mattoliverau06:14
mahaticmattoliverau: good evening!06:17
mattoliveraumahatic: o/06:21
*** trifon has joined #openstack-swift06:24
*** esker has quit IRC06:25
*** esker has joined #openstack-swift06:27
*** baojg has quit IRC06:36
*** mahatic has quit IRC06:38
*** mahatic has joined #openstack-swift06:39
openstackgerritMatthew Oliver proposed openstack/swift-specs: Update sharding spec, notably CountingTrie and shrinking  https://review.openstack.org/20100006:42
*** esker has quit IRC06:45
*** esker has joined #openstack-swift06:50
*** haomaiwang has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** rledisez has joined #openstack-swift07:05
*** fifieldt has joined #openstack-swift07:13
*** esker has quit IRC07:17
*** esker has joined #openstack-swift07:23
openstackgerritMahati Chamarthy proposed openstack/swift: Probe tests for object encryption  https://review.openstack.org/22089707:24
openstackgerritMahati Chamarthy proposed openstack/swift: Modified tests to include real crypto  https://review.openstack.org/21145107:24
openstackgerritMahati Chamarthy proposed openstack/swift: Encrypt flag for probe tests  https://review.openstack.org/21697407:24
openstackgerritMatthew Oliver proposed openstack/swift: Add container and account reverse listings  https://review.openstack.org/12070907:24
openstackgerritChristian Schwede proposed openstack/swift: Add notification middleware  https://review.openstack.org/19675507:31
*** joeljwright has joined #openstack-swift07:31
*** ChanServ sets mode: +v joeljwright07:31
*** trifon has quit IRC07:35
*** geaaru has joined #openstack-swift07:35
*** sanchitmalhotra1 has joined #openstack-swift07:43
*** sanchitmalhotra has quit IRC07:45
*** trifon has joined #openstack-swift07:45
*** esker has quit IRC07:52
*** chlong has quit IRC07:56
*** esker has joined #openstack-swift07:59
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** baojg has joined #openstack-swift08:01
*** baojg has quit IRC08:18
*** acoles_ is now known as acoles08:20
acolesgood morning08:22
*** esker has quit IRC08:24
mahaticgood morning08:26
*** esker has joined #openstack-swift08:29
*** jistr has joined #openstack-swift08:30
*** itlinux has joined #openstack-swift08:40
*** itlinux has quit IRC08:40
*** itlinux has joined #openstack-swift08:41
kota_acoles, mahatic: good morning08:42
mahatickota_: o/08:45
*** baojg has joined #openstack-swift08:46
itlinuxSystem Information: Model: MacBook Pro (13-inch, Retina, Early 2015) • CPU: Intel Core i7-5557U (4 Threads, 2 Cores) @ 3.10 GHz • Memory: 16.00 GB • Uptime: 11 days • Disk Space: 999.70 GB • Graphics: Intel Iris Graphics 6100 • Screen Resolution: 1680 x 1050 (HiDPI Mode) • OS: OS X Yosemite (Version 10.10.5, Build 14F27)08:47
openstackgerritChristian Schwede proposed openstack/swift: Add containeralias middleware  https://review.openstack.org/6249408:49
*** itlinux has quit IRC08:52
*** itlinux has joined #openstack-swift08:53
*** aix has quit IRC08:53
*** esker has quit IRC08:54
openstackgerritMahati Chamarthy proposed openstack/swift: Probe tests for object encryption  https://review.openstack.org/22089708:56
openstackgerritMahati Chamarthy proposed openstack/swift: Encrypt flag for probe tests  https://review.openstack.org/21697408:56
*** sanchitmalhotra has joined #openstack-swift09:00
*** haomaiwang has quit IRC09:01
*** haomaiwa_ has joined #openstack-swift09:01
*** jordanP has joined #openstack-swift09:01
*** sanchitmalhotra1 has quit IRC09:02
*** esker has joined #openstack-swift09:05
*** bsdkurt has quit IRC09:10
*** wuhg has quit IRC09:11
*** aix has joined #openstack-swift09:18
*** trifon has quit IRC09:19
*** trifon has joined #openstack-swift09:19
*** trifon has quit IRC09:22
*** trifon has joined #openstack-swift09:23
*** esker has quit IRC09:25
*** esker has joined #openstack-swift09:33
openstackgerritAlistair Coles proposed openstack/python-swiftclient: Initialise delete_object mock before it is called  https://review.openstack.org/22121909:39
acolesnotmyname: ^^ an attempt at fixing that bug! its a stab in the dark but does it make any sense?09:40
joeljwrightacoles: that bug looks like it might be a timing issue09:45
joeljwrightthose deletes are processed on a thread pool, so the test might well be happening before the calls have been completed in some cases09:46
*** wer has quit IRC09:47
*** wer has joined #openstack-swift09:47
joeljwrightI I would have hoped they would be guaranteed to complete if the call to upload was completed though…09:48
joeljwrightbut looking at the test, there doesn't seem to be any consumption of the results of calling swiftclient.shell.main(argv)09:49
joeljwrightok, ignore me09:51
joeljwrightthe call to the shell should make sure it's done09:51
joeljwrightback to the drawing board...09:51
acolesjoeljwright: hi! yep i had same thought process but I can't see how the delete_segment threads would not complete before the assertion is made.09:53
joeljwrightacoles: yeah, the call to upload certainly waits for the results of the deletes09:55
joeljwrightvery odd09:55
*** baojg has quit IRC09:56
*** baojg has joined #openstack-swift09:56
acolesjoeljwright: so my guess is that maybe the dynamic creation of mock return_value for delete_object is racing on the two delete_segment threads, with only one result being set of course, and that only then getting on call counted.09:56
* acoles waves hands09:56
joeljwrightacoles: sounds like a reasonable guess…09:57
acolesdo we have any mocking experts here?09:57
*** baojg has quit IRC10:00
*** haomaiwa_ has quit IRC10:01
*** haomaiwang has joined #openstack-swift10:01
*** sanchitmalhotra1 has joined #openstack-swift10:05
*** esker has quit IRC10:05
*** sanchitmalhotra has quit IRC10:06
*** esker has joined #openstack-swift10:11
openstackgerritJiri Suchomel proposed openstack/swift: Let object-info find files in a given directory  https://review.openstack.org/18925810:20
*** silor has quit IRC10:20
*** trifon has quit IRC10:28
*** esker has quit IRC10:33
*** aix has quit IRC10:35
*** aix has joined #openstack-swift10:36
*** thurloat_isgone is now known as thurloat10:37
*** esker has joined #openstack-swift10:39
*** sanchitmalhotra has joined #openstack-swift10:58
*** thurloat is now known as thurloat_isgone10:59
*** thurloat_isgone is now known as thurloat11:00
*** sanchitmalhotra1 has quit IRC11:00
*** haomaiwang has quit IRC11:01
*** 92AAB1O7Y has joined #openstack-swift11:01
*** trifon has joined #openstack-swift11:07
*** esker has quit IRC11:10
*** 92AAB1O7Y has quit IRC11:12
*** silor has joined #openstack-swift11:16
*** silor has quit IRC11:18
*** SkyRocknRoll has quit IRC11:18
*** esker has joined #openstack-swift11:18
*** flwang1 has joined #openstack-swift11:18
*** SkyRocknRoll has joined #openstack-swift11:20
*** silor has joined #openstack-swift11:21
*** mahatic has quit IRC11:23
*** marcusvrn_ has joined #openstack-swift11:25
*** mahatic has joined #openstack-swift11:26
*** flwang1 has quit IRC11:26
openstackgerritKota Tsuyuzaki proposed openstack/swift: WIP: PUT/GET path for global ec cluster  https://review.openstack.org/21916511:34
*** esker has quit IRC11:36
*** kota_ has quit IRC11:39
*** early has quit IRC11:41
*** esker has joined #openstack-swift11:45
*** flwang1 has joined #openstack-swift11:48
*** early has joined #openstack-swift11:49
*** SkyRocknRoll has quit IRC11:51
*** bkopilov has quit IRC12:00
openstackgerritHisashi Osanai proposed openstack/swift: Add functional test for access control (PUT/DELETE) with Keystone  https://review.openstack.org/20241112:01
*** esker has quit IRC12:07
*** eandersson has joined #openstack-swift12:11
*** esker has joined #openstack-swift12:17
*** m_kazuhiro has quit IRC12:19
*** chlong has joined #openstack-swift12:22
*** daemontool_ has quit IRC12:23
*** flwang1 has quit IRC12:26
*** flwang1 has joined #openstack-swift12:26
*** km has quit IRC12:27
*** mahatic has quit IRC12:29
*** esker has quit IRC12:38
*** kei_yama has quit IRC12:40
*** flwang1 has quit IRC12:42
*** daemontool_ has joined #openstack-swift12:42
*** esker has joined #openstack-swift12:44
*** mahatic has joined #openstack-swift12:46
*** ppai has quit IRC12:47
*** ho has quit IRC12:50
*** esker has quit IRC12:52
*** esker has joined #openstack-swift12:52
*** esker has quit IRC12:54
*** proteusguy__ has quit IRC12:55
*** esker has joined #openstack-swift12:56
*** esker has quit IRC12:56
*** clyps_ has joined #openstack-swift12:56
*** jordanP has quit IRC12:58
*** mahatic has quit IRC12:59
*** marzif has joined #openstack-swift13:09
*** tongli has joined #openstack-swift13:10
*** marzif has quit IRC13:10
*** haomaiwang has joined #openstack-swift13:10
*** changbl has quit IRC13:11
*** marzif has joined #openstack-swift13:11
*** proteusguy__ has joined #openstack-swift13:12
*** hrou has joined #openstack-swift13:16
*** dustins has joined #openstack-swift13:17
*** daemontool_ has quit IRC13:22
*** breitz has joined #openstack-swift13:23
*** marzif has quit IRC13:23
*** marzif_ has joined #openstack-swift13:23
*** marzif_ has quit IRC13:26
*** marzif_ has joined #openstack-swift13:26
*** marzif has joined #openstack-swift13:29
*** marzif_ has quit IRC13:29
*** itlinux has quit IRC13:46
*** ctrath has joined #openstack-swift13:51
*** nadeem has joined #openstack-swift13:56
*** haomaiwang has quit IRC14:01
*** haomaiwang has joined #openstack-swift14:01
*** jistr is now known as jistr|call14:01
*** ctrath has quit IRC14:02
*** yland has joined #openstack-swift14:02
*** marzif_ has joined #openstack-swift14:03
*** marzif has quit IRC14:03
openstackgerritMerged openstack/python-swiftclient: Initialise delete_object mock before it is called  https://review.openstack.org/22121914:06
*** sanchitmalhotra has quit IRC14:06
*** ctrath has joined #openstack-swift14:07
*** nadeem has quit IRC14:08
*** nadeem has joined #openstack-swift14:08
*** marzif_ has quit IRC14:11
*** marzif has joined #openstack-swift14:11
ylandHello my name is Yolande Amate, I am new to open-source and would like to contribute to openstack-swift. I have successfull installed openstack enabling swift on ubuntu14.04 through devstack. I would like to test some functionalities of openstack like uploading an ubuntu vm image with swift and test access to the os. When I try swift upload I am requested to give " ST_AUTH, ST_USER, and ST_KEY" , so please I would like to know how create a swift accou14:15
ylandnt, or what are the default for newly installed swift.14:15
*** wer_ has joined #openstack-swift14:15
*** wer has quit IRC14:16
ylandI also disabled nova and glance while installing openstack, since I got an error while they were both enabled alongside swift.14:17
*** jistr|call is now known as jistr14:20
*** wbhuber has joined #openstack-swift14:21
*** prometheanfire has joined #openstack-swift14:23
prometheanfiredoes 2.4.0 support any py3 variants?14:23
prometheanfire3.3 or 3.4 for instance?14:23
prometheanfirethink all the deps support it14:23
*** dustins has quit IRC14:25
*** bkopilov has joined #openstack-swift14:27
*** jrichli has joined #openstack-swift14:32
prometheanfiregonna assume no for now, tox doesn't show it14:41
*** jlhinson has joined #openstack-swift14:42
openstackgerritDoug Hellmann proposed openstack/python-swiftclient: Add links for release notes tool  https://review.openstack.org/22132914:42
acolesyland: if you are using devstack then you will be using keystone identity service so you will need to use the OS options with swift CLI14:43
acolesyland: type swift --os-help14:43
MooingLemurprometheanfire: pretty sure py3 support is only "in progress"14:43
acolesprometheanfire: MooingLemur is correct14:43
prometheanfireMooingLemur: ya, that was my last update on the subject14:43
cschwedeyland: Hello! in your devstack VM, cd to the devstack directory; there should be a file called openrc. just do a „source openrc“ and you should be set14:43
acolesyland: heh - cschwede has better answers than me :)14:44
jrichlimahatic, acoles:  great work on feature/crypto!  It was nice to see so much activity while I have been out :-)14:44
acolesjrichli: welcome back14:45
hroujrichli, acoles  +1 !  I'm reviewing the changes as we speak !  Looks great so far.14:45
jrichliacoles: I feel really great.  I didn't work all weekend - but maybe 2 hours14:45
acoleshrou: hold fire on keymaster review - i have another change i'd like to push to gerrit14:46
*** wer_ has quit IRC14:46
hrouacoles, sure thing !  That sounds great, I'm just reviewing the structure which I imagine won't change too much, will hold off on leaving comments though.14:47
acolesjrichli: hrou : i'd like to make the keymaster not have to persist key id's for container and account, but rather always calculate them.14:47
jrichliacoles: I noticed that.  so that means keeping the key_id at a header, right?14:47
jrichliI had only added that for a temporary workaround, but I am fine with keeping it there14:48
acolesjrichli: no. i didnt push that change yet. at least i dont think i did14:48
jrichliI think that is what your comments led me to14:48
*** wer_ has joined #openstack-swift14:48
acolesjrichli: i'll push the change - that will be clearer14:49
hrouacoles, jrichli - I recall at the hackathon jrichli had a concern from a debugging point of view in terms of just dynamically calculating them ?14:49
jrichlihrou - in acoles comments, he had mentioned that the key_id was still saved, so you could go from that.14:49
jrichlihrou - but maybe acoles came up with something even better.  we shall see14:49
acolesjrichli: yeah on the object. here i am just talking about the container and account keys14:50
acolesand no i dont have anything better!14:50
*** baojg has joined #openstack-swift14:50
acolesI just spent a lot of time figuring out why I had 144 func tests errors before realising that resetswift is needed if the proxy is restarted, because otherwise it is impossible to list existing containers14:52
*** david-ly_ is now known as david-lyle14:53
jrichliacoles: I run resetswift all the time.  maybe I shouldn't do it so much14:53
acolesjrichli: we avoid it in production :D :D14:54
hrouAfter sticking crypto in the pipeline ?  yea : )14:54
*** ctrath has quit IRC14:54
*** dustins has joined #openstack-swift14:54
hrouI've gotten to used to it that on our semi production systems (used for testing larger clusters) I've changed resetswift to just be a stop / start swift, to avoid unintentional pain : )14:55
jrichliacoles: I think the newline issue you mentioned in email is the same issue I have been debugging.  the new line is probably there because the etag was not properly decrypted: the crypto-meta it gets is old/incorrect sometimes14:55
*** ctrath has joined #openstack-swift14:55
acolesjrichli: yeah i'd guess its same cause. my only contribution may be to explain the intermittency ;)14:56
jrichliacoles: if you change to always use the same iv for all etags, issues go away14:57
*** ctrath has quit IRC14:57
*** SkyRocknRoll has joined #openstack-swift14:57
jrichlithe intermittency is that the etag crypto-meta only sometimes gets mixed on the wrong response14:57
*** dustins has quit IRC14:57
jrichliso, here is what can happen:14:57
jrichlifake_footers sets the correct etag in the response headers it passes along14:58
acolesjrichli: hrou so, i'd really like to get some stuff merged because the patch chain is just impeding progress and rebase mistakes are just causing unnecessary churn on gerrit14:58
*** minwoob has joined #openstack-swift14:58
jrichlithen the decrypter gets an old etag in its response headers.  what the heck happened in between?  i donno14:58
jrichliacoles: agreed.  let me know what I can do to help with that.14:59
acolesjrichli: we have a -1 comment on the crypto module patch due to not checking size of key14:59
hrouacoles, yea that sounds like a good plan to me, we can always propose additional changes, so maybe don't worry too much about the reviews and just push them in ?15:00
ylandcschwede, acoles thanks for the help. Now I get "Endpoint for object-store not found - have you specified a region?" with swift list and swift upload commands15:00
acolesjrichli: I was intending to fix that next15:00
jrichliacoles: oh, I thought you said mahatic fixed that, but on a different patch.  is that right?15:00
*** fifieldt has quit IRC15:00
*** ctrath has joined #openstack-swift15:00
*** haomaiwang has quit IRC15:01
*** haomaiwang has joined #openstack-swift15:01
*** haomaiwang has quit IRC15:01
acolesjrichli: err, did i say that ? not aware of it.15:01
hroujrichli, I was going through all the changes this morning, I didn't see that, unless it wasn't on the crypto feature branch : /15:02
hrouhttps://review.openstack.org/#/q/status:open+project:openstack/swift+branch:feature/crypto,n,z15:02
jrichliacoles: I must have interpreted something incorrectly15:02
*** dustins has joined #openstack-swift15:02
jrichlihrou: the -1 was cleared, but no changes were made for it15:03
jrichlibecause of rebasing15:03
hroujrichli, ah gotcha, the rebase I guess15:03
hrouRight15:03
hroujrichli, btw re: the etag - well the solution we're proposing for conditional get may just fix that issue for you ; )  Given the fixed iv .. : )15:04
*** kevinc_ has joined #openstack-swift15:05
openstackgerritAlistair Coles proposed openstack/swift: Trivial Key Master for encryption  https://review.openstack.org/19374915:05
acoleshrou: jrichli ^^15:05
acolescan you try that in your patch chains15:06
cschwedeyland: hmm, strange - that should be set too. anyways, try with: export OS_REGION_NAME="RegionOne“15:06
hrouacoles,  perfect that's great I'm going to take a look at that now.15:06
jrichlihrou: true, but I want to find out how the response headers can get mixed like that.  it reveals a problem that needs to be fixed15:06
jrichlihrou: of course, it could be a problem that would go away when fake_footers go away - but i haven't proved that yet15:07
acolesjrichli: how many patches need to be applied to get that error? does it need the container listing patch? does it only happen with the COPY middleware?15:07
hroujrichli, yea I think that's prudent i.e. at least to identify the route case, who knows it may lead to other things as well.15:07
acoleshrou: thanks. its getting smaller each time :)15:08
hrouacoles, which makes reviewing that much easier : )15:08
*** baojg has quit IRC15:09
jrichliacoles: I haven't tried outside of COPY yet.  I haven't looked yet, but i will most likely need to add a similar test case to use - COPY is making a lot more requests happen at once, which I think is what brings it out15:09
*** janonymous_ has joined #openstack-swift15:09
hrouacoles, really quick silly question .. for trivial not important (get to it later) changes I think you mentioned you use "NIT ... followed by comment" ?15:10
acolesjrichli: yep. btw I needed to resolve a few conflicts to apply the copy middleware patch - same for you?15:10
*** trifon has quit IRC15:11
jrichliacoles: that was a few weeks ago :-)  what type of conflicts?  I might have made some obvious/explainable resolutions, but I don't remember anything significant.15:11
acoleshrou: yes use "nit: " for trivial stuff like a comment typo, or just fix it and push a new version to gerrit.15:12
acolesjrichli: there was a method in obj.py i think that got deleted and there was a change in that method on the crypto branch15:12
hrouacoles, thanks!15:12
jrichliacoles: i missed that.  dont suppose you remember the name of the method? i can see if its in my repo15:13
acolesthink it was obj.py handle_copy_request15:14
*** changbl has joined #openstack-swift15:14
acolesalso, i rebased the copy middleware patch on master branch, so grab the latest from patch 15692315:15
patchbotacoles: https://review.openstack.org/#/c/156923/15:15
*** mahatic has joined #openstack-swift15:16
jrichliacoles: yes, I see that the method is no longer there.  there were changes made which were only on feature/crypto?  What was the nature of the change?15:19
hroujrichli, acoles I pulled it down a while ago too but it was fairly trivial for me, that or I just forgot.15:19
*** wbhuber has quit IRC15:19
janonymous_Do someone have trouble when services are run through openstack command , but when checking through swift-init command nothing is shown, instead of services running15:22
jrichliacoles: btw, the total errors/failures I have with my COPY+crypto is (SKIP=17, errors=5, failures=10)15:23
jrichlifunctests15:23
*** wbhuber has joined #openstack-swift15:23
hrouHey janonymous_ what are "openstack" command15:25
hroujanonymous_, do you mean the openstack CLI for swift, I'm not having any issues with that on my system (i.e. using the openstack cli on a running cluster and swift-init showing the processes)15:26
acolesjrichli: https://review.openstack.org/#/c/203310/11/swift/proxy/controllers/obj.py15:26
janonymous_hrou: Hey, yes.15:26
janonymous_hrou: Is it working fine everytime. i mean starting services with openstack commands first .. because when i was doing that pid files were not created but still processes were running15:28
jrichliacoles: that diff only shows the part where we remove the "remove_items" call.  I see that the copy_headers_into method has changed since feature/crypto so that it copies the sysmeta as well.15:34
hroujanonymous_, so in my case I still started the swift process (well the proxy on a given host) through swift-init and I'm using the openstack swift cli to upload/download, so not sure if that matches what you're describing15:34
janonymous_hrou: I'll try to check running it several times using fresh installation i guess for better results.15:34
*** SkyRocknRoll has quit IRC15:34
ylandcschwede: I tried the export command and I also ran "env | grep OS_" which gave me some info including a line containing "OS_REGION_NAME=RegionOne" but I still get the same error even after running ./stack.sh.15:35
janonymous_hrou: Ohh.. not that case , slight different one.15:35
jrichliacoles: the way that I added crypto into the COPY as middleware is I added the items that I know we have added by hand.  maybe I should have made use of git merge, but it sounds like this resulted in fewer errors/failures15:36
cschwedeyland: how does your devstack config look like? can you share it using http://paste.openstack.org/ ?15:37
hroujanonymous_, did you actually start swift through the openstack cli ? I didn't think that was possible, only listing services, let me know if it is I can try it : )15:38
mahaticacoles, jrichli hello, I just through the long scroll back :) I didn fix up the Crypto key length, because was not sure if that'd be the only review15:39
mahaticwent through*15:39
acolesmahatic: ok np i'm on it15:40
ylandcschwede: do you mean my local.conf file?15:40
janonymous_hrou: I prepared a fresh vm and saw status of services through openstack cli it showed running, but when i saw it using swift-init no process were running15:40
cschwedeyland: yep15:40
mahaticacoles: thanks15:41
janonymous_hrou: I'll try again with new setup i think15:41
*** joeljwright has quit IRC15:41
janonymous_hrou: maybe i did something stupid..15:41
hroujanonymous_, how are you listing the status ? 'openstack service show swift' ?15:42
acolesjrichli: k. it was just a thought re the crypto meta mixup, that maybe something went awry, but maybe not.15:42
janonymous_openstack service show15:42
*** devlaps has joined #openstack-swift15:43
hroujanonymous_, yep, so the "enabled" field ?  Interesting I didn't think that implied the service was up and running, not sure what it really implied.15:43
janonymous_hrou: yes15:44
hroujanonymous_, right if I stop swift it still lists it as enabled, I don't think it implies the service is running let me check one thing.15:44
ylandcschwede: local.conf (http://paste.openstack.org/show/450422/) and stackrc(http://paste.openstack.org/show/450423/). This are the only file I modified.15:46
*** barker has joined #openstack-swift15:53
*** barker has quit IRC15:57
cschwedeyland: you don’t need to modify stackrc to disable other services. have a look at http://docs.openstack.org/developer/devstack/configuration.html#swift16:02
cschwedeyland: also, a minimal local.conf for swift with keystone only might look like this: https://gist.github.com/cschwede/a54173fdfc745865233b16:02
*** gyee has joined #openstack-swift16:03
hrouacoles, jrichli, mahatic - I guess at some point we'll end up changing the trivial keymaster to not touch account / container if we decide on the reduced scope  (obj/obj meta only)?16:03
*** annegentle has joined #openstack-swift16:05
acoleshrou: right. container key will be needed because we use that to encrypt the object metadata in container listing.16:05
acoles account key would be redundant i think16:05
mahaticyup, container key will be needed16:05
hrouacoles, mahatic - good point re: container keys !16:06
mahaticacoles: but we probably would still keep that in trivial keymaster, since we need it for future anyway?16:06
mahaticaccount key I mean16:06
hroumahatic, maybe !  It depends, actually, assuming we go with a reduced scope, maybe we need to ignore any keys provided in the encryption / decryption middleware, as on paper we're not in control of the keymaster (and a simple implementation may just always provide a key regardless of the path).16:09
acoleshrou: should we drop it now? make patch smaller :P seriously, if its not used then should we have it there in anticipation of future or leave it to future-us to add back in?16:11
acolesjrichli: ^^16:11
*** jistr has quit IRC16:11
*** mahatic has quit IRC16:13
hrouacoles, jrichli  actually I believe the latest and greatest patch sets have what we want on the engine side (patch 214438) so we'll ignore anything account lvl anyway at this point.16:16
patchbothrou: https://review.openstack.org/#/c/214438/16:16
*** mahatic has joined #openstack-swift16:16
*** esker has joined #openstack-swift16:16
hrouSo even if the trivial keymaster provides a key, just a question of if we want to simplify it even further.16:16
mahatichrou: thatś true16:17
notmynamegood morning16:20
jrichliacoles hrou mahatic: IMO, we could take out the account key in the trivial_keymaster, and it can just be added when / if it is going to be used in the future.16:20
ylandcschwede: Thank very much, all seems to work fine now.16:20
acolesjrichli: +116:21
hroujanonymous_, I'm going to ask some folks I know on the openstack CLI team what the status field should represent (as I see some talk for other components that it may indeed represent if the service is up and running), or if I'm adventurous I'll look at the code later today : )16:21
hroujanonymous_, anyway I played around with it and its always listed as enabled for me, regardless of the status of the swift processes16:22
acolesjrichli: method md5hex(s) in test_crypto.py in patch 193826 appears to be unused? does it get used further up the chain?16:22
patchbotacoles: https://review.openstack.org/#/c/193826/16:22
*** mahatic has quit IRC16:22
janonymous_hrou : yes, that was my concern :)16:27
janonymous_hrou: thanks for looking on the same :)16:27
hroujanonymous_, anytime !  I like using the openstack CLI, glad others do as well (maybe like was a strong word ; )16:27
janonymous_hrou: I'll troubleshoot also for it  :)16:28
janonymous_also16:28
*** jlhinson has quit IRC16:29
*** jlhinson has joined #openstack-swift16:29
ylandIs it possible to upload an operating system vm image with swift and test/run the os with horizon?16:29
jrichliacoles: you are correct.  blow that sucker away!  :-)16:30
janonymous_hrou: Thanks.16:30
acolesjrichli: its toast16:30
jrichlithx!16:30
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925016:31
acolesnotmyname: how was the museum?16:33
notmynameacoles: we had a good time.16:35
acolesjrichli: how come all your first commits are on friday and saturdays? what's going on rest of the week? :P16:35
hrouacoles,  lol!16:36
acolesnotmyname: great. that changelog patch took some persuasion!16:36
jrichliacoles: I know, right?  I have been a little better about being able to work on 'my stuff' at work lately16:36
notmynameyeah, it did. that's for beating it a few times :-)16:36
jrichliacoles notmyname: I was wondering if it would be ok to add the crypto middleware to the pipeline for just the feature/crypto gate tests16:38
notmynamejrichli: yeah, that makes sense16:39
acolesnotmyname: np. be interesting to see if patch 221219 fixes it.16:39
patchbotacoles: https://review.openstack.org/#/c/221219/16:39
jrichlido I have the necessary permissions?16:39
notmynamejrichli: what do you mean?16:40
acolesjrichli: not sure you need any16:40
acolesif its in the sample file it will be used, i think16:40
jrichliI am not sure what is involved.  Just figured that there might be some control over who can change gate tests16:40
openstackgerritJohn Dickinson proposed openstack/python-swiftclient: Add links for release notes tool  https://review.openstack.org/22132916:40
jrichliacoles: oh, I see.16:41
acolesjrichli: not sure if its proxy-server.conf-sample or the one under doc/saio that gets used16:41
openstackgerritAlistair Coles proposed openstack/swift: Cryptography module to be used by middleware  https://review.openstack.org/19382616:42
acoleshrou: mahatic: jrichli: ^^ i made a few fixups and added check on key size.16:43
*** rledisez has quit IRC16:43
acolesjrichli: could you ask Christian Cachin to review that one more time?16:43
jrichliacoles: sure, thanks16:44
hrouacoles, looks great will review, only thing that quickly comes to mind is if we should check the iv length while we're at it. (though we do generate this locally)16:46
acoleshrou: the Cipher class will raise an exception if iv is wrong length - there is a test in test_crypto.py16:47
hrouacoles, ah perfect16:48
acolesjrichli: devstack uses whatever pipeline is in /etc/proxy-server.conf-sample (then patches it for correct auth middleware) so if you push a patch with crypto middlewares in the pipeline that should do the trick. obviously it will need the conf sections for those entry points and the lines in setup.cfg so will have to be based on other patches.16:51
*** trifon has joined #openstack-swift16:55
jrichliacoles: sounds good, thx!16:58
*** aix has quit IRC16:58
*** barker has joined #openstack-swift17:01
openstackgerritJohn Dickinson proposed openstack/swift: Merge branch 'master' into feature/hummingbird  https://review.openstack.org/22141017:02
notmynamedfg: ^17:02
*** trifon has quit IRC17:03
*** trifon has joined #openstack-swift17:04
dfgnotmyname: cool thx. can i just +2 / approve it?17:05
notmynamedfg: yup17:05
dfgnotmyname: thanks a bunch17:06
notmynamedfg: any time :-)17:06
notmynamedfg: probably would be a good idea to try to do that more regularly between you me and redbo. once every week or two17:06
*** eandersson has quit IRC17:07
dfgnotmyname: ya. i think its been almost 2 months or something17:08
*** AndreiaKumpera has joined #openstack-swift17:12
cschwedeyland: great that it works now - you’re welcome!17:12
*** zhill has joined #openstack-swift17:15
*** barker has quit IRC17:17
*** barker has joined #openstack-swift17:31
claygmorning17:31
*** acoles is now known as acoles_17:34
*** thurloat is now known as thurloat_isgone17:42
*** mvandijk has left #openstack-swift17:46
*** aix has joined #openstack-swift18:01
hroujrichli, this version of the keymaster still has the logic for versioned gets, in theory this will go away once we validate the copy middleware and versioned objs?18:07
jrichlihrou: yes.  but I figure we could keep it in for now so that any new errors in those related tests would be revealed - and not looked over b/c of an existing failure.  But I am flexible on that.18:18
*** bil has joined #openstack-swift18:19
bilHi18:20
bilCan someone help me with a question?18:20
hroujrichli, yea keep it for now but eventually remove I think ?  I find it complicates the get path as we have use case where we don't find the key on a path but will not look up if the response has the magical id key path stored.18:21
jrichlihrou: I haven't yet been able to look at the latest patch from acoles18:22
hroujrichli, oh no worries for now !  Basically all that logic hasn't changed its still there, we'll revisit it later.18:23
jrichlibil: everyone on will do their best to help.  What is the question?18:23
*** geaaru has quit IRC18:26
openstackgerritDavid Goetz proposed openstack/swift: use recon diskusage so you can weed out unmounted drives  https://review.openstack.org/22144618:27
bilI need to retrieve X-Storage-Url and X-Auth-Token18:27
*** T0m_ has joined #openstack-swift18:30
*** openstackgerrit has quit IRC18:31
*** openstackgerrit has joined #openstack-swift18:31
jrichlibil: Do you mean as a client, or in some piece of middleware, or something else?18:31
bilseveral ways one as a client18:32
T0m_Is there a way to check the cluster status in Swift?18:32
bilusing curl18:32
biland othe using swiftclient18:32
bilI tried curl -i   -H "Content-Type: application/json"   -d '18:33
bilcurl -i   -H "Content-Type: application/json"   -d '18:33
bil{18:33
openstackgerritDavid Goetz proposed openstack/swift: Better error output in TestHealthCheck  https://review.openstack.org/21218818:33
wbhuberbil: does "swift stat" work for you?18:34
hrouT0m_, you can use swift-init status <server type> which will list the processes PIDs18:34
T0m_would that need to be ran on each server though? I wondered if from one mode you can do a sort of “check status” and it would report back the health of each node18:35
hrouT0m_, for that you need to run it on each, its pretty easy to script something up to accomplish what you want, but others may be aware of something that already exists.18:36
jrichliT0m_ wbhuber: I think that "swift stat" might be what T0m_ is looking for18:36
T0m_Ok thats fine - new to swift and just setup 2 nodes in a cluster and just wondered if there was a way to check the health18:37
notmynameT0m_: yeah, what you're looking for is swift-recon18:37
bilyes18:37
T0m_Ah ok, think I did come across that but i’ll have to look at configuring it - thanks18:37
notmyname`swift stat` gives info about your particular account. not cluster healp info18:37
hrouT0m_, jrichli wbhuber - yea swift stat : ) could work too but it really depends what you're looking for, as that'd be for the account your credentials point too.18:38
*** silor has quit IRC18:38
notmynameT0m_: there's a CLI tool you can run from any machine that (1) has connectivity to everything in teh cluster and (2) the ring file(s)18:38
notmynameT0m_: the only "configuring" you need to do is to make sure you have recon in the pipeline in the configs. which will be the case if you used upstream docs for configuring it18:39
T0m_i wondered if you could see if nodes were in sync, and maybe the count of quarantined objects, or any reported disk failures18:39
notmynameyup18:39
wbhuberbil: great, then do a "swift --verbose stat"18:39
notmynamethat's what it's for18:39
wbhuberbil: you'd see "StorageUrl" and "Auth Token" which are what you wanted in the first place.18:40
* notmyname needs to go to lunch now18:40
torgomaticdfg: ping18:40
wbhubernotmyname: you cannot.18:40
wbhubernotmyname: jk18:40
notmynamewbhuber: heh. tell that to my wife who is waiting downstairs for me ;-)18:41
wbhubernotmyname: she wins. ;-)18:41
bilhere is what I sent http://pastebin.com/u8w365EJ18:45
bili changed my real ip18:45
wbhuberbil: you can put that in a file called "openrc" or "adminrc" similar to this: http://docs.openstack.org/cli-reference/content/cli_openrc.html18:46
wbhuberbil: then do a "source openrc"18:46
*** jlhinson has quit IRC18:46
wbhuberbil: then run "swift --verbose stat" directly18:46
bilok I will try18:47
dfgtorgomatic: whats up?18:47
bilthanks18:47
wbhuberbil: http://pastebin.com/JwT9arcz18:48
wbhuberbil: THat should be your openrc18:48
wbhuberbil: change the IP address as well18:48
wbhuberbil: do a "source openrc"18:48
bilok thanks a lot18:49
bili will try it now18:49
*** T0m_ has left #openstack-swift18:49
*** garthb has joined #openstack-swift18:49
torgomaticdfg: I was thinking about redoing the ratelimiting on slo since we're doing this range thing now and I wanted to run my ideas past you for a sanity check18:52
bilwbhuber18:53
torgomaticsince clients will be able to put a range in a slo manifest, the 1 MiB segment size limit stops helping, because they can just request 1 byte from the 1 MiB segment18:54
bilwbhuber:In the end I need to do this in python so first I want to try it with curl18:54
biland see what response I get18:54
torgomaticand requiring ranges to be at least 1 MiB isn't that great for the folks who want the range stuff18:54
torgomaticso I wanted to (a) limit slo segment size to 1 byte or more (so no 0-byte segments because that's dumb) and then ratelimit only small segments/ranges, where "small" is "less than 1 MiB"18:55
torgomaticthere should probably be a "(b)" in there somewhere, because that's two things, but you see what I mean18:56
torgomaticbasically if the client wants big chunks, feed them as fast as they can eat it18:57
bilwbhuber:or maybe via swift command18:57
claygtorgomatic: dfg is all about ratelimiting18:57
dfgthats true.18:57
torgomaticbut if the client wants small chunks, feed them slowly18:57
claygtorgomatic: yeah %$#@ 'em18:57
dfgtorgomatic: there's still the 1000 max size right?18:57
torgomaticdfg: yeah, I wasn't going to change that18:58
torgomaticthere's still SLO-of-SLOs for people who need lots of segments18:58
dfgya18:58
dfgeverybody's favorite feature18:59
claygummm... i am totally lost on the rfc822 explosion of patches19:00
torgomaticheh, I love that one... people are like "what if I need more than 1000 segments?" and I'm like "let me tell you about exponents"19:01
claygdfg: oh thanks for the push on patch 212188 !!!19:01
patchbotclayg: https://review.openstack.org/#/c/212188/19:01
claygdoes it still need a go fmt?19:01
dfgtorgomatic: ya thats sounds fine. the only thing i could think of is the PUTs would be expensive with all the HEADs to the 1 byte files. but thats not really a concern i guess.19:01
torgomaticdfg: cool, thanks. I'll go work on that then.19:02
dfgso would they get like the first 10 chunks with no limiting and then start after that?19:03
dfgthats how it does it right?19:03
torgomaticdfg: first 10 small chunks, yeah... so if they've got a bunch of 1+ MiB chunks, those don't count, but then they get 10 small ones free and then ratelimit to 1 small per second19:03
dfgya cool.19:03
dfgclayg: np. i should have fixed tat gofmt problem. unless i screwed up the commit19:04
minwoobclayg: I see that https://bugs.launchpad.net/swift/+bug/1491908 is necessary in order for container sync to work, but shouldn't try to make it so the proper response is emitted on the 409 in the normal case, and have the container sync case handle the 409s in its own way?19:12
openstackLaunchpad bug 1491908 in OpenStack Object Storage (swift) "proxy server reports 202 even though EC backend didn't accept object" [Undecided,New]19:12
minwoobshouldn't* we19:12
minwoobThis seems to be a correctness issue if the proxy keeps returning 202 for the 409s.19:13
minwoobBasically, the proposed idea is to have the proxy server return the correct response upon 409, but then in container sync to implement a logic that can flexibly handle the 409s.19:15
*** jlhinson has joined #openstack-swift19:16
*** jkugel has joined #openstack-swift19:25
*** aix has quit IRC19:32
*** yland has quit IRC19:40
minwoobHey peluse - The commit message for your alternate fragments patch (https://review.openstack.org/#/c/213147/) says there are new probe tests. However, I don't see any attached.19:41
minwoobWere you going to add them in?19:42
jrichliall: If you have some time, please review patch 20580319:49
patchbotjrichli: https://review.openstack.org/#/c/205803/19:49
jrichliIt would be great to get it in the next release.  Thank you!19:49
claygminwoob: yes I think that's the correct thing (re: teaching container sync to handle 409 means "already synced") - but I don't know how to do it with a smooth upgrade19:49
claygminwoob: like you can't really upgrade your proxy to start spewing 409's until you're sure all your container-sync clusters (clients) are ready to eat them :'(19:49
minwoobclayg: Right. So it seems that such a patch to fix the proxy server would need to include the logic for handling the 409s in the container sync case.19:52
minwoobIs that going to be particularly difficult?19:52
claygminwoob: but that patch would need to be applied to *both* clusters *at the same time*19:53
minwoobI see.19:53
minwoobShould we wait for post-Liberty for that, then?19:57
claygminwoob: i'm not really sure :\19:58
claygminwoob: I guess updating container sync to handle 409's would just be "the right thing to do"19:58
claygminwoob: when the proxy can start returning 409's instead of 202's is maybe more complicated if we're worried about breaking container sync for existing deployments19:58
claygit's po19:58
claygminwoob: it's possible we could add a shim in the container sync middleware on the target cluster that's like "support_legacy_container_sync_clients" and then you can turn it on to capture the real 409 response and make it a 202 for container sync requests only - maybe19:59
eranromclayg, minwoob Incidently, I was spending today working on this: Here is another option:20:00
minwoobclayg: Yeah, I was thinking along those lines.20:00
eranromIf we follow Clay's previous idea of using Expect 100-continue + timestamp for container sync to prevent multiple uploads, we can translate the 409 to 417 only if the request has the expect 100 continue header, thus not breaking older versions. but perhaps I am missing the beginning of this conversation20:02
bilI need to get storage url fron server I need to do it via V2 keystone using python could someone help me or atleast direct me20:02
bilI got some response via curl20:02
*** dustins has quit IRC20:04
*** lcurtis has joined #openstack-swift20:06
eranromok sorry for the interruption, you were discussing the 409->202 in general with container sync being only part of the picture. So what I am suggesting is not relevant.20:06
claygeranrom: I like the general idea of making the container-sync client somehow explicitly demonstrate that it is "new enough" to recieve the 409 and translate to 202 otherwise20:07
*** barker has quit IRC20:07
claygeranrom: no I think you're on the right track20:07
claygminwoob: new plan - do what eranrom thinks is best - eranrom is smart20:07
minwoob+120:08
eranromwell, thanks :-) but if the translation problem goes beyond container sync then I do not see how to do that. Except perhaps the shim idea :-) thiking...20:09
minwooberanrom: Where is the 417 coming from, btw20:09
eranromthinking...20:09
minwooberanrom: From the above explanation.20:09
eranromits ExpectationFailure: client says expect 100-continue, server says do not continue by sending this20:10
eranrom+1 for the "support_legacy_container_sync_clients"idea with the following additional detail: the "shim" in the container sync middleware will translate from 409 to 202 only if the request has the container sync auth header (so that not every request gets translated back) and from 409 to 417 if we also have the expect header20:19
*** barker has joined #openstack-swift20:25
*** ekarlso has quit IRC20:38
openstackgerritMerged openstack/swift: Merge branch 'master' into feature/hummingbird  https://review.openstack.org/22141020:43
*** tongli has quit IRC20:44
*** trifon_ has joined #openstack-swift20:51
*** trifon has quit IRC20:53
*** kevinc___ has joined #openstack-swift20:55
*** cdelatte has quit IRC20:56
*** kevinc_ has quit IRC20:57
*** ekarlso has joined #openstack-swift20:57
*** ekarlso has quit IRC20:57
*** ekarlso has joined #openstack-swift20:57
*** aix has joined #openstack-swift21:01
*** changbl has quit IRC21:07
*** marzif has quit IRC21:09
*** flwang1 has joined #openstack-swift21:09
*** marzif has joined #openstack-swift21:09
*** lcurtis has quit IRC21:13
*** bil has quit IRC21:14
claygnotmyname: yay settings -> preferences -> change view = "New Screen" !!!21:14
notmynamejust something to try out and see if it sits well with you21:15
openstackgerritBill Huber proposed openstack/swift: Reconstructor GET excludes user_agent in log  https://review.openstack.org/22150621:17
*** haypo has quit IRC21:20
*** nadeem has quit IRC21:33
*** eranrom has quit IRC21:35
peluse__minwoob, wrt the probe tests, yeah I think they ended up on a different patch when I broke a larger one apart a while back.  I'll update the commit msg, thanks21:36
openstackgerritDavid Goetz proposed openstack/swift: go: assign startTime to Now at beginning of replication run  https://review.openstack.org/22151221:36
*** devlaps has quit IRC21:38
*** nadeem has joined #openstack-swift21:39
*** jrichli has quit IRC21:44
claygnotmyname: boooo - the "f" shortcut doesn't work in new screen!21:44
notmynameclayg: and scrolling (in my browser) seems wonky. I'm not in love with the new look21:45
*** darrenc_ is now known as darrenc21:47
claygnotmyname: I don't think the "unified diff" view is available anymore either :\21:50
clayggoodness - why did they have to take out so much good stuff to make the crappy parts less annoying!?21:50
*** jamielennox|away is now known as jamielennox21:51
*** jkugel has quit IRC21:52
peluse__who is 'goodness'?  :)21:54
*** marcusvrn_ has quit IRC21:55
openstackgerritClay Gerrard proposed openstack/swift: Re-organise ssync tests  https://review.openstack.org/22019821:59
openstackgerritClay Gerrard proposed openstack/swift: Fix invalid frag_index header in ssync_sender when reverting EC tombstones  https://review.openstack.org/21783021:59
*** thurloat_isgone is now known as thurloat21:59
*** barker has quit IRC22:02
*** jlhinson has quit IRC22:03
*** annegentle has quit IRC22:13
brianclineare there any known issues around DLOs and publicly-readable container ACLs?22:14
brianclineseeing some weird issues on 2.2.2, probably something dumb but figured I'd ask22:14
torgomaticbriancline: I'd guess that it's related to container listings; DLOs need container listings to be able to do stuff, so if you don't have .rlistings set on the public container, it won't work22:16
torgomaticother than that, I got nothing22:16
brianclinenotmyname: ahhh that would make sense. I'll give that a shot. thanks22:17
*** proteusguy__ has quit IRC22:17
openstackgerritMerged openstack/swift: go: improve replication logging  https://review.openstack.org/22033322:18
brianclineyep, that did it. I figured it was something silly22:28
*** proteusguy__ has joined #openstack-swift22:30
*** wbhuber is now known as wbhuber_22:40
*** hrou has quit IRC22:48
*** ctrath has quit IRC22:49
*** janonymous_ has quit IRC22:51
*** asettle has joined #openstack-swift22:51
*** wbhuber_ has quit IRC22:52
*** nadeem has quit IRC22:55
*** kaliya has joined #openstack-swift22:59
kaliyaHi in Juno I have this recurrent error in swift logs ( http://paste.openstack.org/raw/450899/ ) but I don't know how to troubleshoot further. Glance works fine on swift and object uploads/downloads from swift also is perfect. I think that it might be something old... There are no other hitting requests coming in nor other operations... But this entry is very frequent. Suggestions?23:01
*** ho has joined #openstack-swift23:01
kaliyaSeems that it tries to do a listdir on a file23:02
hogood morning!23:06
kaliyahi ho23:08
hokaliya: hello23:09
*** km has joined #openstack-swift23:10
*** asettle is now known as asettle-afk23:15
torgomatickaliya: it says right there in the output: "Permission denied: '/var/lib/glance/node/2/objects/85/809/2ac8393f1b22d216fdc9915e9968a809'"23:26
torgomaticgo make sure swift can read that directory23:26
*** chlong has quit IRC23:27
*** chlong has joined #openstack-swift23:28
*** cdelatte has joined #openstack-swift23:34
*** cdelatte has quit IRC23:37
*** asettle-afk is now known as asettle23:38
*** kei_yama has joined #openstack-swift23:39
*** hrou has joined #openstack-swift23:44
*** asettle has quit IRC23:48
*** minwoob has quit IRC23:58

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