Sunday, 2020-12-27

*** prometheanfire has quit IRC00:26
*** jrosser has quit IRC00:31
*** jrosser has joined #openstack-swift00:31
*** prometheanfire has joined #openstack-swift00:51
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-swift05:33
*** m75abrams has joined #openstack-swift07:08
*** iokiwi has joined #openstack-swift09:08
iokiwihey where should I look to figure out why I am getting http 412 when creating object (with X-If-None-Matches; "*") after deleting object with same name.09:10
iokiwiswift api is behaving as if the recently delete object still exists i.e it hasn't been cleaned up fully yet. But I am not sure where I should look to inspect the state of the deleted object09:11
*** Jeffrey4l has quit IRC14:04
*** Jeffrey4l has joined #openstack-swift14:04
*** m75abrams has quit IRC14:13
DHEas a user, in some ways it isn't. there is a "tombstone" object left behind so that replication can replicate the delete event15:01
*** timburke has joined #openstack-swift21:28
*** ChanServ sets mode: +v timburke21:28
iokiwiokay cheers. I have admin access to the openstack/swift cluster just not sure where to start (other than skimming the source code) Is that behaviour specified or documented anywhere? The API ref for swift does not even specify that 412 is a possible return code22:02
timburkeiokiwi, i'd use swift-get-nodes to find the disks on which we'd expect to find the object, then start poking around and seeing how they respond to curl22:07
timburkesyntax looks like `swift-get-nodes <ring file> <acct>/<cont>/<obj>`, and it'll even include sample curl commands for doing HEADs22:07
iokiwinice thanks very much timburke.22:21
*** rcernin has joined #openstack-swift22:31

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!