Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  PVC for Single Node

    Posted Fri March 28, 2025 02:08 PM

    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



    ------------------------------
    Brett Coleman
    ------------------------------


  • 2.  RE: PVC for Single Node

    Posted Sun March 30, 2025 11:42 AM

    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.



    ------------------------------
    Diego Visentin
    ------------------------------



  • 3.  RE: PVC for Single Node
    Best Answer

    Posted Mon March 31, 2025 03:24 AM

    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.



    ------------------------------
    Witold Wierzchowski
    Solution Architect
    Cohesive Poland
    ------------------------------

    Original Message


  • 4.  RE: PVC for Single Node

    Posted Mon March 31, 2025 07:35 AM

    Thank you both @Witold Wierzchowski and @Diego Visentin. Those are both great solutions. I'm learning Openshift and Maximo on the fly, so I appreciate          you sharing your knowledge!



    ------------------------------
    Brett Coleman
    ------------------------------

    Original Message


  • 5.  RE: PVC for Single Node

    Posted Mon March 31, 2025 08:25 AM

    I used to do this a whole lot (install NFS - inside or outside of OCP). The LVMs operator is a better deal for SNO. It is a quick install if done manually after SNO is stood up. Assisted Installer installs it automatically with OCP. 



    ------------------------------
    Arif Ali
    ------------------------------

    Original Message


  • 6.  RE: PVC for Single Node

    Posted Mon March 31, 2025 08:18 AM

    Assuming you are using the Interactive CLI (aka pipeline QA), you can type up lvms-vg1 for both RWO and RWX (when asked). This will install the PVC without any problems during the time of the Manage installation. The same could be defined explicitly if you're using direct Ansible.

    Other solutions provided here, are also fine, but they are for after the install.



    ------------------------------
    Arif Ali
    ------------------------------



Related Content