Wednesday, 2017-04-05

*** zul_ has joined #openstack-swift00:07
*** zul_ has quit IRC00:46
*** zhurong has joined #openstack-swift00:46
*** hoonetorg has quit IRC01:02
*** m_kazuhiro has joined #openstack-swift01:17
kota_good morning01:17
m_kazuhirokota_: good morning01:17
kota_m_kazuhiro: hi01:18
*** m_kazuhiro has quit IRC01:19
*** m_kazuhiro has joined #openstack-swift01:22
mattoliveraukota_, m_kazuhiro morning01:30
kota_mattoliverau: o/01:31
m_kazuhiromattoliverau: morning!01:32
openstackgerritEmilien Macchi proposed openstack/swift master: Add sem-ver flag so pbr generates correct version  https://review.openstack.org/45342401:34
*** vint_bra has joined #openstack-swift01:35
*** zhurong has quit IRC01:52
*** yulijie has quit IRC01:56
*** zhurong has joined #openstack-swift01:57
*** chosafine has joined #openstack-swift02:04
*** jamielennox is now known as jamielennox|away02:07
*** tanee_away is now known as tanee02:11
*** jamielennox|away is now known as jamielennox02:21
*** vint_bra has quit IRC02:22
*** winggundamth has joined #openstack-swift02:33
*** zhurong has quit IRC02:38
*** SkyRocknRoll has joined #openstack-swift03:00
*** zhurong has joined #openstack-swift03:13
*** links has joined #openstack-swift03:16
mahaticgood morning03:22
*** klrmn has quit IRC03:25
m_kazuhiromahatic: good morning03:36
*** gkadam has joined #openstack-swift03:45
*** ljjjustin has joined #openstack-swift03:47
mahaticm_kazuhiro: o/03:53
*** chosafine has quit IRC03:54
*** rcernin has joined #openstack-swift04:06
*** stradling has joined #openstack-swift04:09
*** zhurong has quit IRC04:12
*** rcernin has quit IRC04:13
*** m_kazuhiro has quit IRC04:21
*** zaitcev has quit IRC04:35
*** zaitcev has joined #openstack-swift04:35
*** ChanServ sets mode: +v zaitcev04:35
*** zhurong has joined #openstack-swift04:35
*** psachin has joined #openstack-swift04:40
*** chosafine has joined #openstack-swift04:43
mattoliveraumahatic: morning04:43
*** SkyRocknRoll has quit IRC04:47
*** chlong has quit IRC04:49
mahaticmattoliverau: o/04:49
*** chosafine has quit IRC04:55
*** m_kazuhiro has joined #openstack-swift04:58
*** jaosorior_away is now known as jaosorior05:11
*** chosafine has joined #openstack-swift05:13
*** chosafine has quit IRC05:13
*** tonyb_ is now known as tonyb05:25
*** hoonetorg has joined #openstack-swift05:33
openstackgerritjunboli proposed openstack/swift master: Update doc infos to ocata  https://review.openstack.org/45346705:33
*** bkopilov has quit IRC05:35
*** bkopilov has joined #openstack-swift05:35
*** stradling has quit IRC05:36
*** ChubYann has quit IRC05:39
*** cshastri has joined #openstack-swift05:57
*** pcaruana has joined #openstack-swift06:08
*** hoonetorg has quit IRC06:29
*** rcernin has joined #openstack-swift06:31
*** hoonetorg has joined #openstack-swift06:42
*** sputnik13 has quit IRC06:44
*** silor has joined #openstack-swift06:45
*** sputnik13 has joined #openstack-swift06:45
*** tesseract has joined #openstack-swift06:52
*** hseipp has joined #openstack-swift06:53
*** silor1 has joined #openstack-swift06:58
*** dja has quit IRC07:00
*** silor has quit IRC07:00
*** silor1 is now known as silor07:00
acolesgood morning07:17
acoleskota_: clayg: thanks for adding your thought to the etherpad.. good stuff.07:26
kota_good morning acoles07:27
kota_acoles: and just putting small acks to the patch 441921 and moving the patch 44931007:28
patchbothttps://review.openstack.org/#/c/441921/ - swift - Add Composite Ring Functionality07:28
patchbothttps://review.openstack.org/#/c/449310/ - swift - Add id to RingBuilder to differentiate rings in co...07:28
kota_acoles: is the patch 449310 ready for review, right?07:28
patchbothttps://review.openstack.org/#/c/449310/ - swift - Add id to RingBuilder to differentiate rings in co...07:28
acoleskota_: yes and no :)07:28
*** m_kazuhiro_ has joined #openstack-swift07:28
acoleskota_: yes, it's in good shape wrt test etc IMHO07:29
kota_acoles: ok07:29
acoleskota_: no, I think clayg is advocating on etherpad that the id is only set on save() - but I am reading etherpad quickly, need to digest it more07:30
kota_ah, you ware writing the reason for yes/no07:31
*** m_kazuhiro has quit IRC07:31
acoleskota_: I think in my comment on patch 449310 I described that alternative (set id on save, remove the assign_id method)07:32
patchbothttps://review.openstack.org/#/c/449310/ - swift - Add id to RingBuilder to differentiate rings in co...07:32
acoleskota_: yep. yes because... no because ... :)07:32
acoleskota_: an interesting thought from etherpad comments - maybe even a newly created builder does not have an id until it has been saved? at first I thought that too demanding, but actually maybe it's a good idea to always save a *new* builder before using it with composite-builder? If you have any more thoughts on that then please comment on patch.07:38
kota_acoles: i think that from Clay's idea but yes, so the point we can create the new uuid is only at the save method for the builder. and it looks the difference with your patch (I'm at the builder.py on youre patch)07:41
*** oshritf has joined #openstack-swift07:42
*** gkadam is now known as gkadam-afk07:43
*** amoralej|off is now known as amoralej07:43
acoleskota_: I think assign_id would be removed; that code goes to the save method; and the __init__ changes go away07:45
kota_acoles: yes, I'm writing comments about that07:46
acoleskota_:  thanks!07:46
*** SkyRocknRoll has joined #openstack-swift07:48
*** geaaru has joined #openstack-swift07:50
*** silor has quit IRC07:56
*** zacksh has quit IRC07:58
*** zacksh has joined #openstack-swift08:00
*** hseipp has quit IRC08:01
*** cbartz has joined #openstack-swift08:27
*** jaosorior is now known as jaosorior_lunch08:31
*** kei_yama has quit IRC08:38
kota_acoles: pushed my comments on the patch 44931008:41
patchbothttps://review.openstack.org/#/c/449310/ - swift - Add id to RingBuilder to differentiate rings in co...08:41
*** oshritf has quit IRC08:50
dewanee_does anyone know what this can be caused by:08:51
dewanee_swift-object-reconstructor: Unexpected entity in data dir: u'/srv/node/mpath0p1/objects-08:51
dewanee_1/auditor_status_ZBF.json'08:51
*** oshritf has joined #openstack-swift08:51
*** oshritf has quit IRC08:54
dewanee_everything seems to be fine08:59
dewanee_otherwise08:59
*** oshritf has joined #openstack-swift09:00
charzdewanee_: It just a warning message form reconstructor because it's not a partition folder, you can just ignore that.09:05
*** psachin has quit IRC09:07
*** psachin has joined #openstack-swift09:11
dewanee_good to know, thanks charz09:27
charzdewanee_: np :)09:28
dewanee_I have another issue with swift-object-replicator reporting ~50k failures09:30
dewanee_as far as I understand failures are expected but I can't quantify how many should trigger a "something not working" warning09:31
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Refactor diskfile check implementation of automated tiering  https://review.openstack.org/45354809:50
*** m_kazuhiro_ has quit IRC09:56
*** mvk has quit IRC10:00
*** ljjjustin has quit IRC10:12
*** pcaruana|afk| has joined #openstack-swift10:21
*** pcaruana|afk| has quit IRC10:23
*** pcaruana has quit IRC10:24
*** pcaruana has joined #openstack-swift10:25
*** zhurong has quit IRC10:30
*** jaosorior_lunch is now known as jaosorior10:31
*** mvk has joined #openstack-swift10:32
*** hseipp has joined #openstack-swift10:49
*** vint_bra has joined #openstack-swift11:12
*** dja has joined #openstack-swift11:19
*** dja has quit IRC11:24
*** winggundamth has quit IRC11:24
*** dja has joined #openstack-swift11:27
*** stradling has joined #openstack-swift11:30
*** vint_bra has quit IRC12:05
*** klamath has joined #openstack-swift12:07
*** klamath has quit IRC12:07
*** klamath has joined #openstack-swift12:07
*** SkyRocknRoll has quit IRC12:18
*** larivee has joined #openstack-swift12:30
lariveegood day all,   Is there an easier way than to iterate over all object of a tenant to purge that tenant from Swift ? ( from an admin / operator  access view )12:31
*** silor has joined #openstack-swift12:38
acoleslarivee: the account reaper can remove deleted account objects https://docs.openstack.org/developer/swift/overview_reaper.html12:39
lariveethx acoles12:40
*** silor has quit IRC12:47
*** gkadam-afk has quit IRC12:49
*** tongli has joined #openstack-swift12:49
*** psachin has quit IRC12:52
-openstackstatus- NOTICE: The Gerrit service on http://review.openstack.org is being restarted to address hung remote replication tasks, and should return to an operable state momentarily12:52
*** psachin has joined #openstack-swift13:05
*** links has quit IRC13:08
*** catintheroof has joined #openstack-swift13:10
*** catintheroof has quit IRC13:10
*** catintheroof has joined #openstack-swift13:11
*** amoralej is now known as amoralej|lunch13:17
*** chlong has joined #openstack-swift13:17
*** cshastri_ has joined #openstack-swift13:23
*** cshastri has quit IRC13:26
*** psachin has quit IRC13:26
*** cshastri_ has quit IRC13:27
*** psachin_ has joined #openstack-swift13:32
*** psachin_ has quit IRC13:37
EmilienMhello here, can you review this patch please? https://review.openstack.org/#/c/453424/ - it would help TripleO CI to test upgrades from Ocata to Pike. Thanks a lot!13:40
*** cshastri_ has joined #openstack-swift13:40
tdasilvaEmilienM: can you explain that patch, I don't understand it all13:45
tdasilvaEmilienM: I see no files being changed, what am i missing?13:45
EmilienMtdasilva: in the commit message I tried to explain it :D13:45
EmilienMtdasilva: so :13:45
*** _JZ_ has joined #openstack-swift13:45
acolestdasilva: EmilienM I am just reading the linked pbr doc and infer that there is some significance to the Sem-Ver tag??13:45
EmilienMthe tooling that build packages read commit message13:46
*** cshastri__ has joined #openstack-swift13:46
EmilienMand will bump pbr to the next Y number13:46
EmilienMstarting from this commit13:46
EmilienMbecause you didn't push for a tag yet in Pike13:46
tdasilva"We then walk git history back to the last release. Within each commit we look for a Sem-Ver: pseudo header, and if found parse it looking for keywords."13:46
EmilienMyup13:47
EmilienMwe did it in nova, ironic, and all other projects that tripleo use13:47
EmilienMit has zero impact on your project I think, it just help packagers to test upgrades13:47
acolesand Sem-Ver: feature causes a minor version bump13:48
*** cshastri_ has quit IRC13:49
*** psachin_ has joined #openstack-swift13:49
EmilienMacoles: Y13:49
EmilienMX.Y.Z13:49
EmilienMI thought Swift would a Y bump this time13:49
EmilienMbut if you prefer X or Z I don't care13:49
EmilienMjust update the patch, so we can start upgrading swift in our CI13:50
tdasilvaacoles: right, so in X.Y.Z feature will bump Y, but this is all just pseudo versioning. distro packages will start showing up as 2.14.0 correct?13:50
EmilienMyes exact13:50
*** cshastri__ has quit IRC13:50
tdasilvaonce we release swift again, then distro packages will just continue with 2.14.x13:51
tdasilvaweird, but i think I got it13:51
EmilienMwe could get rid of this if projects would produce a tag right after openstack releases (right after ocata GA for example)13:51
EmilienMbut nobody or a few do it13:51
EmilienMwhich is a pain for us, because we can't test upgrades from ocata to pike until m113:51
tdasilvaEmilienM: like a release tag?13:51
EmilienMyes13:51
EmilienMlife would be easier with a tag13:52
EmilienMbut teams want to wait for m1 to push for the first pike tag13:52
EmilienMand when I say pike, I say for all releases, newton, ocata, etc13:52
EmilienMit makes our life harder because we can't test package upgrades13:52
tdasilvaEmilienM: yeah, in swift case is not even about waiting for m1. I think our release policy is more like. "Do we have anything important to release right now, then let's do it"13:53
tdasilvawhenenever in the cycle that happens to be13:53
EmilienMtdasilva: right13:55
EmilienManyway, please take this one in consideration, it would really help. Thanks13:55
*** vint_bra has joined #openstack-swift13:56
*** amoralej|lunch is now known as amoralej13:57
*** cshastri__ has joined #openstack-swift14:02
*** zul has quit IRC14:05
*** jistr is now known as jistr|mtg14:07
*** cshastri__ is now known as cshastri14:12
*** zul has joined #openstack-swift14:22
*** caiobrentano has joined #openstack-swift14:46
*** zul_ has joined #openstack-swift14:46
*** zul_ has quit IRC14:59
jlvillalnotmyname, Did the patchbot leave #openstack-ironic?15:02
* jlvillal realizes that is a rhetorical question :)15:02
*** oshritf has quit IRC15:03
*** chlong has quit IRC15:03
*** chlong has joined #openstack-swift15:04
*** cbartz has left #openstack-swift15:06
*** cshastri has quit IRC15:09
*** psachin_ has quit IRC15:14
*** tongli has quit IRC15:17
*** chlong has quit IRC15:21
*** m_kazuhiro has joined #openstack-swift15:25
*** vint_bra has quit IRC15:30
*** caiobrentano_ has joined #openstack-swift15:31
*** vint_bra has joined #openstack-swift15:32
*** m_kazuhiro has quit IRC15:33
*** caiobrentano has quit IRC15:34
*** chlong has joined #openstack-swift15:34
*** jistr|mtg is now known as jistr15:40
notmynamegood morning16:03
notmynamejlvillal: yes. sorry about that. I'll ask patchbot to rejoin16:04
notmynamejlvillal: patchbot is new and improved. sortof. less crazy. also very slightly less helpful.16:04
jlvillalnotmyname, Thanks!16:04
notmynameEmilienM: if you just need a different version tag, why choose Y before the project has released something that bumps Y? bumping Z seems to more closely match what you're getting at?16:07
notmynameif we bump Y now to get to an effective 2.14.0 does that mean our next tag needs to be 2.14.1?16:08
notmynameI always liked the idea of versions based on VCS tags (instead of strings in text files), but now you're saying that the current version is some combination of VCS tag plus a special magic string in a commit message?16:09
notmynamebut wait. the pbr docs say "A missing Sem-Ver line is equivalent to Sem-Ver: bugfix. " Doesn't that mean we've effectively got 2.13.1 now anyway? (ie incremented Z)16:12
clarkbnotmyname: yes incremented Z if you don't specify16:17
notmynameok, so if that's the case, why the need for the post-ocata patch?16:18
notmynameI don't understand why this patch is needed now, or why it hasn't been needed after past cycle releases16:25
notmyname(and the concept of a commit message in the VCS history having semantic meaning on the produced software as opposed to just describing what/how a particular commit works is scary to me16:26
notmynameacoles: tdasilva: you've looked at this patch, so please tell me where I'm overreacting :-)16:29
*** JimCheung has joined #openstack-swift16:34
acolesnotmyname: tdasilva made a comment earlier that this was 'pseudo versioning' and next release would still be 2.14.0...and at that point I got confused :/16:37
*** chsc has joined #openstack-swift16:42
EmilienMnotmyname: feel free to change it16:43
EmilienMnotmyname: I really don't care about the X Y Z16:43
EmilienMI just need a bump :D16:43
*** tesseract has quit IRC16:43
notmynameEmilienM: how is it not already bumped?16:43
notmynamehow or why this particular patch is fixing something is not at all clear to me16:44
EmilienMnotmyname: when is your lastest release ?16:44
notmynamefor ocata16:44
notmynamewe've landed commits since then, so why isn't pbr calling it 2.13.1 already?16:45
notmynameie something different than the tag that was released most recently16:46
EmilienMnotmyname: because no tag has been pushed, it's a packaging thing16:47
EmilienMnotmyname: distros need a new semver16:47
EmilienMso we either need a tag now, or my patch16:47
*** ChubYann has joined #openstack-swift16:48
notmynamepackagers are using pbr to get a version number?16:50
notmynamewhich looks at the tag (most recent is 2.13.0) and parses commit messages to see if a bigger one is needed16:50
notmynameright?16:50
notmynameand pbr is currently reporting swift as "swift2.13.1.dev61 pre-release bff9f89"16:52
*** hseipp has quit IRC16:53
*** jamielennox has quit IRC17:04
*** jamielennox has joined #openstack-swift17:07
*** jaosorior is now known as jaosorior_away17:08
*** klrmn has joined #openstack-swift17:08
*** neonpastor has joined #openstack-swift17:15
*** mvk has quit IRC17:22
tdasilvanotmyname: maybe i misunderstood, but I don't think that patch forces us to tag our next release as 2.14.117:28
notmynameyeah, that's what I was trying to figure out. does it? but if not, why is it needed anyway? just wanting to understand what's needed, what this fixes, and what the implications are17:29
tdasilvanotmyname: i'm not 100% about this, so take it with a grain of salt:17:39
tdasilvaocata repo for rdo: https://trunk.rdoproject.org/centos7-ocata/b7/c2/b7c2a9196009ef78560acfb3826b9106f95d7fdf_50de241a/17:39
tdasilvaif you search for swift, you will notice 2.13.117:40
tdasilvaand this is rdo master - which i assume will become pike17:40
tdasilvahttps://trunk.rdoproject.org/centos7-master-head/bc/9a/bc9a7075d3accf3160043e8366745a1dd895b08d_0025310a/17:40
tdasilvaalso 2.13.117:40
notmynameok17:40
tdasilvaso I'm assuming that17:41
tdasilvaI'm assuming that EmilienM's patch will push the master version to 2.14.017:41
tdasilvaand allow them to test upgrades17:41
tdasilvaEmilienM: ^^^ is that correct?17:41
notmynameupgrades can't be tested from 2.13.0 to 2.13.1?17:42
tdasilvabut ocata is already at 2.13.117:42
tdasilvaso I assume that's the issue17:42
notmynameoh, interesting. maybe that's the part I didn't catch earlier17:43
notmynameoh! because we've landed backports for ocata17:43
notmynamewhich bumps the Z number automatically17:43
notmynamebut we haven't pushed anything that triggers pbr to bump the Y number, so both master and stable/ocata are listed as 2.13.117:44
notmynameright?17:44
tdasilvathat's how I understood17:45
*** SkyRocknRoll has joined #openstack-swift17:46
*** tonanhngo has joined #openstack-swift17:47
acolestdasilva: thanks again for your work on https://review.openstack.org/#/c/451524/17:47
tdasilvaacoles: i'm afraid the hard part now begins with trying to figure out step 217:48
patchbotNo data found for patch 217:48
tdasilvalol17:48
acolespatchbot has finger on the pulse :)17:48
notmynamethat's weird17:49
*** tonanhngo_ has joined #openstack-swift17:50
tdasilvastep 217:51
patchbotNo data found for patch 217:51
tdasilvap 217:51
patchbotNo data found for patch 217:51
*** tonanhngo has quit IRC17:51
*** SkyRocknRoll has quit IRC17:52
*** SkyRocknRoll has joined #openstack-swift17:52
*** tonanhngo_ has quit IRC17:54
*** tonanhngo has joined #openstack-swift17:55
*** silor has joined #openstack-swift17:58
*** mvk has joined #openstack-swift18:00
*** silor has quit IRC18:10
*** silor has joined #openstack-swift18:11
notmynameEmilienM: is what tdasilva and I were talking about close to the truth about the version numbers?18:11
EmilienMtdasilva: it's correct18:12
*** stradling has quit IRC18:13
EmilienMnotmyname: true18:16
notmynamethanks18:16
*** silor has quit IRC18:16
notmynamethat makes sense to me18:16
notmynamepbr parsing commit message is a separate issue (and one I still don't like), but I understand the need for the patch now18:17
notmynameEmilienM: and to be explicit, does your patch mean that our next tag has to skip 2.14.0?18:17
patchbotNo data found for patch 218:17
notmynamepatchbot: I will cut you18:17
*** silor has joined #openstack-swift18:18
EmilienMnotmyname: I think I never said I liked it18:18
EmilienMI'm an operator who wants to upgrade OpenStack now18:18
notmynameno, that's a separate conversation from the patch and unblocking you18:19
EmilienMnotmyname: let me check that information18:19
EmilienMnotmyname: yes right18:19
notmynameok, thanks18:19
*** geaaru has quit IRC18:23
tdasilvais right we have to skip 2.14.0?18:24
patchbotNo data found for patch 218:24
tdasilvas/is/yes18:24
notmynametdasilva: he's checking :-)18:24
tdasilvaoh18:24
*** silor has quit IRC18:27
*** silor has joined #openstack-swift18:27
EmilienMnotmyname: I'm actually not sure, tbh18:36
EmilienMon my knowledge no but i'm checking history now18:36
*** oshritf has joined #openstack-swift18:37
openstackgerritAlistair Coles proposed openstack/swift master: WIP Add CompositeRingBuilder class  https://review.openstack.org/45382718:38
*** stradling has joined #openstack-swift18:38
EmilienMok so https://review.openstack.org/#/c/427643/ merged and ironic released 7.0.0 after18:39
EmilienMI don't think we need to skip the tag18:39
EmilienMjroll: can you confirm maybe?18:39
*** amoralej is now known as amoralej|off18:41
jroll?18:41
jrollyeah, afaik you don't need to skip it18:41
jrollI couldn't find the docs yesterday, but found the spec18:42
jrolland the spec said pbr will version it at e.g. 6.1.9999.devXXX18:42
jrollbut honestly I'm only 50% sure on this18:42
jrollEmilienM: ^^18:42
acolesclayg: is this the kind of thing you were thinking re etherpad comments: patch 45382718:43
patchbothttps://review.openstack.org/#/c/453827/ - swift - WIP Add CompositeRingBuilder class18:43
acoleskota_: fyi ^^ that's just to test our understanding18:43
notmynamejroll: how can we get more certain? I'd like to understand the impact18:43
* notmyname goes to pick up lunch18:43
jrollnotmyname: the most certain way would be to ask lifeless, read the docs, or read the code. or merge it locally and see what happens.18:44
claygnotmyname: FWIW merging a commit message will *never* break my packages18:45
claygI mean it might - but all that would really happen is I would cuss then fix it18:46
*** hoonetorg has quit IRC18:51
*** SkyRocknRoll has quit IRC18:53
*** silor has quit IRC18:53
*** oshritf has quit IRC18:59
*** oshritf has joined #openstack-swift19:03
*** stradling has quit IRC19:10
*** oshritf has quit IRC19:10
*** oshritf has joined #openstack-swift19:12
*** oshritf has quit IRC19:18
*** oshritf has joined #openstack-swift19:21
tdasilvajust caught up with the conversation on #openstack-dev, seems like the most obvious fix is for rdo package maintainers to use  PBR_VERSION variable ???19:39
notmynameyeah, I think19:39
*** stradling has joined #openstack-swift19:41
*** oshritf has quit IRC19:48
caiobrentano_Hi all! I'm getting some exceptions from object-expirer, resulting in "Unexpected response: 412 Precondition Failed:"... what could I check? I did some tests with x-delete-at, and everything worked as expected19:51
caiobrentano_Apparently the object still exists after this 412 error... but with no expirer header19:51
notmynamecaiobrentano_: any chance you can pastebin the request headers and response headers? (scrub the token at least)19:53
*** oshritf has joined #openstack-swift19:53
caiobrentano_notmyname I can paste bin the log... because I'm not doing any request19:53
*** silor has joined #openstack-swift19:54
caiobrentano_https://pastebin.com/pyhg2EhD19:55
notmynameoh right. expirer. you wouldn't have the request19:56
*** silor1 has joined #openstack-swift19:57
openstackgerritThiago da Silva proposed openstack/pyeclib master: DO NOT MERGE - testing new gate job  https://review.openstack.org/45384719:58
*** silor has quit IRC19:59
*** silor1 is now known as silor19:59
claygcaiobrentano_: I think that can happen if you upload at t0 with x-delete-at t2, then upload again at t1 with no x-delete-at19:59
notmynamecaiobrentano_: is that all you have for that transaction id?20:00
notmynameas normal, i think clayg is way ahead of me. yeah, looks like a mismatched timestamp20:00
claygcaiobrentano_: the x-delete-at t2 is suposed to be reaped, but if there a race it might still do the delete and find the object not having the matching delete-at metadata so the object-server refused to replace the no-supposed-to-be-expired .data with a .ts20:00
*** pcaruana has quit IRC20:01
claygwhich... the expirer *should* be fine with - so the bug to file may just be "not helpful noise in logs in expected failure mode"20:01
claygnotmyname: I'm trying to clease my pallet after freating about automatic package versioning20:02
caiobrentano_clayg right now I don't have further infos... these are log backups with 7-day life span! so, it was created 7 days ago and never modified20:02
notmynameyou should be able to prove out clayg's theory by looking in the logs for that particular object20:02
notmynameclayg: scotch may help ;-)20:02
notmynamecaiobrentano_: eg see if there are multiple PUTs or some DELETE or something20:02
*** oshritf has quit IRC20:06
caiobrentano_notmyname I'll have to talk with the responsible for this objects. This "7-day backup flow" happens for thousands of files... but just this error apparently happens randomly for a small portion20:07
claygcaiobrentano_: and at the end of the day is this object *supposed* to be expired - it should have x-delete-at metadata if so?20:09
caiobrentano_clagy no! it still exists, but with no x-delete-at metadata20:10
*** jamielennox is now known as jamielennox|away20:12
claygso the end state is good afayk and the only "problem" is the unexplicable traceback?20:13
caiobrentano_clayg I just saw this header: X-Object-Meta-Mtime in the object that failed at expirer20:13
claygafaik that's just a swiftclient thing - no real semantic meaning here20:14
caiobrentano_clagy No, the end state is the object not deleted and without expirer headers20:22
clayg... and you want it to be *expired*20:23
caiobrentano_yes... because I can still GET the object20:24
claygI can't really imagine a way where an object that doesn't have x-delete-at metadata could possibly be expired; or a process by which an object *with* x-delete-at metadata could lose it - unless you re-uplod the object w/o the x-delete-at set - in which case... that's expected behavior?20:24
claygmaybe something is wrong with some version of post that causes an object to loose it's x-delete-at metadata20:25
claygwell... acctually i'm not sure if POST *should* clear x-delete-at - maybe?20:25
claygcaiobrentano_: do you know what version of swift this is, and if it's configured with post_as_copy in the proxy?20:26
claygcaiobrentano_: if you dig out the hashdir on disk from the ring - can you check if there's a .meta next to the .data file?20:26
tdasilvaclayg: didn't someone point out the other day that copying an object that is set to expire has issues with it....something like that20:27
tdasilvanevermind, it was object expiration + versioning20:28
caiobrentano_clayg version: "2.10.1"... no post_as_copy conf on proxy20:29
caiobrentano_clayg there's just the .data file20:29
*** patchbot has quit IRC20:30
*** patchbot has joined #openstack-swift20:30
notmynamehttps://review.openstack.org/453847 https://review.openstack.org/453848 patch 1234520:31
patchbotpatch 453847 - pyeclib - DO NOT MERGE - testing new gate job20:31
patchbotpatch 453848 - loci - Update userns info (MERGED)20:31
notmynameskip 23420:32
*** silor has quit IRC20:34
claygso 2.10.1 did have 46d61a4dcd9a5d9157625c06d6fe7d916e80c3d2 (SSC mw)20:35
claygbut post_as_copy is probably still default true20:35
claygcaiobrentano_: you should be able to confirm from the timestamp of the .data when the object was created - you may be able to trace that back to the request20:36
claygit was possibly either a PUT w/o an x-delete-at metadata - or a POST which got translated to a COPY (which on master with post_as_copy=true seems to drop the x-delete-at metadata)20:38
*** xinli has joined #openstack-swift20:38
xinli+acoles: one question in 'All-in-one", in Common Post-Device SetUp, should I define "your-user-name" or I just use my login user name "ubuntu" ?20:40
*** patchbot has quit IRC20:40
*** patchbot has joined #openstack-swift20:41
patchbothello world!20:44
* patchbot is alive20:45
*** rcernin has quit IRC20:45
*** torgomatic has joined #openstack-swift20:46
*** ChanServ sets mode: +v torgomatic20:46
*** stradling has quit IRC20:47
clayginteresting fast-post also resets x-delete-at it seems - caiobrentano_ I would say you're looking for a PUT or a POST on this object after it was originally uploaded which would have very likely reset the x-delete-at20:48
claygxinli: just use ubuntu cc zaitcev you normally have opinions about this?  ;)20:49
notmynameI think zaitcev always logs into the "ubuntu" user ;-)20:50
caiobrentano_clayg I've found 2 PUT requests to an object. But we don't log the headers20:51
caiobrentano_clayg couldn't find any POST20:52
*** m_kazuhiro has joined #openstack-swift20:52
*** hoonetorg has joined #openstack-swift20:53
caiobrentano_clayg I'm pretty sure they upload this files with a cron job doing "swift upload container logs/"20:53
notmynamemeeting time in #openstack-meeting in 3 minutes20:57
caiobrentano_thanks clayg and notmyname! I'm done for now ;)20:58
kota_morning20:59
notmynamehello kota_20:59
kota_hi notmyname20:59
*** dmorita has joined #openstack-swift20:59
notmynamemattoliverau: good morning. around today?21:00
mattoliveraumorning, yup, just a change in time makes it hard (earlier) :)21:00
*** mariusv has quit IRC21:01
*** mariusv has joined #openstack-swift21:03
acolesxinli: you can choose (see https://docs.openstack.org/developer/swift/development_saio.html#what-s-in-a-your-user-name) but I have always created a swift user account and used that. I'm not sure if anything assumes the username is swift, the doc says that is the default but if you are careful to set <your-user-name> wherever needed it should be ok to use another username.21:04
rledisezxinli, acoles: i run with an other user than swift, it works fine21:05
tdasilvaacoles, xinli: yep, what rledisez said21:06
tdasilvai run with 'vagrant'21:06
rledisezbut there are some hardcoded path (eg: /etc/swift/swift.conf) so you still need a root access to create these files21:07
acolestdasilva: rledisez thanks for confirming that21:07
xinlithank you very much,21:08
tdasilvaxinli: for reference: https://github.com/thiagodasilva/ansible-saio21:09
mattoliverauI just run it with a matt user, cause I'm lazy and remembering :P21:09
tdasilvaxinli: also, just fyi, there's a swift community meeting happening right now in #openstack-meeting21:22
xinli+tdasilva21:22
xinlithanks21:22
*** chosafine has joined #openstack-swift21:28
*** chosafine has quit IRC21:39
*** dja has quit IRC21:47
*** JimCheung has quit IRC21:52
*** JimCheung has joined #openstack-swift21:53
pdardeau_ntata: do you know about the your-user-name question and if there are any ill effects of not using swift?21:54
*** catintheroof has quit IRC21:54
acolesclayg: in atlanta someone from storyboard explained to me how we could (if we wanted) trial storyboard - it would create new topics on indexed from a number that would never collide with anything in launchpad, then if/when launchpad was migrated it would all be happy.21:54
pdardeau_ntata: i spoke too soon. i see it's already been answered21:55
zaitcev"OpenStack leadership training thing in Ann Arbor" sounds insanely corporate, both the name and location.21:57
clarkbits at a deli21:58
tdasilvazaitcev: it will start with compliance and ethics training21:58
tdasilvaclayg: we now have a pyeclib job that tests against libec master: https://review.openstack.org/#/c/45384721:59
patchbotpatch 453847 - pyeclib - DO NOT MERGE - testing new gate job21:59
notmynamezaitcev: tdasilva: lol22:00
* mattoliverau is going to find breakfast o/22:00
kota_notmyname: btw, is timburke on vacation?22:00
kota_yet22:01
*** ianychoi has joined #openstack-swift22:01
notmynamekota_: yes22:01
notmynamekota_: for the rest of this week. will be beack monday22:01
kota_notmyname: ok, thanks22:01
acolesgood night22:02
*** chlong has quit IRC22:02
claygtdasilva: you're getting good at this!22:02
zaitcevclarkb: he isn't a squad leader for nothing22:03
claygtdasilva: is it *really* better to commit fixes into project-config instead of a do-the-thing.sh *in* the repo?  https://review.openstack.org/#/c/452886/22:04
patchbotpatch 452886 - openstack-infra/project-config - add /usr/local/lib to library cache (MERGED)22:04
claygtdasilva: do you have any idea how you might demonstrate a test that passes on master but fails/skips on system packages?22:08
claygtdasilva: ... or vice versa?22:09
*** dmorita has quit IRC22:09
*** m_kazuhiro has quit IRC22:10
*** xinli has quit IRC22:11
*** jamielennox|away is now known as jamielennox22:13
*** caiobrentano_ has quit IRC22:17
notmynameFYI next PTG is in Denver Colorado September 11-1522:20
*** foutatoro has joined #openstack-swift22:23
notmynamegood advice (reviews in general, openstack in particular) https://twitter.com/ihrachyshka/status/84475763074881126622:25
zaitcevAww. I may already be in Austin by that time.22:33
*** klamath has quit IRC22:34
*** adriant has joined #openstack-swift23:06
*** vint_bra has quit IRC23:11
zaitcevThis TC document is irritating23:16
zaitcevmaybe my cultural background is a problem23:16
zaitcev"The old confusion about git namespaces is a thing of the past, given how convenient and user friendly these new views are."23:16
*** kei_yama has joined #openstack-swift23:35
*** chsc has quit IRC23:38
*** JimCheung has quit IRC23:41
*** JimCheung has joined #openstack-swift23:42
*** jamielennox is now known as jamielennox|away23:42
*** foutatoro has quit IRC23:43
*** jamielennox|away is now known as jamielennox23:45
*** vint_bra has joined #openstack-swift23:45
*** vint_bra has quit IRC23:50
*** _JZ_ has quit IRC23:53

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