)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"8611d3f92bd15400ca5c8f1d8b3184655053b6c9","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4180a0c0_230d4407","updated":"2026-11-16 18:44:02.000000000","message":"Instead of removing the volume mount, which would remove support for override, lets use the same logic as cinder-volume: https://opendev.org/openstack/openstack-helm/src/branch/master/cinder/templates/statefulset-volume.yaml#L264-L273","commit_id":"3b302732fd443e738aa8adef7f2ea2947bce7268"},{"author":{"_account_id":3009,"name":"Vladimir Kozhukalov","email":"kozhukalov@gmail.com","username":"kozhukalov"},"change_message_id":"6341b50d8ee6f05cef3c504a0b0b7e35657a476c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fc231c89_624ae083","updated":"2026-11-16 18:46:23.000000000","message":"Thanks for the fix. It fixes the issue introduced by the volume.filters removal. But the idea of the change was to rely on the default filters provided in the image but still have the ability to add/override them. Could you please make the mount conditional instead of just removing it? I mean it could be implemented the same way as it is implemented for the cinder volume deployment template?","commit_id":"3b302732fd443e738aa8adef7f2ea2947bce7268"},{"author":{"_account_id":39633,"name":"Mark McCormick","display_name":"Mark","email":"mark.mccormick@chainguard.dev","username":"markm22"},"change_message_id":"e200769e6a494a776a91280b5a14f6cac9a8a668","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c89176a7_7d246d5c","in_reply_to":"4180a0c0_230d4407","updated":"2026-11-18 23:35:55.000000000","message":"Done in PS2. The backup pod now uses the same `conf.rootwrap_filters` loop as the volume pod and mounts the entries that list `backup` in `pods`. With the default empty `rootwrap_filters` it mounts nothing, so the start failure is still fixed.\n\nOne behaviour change to flag: the old template mounted the `volume` entry into the backup pod whatever its `pods` said. I keyed the loop on `backup` so the two pods can be targeted separately, which means an existing `volume` entry with `pods: [volume]` is no longer mounted in the backup pod. There is a `Changelog: changed` note for it. If you would rather keep the old behaviour exactly, I can key it on `volume` instead.","commit_id":"625923de782363a11ec25bc949e081ba0f3ce820"},{"author":{"_account_id":39633,"name":"Mark McCormick","display_name":"Mark","email":"mark.mccormick@chainguard.dev","username":"markm22"},"change_message_id":"e200769e6a494a776a91280b5a14f6cac9a8a668","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d82a3363_efc76d4c","in_reply_to":"fc231c89_624ae083","updated":"2026-11-18 23:35:55.000000000","message":"Done in PS2: the mount is now conditional, using the same loop as the volume pod. The details, and one behaviour change to flag, are in my reply to Mathieu\u0027s comment.","commit_id":"625923de782363a11ec25bc949e081ba0f3ce820"}]}
