Hi Team,

I have a quick question regarding the deployment of PVCs when configuring DocLinks on a single-node OpenShift cluster. As we proceed with our upgrade, I've encountered an issue where deploying PVCs from MAS core defaults to RWX access mode. However, since the single-node setup uses LVM storage with an access mode of RWO, the PVCs fail to bind, and the maxinst pod gets stuck in a pending state while trying to claim the PVCs.

To address this, I wrote a simple command to change the access mode:
oc patch pv <pv name> -p '{"spec":{"accessModes":"ReadWriteOnce"}}'

Before I proceed with implementing this solution, I wanted to check if anyone has encountered this issue or can confirm that the command will work. Has anyone successfully configured DocLinks on a single-node setup? I'd prefer not to have to tear down the cluster repeatedly for troubleshooting.

Our long-term plan is to stand up a full cluster once we move to production, so this issue will likely be irrelevant by then. However, I thought this might be helpful for anyone else who may be in a similar situation.

Thanks in advance for your insights!

Best,
Brett

Hi @Brett Coleman, 
you probably follow the same process, but I usually create an NFS server inside the SNO and then configure Manage attachments accordingly.

Hi Team,

I have a quick question regarding the deployment of PVCs when configuring DocLinks on a single-node OpenShift cluster. As we proceed with our upgrade, I've encountered an issue where deploying PVCs from MAS core defaults to RWX access mode. However, since the single-node setup uses LVM storage with an access mode of RWO, the PVCs fail to bind, and the maxinst pod gets stuck in a pending state while trying to claim the PVCs.

To address this, I wrote a simple command to change the access mode:
oc patch pv <pv name> -p '{"spec":{"accessModes":"ReadWriteOnce"}}'

Before I proceed with implementing this solution, I wanted to check if anyone has encountered this issue or can confirm that the command will work. Has anyone successfully configured DocLinks on a single-node setup? I'd prefer not to have to tear down the cluster repeatedly for troubleshooting.

Our long-term plan is to stand up a full cluster once we move to production, so this issue will likely be irrelevant by then. However, I thought this might be helpful for anyone else who may be in a similar situation.

Thanks in advance for your insights!

Best,
Brett

Hi Brett,

You cannot modify access mode after PVC was created.
The easiest way here is just to set the accessMode in ManageWorkspace CR - see mine below with. Just set accessModes: ReadWriteOnce and that's it. One thing to remember: You cannot do that after PVC is created, so if You already have that, just remove it from the ManageWorkspace CR, wait till operator finishes reconciliation and add persistent volume back.

Hi @Brett Coleman, 
you probably follow the same process, but I usually create an NFS server inside the SNO and then configure Manage attachments accordingly.

Hi Team,

I have a quick question regarding the deployment of PVCs when configuring DocLinks on a single-node OpenShift cluster. As we proceed with our upgrade, I've encountered an issue where deploying PVCs from MAS core defaults to RWX access mode. However, since the single-node setup uses LVM storage with an access mode of RWO, the PVCs fail to bind, and the maxinst pod gets stuck in a pending state while trying to claim the PVCs.

To address this, I wrote a simple command to change the access mode:
oc patch pv <pv name> -p '{"spec":{"accessModes":"ReadWriteOnce"}}'

Before I proceed with implementing this solution, I wanted to check if anyone has encountered this issue or can confirm that the command will work. Has anyone successfully configured DocLinks on a single-node setup? I'd prefer not to have to tear down the cluster repeatedly for troubleshooting.

Our long-term plan is to stand up a full cluster once we move to production, so this issue will likely be irrelevant by then. However, I thought this might be helpful for anyone else who may be in a similar situation.

Thanks in advance for your insights!

Best,
Brett

Hi @Brett Coleman, 
you probably follow the same process, but I usually create an NFS server inside the SNO and then configure Manage attachments accordingly.

Hi Team,

I have a quick question regarding the deployment of PVCs when configuring DocLinks on a single-node OpenShift cluster. As we proceed with our upgrade, I've encountered an issue where deploying PVCs from MAS core defaults to RWX access mode. However, since the single-node setup uses LVM storage with an access mode of RWO, the PVCs fail to bind, and the maxinst pod gets stuck in a pending state while trying to claim the PVCs.

To address this, I wrote a simple command to change the access mode:
oc patch pv <pv name> -p '{"spec":{"accessModes":"ReadWriteOnce"}}'

Before I proceed with implementing this solution, I wanted to check if anyone has encountered this issue or can confirm that the command will work. Has anyone successfully configured DocLinks on a single-node setup? I'd prefer not to have to tear down the cluster repeatedly for troubleshooting.

Our long-term plan is to stand up a full cluster once we move to production, so this issue will likely be irrelevant by then. However, I thought this might be helpful for anyone else who may be in a similar situation.

Thanks in advance for your insights!

Best,
Brett

Hi Team,

I have a quick question regarding the deployment of PVCs when configuring DocLinks on a single-node OpenShift cluster. As we proceed with our upgrade, I've encountered an issue where deploying PVCs from MAS core defaults to RWX access mode. However, since the single-node setup uses LVM storage with an access mode of RWO, the PVCs fail to bind, and the maxinst pod gets stuck in a pending state while trying to claim the PVCs.

To address this, I wrote a simple command to change the access mode:
oc patch pv <pv name> -p '{"spec":{"accessModes":"ReadWriteOnce"}}'

Before I proceed with implementing this solution, I wanted to check if anyone has encountered this issue or can confirm that the command will work. Has anyone successfully configured DocLinks on a single-node setup? I'd prefer not to have to tear down the cluster repeatedly for troubleshooting.

Our long-term plan is to stand up a full cluster once we move to production, so this issue will likely be irrelevant by then. However, I thought this might be helpful for anyone else who may be in a similar situation.

Thanks in advance for your insights!

Best,
Brett