[Update as of Friday, June 6, 2025, 16:00]

The maintenance conducted during the period from May 19 to May 22 has resolved the issues with the snapshot feature, and the snapshot acquisition and related functionalities are now available for use.

However, a new issue has been identified where, under certain conditions, an error occurs when attempting to delete an already acquired snapshot.

■ Incident Details

We have confirmed that in Red Hat OpenStack Platform on mdx II, an error occurs when attempting to delete a volume snapshot under the following conditions:

・The snapshot is of a volume attached to an instance
・There are multiple snapshots of the corresponding volume
・The instance is in a stopped state and you attempt to delete a snapshot other than the most recently acquired one

When this error occurs, it may become impossible to delete other snapshots related to the same volume.

Please note that the following cases are not affected by this issue:

・When deleting snapshots while the instance is running
・When deleting snapshots of volumes that are not attached to any instance

■ How to Check Volume Attachment Status

Access the user portal (https://portal.osaka.mdx.jp/)

Go to the [Project] menu → Open the [Volumes] panel → Open the [Volumes] tab

Check the “Attached To” column in the list of volumes
　- If blank: The volume is not attached to any instance
　- If an instance name and device name are displayed: The volume is attached to an instance

■ Status of Response

This issue is due to a bug in the Red Hat OpenStack Platform, and a fix is currently being worked on by the vendor.

■ Request to Users

If you have taken multiple snapshots of a volume that is attached to an instance,
please delete the snapshots while the instance is in a running state.

If you encounter an error when trying to delete a snapshot and are unable to proceed,
we kindly ask that you contact the following support desk:

■ Emergency Support Desk

mdx2-support[-at]hpc.cmc.osaka-u.ac.jp

We sincerely apologize for the inconvenience caused.
We will continue our efforts to ensure stable operations, and we appreciate your continued support.

————————————————–
To resolve issues related to the snapshot feature, we will perform maintenance on the mdxⅡ system as outlined below.

This maintenance is expected to resolve the issues that have been affecting the snapshot feature.
After the maintenance is completed, the feature should be available for use as intended.

During the maintenance period, all services will be temporarily suspended.
We apologize for the inconvenience and kindly ask for your understanding and cooperation.

mdxⅡ System – Full Service Suspension Period

■ Request to Stop Virtual Machines in Advance

To carry out the maintenance, virtual machines running on the mdxⅡ system must be shut down in advance.
Please stop all virtual machines by 9:00 AM on May 19, 2025, before the maintenance begins.
*If any virtual machine remains running during the maintenance period, we will shut it down from our side.
If the shutdown process takes too long, we may forcibly stop the machine.

We apologize for the inconvenience and appreciate your cooperation.