Description of problem: Give users better feedback when using pool init-cache on a pool with the initialized cache. Version-Release number of selected component (if applicable): stratis-cli-3.2.0-1.el9 stratisd-3.2.2-1.el9 How reproducible: 100% Steps to Reproduce: 1. # stratis pool create test /dev/mapper/vg-lvol0 2. # stratis pool init-cache test /dev/mapper/vg-lvol1 3. # stratis pool init-cache test /dev/mapper/vg-lvol2 Actual results: Execution failed: stratisd failed to perform the operation that you requested. It returned the following information via the D-Bus: ERROR: The input requests initialization of a cache with different block devices from the block devices in the existing cache; the existing cache contains the block device /dev/mapper/vg-lvol2 which the input did not include; the input requested block device /dev/dm-6 which does not exist in the already initialized cache ; to resolve this error, the block devices requested in the input should be the same as the block devices in the existing cache.. Expected results: A message that is easier to understand (e.g., The cache is already initialized for the pool, use add-cache instead). Additional info:
Upstream: https://github.com/stratis-storage/stratis-cli/issues/937
Verified with stratis-cli-3.4.0-1.el9. # stratis pool init-cache test /dev/sdc # stratis pool init-cache test /dev/sdd Execution failed: It appears that you issued an unintended command: Pool already has an initialized cache.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (stratis-cli bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2273