Closed durera closed 4 weeks 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?
I was about to report this issue. The MAS deployment hangs because these 3 pods can't be created.
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:
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
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.
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