PowerVM

Power Virtualization

Learn about the virtualization technologies designed specifically for IBM Power including #PowerVM, #PowerVC, #VM Recovery Manager, #HCM/CMC, and more.


#Power
#TechXchangeConferenceLab

 View Only

  • 1.  PowerVC upgrade to 2.0.2

    Posted Fri February 18, 2022 04:49 PM
    Hi I am running PowerVC 2.0.1 and want to upgrade to 2.0.2 and preview is erroring out.
    #
    powervc-opsmgr install -c pvc_cluster -p

    Friday 18 February 2022 16:48:03 -0500 (0:00:01.808) 0:00:04.792 *******
    fatal: [10.0.161.101]: FAILED! => {"changed": true, "cmd": ["grep", "cluster =", "/opt/ibm/powervc/version.properties"], "delta": "0:00:01.003588", "end": "2022-02-18 16:48:04.886938", "msg": "non-zero return code", "rc": 1, "start": "2022-02-18 16:48:03.883350", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

    TASK [pvc_precheck : get cluster name from /opt/ibm/powervc/version.properties] ***
    fatal: [10.0.161.101]: FAILED! => {"changed": true, "cmd": ["grep", "cluster =", "/opt/ibm/powervc/version.properties"], "delta": "0:00:01.003588", "end": "2022-02-18 16:48:04.886938", "msg": "non-zero return code", "rc": 1, "start": "2022-02-18 16:48:03.883350", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
    ...ignoring
    Friday 18 February 2022 16:48:22 -0500 (0:00:00.452) 0:00:23.385 *******
    fatal: [10.0.161.101]: FAILED! => {
    "assertion": "umask_value.stdout == \"0022\" or umask_value.stdout == \"022\"",
    "changed": false,
    "evaluated_to": false,
    "msg": "umask permissions check failed"
    }

    TASK [pvc_precheck : check umask permissions] **********************************
    fatal: [10.0.161.101]: FAILED! => {
    "assertion": "umask_value.stdout == \"0022\" or umask_value.stdout == \"022\"",
    "changed": false,
    "evaluated_to": false,
    "msg": "umask permissions check failed"
    }

    NO MORE HOSTS LEFT *************************************************************
    10.0.161.101 : ok=39 changed=7 unreachable=0 failed=1 skipped=25 rescued=0 ignored=1


    PLAY RECAP *********************************************************************
    10.0.161.101 : ok=39 changed=7 unreachable=0 failed=1 skipped=25 rescued=0 ignored=1




    ​

    ------------------------------
    Rizwan
    ------------------------------

    #PowerVC


  • 2.  RE: PowerVC upgrade to 2.0.2

    Posted Mon February 21, 2022 01:13 AM
    Hi Rizwan

    For the umask we are expecting the umask value to be 022 or 0022 for proper file permissions.
    If you can edit umask value in /etc/bashrc to 022 or 0022.

    And retry the precheck.

    Regards
    Aman

    ------------------------------
    Aman Sinha
    ------------------------------

    Original Message


  • 3.  RE: PowerVC upgrade to 2.0.2

    Posted Mon February 21, 2022 02:49 AM
    Hi,

    I encountered the same error last year; I reported it ..and basically 2 things U could check

    1) umask value in /etc/bashrc  file >> preview checks this file, and not the umask from the user settings
    2) Try to upgrade directly to 2.0.2.1 ; I think the preview is fixed in that release.

    Br,
    tommi

    ------------------------------
    Tommi Sihvo, Lead Service Architect
    TietoEVRY, Compute Services
    email tommi.sihvo@tietoevry.com mobile +358 (0)40 5180 Finland
    ------------------------------

    Original Message


  • 4.  RE: PowerVC upgrade to 2.0.2

    Posted Mon February 21, 2022 12:26 PM
    Tried installing PowerVC2.0.2.1 and it errored out, below are the three  errors
    1-Monday 21 February 2022 12:13:16 -0500 (0:00:02.697) 0:00:05.215 *******
    fatal: [10.0.161.101]: FAILED! => {"changed": true, "cmd": ["grep", "cluster =", "/opt/ibm/powervc/version.properties"], "delta": "0:00:00.002265", "end": "2022-02-21 12:13:16.233867", "msg": "non-zero return code", "rc": 1, "start": "2022-02-21 12:13:16.231602", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

    2-
    fatal: [10.0.161.101]: FAILED! => {"changed": false, "msg": ["The required ports are in use:- [9292, 9191, 8774, 9000, 9696, 8428, 5470, 5671, 4369, 50110, 8080, 6200, 6201, 6202, 6080, 8778, 8041]. Make these ports available, then run the installation again.", "precheck check_ports_available failed, message: RC_PORTS_IN_USE"]}

    3-NO MORE HOSTS LEFT *************************************************************
    10.0.161.101 : ok=89 changed=10 unreachable=0 failed=1 skipped=73 rescued=0 ignored=1


    PLAY RECAP *********************************************************************
    10.0.161.101 : ok=89 changed=10 unreachable=0 failed=1 skipped=73 rescued=0 ignored=1

    ------------------------------
    Rizwan
    ------------------------------

    Original Message


  • 5.  RE: PowerVC upgrade to 2.0.2

    Posted Tue February 22, 2022 02:01 AM
    Since you are updating from PVC 2.0.2 to 2.0.2.1, shouldn't it be as follows ? 
    1) Run "update_opsmgr.sh" to update the ops-mgr, followed by
    2) powervc-opsmgr update -c <cluster_name> -n <node_ip/hostname>



    ------------------------------
    Dharmesh Kamdar
    ------------------------------

    Original Message


  • 6.  RE: PowerVC upgrade to 2.0.2

    Posted Tue February 22, 2022 06:44 AM
    Hi Dharmesh
    As Tommi suggested, I tried a base install of 2.0.2.1 instead of upgrade of existing  2.0.2 and encountered the same issue.

    ------------------------------
    Rizwan
    ------------------------------

    Original Message


Related Content