Thursday, 2023-09-21

opendevreviewJianjian Huo proposed openstack/swift master: Container-server: add container namespaces GET  https://review.opendev.org/c/openstack/swift/+/89047004:37
opendevreviewJianjian Huo proposed openstack/swift master: WIP: Proxy: Use shard-format for auto cont GETs and updating  https://review.opendev.org/c/openstack/swift/+/89560205:06
opendevreviewAlistair Coles proposed openstack/swift master: proxy-server: add replicated GET path tests  https://review.opendev.org/c/openstack/swift/+/89580213:22
opendevreviewAlistair Coles proposed openstack/swift master: proxy-server: de-duplicate _get_next_response_part method  https://review.opendev.org/c/openstack/swift/+/89091913:22
opendevreviewAlistair Coles proposed openstack/swift master: proxy-server: init GetterBase resource_type with server type  https://review.opendev.org/c/openstack/swift/+/89609813:22
opendevreviewAlistair Coles proposed openstack/swift master: proxy-server: de-duplicate _get_next_response_part method  https://review.opendev.org/c/openstack/swift/+/89091915:16
opendevreviewAlistair Coles proposed openstack/swift master: proxy-server: init GetterBase resource_type with server type  https://review.opendev.org/c/openstack/swift/+/89609815:16
-opendevstatus- NOTICE: The lists.openinfra.dev and lists.starlingx.io sites will be offline briefly for migration to a new server15:32
acolestimburke: sorry I missed them meeting again - hopefully I'll be more regular once the clocks change and it shifts a little earlier15:50
opendevreviewASHWIN A NAIR proposed openstack/swift master: s3api: Support GET/HEAD request with PartNumber  https://review.opendev.org/c/openstack/swift/+/89458016:47
opendevreviewTim Burke proposed openstack/swift master: proxy: Emit counter metrics when a node is skipped due to error-limiting  https://review.opendev.org/c/openstack/swift/+/89597617:00
klamathHas anyone hit this error before? 17:17
klamathSep 21 17:14:43 node container-sharder: Unhandled exception while dumping progress for /srv/node/d455/containers/53872/a60/d2702ecdf65a5632477eb0fc60402a60/DB.db: max() arg is an empty sequence: #012Traceback (most recent call last):#012  File "/usr/local/openstack/lib/python3.6/site-packages/swift/container/sharder.py", line 1905, in _one_shard_cycle#012    self._record_sharding_progress(broker, node, error)#012  File "/usr/local/open17:17
klamathstack/lib/python3.6/site-packages/swift/container/sharder.py", line 657, in _record_sharding_progress#012    CleavingContext.load_all(broker)]) or None#012ValueError: max() arg is an empty sequence17:17
opendevreviewkim woo seok proposed openstack/swift master: Add unittest of swift-recon-cron  https://review.opendev.org/c/openstack/swift/+/89615218:00
opendevreviewkim woo seok proposed openstack/swift master: Add unittest of swift-recon-cron  https://review.opendev.org/c/openstack/swift/+/89615218:03
opendevreviewASHWIN A NAIR proposed openstack/swift master: s3api: Support GET/HEAD request with PartNumber  https://review.opendev.org/c/openstack/swift/+/89458018:06
timburkeklamath, looks like it should be fixed in 2.28.0 (and later), by https://github.com/openstack/swift/commit/e53c82cd32e99513dba00a28c29953cadcc9bd8718:28
timburkeapparently i wrote the fix, but i really don't remember it :P18:30
klamath@timburke is this a soft error?  we are in the middle of a deploy and hit this error on the first node18:30
timburkeyeah, fairly certain -- we've got some very broad exception handling around dumping progress, and it goes back to when we first implemented sharding: https://github.com/openstack/swift/blob/2.32.0/swift/container/sharder.py#L2505-L250918:33
klamathok, we caught this error and started to deep dive on the error, if we can hold off on bumping the version from wallaby to xena id like to18:37
opendevreviewTim Burke proposed openstack/swift stable/wallaby: sharder: Prevent ValueError when no cleaving contexts  https://review.opendev.org/c/openstack/swift/+/89611718:40
timburkelooks like the patch should apply cleanly to wallaby, for what it's worth. hit a conflict trying to cherry-pick to victoria, but i expect it won't be *so* bad to resolve18:42
klamathDo you know how long this will take to merge? 18:43
timburkeshould merge later today. how do you usually get your releases?18:53
klamathwe have a pipeline that grabs master18:54
klamathThanks for backporting this, been tearing my hair out the last hour doing a diff between our swift versions 18:56
timburkehappy to help! yeah, looks like the _record_sharding_progress function was subtly broken when it was introduced in 2.27.0: https://github.com/openstack/swift/commit/1de98348167f9923710d1a6d634ef6d8008eea5d19:01
timburkewhich would also explain the merge conflict trying to go back before wallaby19:01
opendevreviewClay Gerrard proposed openstack/swift master: slo: refactor GET/HEAD response handling  https://review.opendev.org/c/openstack/swift/+/89357820:46
opendevreviewJianjian Huo proposed openstack/swift master: WIP: Proxy: Use shard-format for auto cont GETs and updating  https://review.opendev.org/c/openstack/swift/+/89560221:14
opendevreviewTim Burke proposed openstack/swift master: Drop py2 support  https://review.opendev.org/c/openstack/swift/+/85359023:29

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