RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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