2 Replies Latest reply on Nov 27, 2019 2:27 AM by smitmartijn

    Offline vRNI 4.1 upgrade to 4.2 fails

    WVUGeek001 Lurker

      In the past the only way for our shop to upgrade vRNI is to follow Offline upgrade.  This time around the platform upgrades fine but the

       

      Problem: ElasticSearch javaservice is not running.

      Problem: HMaster javaservice is not running.

      Problem: HRegionServer javaservice is not running.

      Problem: Kafka javaservice is not running.

      Problem: QuorumPeerMain javaservice is not running.

      Problem: ResourceManager javaservice is not running.

      Problem: NodeManager javaservice is not running.

      Problem: SaasListener javaservice is not running.

      Problem: Restapilayer javaservice is not running.

      Problem: TSDB javaservice is not running.

      Problem: SamzaContainer javaservice is not running.

      Problem: Launcher javaservice is not running.

      Problem: Postgresql service is not running.

      Nginx is running

      Patroni is running

      ExpressJSApp is running

      NTP is running and healthy.

       

      aren't running and the proxy doesn't even upgrade after following the same procedure for offline upgrades.  The service states

       

      Problem: CollectorMain javaservice is not running.

      Problem: IpfixProcessor javaservice is not running.

      Postgresql is running

      Nginx is running

      Nfcapd is running

      NTP is running and healthy.

       

      The cli-offline-upgrade.log shows

       

      [Mon Nov 18 22:29:43 UTC 2019] Executing: sudo chef-solo -c /home/ubuntu/build-target/infra-base/infra-automation/upgrade_solo.rb -j /home/ubuntu/build-target/infra-base/infra-automation/roles/lsb_release.json

      ERROR: lsb_release upgrade for ubuntu xenial failed

      + CheckResult 1 'Fail to upgrade infra-base components'

      + RESULT=1

      + ERROR_MSG='Fail to upgrade infra-base components'

       

      The cli.log shows

       

      18-11-2019:22:24:33,10 INFO     [01_upgrade_all_service.py:92] cmd: sudo -u ubuntu /home/ubuntu/build-target/infra-base/upgrade.sh /home/ubuntu/build-target/infra-base none /home/ubuntu/build-target/deployment 1562947515 >> /home/ubuntu/logs/cli-offline-upgrade.log 2>&1

      18-11-2019:22:31:29,13 ERROR    [01_upgrade_all_service.py:100] Error: Service 'infra-base' upragde process exit with 1

      18-11-2019:22:31:29,22 CRITICAL [utils.py:102] cmd: python offline-upgrade/upgrade_scripts/01_upgrade_all_service.py failed

      18-11-2019:22:31:29,30 ERROR    [package_installer_upgrade_runner.py:98] Error running upgrade main [python offline-upgrade/main-upgrade.py]

      18-11-2019:22:31:29,31 ERROR    [package_installer_upgrade_runner.py:99] cmd: python offline-upgrade/upgrade_scripts/01_upgrade_all_service.py failed

      18-11-2019:22:31:29,31 ERROR    [package_installer_upgrade_runner.py:100]

      18-11-2019:22:31:29,31 INFO     [package_installer_upgrade_runner.py:127] Cleaning up files under /tmp/upgrade-bits and /home/consoleuser/downloads

      18-11-2019:22:33:51,207 ERROR    [package_installer_upgrade_runner.py:238] Failed to upgrade

       

      Also found this in the chef-run.log

       

      [2019-11-18T22:31:28+00:00] ERROR: Running exception handlers

      [2019-11-18T22:31:28+00:00] ERROR: Exception handlers complete

      [2019-11-18T22:31:28+00:00] FATAL: Stacktrace dumped to /tmp/chef-cache/chef-stacktrace.out

      [2019-11-18T22:31:28+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report

      [2019-11-18T22:31:28+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[apt-get-upgrade] (lsb_release::xenial line 41) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '100'

       

      What exactly am I missing here?

       

      any help or tips would be greatly appreciated.