From b3e57f5c2b72ead5236f9593ca24f2baad54cf33 Mon Sep 17 00:00:00 2001 From: danielclowers Date: Wed, 17 Sep 2025 09:31:35 -0400 Subject: [PATCH] CNV#69681: Add IBM Fusion Access for SAN release updates --- modules/virt-creating-fusionaccess-cr.adoc | 2 - ...irt-fusion-access-san-release-updates.adoc | 42 +++++++++++++++++++ ...irt-installing-fusion-access-operator.adoc | 4 +- .../install-configure-fusion-access-san.adoc | 8 ++-- 4 files changed, 49 insertions(+), 7 deletions(-) create mode 100644 modules/virt-fusion-access-san-release-updates.adoc diff --git a/modules/virt-creating-fusionaccess-cr.adoc b/modules/virt-creating-fusionaccess-cr.adoc index 2a08ac681679..c63c72a599d7 100644 --- a/modules/virt-creating-fusionaccess-cr.adoc +++ b/modules/virt-creating-fusionaccess-cr.adoc @@ -31,8 +31,6 @@ Creating the `FusionAccess` CR triggers the installation of the correct version . Optional: You can choose to add *Labels* if they are relevant. . Select the *IBM Storage Scale Version* from the drop-down list. -+ -This version is the same version that was used to install the {FusionSAN} Operator. . Click *Create*. diff --git a/modules/virt-fusion-access-san-release-updates.adoc b/modules/virt-fusion-access-san-release-updates.adoc new file mode 100644 index 000000000000..edef746a232b --- /dev/null +++ b/modules/virt-fusion-access-san-release-updates.adoc @@ -0,0 +1,42 @@ +// Module included in the following assemblies: +// +// * virt/fusion_access_SAN/install-configure-fusion-access-san.adoc + +:_mod-docs-content-type: CONCEPT +[id="virt-fusion-access-san-release-updates_{context}"] += IBM Fusion Access for SAN release updates + +[role="_abstract"] +Release updates for IBM Fusion Access for SAN, including new features, bug fixes, and known issues. + +[id="virt-fusion-access-san-new-changes_{context}"] +== New and changed features + +Image registry requirements for kernel module management:: + +{IBMFusionFirst} uses the {product-title} image registry to manage the kernel module. Do not configure the registry to use `emptyDir` storage because it provides only temporary storage and is not suitable for production use. Configure {IBMFusionFirst} to use a different image registry by creating a config map and secret after installing the Operator and before creating the `FusionAccess` CR. (link:https://issues.redhat.com/browse/OCPNAS-213[*OCPNAS-213*]) + +[id="virt-fusion-access-san-bug-fixes_{context}"] +== Bug fixes + +Filesystem creation button stays disabled until daemons are ready:: + +The {IBMFusionFirst} Operator was updated to check the readiness of filesystem daemons before allowing a filesystem to be created. The **Create file system** button in the web console now stays disabled with a tooltip explaining the condition until the environment is ready. This change prevents filesystems from appearing stuck during creation. (link:https://issues.redhat.com/browse/OCPNAS-184[*OCPNAS-184*]) + +Filesystems cannot be deleted from the user interface:: + +The {product-title} web console does not support deleting filesystems. To delete a filesystem, use the {oc-first}. (link:https://issues.redhat.com/browse/OCPNAS-217[*OCPNAS-217*]) + +[id="virt-fusion-access-san-known-issues_{context}"] +== Known issues + +Filesystem creation might fail during core pod deletion:: + +Filesystem creation might fail if core pods are deleted at the same time. The filesystem might be partially created on the LUN, which results in the following persistent error: ++ +[source,terminal] +---- +Disk may still belong to an active file system +---- ++ +No workaround is available. Contact IBM Support for assistance. (link:https://issues.redhat.com/browse/OCPNAS-233[*OCPNAS-233*]) \ No newline at end of file diff --git a/modules/virt-installing-fusion-access-operator.adoc b/modules/virt-installing-fusion-access-operator.adoc index ade60c1ce939..94e4279f3c8e 100644 --- a/modules/virt-installing-fusion-access-operator.adoc +++ b/modules/virt-installing-fusion-access-operator.adoc @@ -23,13 +23,13 @@ Install the {FusionSAN} Operator from the *OperatorHub* in the {product-title} w . On the *Install Operator* page, keep the default selections for *Update Channel*, *Version*, and *Installation mode*. -. Verify that *Operator recommended Namespace* is selected for *Installed Namespace*. +. Verify that *Operator recommended Namespace* is selected for *Installed Namespace*. + This installs the Operator in the `ibm-fusion-access` namespace. If this namespace does not yet exist, it is automatically created. + [WARNING] ==== -If you install the {FusionSAN} Operator in a namespace other than `ibm-fusion-access`, {FusionSan} does not work. +You must install the {FusionSAN} Operator in the `ibm-fusion-access` namespace. Installation in any other namespace is not supported. ==== . Verify that the *Automatic* default is selected for *Update Approval*. diff --git a/virt/fusion_access_SAN/install-configure-fusion-access-san.adoc b/virt/fusion_access_SAN/install-configure-fusion-access-san.adoc index 655aad5ed995..26244e529694 100644 --- a/virt/fusion_access_SAN/install-configure-fusion-access-san.adoc +++ b/virt/fusion_access_SAN/install-configure-fusion-access-san.adoc @@ -1,8 +1,8 @@ :_mod-docs-content-type: ASSEMBLY +include::_attributes/common-attributes.adoc[] [id="install-configure-fusion-access-san"] = Installing and configuring {IBMFusionFirst} -include::_attributes/common-attributes.adoc[] :context: install-configure-fusion-access-san toc::[] @@ -28,8 +28,10 @@ include::modules/virt-creating-filesystem-fusion-access-san.adoc[leveloffset=+1] Once you create a storage cluster with file systems, you can create a virtual machine (VM) on the storage cluster. -Create a VM from an instance type or template and select one of the file systems you created as the storage type. +Create a VM from an instance type or template and select a storage class that corresponds to one of the file systems you created as the storage type. * xref:../../virt/creating_vm/virt-creating-vms-from-instance-types.adoc#virt-creating-vms-from-instance-types[Creating virtual machines from instance types]. -* xref:../../virt/creating_vm/virt-creating-vms-from-templates.adoc#virt-creating-vms-from-templates[Creating virtual machines from templates]. \ No newline at end of file +* xref:../../virt/creating_vm/virt-creating-vms-from-templates.adoc#virt-creating-vms-from-templates[Creating virtual machines from templates]. + +include::modules/virt-fusion-access-san-release-updates.adoc[leveloffset=+1] \ No newline at end of file