MAS install second instance

[zoltanpesko]

MAS CLI version

latest

CLI function used

install

What happened?

i try to install an second instance of MAS using the latest MAS CLI pipeline, v13.17.0 using the following command:

And the DRO wants to install and tries to add a new PVC.

export IBM_ENTITLEMENT_KEY=x
mas install --mas-catalog-version v9-250403-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
  --mas-channel 9.0.x --mas-instance-id test --mas-workspace-id test --mas-workspace-name "test" \
  --additional-configs "/mascli/" \
  --disable-walkme \
  --storage-class-rwo "ocs-external-storagecluster-ceph-rbd" --storage-class-rwx "ocs-external-storagecluster-cephfs" \
  --storage-pipeline "ocs-external-storagecluster-cephfs" --storage-accessmode "ReadWriteMany" \
  --uds-email "[email protected]" --uds-firstname "zoltan" --uds-lastname "pesko" \
  --dro-namespace "redhat-marketplace" \
  --accept-license --no-confirm

What am I doing wrong? I would like to have 1 SLS and use the "old" DRO. thanks in adavance (edited)

Should I have a separate DRO? Should I use a different namespace?

Relevant log output

TASK [ibm.mas_devops.dro : Create DRO PVC] *************************************
fatal: [localhost]: FAILED! => changed=false 
  msg: 'Failed to patch object: b''{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"PersistentVolumeClaim \\"rhm-data-service-rhm-data-service-0\\" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims\\n\xc2\xa0\xc2\xa0core.PersistentVolumeClaimSpec{\\n\xc2\xa0\xc2\xa0\\t... // 2 identical fields\\n\xc2\xa0\xc2\xa0\\tResources:        {Requests: {s\\"storage\\": {i: {...}, s: \\"1Gi\\", Format: \\"BinarySI\\"}}},\\n\xc2\xa0\xc2\xa0\\tVolumeName:       \\"pvc-a924e1e8-17e3-4289-8302-8dec96d6196d\\",\\n-\xc2\xa0\\tStorageClassName: \\u0026\\"ocs-external-storagecluster-cephfs\\",\\n+\xc2\xa0\\tStorageClassName: \\u0026\\"ocs-external-storagecluster-ceph-rbd\\",\\n\xc2\xa0\xc2\xa0\\tVolumeMode:       \\u0026\\"Filesystem\\",\\n\xc2\xa0\xc2\xa0\\tDataSource:       nil,\\n\xc2\xa0\xc2\xa0\\tDataSourceRef:    nil,\\n\xc2\xa0\xc2\xa0}\\n","reason":"Invalid","details":{"name":"rhm-data-service-rhm-data-service-0","kind":"PersistentVolumeClaim","causes":[{"reason":"FieldValueForbidden","message":"Forbidden:
    spec is immutable after creation except resources.requests for bound claims\\n\xc2\xa0\xc2\xa0core.PersistentVolumeClaimSpec{\\n\xc2\xa0\xc2\xa0\\t... // 2 identical fields\\n\xc2\xa0\xc2\xa0\\tResources:        {Requests: {s\\"storage\\": {i: {...}, s: \\"1Gi\\", Format: \\"BinarySI\\"}}},\\n\xc2\xa0\xc2\xa0\\tVolumeName:       \\"pvc-a924e1e8-17e3-4289-8302-8dec96d6196d\\",\\n-\xc2\xa0\\tStorageClassName: \\u0026\\"ocs-external-storagecluster-cephfs\\",\\n+\xc2\xa0\\tStorageClassName: \\u0026\\"ocs-external-storagecluster-ceph-rbd\\",\\n\xc2\xa0\xc2\xa0\\tVolumeMode:       \\u0026\\"Filesystem\\",\\n\xc2\xa0\xc2\xa0\\tDataSource:       nil,\\n\xc2\xa0\xc2\xa0\\tDataSourceRef:    nil,\\n\xc2\xa0\xc2\xa0}\\n","field":"spec"}]},"code":422}\n'''
  reason: Unprocessable Entity

[zoltanpesko]

2 things:

1. Need to use same setting(e-mail, FirstName, LastName)
2. Correct storage class I found the issue for the DRO, if I use the automatic storage class detection, the second installer uses ocs-external-storageclsluster-cephfs, however the original installer used ocs-external-storagecluater-rbd. When I manually specified the correct storage class, the installer went through Solution, add manually the storage class: Question 5.

Use the auto-detected storage classes? [y/n] n

And after add the correct (previously used storage class)

[terc1997]

Fixed on ansible-devops#1752