Friday, 2017-10-06

*** _CrustY has quit IRC01:26
*** _CrustY has joined #swift301:26
*** onovy has quit IRC02:08
*** onovy has joined #swift302:10
*** _CrustY has quit IRC06:00
*** _CrustY has joined #swift306:03
*** [-mugatu-] has quit IRC06:45
*** [-mugatu-] has joined #swift306:48
*** [-mugatu-] has quit IRC07:42
*** [-mugatu-] has joined #swift314:36
*** tgk has joined #swift314:45
tgkHi. Is this a good place to get help troubleshooting a swift3 install?14:54
*** chsc has joined #swift315:19
timburketgk: yeah! what sort of issues are you running into?15:43
tgkThanks timburke15:43
tgkI've been trying to setup swift3 in my openstack/swift servers on CentOS 7 and got some errors that I need some help troubleshooting. My EC2 key authentication goes through ok according to keystone logs, but all my requests using s3curl end with Internal Error - Invalid Bucket - Could not parse the specified URI. I'm running s3curl from the same box that runs swift-proxy, trying to retrieve http://127.0.0.1:8080/15:43
tgkI'm running Pike btw15:44
timburkeoh good; i know there was an issue with ocata keystone15:45
tgkyeah, that was the main reason I upgraded to pike15:45
tgkand the old keystone errors from ocata when trying to authenticate with EC2 keys are no longer there, so that's good15:46
timburkewhat's the name of the bucket you're trying to hit? we try to enforce the same naming restrictions as AWS, but they aren't consistent -- you might want to try switching dns_compliant_bucket_names to False in the swift3 config15:47
tgkI created a bucket called "test" to keep it simple15:48
tgkLet me try the dns_compliant_bucket_names option... that's in the proxy-server.conf, right?15:48
timburkeyup. but "test" should be fine on both... i wonder if s3curl's trying to use virtual-host style requests? try throwing a --verbose on there to see what gets plumbed down to curl15:49
timburkei'm thinking it might be trying to contact http://test.127.0.0.1:8080/15:50
timburkewhich won't make sense :P but you could add an entry for test.localhost to your /etc/hosts and try that way15:51
timburkethough... no... it usually takes the full url, doesn't it? let me dig around a little...15:52
tgkI pasted some logs and output here: https://pastebin.com/ehcCQUKu15:54
timburkewell...that's a special kind of stupid on our part. sorry there15:57
timburkelooks like it's coming out of either https://github.com/openstack/swift3/blob/master/swift3/s3_token_middleware.py#L202-L204 or https://github.com/openstack/swift3/blob/master/swift3/s3_token_middleware.py#L321-L32515:57
timburkeyou said that keystone seemed happy, though? makes me think it's the latter, in which case i wonder what the reply looks like from keystone...15:58
tgkyes, I see a 200 reply in keystone logs on authentication, and it's something else when my keys are incorrect15:58
timburketry turning on debug logging for s3token -- you don't want to run with that in production because of https://github.com/openstack/swift3/blob/master/swift3/s3_token_middleware.py#L294-L295 but it's really handy to see the complete keystone response16:00
tgkok. How do I enable debug? Under the [filter:swift3] section of proxy-server.conf?16:02
tgksorry, I meant, filter:s3token16:02
timburkeyep; log_level = DEBUG iirc16:06
timburke...which i should really call out in the sample config...16:07
tgkI tried both "log_level = DEBUG" and "set log_level = DEBUG" under [filter:s3token], but the output in /var/log/swift/swift.log seems to be the same when trying s3curl16:12
timburkemaybe check /var/log/syslog? i really ought to invest some time into learning more about how to configure swift's logging...16:16
timburkefwiw, i typically set log_level = DEBUG in the [DEFAULT] section for development, then get everything out of /var/log/syslog16:17
timburkeand i don't have any other logging config to speak of16:18
tgksounds simpler that way. I'll give it a try.16:18
timburkebiggest downside is that it's also noisier :-)16:19
tgkah, ok, I got some logs... let me paste them16:21
tgkhttps://pastebin.com/K9eLN7kE16:23
tgkrelevant part is most likely:16:24
tgk7.Oct  6 12:20:53 openstack-host01 proxy-server: Error on keystone reply: 20016:24
tgkbut I only see a long output with all the endpoints... I don't see anything pointing at an error16:27
timburkewhat version of swift3 is this? is it a tagged release, or coming off master?16:29
tgkopenstack-swift-plugin-swift3-1.11.0-1.el7.noarch16:29
tgkout of the official repo16:30
timburkei really need to go review https://review.openstack.org/#/c/504479/ so we actually have a release that includes https://github.com/openstack/swift3/commit/807ed38 :-(16:30
patchbotpatch 504479 - swift3 - Change log updates for version 1.1216:30
tgkIs 1.12 in any public repo?16:33
timburkeno, it hasn't been tagged yet. that's part of the problem16:34
tgkI guess I'll give it another try once that version is released :)16:34
timburkefwiw, we work hard to keep tip of master stable -- the company i work for often releases from master (sometimes even with some in-review patches) to get fixes that haven't been officially released yet16:35
tgkI'm not testing in prod, so if there's a release candidate with the patch, I could try it too16:38
tgkbut I think the version I'm running matches the latest in github16:40
timburkeif it were me, i'd just do a `pip install git+https://github.com/openstack/swift3.git` ;-)16:40
tgkI'll give it a shot. I really appreciate you taking the time to look at this with me.16:43
tgkThanks!!16:43
timburkesure! thanks for prodding me to look at swift3 more today :-) i've been owing kota_ some reviews/patchsets16:45
*** openstack has joined #swift317:09
*** ChanServ sets mode: +o openstack17:09
*** tgk has quit IRC21:37
*** chsc has quit IRC23:21
*** chsc has joined #swift323:41
*** chsc has joined #swift323:41
*** chsc has quit IRC23:45

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