Tuesday, 2017-02-14

*** klamath has quit IRC00:05
*** _JZ_ has quit IRC00:07
JimCheungMorning Kota_:00:09
kota_morning!00:09
kota_JimCheung: ^^00:09
JimCheungKota_: We're getting ready to put the 3rd party testing/verification online.  In the mean time, do you have any additional comments on the code review?  https://review.openstack.org/#/c/424353/00:14
patchbotpatch 424353 - liberasurecode - Add Phazr.IO libphazr backend to liberasurecode00:14
*** catintheroof has quit IRC00:25
*** dmorita has joined #openstack-swift00:26
*** oshritf has quit IRC00:28
mattoliveraukota_: morning00:35
kota_mattoliverau: o/00:35
*** dmorita has quit IRC00:42
*** dmorita has joined #openstack-swift00:47
*** dmorita has quit IRC00:54
*** gatuus has quit IRC01:02
*** jamielennox is now known as jamielennox|away01:09
*** jamielennox|away is now known as jamielennox01:17
openstackgerritKota Tsuyuzaki proposed openstack/swift master: EC Fragment Duplication - Foundational Global EC Cluster Support  https://review.openstack.org/21916501:35
*** sams-gleb has joined #openstack-swift01:54
*** sams-gleb has quit IRC01:59
*** cdelatte has quit IRC01:59
*** tqtran has quit IRC02:02
*** dmorita has joined #openstack-swift02:14
*** klrmn has quit IRC02:19
*** dmorita has quit IRC02:21
*** tanee_away is now known as tanee02:22
*** JimCheung has quit IRC02:34
*** adu has joined #openstack-swift02:48
*** Jeffrey4l_ has quit IRC03:08
*** Jeffrey4l_ has joined #openstack-swift03:09
*** Jeffrey4l_ has quit IRC03:13
*** Jeffrey4l_ has joined #openstack-swift03:14
*** Jeffrey4l_ has quit IRC03:16
*** Jeffrey4l_ has joined #openstack-swift03:16
*** adu has left #openstack-swift03:16
*** dmorita has joined #openstack-swift03:17
*** klrmn has joined #openstack-swift03:20
*** dmorita has quit IRC03:26
*** JimCheung has joined #openstack-swift03:27
*** JimCheung has quit IRC03:31
mahaticgood morning03:34
mattoliveraumahatic: morning03:39
mahaticmattoliverau: o/03:39
*** SkyRocknRoll has joined #openstack-swift03:43
*** david-lyle_ has joined #openstack-swift03:56
*** sams-gleb has joined #openstack-swift03:57
*** david-lyle has quit IRC03:58
*** takashi has joined #openstack-swift03:59
*** links has joined #openstack-swift03:59
*** sams-gleb has quit IRC04:02
*** dmorita has joined #openstack-swift04:08
*** SkyRocknRoll has quit IRC04:12
*** dmorita has quit IRC04:12
*** psachin has joined #openstack-swift04:27
*** zaitcev has quit IRC04:32
*** tanee is now known as tanee_away04:34
*** tanee_away is now known as tanee04:37
*** SkyRocknRoll has joined #openstack-swift04:40
*** sams-gleb has joined #openstack-swift04:59
*** tqtran has joined #openstack-swift05:01
*** zul has quit IRC05:02
*** sams-gleb has quit IRC05:03
*** tqtran has quit IRC05:06
*** klrmn has quit IRC05:10
*** dja has quit IRC05:13
*** cshastri has joined #openstack-swift05:13
openstackgerritClay Gerrard proposed openstack/swift master: Deprecate broken handoffs_first in favor of handoffs_only  https://review.openstack.org/42549305:13
*** zul has joined #openstack-swift05:25
*** SkyRocknRoll has quit IRC05:37
*** Jeffrey4l_ has quit IRC05:37
*** Jeffrey4l_ has joined #openstack-swift05:40
jrichliclayg: what is our guarantee that probetests will pass against a particular configuration?  I only ask because 'handoffs_only' mode breaks all tests that assert reconstruction.05:49
jrichlibut 'handoffs_only' is not a normal setting, so maybe it is ok for them to just fail (no need to put in a check for mode and skip test)05:50
*** links has quit IRC05:55
claygjrichli: I don't think that's strongly defined - there are definately some options/configs that cause probe tests to fail06:06
jrichliclayg: ok.  in a way, i sort of like that they fail in that mode.  it serves to emphasize that it is an invalid way to run things wrt to reconstruction.06:08
claygTo the extend we believe developers can extrat useful information from the probetest suite when running it against a given configuration - we should (probably not must?) try to support that06:09
jrichlitrue ... i can see it that way as well06:09
claygsupport can either be raising a skiptest that includes the tests requirements; or even possibly altering the expected behavior06:10
clayglike the required_replicas tests just skiptest06:11
*** links has joined #openstack-swift06:11
claygtest expirer raises skiptest06:12
claygcontainer sync raises skiptest06:12
*** jtomasek has quit IRC06:12
claygtest_merge_policy_index hits /info06:14
claygjrichli: which tests fail?06:15
jrichliclayg: http://paste.openstack.org/show/598745/06:17
jrichliwhich I think are all failing in a way that makes sense06:18
claygi like that all of them say "rebuild" or "reconstruct" - it's telling me the change works!  :P06:18
jrichliexactly - that is what i was expressing about the failures serving a sort of purpose06:19
claygheh06:19
claygi can't make a judgement w/o trying to fix it06:21
jrichliabout which way to go for support?  yeah, maybe that would be a good follow-up.  or are you wanting to add that support now?06:22
clayg... and even fixing the tests once doesn't mean the next rebuild/reconstruct probetest we *add* won't introduce a similar failure06:22
claygwe have a similar problem with encryption - probetests worked with encryption at one time - do they *still* work?  dunno!06:23
jrichliyes, they do.  i typically run with crypto on in prob half my environments.06:24
claygnice!06:24
jrichliyou have to have it setup for container-sync for that to work though06:24
clayg... right - the way those skip is pretty nice06:24
jrichliheh - actually, maybe the container-sync tests are the only ones that are really testing the crypto at a probetest level.06:26
jrichlicause the body doesn't match if crypto isn't in the internal-client pipeline.  so it is going through get/put and verifying the body contents.06:26
claygso I'm pretty sure in this case it would *not* be appropriate to change the assertion - so at best we're talking about skipping - it could delay that until the last moment - and the either fail "frag rebuilt in handoffs_first" or skip "test requires handoffs_only False to assert rebuild"06:26
claygbut if it just "passed" you dev could be in handoffs_only and get a false sense of security (could happen with skips too to a lesser degree)06:27
jrichlithat sounds good - wait until the last moment06:29
claygperhaps the most correct thing to do is fail - but with better annotatin "failed because handoffs_only is on"06:29
jrichlieven better!  +106:30
claygidk, maybe skip is better06:31
jrichlithen devs can still essentially assert the expected handoffs_only failures, and it still reveals an invalid way to run06:31
clayg... does that have long term value?06:32
clayglike someone staring at broken probests only to realize they've had handoffs_only turned is worth avoiding06:32
jrichliI dont know how ops uses or doesn't use the probetests for verification.  I am pretty sure that SL uses them at some point.06:33
claygbut the cheapest solution to that is to pre-check in probe.common?06:33
claygthe probetests can only run in a development environment - the audiance might have different titles/roles at their org - but if you're running development tests in a development environment - I hope I can treat you like a developer :\06:35
jrichliok, right ...06:35
jrichliso one big pre-check with a warning - prob what i'd do06:37
jrichliand skips06:38
claygmaybe ony in the ECProbeTest case?06:38
jrichliyep06:39
clayg... same sort of "probetests pass I must not have broken rebuild" risk :\06:39
jrichliwell, i really liked the "failed because handoffs_only is on" in exactly the right spots.  its just more work.06:40
claygjrichli: ok, so ECProbeTest could parse the reconstructor config for each node on start up and just keep a map06:41
claygthen anytime when you fail in those existing tests you say "... and also probably you left handoffs_only on"06:42
claygthen if we forget to add that same decoration to another test in the future that also fails with handoffs_only on - at least you still have the message on the others?06:42
clayg... but you can't "run tests" with handoffs_only on - that's not a supported config?06:42
claygit all feels rather arbitrary06:43
mahatic..but how likely is it that devs would turn on handoffs_only and then run probe tests?06:44
jrichliits weird cause we have a defined/valid behavior for an invalid mode of operation :-)06:44
mahaticunless we're testing a feature, in which case we'd already some context06:45
mahatics/already/already have06:45
jrichlithe map sounds like a plan.06:45
jrichlimahatic: true, it would be rare.  I am not probably the normal dev case, but I know that I have left weird configs like this in my environments and didn't realize it later. :/06:46
jrichlibecause I don06:47
jrichli't use vagrant - and I reuse my VMs - I am more vulnerable to that sort of thing06:47
*** links has quit IRC06:48
mahaticright. so maybe leaving a meaningful message on the failure "fails because of handoffs_only mode is on" would do, although we may face inconsistencies in future if we forget to add the msg to newer tests06:49
mahaticbut maybe it's better than leaving as is?06:49
claygjrichli: +1 to that - probe.common's checks exist because of the time I lost only to discover my config was no longer "supported" because I changed it while reviewing some unrelated thing06:49
jrichliits my bed time.  you all have a good night / day :-)06:52
*** oshritf has joined #openstack-swift06:53
*** rcernin has joined #openstack-swift06:54
mahaticjrichli: good night!06:56
*** oshritf has quit IRC06:59
*** sams-gleb has joined #openstack-swift07:01
*** links has joined #openstack-swift07:02
*** tqtran has joined #openstack-swift07:04
*** oshritf has joined #openstack-swift07:05
*** sams-gleb has quit IRC07:05
*** tqtran has quit IRC07:08
*** ChubYann has quit IRC07:08
*** takashi has quit IRC07:14
*** tesseract has joined #openstack-swift07:15
*** SkyRocknRoll has joined #openstack-swift07:16
*** sams-gleb has joined #openstack-swift07:25
*** bkopilov has quit IRC07:26
*** bkopilov_ has quit IRC07:27
*** reedip has left #openstack-swift07:29
*** oshritf has quit IRC07:40
*** zul has quit IRC07:50
*** links has quit IRC07:50
*** links has joined #openstack-swift07:52
openstackgerritMerged openstack/swift master: Hisashi Osanai's responsibility has been changed  https://review.openstack.org/43274707:56
openstackgerritMerged openstack/swift master: Add Apache License 2.0 description in ../conf.py  https://review.openstack.org/43271807:57
openstackgerritMerged openstack/swift master: [Trivial]Fix some type errors in ../sample.conf  https://review.openstack.org/43274007:57
openstackgerritMerged openstack/swift master: Fix swift-get-nodes arg parsing for missing ring  https://review.openstack.org/40601207:58
*** takashi has joined #openstack-swift08:01
*** pcaruana has joined #openstack-swift08:11
*** amoralej|off is now known as amoralej08:15
*** rledisez has joined #openstack-swift08:19
*** geaaru has joined #openstack-swift08:34
*** zul has joined #openstack-swift08:54
*** joeljwright has joined #openstack-swift09:02
*** ChanServ sets mode: +v joeljwright09:02
*** tqtran has joined #openstack-swift09:05
*** tqtran has quit IRC09:09
*** psachin has quit IRC09:11
*** psachin has joined #openstack-swift09:11
*** psachin has quit IRC09:17
*** Dw_Sn has joined #openstack-swift09:19
Dw_SnI have n00b question, I have private buckets " S3 " interface , I am using keystone for auth, can I allow HTTP apps like wget to be able to download the files with authentication tokens ? instead of going into dashboard or using s3cmd or aws cli ?09:19
openstackgerritChristian Schwede proposed openstack/swift master: Add support to increase object ring partition power  https://review.openstack.org/33729709:24
openstackgerritChristian Schwede proposed openstack/swift master: Add support to increase object ring partition power  https://review.openstack.org/33729709:26
*** bkopilov has joined #openstack-swift09:26
*** bkopilov_ has joined #openstack-swift09:27
*** jordanP has joined #openstack-swift09:29
cschwede_notmyname: ^^ Next patchset. It would be nice to merge it soon, but I don't want to rush it - we might want to merge it shortly *after* the release?09:32
*** psachin has joined #openstack-swift09:34
*** psachin has quit IRC09:36
*** psachin has joined #openstack-swift09:36
*** dmorita has joined #openstack-swift09:41
*** oshritf has joined #openstack-swift09:51
*** cbartz has joined #openstack-swift09:52
*** cbartz has quit IRC09:53
*** dmorita has quit IRC09:54
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873609:55
*** tesseract-RH has joined #openstack-swift09:56
*** psachin has quit IRC10:00
*** silor has joined #openstack-swift10:00
*** psachin has joined #openstack-swift10:01
*** tesseract has quit IRC10:04
*** dmorita has joined #openstack-swift10:10
*** silor1 has joined #openstack-swift10:10
*** silor has quit IRC10:12
*** silor1 is now known as silor10:12
*** dmorita has quit IRC10:14
*** mvk has quit IRC10:26
onovynotmyname: hi. i send few reviews for newton stable branch. can you look into it please?10:26
*** mvk has joined #openstack-swift10:52
*** tqtran has joined #openstack-swift11:07
*** sams-gleb has quit IRC11:11
*** tqtran has quit IRC11:11
*** sams-gleb has joined #openstack-swift11:11
*** kei_yama has quit IRC11:11
*** dmorita has joined #openstack-swift11:12
*** sams-gleb has quit IRC11:15
*** dmorita has quit IRC11:17
*** JimCheung has joined #openstack-swift11:35
*** dmorita has joined #openstack-swift11:39
*** JimCheung has quit IRC11:40
*** sams-gleb has joined #openstack-swift11:53
*** cbartz has joined #openstack-swift11:59
*** bkopilov has quit IRC12:43
*** bkopilov_ has quit IRC12:43
*** SkyRocknRoll has quit IRC13:03
*** cshastri has quit IRC13:04
*** catintheroof has joined #openstack-swift13:07
*** tqtran has joined #openstack-swift13:08
*** tqtran has quit IRC13:13
*** jamielennox is now known as jamielennox|away13:21
*** links has quit IRC13:28
*** mvk has quit IRC13:32
*** amoralej is now known as amoralej|lunch13:50
*** cbartz has quit IRC13:59
*** cbartz has joined #openstack-swift14:00
*** takashi has quit IRC14:03
*** klamath has joined #openstack-swift14:09
Dw_SnI am getting this error "proxy-server: Deferring reject downstream" I have S3 enabled on swift, the buckets are public so I am not using any auth..14:11
*** bkopilov has joined #openstack-swift14:24
*** bkopilov_ has joined #openstack-swift14:24
*** geaaru has quit IRC14:25
*** mvk has joined #openstack-swift14:26
*** links has joined #openstack-swift14:29
*** rsFF- has quit IRC14:45
*** dmorita has quit IRC14:46
*** bkopilov_ has quit IRC14:47
*** bkopilov has quit IRC14:47
*** caiobrentano has joined #openstack-swift14:48
*** rsFF has joined #openstack-swift14:48
*** amoralej|lunch is now known as amoralej14:49
*** neonpastor has joined #openstack-swift14:49
*** briancline has quit IRC14:52
*** briancline has joined #openstack-swift14:52
*** dmorita has joined #openstack-swift15:02
onovynotmyname: ah. jenkins for stable branch is broken. who will fix it? :)15:02
*** dmorita has quit IRC15:06
*** sams-gleb has quit IRC15:10
*** sams-gleb has joined #openstack-swift15:11
*** Dw_Sn has quit IRC15:14
*** bkopilov has joined #openstack-swift15:15
*** sams-gleb has quit IRC15:15
*** bkopilov_ has joined #openstack-swift15:15
*** sams-gleb has joined #openstack-swift15:28
*** dmorita has joined #openstack-swift15:34
*** _JZ_ has joined #openstack-swift15:38
*** dmorita has quit IRC15:39
*** tonanhngo has joined #openstack-swift15:43
*** links has quit IRC15:47
*** dmorita has joined #openstack-swift15:50
*** psachin has quit IRC15:52
*** gatuus has joined #openstack-swift15:53
*** mvk has quit IRC15:54
*** dmorita has quit IRC15:54
*** rcernin has quit IRC16:11
notmynamegood morning16:26
*** david-lyle has joined #openstack-swift16:26
notmynameonovy: I'll be getting on the bus in about 10 minutes. I'll check when I get to the office. thanks for bringing it up16:26
*** david-lyle_ has quit IRC16:29
*** dmorita has joined #openstack-swift16:36
*** chsc has joined #openstack-swift16:38
*** chsc has joined #openstack-swift16:38
*** joeljwright has quit IRC16:38
*** joeljwright has joined #openstack-swift16:38
*** ChanServ sets mode: +v joeljwright16:38
*** dmorita has quit IRC16:40
*** rcernin has joined #openstack-swift16:49
*** cbartz has quit IRC16:49
*** mvk has joined #openstack-swift16:55
*** tqtran has joined #openstack-swift16:57
*** catintheroof has quit IRC17:07
*** catintheroof has joined #openstack-swift17:07
*** dmorita has joined #openstack-swift17:07
*** dmorita has quit IRC17:12
notmynamegood morning (for realz)17:19
*** pcaruana has quit IRC17:31
*** rledisez has quit IRC17:34
*** JimCheung has joined #openstack-swift17:35
*** nicodemus_ has joined #openstack-swift17:39
nicodemus_hello17:43
nicodemus_I'm preparing to deploy a swift cluster, my datanodes have 20 2TB SATA disks, two 240GB SSD disks and two 16GB SATADOM modules17:44
nicodemus_I was wondering what would be the ideal disk layout for this datanode (obviously the OS will be installed in the SATADOM modules in RAID 1)17:45
*** gatuus has quit IRC17:47
*** gatuus has joined #openstack-swift17:48
*** JimCheung has quit IRC17:49
*** JimCheung has joined #openstack-swift17:50
*** dmorita has joined #openstack-swift17:53
claygheyoh!17:57
clayghappy valentines day17:57
gatuus^.^18:05
claygI want to point lp bug #1664474 at http://docs.openstack.org/developer/swift/overview_large_objects.html but I'm embarrassed it still mentions DLO first?18:14
openstackLaunchpad bug 1664474 in OpenStack Object Storage (swift) "Uploading large video data to swift storage" [Undecided,New] https://launchpad.net/bugs/166447418:14
claygI thought there was a change to fix that order?!18:14
*** dmorita has quit IRC18:15
*** Renich has joined #openstack-swift18:15
Renichhello18:16
claygidk, i couldn't find the change :'(18:16
*** oshritf has quit IRC18:16
RenichI am getting many of these: https://paste.fedoraproject.org/558239/09623014/18:17
Renichany ideas?18:17
claygio conention on the storage nodes18:18
claygyou can stop background daemons in the short term18:18
claygif the problem goes away you can try to tune those18:18
claygif not - you can try to tune your object-servers18:18
clayg... or both18:18
claygmore complex deployment topologies like servers-per-port or seperate-replication-networks are targeted at mitigating and isolating io conention18:19
*** tesseract-RH has quit IRC18:26
notmynamenicodemus_: nothing fancy. put the HDDs into the object ring, but the SSDs into the account and container rings, and put the OS on the fast flash (like you said).18:27
*** aluria has joined #openstack-swift18:27
*** klrmn has joined #openstack-swift18:29
*** Renich has quit IRC18:30
*** Renich has joined #openstack-swift18:30
*** dmorita has joined #openstack-swift18:31
*** dmorita has quit IRC18:35
*** jordanP has quit IRC18:38
aluriahi o/ -- I was looking for info on account-replicator.failures counter, but I can't find it in http://docs.openstack.org/developer/swift/admin_guide.html#recon-replication18:41
*** DuncanT has quit IRC18:41
aluriadoes this counter only get reset when restarting the swift-account-replicator process?18:41
aluriahow can I find the reason of those failures?18:43
notmynamealuria: it gets reset on every cycle18:46
alurianotmyname: by cycle, you mean everytime replication finishes?18:47
notmynamealuria: yep. normally you run the replicators in a "forever" mode (technically, there's a "once" mode and this is the not-once mode, ie forever)18:48
notmynamealuria: ...and it will process data. wait. and process again18:48
notmynamealuria: stats a reset at the start of each process cycle18:48
alurianotmyname: I see -- thanks for the clarification18:48
notmynamealuria: you can see it at https://github.com/openstack/swift/blob/master/swift/common/db_replicator.py#L628 inside of run_once(). and the run_forever() method just repeatedly calls run_once()18:49
nicodemus_notmyname, thanks!18:50
notmynamealuria: that code is shared by both the account and the container replicator18:50
Renichclayg: was that for me?18:50
alurianotmyname: ack -- and apart from looking the return codes for the http methods, is there any other source of info on the reason of a failure? ie. I see that localhost:6000/recon/object shows failures per storage18:51
*** tnovacik has joined #openstack-swift18:57
*** dmorita has joined #openstack-swift19:17
*** ChubYann has joined #openstack-swift19:18
*** zaitcev has joined #openstack-swift19:19
*** ChanServ sets mode: +v zaitcev19:19
*** dmorita has quit IRC19:22
*** amoralej is now known as amoralej|off19:23
*** _JZ_ has quit IRC19:28
*** Renich has quit IRC20:01
*** dmorita has joined #openstack-swift20:04
*** dmorita has quit IRC20:09
claygRenich: yes, good luck20:14
*** jamielennox|away is now known as jamielennox20:17
*** openstackgerrit has quit IRC20:18
*** CowboyPride has quit IRC20:22
*** abqkawi1000 has joined #openstack-swift20:37
*** JimCheung has quit IRC20:41
*** JimCheung has joined #openstack-swift20:45
*** dmorita has joined #openstack-swift20:51
abqkawi1000Hoping someone can point me in the right direction.  I am unable to get my swift-proxy to cooperate with keystone.  I have double checked that the swift user has admin on the service tenant with: openstack role list --project service --user swift.20:51
abqkawi1000My output from client:swift -V 2 -A http://10.203.2.1:5000/v2.0 -U admin:myadminname -K myadminpass stat --debug DEBUG:keystoneclient.auth.identity.v2:Making authentication request to http://10.203.2.1:5000/v2.0/tokens INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 10.203.2.1 DEBUG:requests.packages.urllib3.connectionpool:"POST /v2.0/tokens HTTP/1.1" 200 3689 INFO:requests.packages.urll20:52
abqkawi1000Ack--- ok pate buffer20:52
abqkawi1000From my client --swift -V 2 -A http://10.203.2.1:5000/v2.0 -U admin:myadminname -K myadminpass stat --debug DEBUG:keystoneclient.auth.identity.v2:Making authentication request to http://10.203.2.1:5000/v2.0/tokens INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 10.203.2.1 DEBUG:requests.packages.urllib3.connectionpool:"POST /v2.0/tokens HTTP/1.1" 200 368920:53
abqkawi1000INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 10.203.0.101 DEBUG:requests.packages.urllib3.connectionpool:"HEAD /v1/AUTH_175ea570020a4fe8a8bd1ed2f7070d84 HTTP/1.1" 503 0 INFO:swiftclient:REQ: curl -i http://10.203.0.101:8080/v1/AUTH_175ea570020a4fe8a8bd1ed2f7070d84 -I -H "X-Auth-Token: gAAAAABYo2quDtDS8GTAIKoziw5--ujlbdSXFs_sFVmSKwSPzsy1ixSARZ2HV4QZ0lMVg6UG1z8ZjlIt2_ac1GDrq3an4H7cY_NLb20:53
patchbotError: No closing quotation20:53
abqkawi1000Then20:53
abqkawi1000INFO:swiftclient:RESP STATUS: 503 Service Unavailable INFO:swiftclient:RESP HEADERS: {u'Date': u'Tue, 14 Feb 2017 20:38:06 GMT', u'Content-Length': u'0', u'Content-Type': u'text/html; charset=UTF-8', u'X-Trans-Id': u'txb205b4ec511e48f18eb1e-0058a36aae'}20:53
abqkawi1000EBUG:requests.packages.urllib3.connectionpool:"HEAD /v1/AUTH_175ea570020a4fe8a8bd1ed2f7070d84 HTTP/1.1" 503 0 INFO:swiftclient:REQ: curl -i http://10.203.0.101:8080/v1/AUTH_175ea570020a4fe8a8bd1ed2f7070d84 -I -H "X-Auth-Token: gAAAAABYo2quDtDS8GTAIKoziw5--ujlbdSXFs_sFVmSKwSPzsy1ixSARZ2HV4QZ0lMVg6UG1z8ZjlIt2_ac1GDrq3an4H7cY_NLbBuwlCi86wxs9u0qhrtY9Kf_JAYcZP6_k7iNzAV276TzYGA0BnuSPL1a3h4vfA"20:53
abqkawi1000From proxy server20:54
abqkawi1000Feb 14 13:35:44 cee-cldswift proxy-server: Rejecting request Feb 14 13:35:44 cee-cldswift proxy-server: Identity server rejected authorization Feb 14 13:35:44 cee-cldswift proxy-server: Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}20:54
abqkawi1000From controller20:54
abqkawi10002017-02-14 20:38:07.103 21283 INFO keystone.common.wsgi [req-07f2cdeb-6109-4c6d-8c5b-7d65df45b68a - - - - -] POST http://10.203.2.1:35357/v3/auth/tokens 2017-02-14 20:38:07.116 21283 WARNING keystone.common.wsgi [req-07f2cdeb-6109-4c6d-8c5b-7d65df45b68a - - - - -] Authorization failed. The request you have made requires authentication. from 10.203.2.920:54
abqkawi10002017-02-14 20:38:07.120 21283 INFO eventlet.wsgi.server [req-07f2cdeb-6109-4c6d-8c5b-7d65df45b68a - - - - -] 10.203.0.101,10.203.2.9 - - [14/Feb/2017 20:38:07] "POST /v3/auth/tokens HTTP/1.1" 401 419 0.020417 2017-02-14 20:38:09.155 21279 DEBUG keystone.middleware.auth [req-28fb8ba2-3b99-4e68-a57a-9c3038f771f4 - - - - -] There is either no auth token in the request or the certificate issuer is not trusted.20:55
abqkawi1000No auth context will be set. _build_auth_context /usr/lib/python2.7/dist-packages/keystone/middleware/auth.py:7120:55
*** dmorita has quit IRC20:55
*** caiobrentano_ has joined #openstack-swift21:02
jrichliabqkawi1000: I am not very experienced with keystone, but I'd say either your token was rejected by keystone, or swift has no authority to talk to keystone.21:03
*** caiobrentano has quit IRC21:04
abqkawi1000jrichli:  Yes that is exactly what it feels like to me21:04
jrichliabqkawi1000: you can use http://paste.openstack.org/ when you want to share some logs such as this, btw21:04
abqkawi1000jrichli: ah thanks for that log paste url21:04
jrichlinp21:05
abqkawi1000so how do I make keystone trust my swift proxy box?  I setup user swift that is admin for the service project21:05
abqkawi1000jrichli:  my proxy-server.conf users the swift user and password in authtoken middleware21:07
jrichliabqkawi1000: since i am not very experienced with keystone, I am going to first point you here: http://docs.openstack.org/developer/swift/overview_auth.html#troubleshooting-tips-for-keystoneauth-deployment21:07
jrichliabqkawi1000: but i will be poking around myself to see if i can help more21:07
abqkawi1000jrichli: terrific!  I will be reading myself.  Thanks a ton!21:08
zaitcevMan, now that portante is no more, coverage keeps slipping.21:08
zaitcevOr, actually, it's very good in numbers - 93%, but also a huge number of small gaps.21:09
mattoliverauMorning21:11
*** abqkawi1000 has quit IRC21:12
*** abqkawi1000 has joined #openstack-swift21:13
*** tnovacik has quit IRC21:15
notmynamehello mattoliverau21:15
*** abqkawi1000 has quit IRC21:15
*** abqkawi1000 has joined #openstack-swift21:16
mattoliveraunotmyname: hey man, how was the field trip yesterday?21:16
jrichliabqkawi1000: I think swift has to be setup as a 'service' in keystone rather than a user.  at least, that is what i have seen done21:16
notmynamemattoliverau: yesterday was good. thanks21:16
abqkawi1000rjichli:  correct.  The swift service ID shows up with a openstack service list21:17
abqkawi1000jrichli: my endpoints are setup pointing to my swift proxy21:18
*** silor has quit IRC21:18
abqkawi1000jrichli:  This is what puzzles me  "There is either no auth token in the request or the certificate issuer is not trusted. No auth context will be set."21:20
abqkawi1000jrlichli:  I am hitting http so I cannot imagine why a cert is an issue.  Why a token would have been stripped boggles me.  From my proxy it is clear a /v1/AUTH_***************  was sent to keystone21:21
tdasilvazaitcev: maybe we can convince portante to come back ;)21:27
notmynametdasilva: I think you'd be better able to do that than anyone else in here ;-)21:27
*** gatuus has quit IRC21:27
tdasilvanotmyname: believe me, i've tried...21:28
notmynameheh. believe me, me too ;-)21:29
tdasilvaheh21:30
*** dmorita has joined #openstack-swift21:32
notmynamein another episode of "FYI in OpenStack..."21:34
notmynamethe TC decided, in their meeting that ended 30 min ago, that there is now a "only infra-approved bots are allowed on Gerrit"21:34
notmynamewhen I asked about more detail about how that would be addressed..21:35
*** Jeffrey4l_ has quit IRC21:35
notmynameI was told "it's done not by active policing in any automated fashion - but by referring to it as an agreement when a misbehaving bot surfaces"21:35
*** Jeffrey4l_ has joined #openstack-swift21:35
notmynameso there's that. if you use a bot to post on gerrit, I guess it's not allowed any more21:35
*** dmorita has quit IRC21:36
tdasilvadoes that mean clayg can't do reviews anymore?21:39
*** rcernin has quit IRC21:44
notmynamethat's hilarious21:44
jrichlitdasilva: lol21:45
*** dmorita has joined #openstack-swift21:46
*** dmorita has quit IRC21:53
mattoliveraulol21:59
*** dmorita has joined #openstack-swift22:09
*** dmorita has quit IRC22:13
*** gatuus has joined #openstack-swift22:23
pdardeauis the eviction of object data from page cache controlled by "keep_cache_size" in diskfile.py?22:24
pdardeau(default of 5MB)?22:25
*** dmorita has joined #openstack-swift22:25
notmynamepdardeau: yes. but also the other config var in there. keep_cache_private = T|F or something like that22:27
notmynameIIRC it effectively comes down to publicly accessible content that is small is kept in the cache22:27
notmynamebut also, IIRC it's a little confusing at first glance because it's phrased negatively22:28
pdardeaunotmyname: thx. this one? keep_cache: should resulting reads be kept in the buffer cache22:29
notmynameyeah that sounds right22:29
notmynamepdardeau: in practice, I'm not sure it actually helps anything. and I'm pretty sure it's never actually been measured. and I worry that it might actually hurt things in some cases22:31
notmynameI'm much *much* more interested in the OVH work around small file optimization instead of this22:31
*** tonanhngo_ has joined #openstack-swift22:34
*** sanchitmalhotra1 has joined #openstack-swift22:34
*** klrmn1 has joined #openstack-swift22:36
notmynameI just got an email with logistics info about the PTG. check your email and you'll likely have one too (sent individually, so no link)22:38
*** tonyb_ has joined #openstack-swift22:38
*** kozhukalov_ has joined #openstack-swift22:40
*** dims has joined #openstack-swift22:41
*** mtreinish_ has joined #openstack-swift22:41
notmynamechangelog entries: "some pretty core parts of swift that you just assumed were working now work even better."22:41
*** klrmn has quit IRC22:42
*** tonanhngo has quit IRC22:42
*** dims_ has quit IRC22:42
*** mtreinish has quit IRC22:42
*** sanchitmalhotra has quit IRC22:42
*** kozhukalov has quit IRC22:42
*** tonyb has quit IRC22:42
*** wasmum has quit IRC22:42
*** jamielennox has quit IRC22:42
*** fungi has quit IRC22:42
*** mtreinish_ is now known as mtreinish22:42
*** sanchitmalhotra1 is now known as sanchitmalhotra22:43
jrichlinotmyname: sounds good!  better than i could have come up with22:44
*** kozhukalov_ is now known as kozhukalov22:44
notmynamemostly I just consolidate it down to "Swift 1.13.0: the best one yet, please upgrade"22:44
notmynameoh. yeah. 1.13.0 was the best one at that time.22:45
notmynameturns out 2.13.0 is the best one, now22:45
*** tonanhngo_ has quit IRC22:46
*** zigo has quit IRC22:46
*** chlong has quit IRC22:46
*** early has quit IRC22:46
*** swifterdarrell has quit IRC22:46
*** mmotiani has quit IRC22:46
*** AbyssOne has quit IRC22:46
*** CrackerJackMack has quit IRC22:46
*** mcarden has quit IRC22:46
*** darrenc has quit IRC22:46
*** mattoliverau has quit IRC22:46
*** jarbod_ has quit IRC22:46
*** cppforlife_ has quit IRC22:46
*** dcourtoi has quit IRC22:46
*** tonyb_ is now known as tonyb22:46
*** swifterdarrell has joined #openstack-swift22:47
*** ChanServ sets mode: +v swifterdarrell22:47
*** early has joined #openstack-swift22:48
*** acorwin has quit IRC22:48
*** fungi has joined #openstack-swift22:50
*** zigo has joined #openstack-swift22:52
*** chlong has joined #openstack-swift22:52
*** AbyssOne has joined #openstack-swift22:52
*** mcarden has joined #openstack-swift22:52
*** darrenc has joined #openstack-swift22:52
*** mattoliverau has joined #openstack-swift22:52
*** jarbod_ has joined #openstack-swift22:52
*** dcourtoi has joined #openstack-swift22:52
*** adams.freenode.net sets mode: +v mattoliverau22:52
*** acorwin has joined #openstack-swift22:52
*** tonanhngo has joined #openstack-swift22:52
*** sams-gleb has quit IRC22:53
*** cppforlife_ has joined #openstack-swift22:53
*** zigo is now known as Guest2705722:54
*** dmorita has quit IRC23:00
*** abqkawi1000_ has joined #openstack-swift23:01
*** CrackerJackMack has joined #openstack-swift23:01
*** abqkawi1000 has quit IRC23:01
*** dmorita has joined #openstack-swift23:03
*** nicodemus_ has quit IRC23:13
MooingLemurWhat could cause the condition that while all devices have weight 0 and no partitions assigned, but the node has 23 container dbs and container-replicator doesn't remove them?23:16
MooingLemurhttps://bpaste.net/show/3702d8f1e36d23:17
MooingLemur2.7.0 from centos-openstack-mitaka23:18
*** dja has joined #openstack-swift23:28
*** kei_yama has joined #openstack-swift23:30
MooingLemur"attempted: 23" attempted to do what?  I don't even see any connect()s when stracing :)23:35
notmynamedude. it tried soooooo hard to do it. you don't even know. not once. not twice. 23 TIMES! that's pretty hard work. ;-)23:37
*** chsc has quit IRC23:38
notmynamehmm...looking at the code to refresh my memory on that23:39
notmynamelooks like maybe there's 23 DBs that are in the deleted state23:39
notmynamespecifically deleted but not yet past the reclaim age23:41
notmynameat least that seems like a code path that would increment the attemted count but not do anything else23:42
MooingLemuroh, maybe.. I haven't tried running sql on those yet.23:42
notmynamecan you check the disks to see if there are .db files there? how many? what happens if you do swift-container-info on them?23:42
MooingLemuroh, I could do that too23:42
MooingLemurthere are *.db files23:42
notmynameit would be really cool if there are 23 .db files ;-)23:43
*** dmorita has quit IRC23:44
MooingLemurhere's one https://bpaste.net/show/c25b4dd072ed23:44
MooingLemurit's a 2.5GB .db file :)23:45
MooingLemur-[/srv/node:#]- find . -name \*.db | wc -l23:45
MooingLemur2323:45
*** dmorita has joined #openstack-swift23:46
notmynamenice!23:46
MooingLemurif it's supposed to be deleted, I'm satisfied, and I'll be happy to proceed knowing that I'm not going to lose anything real by wiping this data23:46
*** dmorita has quit IRC23:47
notmynameyep. so that DB is deleted (see the delete timestamp as the latest)23:47
notmynamethe size is just from the fact that you could have had a lot of tombstone rows in it  (and we never vacuum the DBs)23:47
MooingLemuryeah23:48
notmynameso as long as you have a healthy cluster and you've had a container replication cycle complete successfully, you're totally ok by yanking the drive23:48
MooingLemurI'm just wondering why it's been there since May of last year though (May 13 is the mtime for that db)23:48
MooingLemurcould it be because the account doesn't exist anymore?23:48
notmynameyou said this is on a drive with zero weight?23:49
MooingLemuryeah23:49
notmynamecould be the fact the account doesn't exist23:49
notmynamecould be the fact it's zero weight23:49
notmynamethat sounds like the sort of corner case we'd have in swift ;-)23:49
MooingLemurit's zero weight as of this week.  It drained all the dbs except for these 2323:49
notmyname(read: "bug")23:49
notmynamesince it's just 23 of them, a quick by-hand check for the delete timestamp would be what you need to check. and a check in the logs that replication cycle is good (but I think that is shown in the first pastebin you had)23:50
MooingLemuryeah, I'm satisfied.  Thanks for the explanation :D23:51
notmynameMooingLemur: might be worth opening a bug in LP about it. "empty container db on zero-weight drive doesn't get deleted"23:51
*** sams-gleb has joined #openstack-swift23:54
*** wasmum has joined #openstack-swift23:57
*** dmorita has joined #openstack-swift23:58
*** sams-gleb has quit IRC23:58

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