Hide Forgot
Description of problem: In the Horizon dashboard, on the Volume page, there is a button to "Initiate Transfer" of a volume from one instance/project to another. On that screen, the admin is required to record 2 important values, "auth_key" and "id". Version-Release number of selected component (if applicable): RHEL-OSP 7.0 Steps to Reproduce: 1. Click on Projects > Volumes 2. In the Actions column of the volume to transfer, select Create Transfer. 3. In the Create Transfer dialog box, enter a name for the transfer and click Create Volume Transfer. 4. The volume transfer is created and in the Volume Transfer screen you can capture the transfer ID and the authorization key to send to the recipient project. Actual results: The admin is required to save the transfer_id and the auth_key. Expected results: The OpenStack dashboard should give the user the ability to save a csv of the values or copy both to the clipboard. Additional info: 4.1.7.2. Transfer a Volume Using the Dashboard https://access.redhat.com/documentation/en/red-hat-enterprise-linux-openstack-platform/version-7/red-hat-enterprise-linux-openstack-platform-7-instances-and-images-guide/chapter-4-manage-volumes/
There is an ongoing review on https://review.openstack.org/#/c/248082/1 This feature clearly missed Liberty release (6 weeks ago, feature freeze was 3 weeks earlier). Moving this RFE to Mitaka
Moving to Newton, as the patch did not land yet upstream.
This has been merged upstream, would be available on Newton.
Bulk update to reflect scope of Red Hat OpenStack Platform 9 and Red Hat OpenStack Platform does not include this issue (No pm_ack+).
How to test: 1. Click on Projects > Volumes 2. In the Actions column of the volume to transfer, select Create Transfer. 3. In the Create Transfer dialog box, enter a name for the transfer and click Create Volume Transfer. 4. The volume transfer is created 5. In the Volume Transfer screen there should be a button for downloading the credentials.
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, 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/RHEA-2017:1245