ibm-mas / cli

Maximo Application Suite command line interface
https://ibm-mas.github.io/cli/
Eclipse Public License 2.0
23 stars 17 forks source link

Manage advanced settings do not work on SNO #1192

Closed durera closed 4 weeks ago

durera commented 1 month ago

MAS CLI version

10.7.3

CLI function used

install

What happened?

The primary pipeline params are as expected, indicating that we are not using a RWX storage class:

{"name":"storage_class_rwx","value":""}
{"name":"storage_class_rwo","value":"lvms-vg1"}

The additional param for a specific storage class for manage doclinks is not defined, and the access mode is wrong. I'm not familiar with this area, but the problem is specifically regarding handling of Manage advanced settings

{"name":"mas_app_settings_doclinks_pvc_storage_class","value":""}
{"name":"mas_app_settings_doclinks_pvc_accessmode","value":"ReadWriteMany"}

Looking at all the Manage advanced settings, it looks like none are set up SNO friendly, so I would imagine that since these were added they have never worked for a SNO install.

mas_app_settings_aio_flag: 'false'
mas_app_settings_base_lang: CS
mas_app_settings_bim_pvc_accessmode: ReadWriteMany
mas_app_settings_bim_pvc_storage_class: ''
mas_app_settings_default_jms: 'true'
mas_app_settings_demodata: 'false'
mas_app_settings_doclinks_pvc_accessmode: ReadWriteMany
mas_app_settings_doclinks_pvc_storage_class: ''
mas_app_settings_jms_queue_pvc_accessmode: ReadWriteMany
mas_app_settings_jms_queue_pvc_storage_class: ''
mas_app_settings_persistent_volumes_flag: 'true'
mas_app_settings_secondary_langs: EN
mas_app_settings_server_bundles_size: snojms
mas_app_settings_server_timezone: GMT

I don't know the details about what each of these do and what the expectations are in terms of what they should be set to with/without SNO involved. I'm guessing the fact mas_app_settings_persistent_volumes_flag=true means that the doclinks pvc params become active in the install, but the value for the class hasn't been initialized at all, I would guess that in the code it's hardwired to copy the RWX storage class to these values when mas_app_settings_persistent_volumes_flag is set to true, but needs to have an "if SNO copy RWO values".

Relevant log output

See above
MaximoMiller commented 1 month ago

Is there a way to vote or show support of a bug so they see it is impacting more people and will get more quickly addressed?

ederfalmeida commented 1 month ago

I was about to report this issue. The MAS deployment hangs because these 3 pods can't be created.

image