[patch] fix upgrade from 9.0 to 9.1 with non standard storage class

[terc1997]

Description

When upgrade MAS from 9.0 to 9.1, it requires to deploy Manage Foundation which requires Db2. When using the Storage Classes (SC) listed here the pipelines work as expected, because even storage_class_rwo and storage_class_rwx are empty, the Ansible collection will fetch one of the aforementioned SCs. When they're not present, the installation doesn't detect them and keep storage_class_rwo and storage_class_rwx empty throwing an error.

Solution

The solution was to introduce two new parameters for interactive and non-interactive mode to allow input SC values

Related PRs

• [patch] add storage class rwo and rwx params to upgrade pipelinerun python-devops#516

Linked issues

• mas upgrade for MAS v9.0 envs without Manage fails #2538

Tests

Interactive

Noninteractive

without storage_class_rw* + without --no-confirm

without storage_class_rw* + --no-confirm

without storage_class_rw* + --no-confirm + default storage class (nfs-client)