Upgrade from VIC 1.3.1 to 1.4.3 failed because h5 and flex plugin cannot be upgraded

[jitinkumar2018]

Bug Report Basic Information
REQUIRED:

vCenter Server version: 6.5 U2
Embedded or external PSC: No
Filename of the OVA you deployed: v1.4.3-rc1-6053-e7623444
How was the OVA deployed? Flex client
Does the VIC appliance recieve configuration by DHCP? No
What stage of the Appliance Lifecycle is the VIC appliance in? Upgrade
VIC appliance support bundle:
vic_appliance_logs_2018-09-11-13-48-40.tar.gz
Old Version of VIC appliance:
appliance=v1.3.1-3409-132fb13d harbor=harbor-offline-installer-v1.3.0.tgz engine=vic_v1.3.1.tar.gz admiral=vmware/admiral:vic_v1.3.0 6f1d13decebe vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:latest 44e47c4b40ab
New Version of VIC appliance:
appliance=v1.4.3-rc1-6053-e7623444 harbor=harbor-offline-installer-v1.5.3-build.473.tgz engine=vic_v1.4.3-rc1.tar.gz admiral=vmware/admiral:vic_v1.4.3-rc1 b1416b4c9f6a vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:v1.4.3-rc1 5e949e13899a
Were the hard disks from the old appliance moved properly to the new appliance? YES
appliance upgrade script run log:
upgrade.log
Was the new appliance initialized before running the appliance upgrade script? NO

Bug Report Detailed Information
What operation was being performed when the failure was noticed? Upgrade from 1.3.1 to 1.4.3 by manual method.

Steps Taken: Manually moved the disks from old VIC appliance to new VIC appliance as stated in the upgrade document.
Then executed: ./upgrade.sh --manual-disks
and enter yes when it asks to upgrade ui plugin

It hits an error when trying to upgrade flex and h5 plugin

Error: Upgrade failed.

[lgayatri]

Log snippet:

set owner for /etc/vmware/psc/harbor/psc-config.keystore
set perms for /etc/vmware/psc/harbor/psc-config.properties
set owner for /etc/vmware/psc/harbor/psc-config.properties
perms ok for /etc/vmware/psc/harbor/tokens.properties
set owner for /etc/vmware/psc/harbor/tokens.properties
2018-09-11 13:36:02 [=] Finished preparing upgrade environment
2018-09-11 13:36:02 [=] 
-------------------------
Starting VIC UI Plugin Upgrade 2018-09-11 13:33:18 +0000 UTC

register payload - {"vc":"${vc_info}","plugin":"${plugin}"}
2018-09-11 13:36:02 [=] Waiting for upgrade appliance flex plugin...
register payload - {"vc":"${vc_info}","plugin":"${plugin}"}
2018-09-11 13:36:12 [=] Waiting for upgrade appliance flex plugin...
...
register payload - {"vc":"${vc_info}","plugin":"${plugin}"}
2018-09-11 13:40:54 [=] Waiting for upgrade appliance flex plugin...
register payload - {"vc":"${vc_info}","plugin":"${plugin}"}
2018-09-11 13:41:04 [=] WARNING: Plugin upgrade failed for the FLEX client. This is expected on vCenter versions 6.7 or higher.
2018-09-11 13:41:04 [=] WARNING: If you expected this to pass on older versions of vSphere, please check your credentials and try again, or contact VMware Support.
register payload - {"vc":"${vc_info}","plugin":"${plugin}"}
2018-09-11 13:41:04 [=] Waiting for upgrade appliance h5 plugin...
register payload - {"vc":"${vc_info}","plugin":"${plugin}"}
...
2018-09-11 13:45:57 [=] Waiting for upgrade appliance h5 plugin...
register payload - {"vc":"${vc_info}","plugin":"${plugin}"}
2018-09-11 13:46:07 [=] Failed to upgrade appliance h5 plugin. Check vCenter target settings, or contact VMware support.
2018-09-11 13:46:07 [=] 
2018-09-11 13:46:07 [=] -------------------------
2018-09-11 13:46:07 [=] Upgrade failed.
2018-09-11 13:46:07 [=] Please save /var/log/vmware/upgrade.log and contact VMware support.
2018-09-11 13:46:07 [=] -------------------------

[lgayatri]

@renmaosheng

[stuclem]

I think that this might be related to what I found in #2021. I think that the manual method, as documented, is broken since 1.4.1.

[zjs]

It seems like this specific issue may be the result of a quoting error in the upgrade script:

vic-product/installer/build/scripts/upgrade/upgrade.sh

Lines 100 to 101 in 0220fd5

	local payload='{"vc":"${vc}","plugin":"${plugin}"}'
	local payload_info='{"vc":"${vc_info}","plugin":"${plugin}"}'

This causes the JSON object {"vc":"${vc}","plugin":"${plugin}"} to be sent to the register API, instead of a JSON object with ${vc} and ${plugin} properly substituted. (It looks like this was introduced while addressing review comments on #1979; the revised implementation does not appear to have been reviewed.)

I would expect this to cause all upgrades to fail, independently of the issue noted in #2021.

[zjs]

This error is correctly flagged by shellcheck. We should investigate automatically running it in CI (like we've been working towards in vmware/vic-tools). In the meantime, we should be diligent about running it manually when making changes to shell scripts.

In installer/build/scripts/upgrade/upgrade.sh line 97:
  local vc='{"target":"'"${VCENTER_TARGET}"'","user":"'"${VCENTER_USERNAME}"'","password":"'"${VCENTER_PASSWORD}"'","thumbprint":"'"${VCENTER_FINGERPRINT}"'"}'
        ^-- SC2034: vc appears unused. Verify it or export it.


In installer/build/scripts/upgrade/upgrade.sh line 98:
  local vc_info='{"target":"'"${VCENTER_TARGET}"'","user":"'"${VCENTER_USERNAME}"'","thumbprint":"'"${VCENTER_FINGERPRINT}"'"}'
        ^-- SC2034: vc_info appears unused. Verify it or export it.


In installer/build/scripts/upgrade/upgrade.sh line 99:
  local plugin='{"preset":"'"${preset}"'","force":true}'
        ^-- SC2034: plugin appears unused. Verify it or export it.


In installer/build/scripts/upgrade/upgrade.sh line 100:
  local payload='{"vc":"${vc}","plugin":"${plugin}"}'
                ^-- SC2016: Expressions don't expand in single quotes, use double quotes for that.


In installer/build/scripts/upgrade/upgrade.sh line 101:
  local payload_info='{"vc":"${vc_info}","plugin":"${plugin}"}'
                     ^-- SC2016: Expressions don't expand in single quotes, use double quotes for that.

[zjs]

Verified #2053 by applying the patch to the upgrade.sh file and re-running upgrade on that system.

Console Output

root@vic-st-h2-132 [ /etc/vmware/upgrade ]# ./upgrade-patched.sh --manual-disks
-------------------------------
VIC Appliance Upgrade to v1.4.3
-------------------------------
2018-09-11 19:45:07 [=] Values containing $ (dollar sign), ` (backquote), ' (single quote), " (double quote), and \ (backslash) will not be substituted properly.

2018-09-11 19:45:07 [=] Change any input (passwords) containing these values before running this script.

Enter vCenter Server FQDN or IP: w2hs2-vrops08.eng.vmware.com

Enter vCenter Administrator Username: [email protected]

Enter vCenter Administrator Password:

If using an external PSC, enter the FQDN of the PSC instance (leave blank otherwise):

If using an external PSC, enter the PSC Admin Domain (leave blank otherwise):
Please verify the vCenter IP and TLS fingerprint: w2hs2-vrops08.eng.vmware.com 04:59:CA:CF:33:A1:60:B9:17:EC:B4:E2:0C:2D:F8:FA:70:BF:BF:C3

Is the fingerprint correct? (y/n): y

Enter vCenter Datacenter of the old VIC appliance: Datacenter

Enter old VIC appliance IP:

Enter old VIC appliance username:

Upgrade VIC UI Plugin? (y/n): y

2018-09-11 19:50:15 [=]

-------------------------

Starting upgrade 2018-09-11 19:45:07 +0000 UTC
2018-09-11 19:50:15 [=]

2018-09-11 19:50:15 [=] Detected old appliance's version as v1.3.1.

2018-09-11 19:50:15 [=] If the old appliance's version is not detected correctly, please enter "n" to abort the upgrade and contact VMware support.

2018-09-11 19:50:15 [=]

2018-09-11 19:50:15 [=] Do you wish to proceed with upgrade? [y/n]

y

2018-09-11 19:50:20 [=] Continuing with upgrade

2018-09-11 19:50:20 [=]

2018-09-11 19:50:20 [=] Preparing upgrade environment

2018-09-11 19:50:20 [=] Disabling and stopping Admiral and Harbor

2018-09-11 19:50:30 [=] Registering the appliance in PSC

2018-09-11 19:51:02 [=] Finished preparing upgrade environment

2018-09-11 19:51:02 [=]

-------------------------

Starting VIC UI Plugin Upgrade 2018-09-11 19:45:07 +0000 UTC
2018-09-11 19:51:27 [=]

-------------------------

Starting Admiral Upgrade 2018-09-11 19:45:07 +0000 UTC
2018-09-11 19:51:27 [=] Performing pre-upgrade checks

2018-09-11 19:51:27 [=] Starting Admiral upgrade

2018-09-11 19:51:31 [=] Updating Admiral configuration

2018-09-11 19:51:31 [=] Restarting Admiral

2018-09-11 19:52:20 [=]

-------------------------

Starting Harbor Upgrade 2018-09-11 19:45:07 +0000 UTC
2018-09-11 19:52:20 [=] Performing pre-upgrade checks

2018-09-11 19:52:20 [=] Starting Harbor upgrade

2018-09-11 19:52:20 [=] [=] Shutting down Harbor

2018-09-11 19:52:20 [=] [=] Migrating Harbor configuration and data

2018-09-11 19:52:20 [=] Testing database credentials...

2018-09-11 19:52:23 [=] Backing up harbor config...

2018-09-11 19:52:29 [=] [=] Successfully migrated Harbor configuration and data

2018-09-11 19:52:29 [=] Harbor upgrade complete

2018-09-11 19:52:29 [=] Starting Harbor

2018-09-11 19:52:34 [=] Enabling and starting Admiral and Harbor

2018-09-11 19:52:34 [=]

2018-09-11 19:52:34 [=] -------------------------

2018-09-11 19:52:34 [=] Upgrade completed successfully. Exiting. All vSphere Client users must log out and log back in again twice to see the vSphere Integrated Containers plug-in.

2018-09-11 19:52:34 [=] -------------------------

2018-09-11 19:52:34 [=]

upgrade.log

2018-09-11 19:50:15 [=] 
-------------------------
Starting upgrade 2018-09-11 19:45:07 +0000 UTC
2018-09-11 19:50:15 [=]

2018-09-11 19:50:15 [=] Detected old appliance's version as v1.3.1.

2018-09-11 19:50:15 [=] If the old appliance's version is not detected correctly, please enter "n" to abort the upgrade and contact VMware support.

2018-09-11 19:50:15 [=]

2018-09-11 19:50:15 [=] Do you wish to proceed with upgrade? [y/n]

2018-09-11 19:50:20 [=] Continuing with upgrade

2018-09-11 19:50:20 [=]

2018-09-11 19:50:20 [=] Preparing upgrade environment

2018-09-11 19:50:20 [=] Disabling and stopping Admiral and Harbor

2018-09-11 19:50:30 [=] Registering the appliance in PSC

register payload - {"target":"w2hs2-vrops08.eng.vmware.com","user":"[email protected]","thumbprint":"04:59:CA:CF:33:A1:60:B9:17:EC:B4:E2:0C:2D:F8:FA:70:BF:BF:C3","externalpsc":"","pscdomain":""}

[0][I][2018-09-11T19:50:50.450Z][1][SsoPscCommand][getToken][Initializing...]

[1][I][2018-09-11T19:50:50.485Z][1][PscSettings][validateConfig][PSC configuration:]

[2][I][2018-09-11T19:50:50.485Z][1][PscSettings][validateConfig][- client: harbor]

[3][I][2018-09-11T19:50:50.485Z][1][PscSettings][validateConfig][- domainController: w2hs2-vrops08.eng.vmware.com]

[4][I][2018-09-11T19:50:50.485Z][1][PscSettings][validateConfig][- domainControllerPort: 443]

[5][I][2018-09-11T19:50:50.485Z][1][PscSettings][validateConfig][- keystoreFile: /etc/vmware/psc/harbor/psc-config.keystore]

[6][I][2018-09-11T19:50:50.485Z][1][PscSettings][validateConfig][- solutionUser: harbor-9281caef-bc01-4c53-82d4-0c69e63cfb12]

[7][I][2018-09-11T19:50:50.485Z][1][PscSettings][validateConfig][- tenant: vsphere.local]

[8][I][2018-09-11T19:50:50.712Z][1][SsoPscCommand][getToken][Getting SSO cert...]

[9][I][2018-09-11T19:50:50.961Z][1][SsoPscCommand][getToken][Building STSAdapter...]

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[10][I][2018-09-11T19:50:51.568Z][1][SsoPscCommand][getToken][Getting SAML token...]

log4j:WARN No appenders could be found for logger (org.springframework.web.client.RestTemplate).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

[11][I][2018-09-11T19:50:54.382Z][1][SsoPscCommand][getToken][Done! Token stored in '/etc/vmware/psc/harbor/tokens.properties'.]

[0][I][2018-09-11T19:50:54.667Z][1][SsoPscCommand][getToken][Initializing...]

[1][I][2018-09-11T19:50:54.711Z][1][PscSettings][validateConfig][PSC configuration:]

[2][I][2018-09-11T19:50:54.711Z][1][PscSettings][validateConfig][- client: engine]

[3][I][2018-09-11T19:50:54.711Z][1][PscSettings][validateConfig][- domainController: w2hs2-vrops08.eng.vmware.com]

[4][I][2018-09-11T19:50:54.712Z][1][PscSettings][validateConfig][- domainControllerPort: 443]

[5][I][2018-09-11T19:50:54.712Z][1][PscSettings][validateConfig][- keystoreFile: /etc/vmware/psc/engine/psc-config.keystore]

[6][I][2018-09-11T19:50:54.712Z][1][PscSettings][validateConfig][- solutionUser: engine-15abf323-7d05-4c8b-b25e-3070aa6905ef]

[7][I][2018-09-11T19:50:54.712Z][1][PscSettings][validateConfig][- tenant: vsphere.local]

[8][I][2018-09-11T19:50:54.970Z][1][SsoPscCommand][getToken][Getting SSO cert...]

[9][I][2018-09-11T19:50:55.247Z][1][SsoPscCommand][getToken][Building STSAdapter...]

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[10][I][2018-09-11T19:50:55.770Z][1][SsoPscCommand][getToken][Getting SAML token...]

log4j:WARN No appenders could be found for logger (org.springframework.web.client.RestTemplate).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

[11][I][2018-09-11T19:50:58.412Z][1][SsoPscCommand][getToken][Done! Token stored in '/etc/vmware/psc/engine/tokens.properties'.]

[0][I][2018-09-11T19:50:58.720Z][1][SsoPscCommand][getToken][Initializing...]

[1][I][2018-09-11T19:50:58.755Z][1][PscSettings][validateConfig][PSC configuration:]

[2][I][2018-09-11T19:50:58.756Z][1][PscSettings][validateConfig][- client: admiral]

[3][I][2018-09-11T19:50:58.756Z][1][PscSettings][validateConfig][- domainController: w2hs2-vrops08.eng.vmware.com]

[4][I][2018-09-11T19:50:58.756Z][1][PscSettings][validateConfig][- domainControllerPort: 443]

[5][I][2018-09-11T19:50:58.756Z][1][PscSettings][validateConfig][- keystoreFile: /etc/vmware/psc/admiral/psc-config.keystore]

[6][I][2018-09-11T19:50:58.756Z][1][PscSettings][validateConfig][- solutionUser: admiral-85e34bbf-9dcd-4fa5-9aa5-1dde275d7b18]

[7][I][2018-09-11T19:50:58.756Z][1][PscSettings][validateConfig][- tenant: vsphere.local]

[8][I][2018-09-11T19:50:58.994Z][1][SsoPscCommand][getToken][Getting SSO cert...]

[9][I][2018-09-11T19:50:59.255Z][1][SsoPscCommand][getToken][Building STSAdapter...]

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[10][I][2018-09-11T19:50:59.781Z][1][SsoPscCommand][getToken][Getting SAML token...]

log4j:WARN No appenders could be found for logger (org.springframework.web.client.RestTemplate).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

[11][I][2018-09-11T19:51:02.066Z][1][SsoPscCommand][getToken][Done! Token stored in '/etc/vmware/psc/admiral/tokens.properties'.]

perms ok for /etc/vmware/psc/admiral/psc-config.keystore

owner ok for /etc/vmware/psc/admiral/psc-config.keystore

perms ok for /etc/vmware/psc/admiral/psc-config.properties

owner ok for /etc/vmware/psc/admiral/psc-config.properties

perms ok for /etc/vmware/psc/admiral/tokens.properties

owner ok for /etc/vmware/psc/admiral/tokens.properties

perms ok for /etc/vmware/psc/engine/psc-config.keystore

owner ok for /etc/vmware/psc/engine/psc-config.keystore

perms ok for /etc/vmware/psc/engine/psc-config.properties

owner ok for /etc/vmware/psc/engine/psc-config.properties

perms ok for /etc/vmware/psc/engine/tokens.properties

owner ok for /etc/vmware/psc/engine/tokens.properties

perms ok for /etc/vmware/psc/harbor/psc-config.keystore

owner ok for /etc/vmware/psc/harbor/psc-config.keystore

perms ok for /etc/vmware/psc/harbor/psc-config.properties

owner ok for /etc/vmware/psc/harbor/psc-config.properties

perms ok for /etc/vmware/psc/harbor/tokens.properties

owner ok for /etc/vmware/psc/harbor/tokens.properties

2018-09-11 19:51:02 [=] Finished preparing upgrade environment

2018-09-11 19:51:02 [=]

-------------------------

Starting VIC UI Plugin Upgrade 2018-09-11 19:45:07 +0000 UTC
register payload - {"vc":{"target":"w2hs2-vrops08.eng.vmware.com","user":"[email protected]","thumbprint":"04:59:CA:CF:33:A1:60:B9:17:EC:B4:E2:0C:2D:F8:FA:70:BF:BF:C3"},"plugin":{"preset":"FLEX","force":true}}

register payload - {"vc":{"target":"w2hs2-vrops08.eng.vmware.com","user":"[email protected]","thumbprint":"04:59:CA:CF:33:A1:60:B9:17:EC:B4:E2:0C:2D:F8:FA:70:BF:BF:C3"},"plugin":{"preset":"H5","force":true}}

2018-09-11 19:51:27 [=]

-------------------------

Starting Admiral Upgrade 2018-09-11 19:45:07 +0000 UTC
2018-09-11 19:51:27 [=] Performing pre-upgrade checks

2018-09-11 19:51:27 [=] Starting Admiral upgrade

2018-09-11 19:51:31 [=] Updating Admiral configuration

2018-09-11 19:51:31 [=] Restarting Admiral

2018-09-11 19:52:20 [=]

-------------------------

Starting Harbor Upgrade 2018-09-11 19:45:07 +0000 UTC
Getting password from harbor.cfg

2018-09-11 19:52:20 [=] Performing pre-upgrade checks

2018-09-11 19:52:20 [=] Starting Harbor upgrade

2018-09-11 19:52:20 [=] [=] Shutting down Harbor

2018-09-11 19:52:20 [=] [=] Migrating Harbor configuration and data

2018-09-11 19:52:20 [=] Testing database credentials...

Trying to start mysql server...

Waiting for MySQL start...

2018-09-11 19:52:21 140737353451456 [Note] mysqld (mysqld 10.2.14-MariaDB) starting as process 8 ...

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Uses event mutexes

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Number of pools: 1

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Using SSE2 crc32 instructions

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Completed initialization of buffer pool

2018-09-11 19:52:21 140736424679168 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2018-09-11 19:52:21 140737353451456 [Note] InnoDB: Highest supported file format is Barracuda.

2018-09-11 19:52:22 140737353451456 [Note] InnoDB: 128 out of 128 rollback segments are active.

2018-09-11 19:52:22 140737353451456 [Note] InnoDB: Creating shared tablespace for temporary tables

2018-09-11 19:52:22 140737353451456 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2018-09-11 19:52:22 140737353451456 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2018-09-11 19:52:22 140737353451456 [Note] InnoDB: 5.7.21 started; log sequence number 1874458

2018-09-11 19:52:22 140735517017856 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2018-09-11 19:52:22 140737353451456 [Note] Plugin 'FEEDBACK' is disabled.

2018-09-11 19:52:22 140737353451456 [Note] Server socket created on IP: '::'.

2018-09-11 19:52:22 140737353451456 [Note] Reading of all Master_info entries succeded

2018-09-11 19:52:22 140737353451456 [Note] Added new Master_info '' to hash table

2018-09-11 19:52:22 140737353451456 [Note] mysqld: ready for connections.

Version: '10.2.14-MariaDB'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

2018-09-11 19:52:22 140735517017856 [Note] InnoDB: Buffer pool(s) load completed at 180911 19:52:22

DB test passed.

Success to validate harbor.cfg.

2018-09-11 19:52:23 [=] Backing up harbor config...

Trying to start mysql server...

Waiting for MySQL start...

2018-09-11 19:52:24 140737353451456 [Note] mysqld (mysqld 10.2.14-MariaDB) starting as process 8 ...

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Uses event mutexes

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Number of pools: 1

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Using SSE2 crc32 instructions

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Completed initialization of buffer pool

2018-09-11 19:52:24 140736433071872 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Highest supported file format is Barracuda.

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1874458

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: 128 out of 128 rollback segments are active.

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Creating shared tablespace for temporary tables

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2018-09-11 19:52:24 140737353451456 [Note] InnoDB: 5.7.21 started; log sequence number 1874477

2018-09-11 19:52:24 140735517017856 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2018-09-11 19:52:24 140737353451456 [Note] Plugin 'FEEDBACK' is disabled.

2018-09-11 19:52:24 140737353451456 [Note] Recovering after a crash using tc.log

2018-09-11 19:52:24 140737353451456 [Note] Starting crash recovery...

2018-09-11 19:52:24 140737353451456 [Note] Crash recovery finished.

2018-09-11 19:52:24 140737353451456 [Note] Server socket created on IP: '::'.

2018-09-11 19:52:24 140737353451456 [Note] Reading of all Master_info entries succeded

2018-09-11 19:52:24 140737353451456 [Note] Added new Master_info '' to hash table

2018-09-11 19:52:24 140737353451456 [Note] mysqld: ready for connections.

Version: '10.2.14-MariaDB'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

2018-09-11 19:52:24 140735517017856 [Note] InnoDB: Buffer pool(s) load completed at 180911 19:52:24

Performing backup...

Backup performed.

Success to backup harbor.cfg.

Trying to start mysql server...

Waiting for MySQL start...

2018-09-11 19:52:25 140737353451456 [Note] mysqld (mysqld 10.2.14-MariaDB) starting as process 11 ...

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Uses event mutexes

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Number of pools: 1

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Using SSE2 crc32 instructions

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Completed initialization of buffer pool

2018-09-11 19:52:25 140736433071872 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Highest supported file format is Barracuda.

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1874458

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: 128 out of 128 rollback segments are active.

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Creating shared tablespace for temporary tables

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2018-09-11 19:52:25 140737353451456 [Note] InnoDB: 5.7.21 started; log sequence number 1874477

2018-09-11 19:52:25 140735517017856 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2018-09-11 19:52:25 140737353451456 [Note] Plugin 'FEEDBACK' is disabled.

2018-09-11 19:52:25 140737353451456 [Note] Recovering after a crash using tc.log

2018-09-11 19:52:25 140737353451456 [Note] Starting crash recovery...

2018-09-11 19:52:25 140737353451456 [Note] Crash recovery finished.

2018-09-11 19:52:25 140737353451456 [Note] Server socket created on IP: '::'.

2018-09-11 19:52:25 140737353451456 [Note] Reading of all Master_info entries succeded

2018-09-11 19:52:25 140737353451456 [Note] Added new Master_info '' to hash table

2018-09-11 19:52:25 140737353451456 [Note] mysqld: ready for connections.

Version: '10.2.14-MariaDB'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

2018-09-11 19:52:25 140735517017856 [Note] InnoDB: Buffer pool(s) load completed at 180911 19:52:25

Version is not specified. Default version is head.

Performing upgrade head...

INFO  [alembic.runtime.migration] Context impl MySQLImpl.

INFO  [alembic.runtime.migration] Will assume non-transactional DDL.

1.3.0

INFO  [alembic.runtime.migration] Context impl MySQLImpl.

INFO  [alembic.runtime.migration] Will assume non-transactional DDL.

INFO  [alembic.runtime.migration] Running upgrade 1.3.0 -> 1.4.0, 1.3.0 to 1.4.0

INFO  [alembic.runtime.migration] Running upgrade 1.4.0 -> 1.5.0, 1.4.0 to 1.5.0

deployed with admiral, migrating all replication policies with manual trigger

INFO  [alembic.runtime.migration] Context impl MySQLImpl.

INFO  [alembic.runtime.migration] Will assume non-transactional DDL.

1.5.0 (head)

Upgrade performed.

input version: 1.3.0, migrator chain: ['1.5.0']

migrating to version 1.5.0

Written new values to /harbor-migration/harbor-cfg/harbor.cfg

The path of the migrated harbor.cfg is not set, the input file will be overwritten.

2018-09-11 19:52:29 [=] [=] Successfully migrated Harbor configuration and data

2018-09-11 19:52:29 [=] Harbor upgrade complete

2018-09-11 19:52:29 [=] Starting Harbor

Old data version: appliance=v1.3.1-3409-132fb13d

harbor=harbor-offline-installer-v1.3.0.tgz

engine=vic_v1.3.1.tar.gz

admiral=vmware/admiral:vic_v1.3.0 6f1d13decebe

vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:latest 44e47c4b40ab

admiral=vmware/admiral:vic_v1.4.3-rc1 b1416b4c9f6a

vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:v1.4.3-rc1 5e949e13899a

Set new data version: appliance=v1.4.3-rc1-6053-e7623444

harbor=harbor-offline-installer-v1.5.3-build.473.tgz

engine=vic_v1.4.3-rc1.tar.gz

admiral=vmware/admiral:vic_v1.4.3-rc1 b1416b4c9f6a

vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:v1.4.3-rc1 5e949e13899a

2018-09-11 19:52:34 [=] Enabling and starting Admiral and Harbor

Created symlink from /etc/systemd/system/vic-appliance.target.wants/admiral.service to /usr/lib/systemd/system/admiral.service.

Created symlink from /etc/systemd/system/vic-appliance.target.wants/harbor.service to /usr/lib/systemd/system/harbor.service.

2018-09-11 19:52:34 [=]

2018-09-11 19:52:34 [=] -------------------------

2018-09-11 19:52:34 [=] Upgrade completed successfully. Exiting. All vSphere Client users must log out and log back in again twice to see the vSphere Integrated Containers plug-in.

2018-09-11 19:52:34 [=] -------------------------

2018-09-11 19:52:34 [=]

[jitinkumar2018]

@lgayatri @wjun @stuclem Upgrade from 1.3.1 to 1.4.3 successful on Scale Testbed with latest RC1 build vic-dev-v1.4.3-rc1-6137-ea764a69.ova.

[stuclem]

Great! Doc update in progress in #2021