Comment 5 for bug 1945239

> Hi Nobuto, for pure-storage they should report stateless=False for releases they don't support AA HA. See discussion at https://review.opendev.org/c/openstack/charm-cinder/+/814845

I get your point and indeed "stateless=True" was misused for some time. But the problems here are:

1. storage backend setup by a subordinate charm (previously stateless=True) will stop working just after upgrading the cinder charm with "Volume driver reported an error: Active-Active configuration is not currently supported by driver". Thus I stated as a backward compatibility even if the original value was misused.

This needs to be addressed in each charm in a coordinated way (we can't release cinder first without waiting for *all* of the supported charms report their support status correctly, and the coordinate upgrade must be covered in the release notes in my opinion.

2. Have you considered the multi-backend scenarios and mixture of stateless and statefull backend? Let's say focal-ussuri with Ceph(rbd) and Purestorage.

With the new behavior and if charm-purestorage reports stateless=False, what happens to volume service status of Ceph? Previously host= was in cinder.conf but with the new behavior, neither of host= or cluster= will be in cinder.conf while ceph expects one of those?

I may be too scared of the change probably but wanted to raise my concern here.