Thursday, 2018-12-27

*** mikecmpbll has quit IRC00:37
*** psachin has joined #openstack-swift03:03
viks__notmyname: I enabled it now, but even though my admin is a reseller admin, i get `<html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>` for account delete request. Is there any other settings i need to change?05:13
viks__notmyname:  It seems it's working and problem at my end..06:15
viks__the above error is because i used single quote for -> 'X-Auth-Token: $TOKEN',  changing it to double quotes resolved this error.06:52
*** e0ne has joined #openstack-swift06:53
*** e0ne has quit IRC07:55
*** gkadam has joined #openstack-swift08:40
*** e0ne has joined #openstack-swift09:04
*** e0ne has quit IRC09:05
*** e0ne has joined #openstack-swift09:25
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Enable to configure object-expirer in object-server.conf  https://review.openstack.org/60195009:52
*** mikecmpbll has joined #openstack-swift10:27
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Enable to configure object-expirer in object-server.conf  https://review.openstack.org/60195010:41
*** mikecmpbll has quit IRC11:04
DHEviks__: shells when using single-quotes and $dollarsigns won't expand the variable.11:25
*** gkadam_ has joined #openstack-swift11:42
*** gkadam has quit IRC11:44
*** e0ne has quit IRC11:46
*** e0ne has joined #openstack-swift11:47
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Add object-expirer new mode to execute tasks from general task queue  https://review.openstack.org/51738911:47
*** gkadam_ has quit IRC11:48
*** gkadam has joined #openstack-swift11:59
*** csmart has left #openstack-swift12:04
*** csmart has joined #openstack-swift12:04
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Add object-expirer new mode to execute tasks from general task queue  https://review.openstack.org/51738912:06
viks__DHE:  Thanks.. Now it works..12:11
*** e0ne has quit IRC12:34
*** gkadam_ has joined #openstack-swift12:43
*** gkadam has quit IRC12:45
*** psachin has quit IRC13:21
*** viks__ has quit IRC14:15
*** gkadam_ has quit IRC16:14
*** jdewald42 has joined #openstack-swift16:51
jdewald42Hi there, I recently discovered that one of our proxy and container server nodes has been upgraded to 2.19 whereas our other servers are running 2.7. We actually want everything to run 2.7 and wanted to confirm whether it is possible to downgrade that one server. It is not an acting in an object server capacity.16:56
jdewald42(ideally we want to upgrade everything, but that's for another day)16:56
DHEI mean.. if in doubt, just rm -rf the container storage space while the service is offline, downgrade, and let replication deal with it16:57
jdewald42nice17:03
jdewald42Is it safe to attempt the downgrade with the containers as-is and remove them if it goes sideways? I wouldn't expect it to impact any other servers17:07
DHEI don't know either way. My gut says it would be okay, but I have no standing either way to make such a claim.17:17
DHELetting replication deal with it just seems safest. Treat it like a hard drive failure17:18
jdewald42Seems reasonable, thanks!17:28
timburkejdewald42: i have no reason to think that a downgrade would be problematic, provided you haven't tried to use any new features that 2.19 would enable (like container sharding)17:36
timburkesome of those container may have an extra table but it shouldn't impact the old code17:36
jdewald42Nice, correct we have not enabled sharding yet17:38
timburkesince replication works by rsync when there's a large diff, we have to be fairly careful that not only can new servers read old dbs, but also that new dbs can be used by old servers (or we have to shut down replication very early on, such as what we do if a container *does* have sharding enabled)17:38
timburkeso, if a downgrade *does* cause problems, (1) i'd be interested to hear, just for my own knowledge and (2) you'll probably be safest to nuke the db and let replication fix it17:40
jdewald42I see, so you're thinking an in-place downgrade *should* be safe17:42
timburkepretty sure. but it's also something that we haven't tested much17:42
timburkeas a general rule, we like upgrades more ;-)17:42
jdewald42totally understandable17:43
*** e0ne has joined #openstack-swift17:45
*** e0ne has quit IRC17:59
openstackgerritTim Burke proposed openstack/swift master: py3: Port the acl, account_quotas, cname_lookup, container_sync  https://review.openstack.org/61807718:56
openstackgerritMerged openstack/swift master: py3: Port the acl, account_quotas, cname_lookup, container_sync  https://review.openstack.org/61807720:03
*** jdewald42 has quit IRC20:05
*** mikecmpbll has joined #openstack-swift22:14
openstackgerritTim Burke proposed openstack/swift master: Run ceph-s3-tests job less  https://review.openstack.org/62757222:36
timburke22:53
openstackgerritTim Burke proposed openstack/swift master: Address some review comments  https://review.openstack.org/62757423:02
openstackgerritTim Burke proposed openstack/swift master: Move KMIP conf validation out of _get_root_secret  https://review.openstack.org/58967323:26

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