VMware Aria Operations for Logs 8.14.1
search cancel

VMware Aria Operations for Logs 8.14.1

book

Article ID: 338305

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article covers the changes made in VMware Aria Operations for Logs 8.14.1 from previous versions.

The following issues have been resolved as of vRealize Operations for Logs 8.14.1:
  • VMware Aria Operations for Logs cannot connect to a webhook server with a self-signed certificate.
You cannot integrate VMware Aria Operations for Logs with a webhook server that uses a self-signed certificate as the self-signed certificate is not trusted.
  • The triggered alert is listed in the history but not delivered to VMware Aria Operations and email.
After integrating the VMware Aria Operations for Logs 8.10.2 version with VMware Aria Operations, when you configure an alert, add extracted fields to the alert query, and trigger an alert, the alert is not delivered to the email recipients and to the VMware Aria Operations user interface.
  • The first token in the vCenter Server logs is truncated when forwarded from VMware Aria Operations for Logs using the Syslog format.
If the VMware Aria Operations for Logs forwarder is configured to use Syslog forwarding, the first token in the vCenter Server logs may be truncated at the forwarding destination.
  • The test alert sent to a webhook URL fails because of basic authentication issues.
When you create a webhook of Custom endpoint type, add basic authentication to the webhook, and then test the alert, the alert fails. This happens when the credentials are rejected because of basic authentication issues.
  • While attempting to import archived logs, the import process became stuck and never reached completion.
When you are importing a large number of archived events back into VMware Aria Operations for Logs, the standard log importer tool fails, and displays a message such as
failed to import parsed messages from 0 to 1000 in the /var/log/loginsight/importer.log file.
Additionally, the importer does not take into account disk blocks or ingestion speed.

The following CVEs have been resolved as of vRealize Operations for Logs 8.14.1:
Component Name CVE
berkeleydb CVE-2016-0682
CVE-2016-0689
CVE-2016-0692
CVE-2016-0694
CVE-2016-3418
CVE-2017-3604
CVE-2017-3605
CVE-2017-3606
CVE-2017-3607
CVE-2017-3608
CVE-2017-3609
CVE-2017-3610
CVE-2017-3611
CVE-2017-3612
CVE-2017-3613
CVE-2017-3614
CVE-2017-3615
CVE-2017-3616
CVE-2017-3617
bind CVE-2023-2828
CVE-2023-2829
CVE-2023-2911
c-ares CVE-2020-8277
CVE-2021-3672
CVE-2022-4904
CVE-2023-31124
CVE-2023-31130
CVE-2023-31147
CVE-2023-32067
cloud-init CVE-2023-1786
com.fasterxml.jackson.core:jackson-databind CVE-2020-36518
CVE-2021-46877
commons-io:commons-io CVE-2021-29425
curl CVE-2020-8169
CVE-2020-8177
CVE-2020-8231
CVE-2020-8284
CVE-2020-8285
CVE-2020-8286
CVE-2021-22876
CVE-2021-22890
CVE-2021-22897
CVE-2021-22898
CVE-2021-22922
CVE-2021-22923
CVE-2021-22924
CVE-2021-22925
CVE-2021-22926
CVE-2021-22946
CVE-2021-22947
CVE-2022-22576
CVE-2022-27774
CVE-2022-27775
CVE-2022-27776
CVE-2022-27781
CVE-2022-27782
CVE-2022-32206
CVE-2022-32208
CVE-2022-32221
CVE-2022-35252
CVE-2022-43552
CVE-2023-23916
CVE-2023-27533
CVE-2023-27534
CVE-2023-27535
CVE-2023-27536
CVE-2023-27537
CVE-2023-27538
CVE-2023-28319
CVE-2023-28320
CVE-2023-28321
CVE-2023-28322
expat CVE-2013-0340
gcc CVE-2019-14250
giflib CVE-2023-39742
grub2 CVE-2015-8370
jdk-openjdk CVE-2023-21930
CVE-2023-21937
CVE-2023-21938
CVE-2023-21939
CVE-2023-21954
CVE-2023-21967
CVE-2023-21968
CVE-2023-22025
CVE-2023-22041
CVE-2023-22043
CVE-2023-22044
CVE-2023-22045
CVE-2023-22049
CVE-2023-22067
CVE-2023-22081
json-c CVE-2020-12762
CVE-2021-32292
jvm-hotspot-openjdk CVE-2023-21930
CVE-2023-21937
CVE-2023-21938
CVE-2023-21939
CVE-2023-21954
CVE-2023-21967
CVE-2023-21968
CVE-2023-22025
CVE-2023-22041
CVE-2023-22043
CVE-2023-22044
CVE-2023-22045
CVE-2023-22049
CVE-2023-22067
CVE-2023-22081
kerberos CVE-2023-36054
libcap CVE-2023-2602
CVE-2023-2603
libtiff CVE-2022-2056
CVE-2022-2057
CVE-2022-2058
CVE-2022-2953
CVE-2022-34526
CVE-2022-3570
CVE-2022-3597
CVE-2022-3598
CVE-2022-3599
CVE-2022-3626
CVE-2022-3627
CVE-2022-3970
CVE-2022-4645
CVE-2022-48281
CVE-2023-0795
CVE-2023-0796
CVE-2023-0797
CVE-2023-0798
CVE-2023-0799
CVE-2023-0800
CVE-2023-0801
CVE-2023-0802
CVE-2023-0803
CVE-2023-0804
CVE-2023-1916
CVE-2023-26965
CVE-2023-2731
CVE-2023-2908
CVE-2023-30775
CVE-2023-3316
CVE-2023-3576
CVE-2023-3618
libuv CVE-2020-8252
libwebp CVE-2023-1999
linux-pam CVE-2020-27780
CVE-2020-36394
CVE-2022-28321
linux_kernel CVE-2015-2877
CVE-2015-7312
CVE-2018-5407
CVE-2019-20794
CVE-2020-12364
CVE-2020-26140
CVE-2020-26141
CVE-2020-26145
CVE-2020-36691
CVE-2021-20177
CVE-2021-29155
CVE-2021-3669
CVE-2021-4148
CVE-2021-4150
CVE-2022-0168
CVE-2022-1280
CVE-2022-20166
CVE-2022-2327
CVE-2022-29900
CVE-2022-29901
CVE-2022-3169
CVE-2022-39188
CVE-2022-40982
CVE-2022-4129
CVE-2022-4269
CVE-2022-4744
CVE-2022-48502
CVE-2023-0030
CVE-2023-1076
CVE-2023-1077
CVE-2023-1206
CVE-2023-1582
CVE-2023-1611
CVE-2023-1859
CVE-2023-1989
CVE-2023-2002
CVE-2023-2007
CVE-2023-20569
CVE-2023-20588
CVE-2023-20593
CVE-2023-2124
CVE-2023-2163
CVE-2023-2176
CVE-2023-2177
CVE-2023-2269
CVE-2023-23000
CVE-2023-2513
CVE-2023-3022
CVE-2023-30456
CVE-2023-3090
CVE-2023-3111
CVE-2023-31436
CVE-2023-32249
CVE-2023-32251
CVE-2023-32253
CVE-2023-32255
CVE-2023-32256
CVE-2023-3268
CVE-2023-3338
CVE-2023-3390
CVE-2023-34256
CVE-2023-35001
CVE-2023-3609
CVE-2023-3611
CVE-2023-3772
CVE-2023-3776
CVE-2023-3866
CVE-2023-39194
CVE-2023-40283
CVE-2023-4128
CVE-2023-4206
CVE-2023-4207
CVE-2023-4208
CVE-2023-4732
ncurses CVE-2019-17594
CVE-2019-17595
CVE-2021-39537
CVE-2022-29458
CVE-2023-29491
nss CVE-2019-11729
CVE-2019-11745
CVE-2022-38476
numpy CVE-2021-34141
open-vm-tools CVE-2023-20900
openssl CVE-2019-1551
CVE-2020-1968
CVE-2020-1971
CVE-2021-23839
CVE-2021-23840
CVE-2021-23841
CVE-2021-3712
CVE-2021-4160
CVE-2022-0778
CVE-2022-1292
CVE-2022-2068
CVE-2022-4304
CVE-2023-0215
CVE-2023-0286
CVE-2023-0464
CVE-2023-0465
CVE-2023-0466
org.apache.activemq:activemq-core CVE-2023-46604
org.apache.cassandra:apache-cassandra CVE-2023-30601
org.eclipse.jetty:jetty-server CVE-2020-27216
CVE-2020-27218
CVE-2020-27223
CVE-2021-28165
CVE-2021-28169
CVE-2021-34428
CVE-2022-2047
CVE-2022-2048
CVE-2023-26048
CVE-2023-26049
CVE-2023-36478
CVE-2023-36479
CVE-2023-40167
org.hsqldb:hsqldb CVE-2022-41853
org.xerial.snappy:snappy-java CVE-2023-34453
CVE-2023-34454
CVE-2023-34455
org.yaml:snakeyaml CVE-2017-18640
pcre CVE-2019-20838
CVE-2020-14155
perl CVE-2023-31484
CVE-2023-31486
python CVE-2007-4559
CVE-2018-25032
CVE-2022-48560
CVE-2022-48564
CVE-2022-48565
CVE-2022-48566
CVE-2023-24329
CVE-2023-27043
sudo CVE-2023-28486
CVE-2023-28487
sysstat CVE-2023-33204
systemd CVE-2019-14899
CVE-2023-26604
tinyxml CVE-2021-42260
unzip CVE-2022-0529
CVE-2022-0530
util-linux CVE-2020-21583
xz CVE-2022-1271


Environment

VMware Aria Operations for Logs 8.14.x

Resolution

Prerequisites

  • Create a snapshot or backup copy of the VMware Aria Operations for Logs virtual appliance(s)
  • Obtain a copy of the VMware Aria Operations for Logs upgrade bundle .pak file for the release you are upgrading to
  • Verify that you are logged in to the VMware Aria Operations for Logs web user interface as a user with the Edit Admin permission. The URL format is https://log-insight-host, where log-insight-host is the IP address or host name of the primary node of the VMware Aria Operations for Logs virtual cluster.
  • Make a note of any nodes you are upgrading that are in maintenance mode. Ensure you take all nodes out of maintenance mode prior to the upgrade.  When the upgrade is finished, you may move them from the state Connected to Maintenance mode.

 

Procedure

  1. Download the upgrade .pak file from the Broadcom Support Portal.
  2. Under Management, click Cluster.
  3. Click 'Upgrade Cluster' to upload the pak file.
  4. Accept the new EULA to complete the upgrade procedure.

What to do next

  • After the primary node upgrade process is complete, you can view the remaining upgrade process, which is automatic.
  • Check for the email sent to the Admin to confirm the upgrade completed successfully.
  • After upgrade, all nodes are brought online even if they were in maintenance mode before the upgrade. Move these nodes back to maintenance mode as needed.
  • Remove the snapshots from the VMware Aria Operations for Logs appliance(s) within ~72 hours after a successful upgrade to avoid performance issues

Additional Information

Once the update is complete, delete the snapshots you made before the software update.