Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
This article covers the fixes made in VMware Aria Operations 8.12.1 from previous versions.VMware Aria Operations 8.12.1 contains all previous fixes from VMware Aria Operations 8.12 Hot Fix 1, plus addresses the following issues: Scoreboard widget is throwing JS exception when double clicking on sparkline.Analytics Forward Data Region used for the time-series data coming from the CP.[Log Integration] [Certificate] Auto-accept of imported certificate doesn't work properly for the VMware Aria Operations for Logs Cloud Account.The cluster costs are incorrect incase of hybrid clouds during the crossover of billing cycle.Absent comma in the scripts.python.cprcReEncryptPassword.main().Empty widgets on Multi-Cloud Overview page.Reconfiguring HA proxy even if there is no certificate change.In hybrid clouds, the cluster costs when added up do not match with the billing expenses.[CP] - /var/log/auth.log rotation needs to happen more frequently.suite-api catalina.out log path is incorrect.Handle statementCycle param in Statement Bill v3 API correctly as MM/YYYY and not M/YYYY for single digit months (Jan to Sept).[GCP MP] As per Platform Safegaurd, one property is changing every collection cycle.Billing collection is stopped in case API token for GCVE adapter is from ORG Owner.[VMware Aria Operations Cloud] [CAS MP] Two vRA OOTB dashboard data are impacted, with missing widget information, after upgrading VMware Aria Operations Cloud.Upgrade Summary report is not generated.VMware Aria Operations for Logs instance/cloud account creation is failing in VMware Aria Operations onPrem, with FIPS on option.[NSX-T MP] Duplicate Metric Definition in describe.xml.[Rest API support] Add Workload automation network settings to policy import/export. The following CVEs have been resolved as of VMware Aria Operations 8.12.1: Component NameCVEcontainerdCVE-2023-24540CVE-2023-29400CVE-2023-24539CVE-2023-24534CVE-2023-24536CVE-2022-41720CVE-2022-41725CVE-2023-24537CVE-2023-24538CVE-2023-24532CVE-2022-41722CVE-2022-41724haproxyCVE-2023-0056CVE-2023-0836linuxCVE-2018-19406CVE-2023-2483CVE-2023-2248CVE-2022-29900CVE-2022-29901CVE-2023-2124CVE-2023-32233CVE-2023-1859CVE-2023-31436CVE-2023-2269CVE-2023-2177CVE-2023-1989CVE-2023-30456CVE-2023-1611CVE-2023-1076CVE-2022-4269net-snmpCVE-2022-44793CVE-2022-44792net.minidev:json-smartCVE-2021-27568org.codehaus.jettison:jettisonCVE-2023-1436org.hsqldb:hsqldbCVE-2022-41853org.springframework:spring-coreCVE-2023-20861org.springframework.security:spring-security-coreCVE-2023-20862org.springframework.security:spring-security-webCVE-2023-20862rpm-libsCVE-2021-20271vimCVE-2022-2571CVE-2022-2923CVE-2022-2862CVE-2022-3234CVE-2022-3297CVE-2022-2286CVE-2022-2345CVE-2022-2581CVE-2022-2522CVE-2022-2816CVE-2022-2288CVE-2022-2580CVE-2022-2817CVE-2022-2980CVE-2022-2264CVE-2022-2285CVE-2022-2284CVE-2022-2257CVE-2022-2287CVE-2022-3037CVE-2022-2344CVE-2022-2849CVE-2022-3134CVE-2022-2343CVE-2022-2874CVE-2022-4293CVE-2022-3099CVE-2022-4141CVE-2022-3235CVE-2022-3256CVE-2022-3491CVE-2022-3278CVE-2022-3352CVE-2022-2289CVE-2022-3016CVE-2022-2845CVE-2022-3153CVE-2022-2982CVE-2022-2598CVE-2022-3705CVE-2022-3296CVE-2022-2889CVE-2023-2610CVE-2023-2426CVE-2023-1264CVE-2023-1175CVE-2023-1170CVE-2022-2304webkitCVE-2023-32409
VMware Aria Operations 8.12 can be applied to any 8.6.x - 8.10.x environment.It is recommended to take snapshots following How to take a Snapshot of VMware Aria Operations before upgrading. Download the VMware Aria Operations 8.12 upgrade PAK file from VMware Downloads.Log in to the master node VMware Aria Operations Administrator interface of your cluster at https://master-node-FQDN-or-IP-address/admin.Click Software Update in the left panel.Click Install a Software Update in the main panel.Follow the steps in the wizard to locate and install your PAK file.Install the product update PAK file. Wait for the software update to complete. When it does, the Administrator interface logs you out.Log back into the master node Administrator interface. The main Cluster Status page appears and cluster goes online automatically. The status page also displays the Bring Online button, but do not click it. Clear the browser caches and if the browser page does not refresh automatically, refresh the page. The cluster status changes to Going Online. When the cluster status changes to Online, the upgrade is complete. Note: If a cluster fails and the status changes to offline during the installation process of a PAK file update then some nodes become unavailable. To fix this, you can access the Administrator interface and manually take the cluster offline and click Finish Installation to continue the installation process. Click Software Update to check that the update is done. A message indicating that the update completed successfully appears in the main pane.
Once the update is complete, delete the snapshots you made before the software update.