{"id":5817,"date":"2025-05-08T15:39:30","date_gmt":"2025-05-08T06:39:30","guid":{"rendered":"https:\/\/mdx.jp\/?post_type=mdx2_news&p=5817"},"modified":"2025-06-06T16:21:37","modified_gmt":"2025-06-06T07:21:37","slug":"%ef%bc%88%e7%b5%82%e4%ba%86%ef%bc%89mdx%e2%85%b1%e3%82%b7%e3%82%b9%e3%83%86%e3%83%a0-%e3%83%a1%e3%83%b3%e3%83%86%e3%83%8a%e3%83%b3%e3%82%b9%e3%81%ab%e4%bc%b4%e3%81%86%e3%82%b5%e3%83%bc%e3%83%93","status":"publish","type":"mdx2_news","link":"https:\/\/mdx.jp\/en\/mdx2\/news\/5817","title":{"rendered":"\uff08Closed\uff09Temporary Suspension of Services Due to mdx\u2161 System Maintenance (May 19 \u2013 May 22)"},"content":{"rendered":"

[Update as of Friday, June 6, 2025, 16:00]<\/strong><\/p>\n

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.<\/p>\n

However, a new issue has been identified where, under certain conditions, an error occurs when attempting to delete an already acquired snapshot.<\/p>\n

\u25a0 Incident Details<\/h4>\n

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:<\/p>\n

\u30fbThe snapshot is of a volume attached to an instance
\n\u30fbThere are multiple snapshots of the corresponding volume
\n\u30fbThe instance is in a stopped state and you attempt to delete a snapshot other than the most recently acquired one <\/p>\n

When this error occurs, it may become impossible to delete other snapshots related to the same volume.<\/p>\n

Please note that the following cases are not affected by this issue:<\/p>\n

\u30fbWhen deleting snapshots while the instance is running
\n\u30fbWhen deleting snapshots of volumes that are not attached to any instance <\/p>\n

\u25a0 How to Check Volume Attachment Status<\/h4>\n

Access the user portal (https:\/\/portal.osaka.mdx.jp\/<\/a>)<\/p>\n

Go to the [Project] menu \u2192 Open the [Volumes] panel \u2192 Open the [Volumes] tab<\/p>\n

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

\u25a0 Status of Response<\/h4>\n

This issue is due to a bug in the Red Hat OpenStack Platform, and a fix is currently being worked on by the vendor.<\/p>\n

\u25a0 Request to Users<\/h4>\n

If you have taken multiple snapshots of a volume that is attached to an instance,
\nplease delete the snapshots while the instance is in a running state.<\/p>\n

If you encounter an error when trying to delete a snapshot and are unable to proceed,
\nwe kindly ask that you contact the following support desk:<\/p>\n

\u25a0 Emergency Support Desk<\/h4>\n

mdx2-support[-at]hpc.cmc.osaka-u.ac.jp<\/code><\/p>\n

We sincerely apologize for the inconvenience caused.
\nWe will continue our efforts to ensure stable operations, and we appreciate your continued support.<\/p>\n

\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2014\u2013
\nTo resolve issues related to the snapshot feature, we will perform maintenance on the mdx\u2161 system as outlined below.<\/p>\n

This maintenance is expected to resolve the issues that have been affecting the snapshot feature.
\nAfter the maintenance is completed, the feature should be available for use as intended.<\/p>\n

During the maintenance period, all services will be temporarily suspended.
\nWe apologize for the inconvenience and kindly ask for your understanding and cooperation.<\/p>\n

mdx\u2161 System – Full Service Suspension Period<\/h3>\n\n\n
mdx\u2161 System<\/th>\nMay 19, 2025 (Mon) 9:00 AM \uff5e May 22, 2025 (Thu) 6:00 PM<\/td>\n<\/tr>\n<\/table>\n

\u25a0 Request to Stop Virtual Machines in Advance<\/h4>\n

To carry out the maintenance, virtual machines running on the mdx\u2161 system must be shut down in advance.
\nPlease stop all virtual machines by 9:00 AM on May 19, 2025, before the maintenance begins.<\/strong>
\n*If any virtual machine remains running during the maintenance period, we will shut it down from our side.
\nIf the shutdown process takes too long, we may forcibly stop the machine.<\/code><\/p>\n

We apologize for the inconvenience and appreciate your cooperation.<\/p>\n","protected":false},"featured_media":0,"parent":0,"template":"","meta":{"_acf_changed":false,"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false},"mdx2_news-cat":[124859],"class_list":["post-5817","mdx2_news","type-mdx2_news","status-publish","hentry","mdx2_news-cat-maintenance","en-US"],"acf":[],"jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/5817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news"}],"about":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/types\/mdx2_news"}],"version-history":[{"count":3,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/5817\/revisions"}],"predecessor-version":[{"id":5859,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news\/5817\/revisions\/5859"}],"wp:attachment":[{"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/media?parent=5817"}],"wp:term":[{"taxonomy":"mdx2_news-cat","embeddable":true,"href":"https:\/\/mdx.jp\/wp-json\/wp\/v2\/mdx2_news-cat?post=5817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}