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.  Failing Update of Power VC 2.0.2.1 to 2.0.3

    Posted Fri November 11, 2022 09:44 AM
    Hi,

     Tried to update single node PowerVC 2.0.2.1 too 2.0.3 on RHEL ppc64le and got stalled in the process.
     Followed this good guide :Reduce downtime with 'PowerVC Rolling Upgrade'
    - opsmgr update : ok  
    - monitoring update: ok

    -  But  PowerVC upgrade fails:

    Initially had issues with mariadb, applied  iFIX 2.0.3-PowerVC-RHEL-SLES-NOARCH-APAR-IT41045 and manuallyinstalled mariadb and galera but now facing issue with HAproxy not being able to start.
    TASK [pvc_haproxy : Configure haproxy.cfg] *************************************
    changed: [10.1.3.45]
    Thursday 10 November 2022  16:22:28 +0100 (0:00:00.981)       0:01:14.400 *****
    
    TASK [pvc_haproxy : Drop base haproxy config] **********************************
    ok: [10.1.3.45]
    Thursday 10 November 2022  16:22:29 +0100 (0:00:00.730)       0:01:15.131 *****
    changed: [10.1.3.45]
    
    TASK [pvc_haproxy : Generate haproxy configuration] ****************************
    changed: [10.1.3.45]
    [WARNING]: flush_handlers task does not support when conditional
    Thursday 10 November 2022  16:22:29 +0100 (0:00:00.431)       0:01:15.562 *****
    
    RUNNING HANDLER [pvc_haproxy : Restart haproxy] ********************************
    fatal: [10.1.3.45]: FAILED! => {"changed": false, "msg": "Unable to start service haproxy: Job for haproxy.service failed because the control process exited with error code.\nSee \"systemctl status haproxy.service\" and \"journalctl -xe\" for details.\n"}
    Thursday 10 November 2022  16:22:29 +0100 (0:00:00.553)       0:01:16.116 *****
    
    NO MORE HOSTS LEFT *************************************************************
    
    PLAY RECAP *********************************************************************
    10.1.3.45                  : ok=84   changed=12   unreachable=0    failed=1    skipped=90   rescued=0    ignored=0​

    Gathered output of # systemctl status haproxy.service:

    ● haproxy.service - HAProxy Load Balancer
       Loaded: loaded (/usr/lib/systemd/system/haproxy.service; enabled; vendor press
    et: disabled)
       Active: failed (Result: exit-code) since Thu 2022-11-10 16:26:21 CET; 4s ago
    
    Nov 10 16:26:21 App11PowerVC202bis haproxy[93609]: [ALERT] 313/162621 (93609) :
    Parsing [/etc/haproxy/conf.d/swift.cfg:4]: frontend 'swift-front' has the same nn
    ame as frontend 'swift-front' declared at /etc/haproxy/haproxy.cfg:439.
    Nov 10 16:26:21 App11PowerVC202bis haproxy[93609]: [ALERT] 313/162621 (93609) :
    Parsing [/etc/haproxy/conf.d/swift.cfg:16]: backend 'swift-back' has the same naa
    me as backend 'swift-back' declared at /etc/haproxy/haproxy.cfg:451.
    Nov 10 16:26:21 App11PowerVC202bis haproxy[93609]: [ALERT] 313/162621 (93609) :
    Error(s) found in configuration file : /etc/haproxy/conf.d/swift.cfg
    Nov 10 16:26:21 App11PowerVC202bis haproxy[93609]: [ALERT] 313/162621 (93609) :
    Parsing [/etc/haproxy/conf.d/ttv-validation.cfg:4]: frontend 'ttv-validation-froo
    nt' has the same name as frontend 'ttv-validation-front' declared at /etc/haproxx
    y/haproxy.cfg:464.
    Nov 10 16:26:21 App11PowerVC202bis haproxy[93609]: [ALERT] 313/162621 (93609) :
    Parsing [/etc/haproxy/conf.d/ttv-validation.cfg:16]: backend 'ttv-validation-bacc
    k' has the same name as backend 'ttv-validation-back' declared at /etc/haproxy/hh
    aproxy.cfg:476.
    Nov 10 16:26:21 App11PowerVC202bis haproxy[93609]: [ALERT] 313/162621 (93609) :
    Error(s) found in configuration file : /etc/haproxy/conf.d/ttv-validation.cfg
    "haproxyerror" 14L, 1915C​
    but no way to go further in the update process.

    Any clue how to solve this?


    ------------------------------
    ALBERT VALLS
    ------------------------------

    #PowerVC


  • 2.  RE: Failing Update of Power VC 2.0.2.1 to 2.0.3

    Posted Wed November 16, 2022 12:01 PM
    Hi Albert, I have the same error.
    Could you solve it?

    Regards,
    Víctor GUZ

    ------------------------------
    Victor Guzman
    ------------------------------



  • 3.  RE: Failing Update of Power VC 2.0.2.1 to 2.0.3

    Posted Wed November 16, 2022 10:17 PM
    Hi Albert
    I found the error, what happens is that the configuration file for the startup of the haproxy service is calling two configuration files:

    cat /usr/lib/systemd/system/haproxy.service
    [service]
    Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid" "CFGDIR=/etc/haproxy/conf.d"
    EnvironmentFile=/etc/sysconfig/haproxy
    ExecStartPre=/usr/sbin/haproxy -f $CONFIG -f $CFGDIR -c -q $OPTIONS
    ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -f $CFGDIR -p $PIDFILE $OPTIONS
    ExecReload=/usr/sbin/haproxy -f $CONFIG -f $CFGDIR -c -q $OPTIONS

    Here we must delete -f $CONFIG on all three lines and save the file, after that execute:

    systemctl daemon-reload
    systemctl stop haproxy
    systemctl start haproxy

    After that, continue with the upgrade process.

    Regards,
    Víctor

    ------------------------------
    Victor Guzman
    ------------------------------



  • 4.  RE: Failing Update of Power VC 2.0.2.1 to 2.0.3

    Posted Thu November 17, 2022 09:49 AM
    Many thanks Victor.

    Yes, it worked with this workaround.

    ------------------------------
    ALBERT VALLS BADIA
    ------------------------------