You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current README file under the "OS Support" section lists the following supported operating systems:
RHEL 7 on x86_64, PPC64, and PPC64LE
RHEL 8 on x86_64 and PPC64LE
UBUNTU 20 on x86_64 and PPC64LE
SLES 15 on x86_64 and PPC64LE
However, it does not mention Ubuntu 22.04 on x86_64 and PPC64LE architectures. As of IBM Storage Scale version 5.2.1, Ubuntu 22.04 is fully supported on these architectures when using the Ansible-based installer. Clients expect this support to be reflected in the README for this project.
Steps to Reproduce:
Open the project's README file.
Navigate to the "OS Support" section.
Observe the absence of Ubuntu 22.04 as a supported platform.
Expected Behavior: The README should explicitly mention that Ubuntu 22.04 on x86_64 and PPC64LE is supported
Environment:
IBM Storage Scale 5.2.1
Ubuntu 22.04 on x86_64 and PPC64LE
The text was updated successfully, but these errors were encountered:
Description of the Bug:
The current README file under the "OS Support" section lists the following supported operating systems:
RHEL 7 on x86_64, PPC64, and PPC64LE
RHEL 8 on x86_64 and PPC64LE
UBUNTU 20 on x86_64 and PPC64LE
SLES 15 on x86_64 and PPC64LE
However, it does not mention Ubuntu 22.04 on x86_64 and PPC64LE architectures. As of IBM Storage Scale version 5.2.1, Ubuntu 22.04 is fully supported on these architectures when using the Ansible-based installer. Clients expect this support to be reflected in the README for this project.
Steps to Reproduce:
Open the project's README file.
Navigate to the "OS Support" section.
Observe the absence of Ubuntu 22.04 as a supported platform.
Expected Behavior: The README should explicitly mention that Ubuntu 22.04 on x86_64 and PPC64LE is supported
Environment:
IBM Storage Scale 5.2.1
Ubuntu 22.04 on x86_64 and PPC64LE
The text was updated successfully, but these errors were encountered: