7.0.1
Table Of Contents
- Upgrading from vRealize Automation 7.0 to 7.0.1
- Contents
- Updated Information
- Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Reconfigure External Workflow Timeouts
- Verify That vRealize Orchestrator Service is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL Environment
- Ensure Deployed Virtual Machines Register With Software Service
- Restore Changes to Logging
- Troubleshooting the Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not Available to Request
Perform this procedure for each replica appliance node sequentially, and then for the master node.
Note When you perform this procedure, you might see these warning messages:
n
WARNING: Re-reading the partition table failed with error 16:
Device or resource busy. The kernel still uses the old table. The
new table will be used at the next reboot or after you run
partprobe(8) or kpartx(8) Syncing disks.
n
Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel
of the change, probably because it/they are in use. As a result, the old partition(s) will remain
in use. You should reboot now before making further changes.
Ignore this message: You should reboot now before making further changes. If you reboot your system
before step 10, you will corrupt the upgrade process.
Procedure
1 Power on and SSH login to the vRealize Automation appliance.
2 Stop all vRealize Automation services.
a service vcac-server stop
b service vco-server stop
c service vpostgres stop
3 Unmount the swap partition:
swapoff -a
4 Delete the existing Disk 1 partitions and create a 44 GB root partition and a 6 GB swap partition:
(echo d; echo 2; echo d; echo 1; echo n; echo p; echo ; echo ; echo '+44G'; echo
n; echo p; echo ; echo ; echo ; echo w; echo p; echo q) | fdisk /dev/sda
5 Change the swap partition type.
(echo t; echo 2; echo 82; echo w; echo p; echo q) | fdisk /dev/sda
6 Set the Disk 1 bootable flag:
(echo a; echo 1; echo w; echo p; echo q) | fdisk /dev/sda
7 Register the partition changes with the Linux kernel.
partprobe
Note If you see a message telling you to reboot before you make further changes, ignore the
message. Rebooting the system before step 10 corrupts the upgrade process.
8 Format the new swap partition.
mkswap /dev/sda2
Upgrading from vRealize Automation 7.0 to 7.0.1
VMware, Inc. 15