Search Results

VMware Cloud Foundation 5.2.1 has just been released. omponent Version What’s New Relevant Links SDDC Manager 5.2.1 Reduced Downtime Upgrade (RDU) support for vCenter NSX in-place upgrades for clusters that use vSphere Lifecycle Manager baselines Support for vSphere Lifecycle Manager baseline and vSphere Lifecycle Manager image-based clusters in same workload domain. Support for the "License Now" option for vSAN add-on licenses based on capacity per tebibyte (TiB) Set up VMware Private AI Foundation infrastructure from the vSphere Client Manage all SDDC certificates and passwords from a single UI Release Notes VCF 5.2.1 Build Number 24307856 vCenter Server 8.0u3c Resolves an issue with the vSphere Client becoming unresponsive when a session stays idle for more than 50 minutes Built on top of VC 8.0u3b which delivered critical security fixes resolving  CVE-2024-38812 and CVE-2024-38813 and bug fixes. Release Notes VC 8.0U3c Build Number 24305161   ESXi 8.0u3b Bugs and Security Fixes DPU/SmartNIC :VMware vSphere Distributed Services Engine support with NVIDIA Bluefield-3 DPUs Design improvements for cloud-init guestInfo variables Release Notes ESXi 8.0U3b Build Number  24280767  NSX 4.2.1 NSX now supports a number of enhancements that help the customer provide high availability for networking including TEP Groups, monitoring for dual DPU deployments, improved alarms on the NSX Edge. As part of our multi-tenancy feature set we now offer the exposure of NSX Projects as folders in vCenter. NSX now supports VRF configuration at the Global Manager level. This allows customers a single place to configure stretched T0 Gateways. Invoke NSX In-Place Upgrades on non-VLCM clusters now in a VCF environment, and leverage faster upgrades of NSX enabled hypervisors without having to migrate your workloads. Release Notes NSX 4.2.1 Build Number 24304122   VMware Aria Suite Lifecycle  8.18 with updated versions of the following: Supported with PSPAK 3 Product Support Pack 3 adds support for:            VMware Aria Automation 8.18.1            VMware Aria Orchestrator 8.18.1            VMware Aria Operations for Networks 6.14.0 Release Notes VMware Aria Suite Lifecycle 8.18 Product Support Pack Build Number 24286744 VMware Aria Automation 8.18.1 NSX network and security group automation with discovered resources from NSX Projects and VPCs Onboarding of vSphere namespaces to be used in the Cloud Consumption Interface Support 64 disks on Paravirtual SCSI (PVSCSI) controller Include DGCM Exporter by default in Deep Learning VM Release Notes vRA 8.18.1 Build Number  24280767  VMware Aria Operations 8.18.1 Resolves important security and functionality issues. Release Notes Aria Ops 8.18.1 Build Number 24267784   VMware Aria Operations for Networks 6.14 Plan blueprint can be created for the workloads based on various scoping criteria and have those workloads migrated through VMware HCX NSX Assessment Dashboard Improvements Flow-based application discovery with CSV upload Release Notes Aria Ops 6.14 Build Number   1725688792 There are a bunch of Product Support Packs released to support VMware Aria Suite Lifecycle's upgrade and support latest products like VMware Aria Automation 8.18.1 VMware Aria Orchestrator 8.18.1 VMware Aria Operations for Networks 6.14.0 Product Support Pack Download Link Release Notes vRealize Suite Lifecycle Manager Product Support Pack 20 8.10 PSPACK 20 8.10 PSPACK RN VMware Aria Suite Lifecycle 8.12.0 PSPACK 12 8.12 PSPACK 12 8.12 PSPACK RN VMware Aria Suite Lifecycle 8.14.0 PSPACK 10 8.14 PSPACK 10 8.14 PSPACK RN VMware Aria Suite Lifecycle 8.16.0 PSPACK 6 8.16.0 PSPACK 6 8.16 PSPACK RN VMware Aria Suite Lifecycle 8.18.0 PSPACK 3 8.18 PSPACK 3 8.18 PSPACK RN

VMware Aria Suite Lifecycle 8.18.0 Product Support Pack 4adds support for: VMware Aria Operations for Logs 8.18.1 VMware Aria Operations 8.18.2 Release Notes: https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-suite-lifecycle/8-18/release-notes/Chunk708728041.html#Chunk708728041 Download Link: https://support.broadcom.com/web/ecx/solutiondetails?patchId=5630

The VMware Aria Suite Lifecycle documentation has a new home! Previously hosted on VMware Docs , it has now been relocated to Broadcom's TechDocs platform . Here is a collection of links that might be helpful Installation and Upgrade Guide https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-suite-lifecycle/8-18/vmware-aria-suite-lifecycle-installation-upgrade-and-management-8-18.html Security Hardening Guide https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-suite-lifecycle/8-18/vrealize-suite-lifecycle-manager-security-hardening-guide-8-18.html Release Notes (New Release, Patches and Product Support Packs) https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-suite-lifecycle/8-18/release-notes.html API Programming Guide https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-suite-lifecycle/8-18/vmware-aria-suite-lifecycle-programming-guide-8-18.html Documentation Legal Notice https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-suite-lifecycle/8-18/documentation-legal-notice-english-public.html

This blog is available in PDF format too. Download the PDF attached below to consume it. Demo Pre-Requisites vIDM LB url ( if clustered ) or vIDM FQDN ( single ) vIDM local Account vIDM local Account Password AD User Name AD Password Domain Procedure Phase-1 As a first step, fetch the session token. This can be done by using below API Method POST URL {{idmurl}}/SAAS/API/1.0/REST/auth/system/login Payload { "username": "{{idmlocalusername}}", "password": "{{idmlocalpassword}}", "issueToken": "true" } Response false eyJ0eXAiOiJKV1Q****9XsskFqilcg Note: sessionToken on the above response has been trimmed Copy this session into a variable called vIDMSessionToken in Postman Phase-2 As next step , we will create oauth2clients by running an API. This definition will enable a service or its users to authenticate to VMware Identity Manager using the OAuth2 protocol. In short client is created by admin with trust and APIs can use client:secret to get token and auth happens Method POST ​ URL {{idmurl}}/SAAS/jersey/manager/api/oauth2clients {{idmurl}} is a variable for vIDM FQDN Payload { "clientId":"admintesttwo", "secret":"Vk13YXJlMTIzIQ==", "scope":"user admin", "authGrantTypes":"password", "tokenType":"Bearer", "tokenLength":23, "accessTokenTTL":36000, "refreshTokenTTL":432000 } ​clientId is a name given to the client which would be created. This can be any given name. The secret is the base64 encoded password you would like to assign to this client Response { "clientId": "admintesttwo", "secret": "Vk13YXJlMTIzIQ==", "scope": "user admin", "authGrantTypes": "password", "redirectUri": null, "tokenType": "Bearer", "tokenLength": 32, "accessTokenTTL": 36000, "refreshTokenTTL": 432000, "refreshTokenIdleTTL": null, "rememberAs": null, "resourceUuid": null, "displayUserGrant": true, "internalSystemClient": false, "activationToken": null, "strData": null, "inheritanceAllowed": false, "returnFailureResponse": false, "_links": { "self": { "href": "/SAAS/jersey/manager/api/oauth2clients/admintesttwo" } } } If this API is successful, then there is a 201 Created response is triggered Headers Key Content-Type Value application/vnd.vmware.horizon.manager.oauth2client+json Key Accept Value application/vnd.vmware.horizon.manager.oauth2client+json If we login into vIDM , Under Administration Console click on Catalog and then select Settings. Once we browse to Remote App Access. You would be able to see the client id Clicking on it will provide more details about the OAuth2Client created Phase-3 Once the client id is created , we now need to go ahead and fetch the token for AD authentication Method POST ​ URL {{idmurl}}/SAAS/auth/oauthtoken?grant_type=password ​ Body ( form data ) {{username}} {{password}} {{domain}} {{username}} refers to the AD username {{password}} refers to AD username's password {{domain}} refers to the domain where the user belongs to Authorization Basic {{clientid}}:{{secret}} In the previous step we did create the clientid and then secret ( base64 encoded ) password Content-Type Use it to fetch the t Content-Type multipart/form-data ​ I'd copy this access token into a variable again and call it as a adusertoken Now , let's execute a Get Environment API call to fetch details . These are vRSLCM's APIs. Method Get ​ URL {{lcmurl}}/lcm/lcops/api/v2/environments/{{geenvid}} ​ Authorization Bearer Token {{adusertoken}} {{adusertoken}} is the token captured above Response { "vmid": "90b3269b-9338-4cab-9b3c-f744a2a1e13b", "transactionId": null, "tenant": "default", "environmentName": "globalenvironment", "environmentDescription": "", "environmentId": "globalenvironment", "state": null, "status": "COMPLETED", "environmentData": * * * "{\"environmentId\":\"globalenvironment\",\"environmentName\":\"globalenvironment\",\"environmentDescription\":null,\"environmentHealth\":null,\"logHistory\":\"[ {\\n \\\"logGeneratedTime\\\" : 1657682435109,\\n \ "dataCenterName": null } Truncated version of the response This is how one may generate access token using a AD user account and then use it

Understanding Creutzfeldt-Jakob Disease (CJD) Creutzfeldt-Jakob Disease (CJD) is a rare and rapidly progressing neurodegenerative condition that primarily affects the brain. It is classified as a prion disease, which means that it is caused by abnormal proteins (prions) that damage brain tissue, leading to severe neurological symptoms. Although CJD is rare, with approximately one to two cases per million people per year worldwide, its effects can be devastating. This blog aims to provide an overview of CJD, including its symptoms, types, diagnosis, and treatment options. What is CJD? CJD belongs to a family of diseases known as prion diseases, which includes other rare conditions like Kuru, fatal familial insomnia, and Gerstmann-Sträussler-Scheinker syndrome. Prions are misfolded proteins that cause a cascade of abnormal folding in healthy proteins in the brain. This leads to cell death and tissue damage, ultimately causing brain shrinkage and spongiform changes, which are characteristic of the disease. Types of CJD There are four main types of CJD: Sporadic CJD (sCJD): This is the most common form, accounting for 85-90% of cases. It usually occurs randomly in people aged 60-65, with no known risk factors or genetic link. Familial or Inherited CJD (fCJD): Caused by a mutation in the PRNP gene, which encodes the prion protein. Makes up 10-15% of CJD cases. Individuals with a family history of CJD or other prion diseases are at higher risk. Acquired CJD: Results from exposure to infectious prions from contaminated medical equipment, organ transplants, or consumption of infected beef (Bovine Spongiform Encephalopathy or “mad cow disease”). While extremely rare, outbreaks of variant CJD (vCJD) have been linked to BSE. Variant CJD (vCJD): Linked to exposure to BSE in cattle. Typically affects younger individuals, and the disease course is longer than other forms of CJD. Symptoms of CJD CJD is characterized by rapid mental deterioration, leading to severe disability and death within a year in most cases. Common symptoms include: Rapidly progressive dementia Memory loss and confusion Personality changes Hallucinations Muscle stiffness or twitching Difficulty with coordination and balance Speech and vision problems Eventually, patients enter a coma-like state and often succumb to pneumonia or other infections. Diagnosis of CJD Diagnosing CJD is challenging due to its rarity and similarity to other neurological disorders. Typically, a combination of tests is used, including: Electroencephalogram (EEG): Measures brain wave patterns and can show characteristic changes in CJD. MRI Scans: Can reveal brain abnormalities indicative of CJD. Cerebrospinal Fluid (CSF) Tests: Detects certain proteins that are markers for prion disease. Genetic Testing: For individuals with a family history, genetic tests can identify mutations associated with familial CJD. Treatment and Management Currently, there is no cure for CJD. Treatment focuses on alleviating symptoms and providing supportive care. This may include: Pain relief Medications to reduce muscle spasms Psychological support for patients and families Ensuring a comfortable environment for end-of-life care Researchers are actively exploring new treatments, including drugs that target prions and gene therapies, but these are still in experimental stages. Prevention and Risk Mitigation Preventing CJD is challenging due to its sporadic nature. However, some steps can be taken to reduce the risk of acquired CJD: Implementing strict controls on the use of medical equipment, particularly in neurosurgery, to avoid cross-contamination. Regulating the food supply to prevent exposure to BSE. Genetic counseling for individuals with a family history of CJD. Living with CJD CJD is a devastating disease, not only for the individual but also for their families. The rapid progression and lack of effective treatment options make it particularly hard to cope with. Support groups and counseling can provide emotional and psychological support during this difficult time. Conclusion Creutzfeldt-Jakob Disease is a rare but fatal neurodegenerative disorder caused by prions. Despite its rarity, understanding the disease, its symptoms, and its progression is crucial for healthcare professionals and researchers. While there is currently no cure, ongoing research offers hope for the development of effective treatments in the future. For those looking for more information or support, organizations such as the CJD Foundation and local prion disease centers can provide valuable resources and guidance.

VMware Aria Suite Lifecycle 8.18.0 Product Support Pack 2 is now released. This Product Support Pack provides support for installing or upgrade of VMware Aria Operations 8.18.1 Download Link https://support.broadcom.com/web/ecx/solutiondetails?patchId=5527 Release Notes https://docs.vmware.com/en/VMware-Aria-Suite-Lifecycle/8.18/rn/vmware-aria-suite-lifecycle-818-product-support-pack-release-notes/index.html

There's always an ask to me on what versions are supported with a specific product support pack. That's the reason i've written this blog which has screenshots of every product support pack released for last few versions of VMware Aria Suite Lifecycle What is a Product Support Pack? In VMware Aria Suite Lifecycle, a Product Support Pack is a software package that updates an existing product support policy to incorporate support for new releases of VMware Aria suite of products. Here's a link to another blog i have written which explains why you need a Product Support Pack: https://www.arunnukula.com/post/why-do-i-need-product-support-packs-let-s-learn VMware Aria Suite Lifecycle 8.18.0 8.18 PSPACK 1 8.18.0 GA VMware Aria Suite Lifecycle 8.16.0 8.16.0 GA VMware Aria Suite Lifecycle 8.14.0 8.14.0 PSPACK 8 8.14.0 PSPACK 7 8.14.0 PSPACK 6 8.14.0 PSPACK 5 8.14.0 PSPACK 4 8.14.0 PSPACK 3 8.14.0 PSPACK 2 8.14.0 PSPACK 1 8.14.0 GA VMware Aria Suite Lifecycle 8.12.0 8.12.0 PSPACK 10 8.12.0 PSPACK 9 8.12.0 PSPACK 8 8.12.0 PSPACK 7 8.12.0 PSPACK 6 8.12.0 PSPACK 5 8.12.0 PSPACK 4 8.12.0 PSPACK 3 8.12.0 PSPACK 2 8.12.0 PSPACK 1 8.12.0 GA

This option is only available in a non-VCF aware VMware Aria Suite Lifecycle Good News The online upgrade of VMware Aria Suite Lifecycle was affected by changes on Day-2 in May. However, the issue has been resolved and the service is now restored. When Customers are in connected mode, they have the option to select "Check Online" followed by "Check for Upgrade" to verify the presence of a new manifest and confirm the identification of a new upgrade. Subsequently, they can click on "Upgrade" to continue with the workflow. Please note that customers who are using VMware Aria Suite Lifecycle 8.16.0 Patch 1 or PSPACK 4 are advised to install PSPACK 5 for version 8.16.0 in order to restore this feature in the UI

Login into VMware Aria Suite Lifecycle Go to Lifecycle Operations and Settings Click on System Upgrade Select "Check Online" and then click on "Check for Upgrade" It would return stating the new VMware Aria Suite Lifecycle 8.18.0 is available Ensure a snapshot is taken before triggering an upgrade Click on "Upgrade" to begin the upgrade workflow Pre-checks are fine and now the upgrade starts Remember the logs you can monitor Pre-Upgrade & Upgrade Phase /var/log/vmware/capengine/cap-non-lvm-update/worflow.log /var/log/vmware/capenginecap-non-lvm-updateinstaller-<>.log Post Update Phase /var/log/bootstrap/postupdate.log /data/script.log /var/log/vrlcm/vmware_vrlcm.log Services would restart which means it's in postupgrade phase Upgrade is now complete Happy Upgrades

VMware Cloud Foundation 5.2 which comprises of VMware Aria Suite 8.18.0 comes with the following new versions of the products Product Version VMware Aria Suite Lifecycle 8.18.0 VMware Aria Operations 8.18.0 VMware Aria Automation 8.18.0 VMware Aria Operations for Networks 6.13.0 VMware Aria Operations for Logs 8.18.0 VMware Aria Automation Orchestrator 8.18.0 From where can I download the VMware Aria Suite Lifecycle 8.18.0 upgrade package? Click here which would open a browser which will take you to Broadcom Support Portal. Following screen is what you would see VMware Aria Suite Lifecycle 8.18 Easy Installer for Automation and vIDM binary helps you to install VMware Aria Suite Lifecycle , VMware Identity Manager and VMware Aria Automation together The VMware Aria Suite Lifecycle 8.18 Update Repository Archive is the upgrade package specifically designed for VMware Aria Suite Lifecycle 8.18.0. If you are currently using an older version of Suite Lifecycle, you can utilize this package to upgrade to version 8.18.0. VMware Aria Suite Lifecycle 8.18 Easy Installer binary helps you to only install VMware Aria Suite Lifecycle , this does not contain VIDM and Automation binaries This link will take you to the page where you can download all the binaries mentioned above Product Support Packs have been launched to assist with upgrading VMware Aria Suite Lifecycle to version 8.18.0 if you are in VCF Aware Mode If your VMware Aria Suite Lifecycle is in Non-VCF aware mode, then there is no need to apply these product support packs on previous versions of Suite Lifecycle, just download the upgrade repo and then upgrade Policy Screenshot once an upgrade to VMware Aria Suite Lifecycle 8.18.0 is completed PSPACK Information Download Link Release Notes vRealize Suite Lifecycle Manager 8.8.2 PSPACK 11 Download Link Release Notes vRealize Suite Lifecycle Manager 8.10.0 PSPACK 19 Download Link Release Notes VMware Aria Suite Lifecycle 8.12.0 PSPACK 11 Download Link Release Notes VMware Aria Suite Lifecycle 8.14.0 PSPACK 9 Download Link Release Notes VMware Aria Suite Lifecycle 8.16.0 PSPACK 5 Download Link Release Notes

VMware Aria Suite Lifecycle 8.16.0 Product Support Pack 4 is now released This Product Support Pack provides support for VMware Aria Operations 8.17.2 VMware Aria Operations for Logs 8.16.1 Click here for Release Notes Click here for Downloading Product Support Pack 4 After applying VMware Aria Suite Lifecycle 8.16.0 Product Support Pack 4, you would see that the My VMware Options would no longer be available

Goal Upgrade an existing VMware Aria Automation 8.xx.xx to 8.17.0 Pre-Requisites VMware Aria Suite Lifecycle 8.16.0 Product Support Pack 3 binary VMware Aria Automation 8.17.0 Upgrade Repo iso Healthy VMware Aria Automation and VMware Aria Suite Lifecycle Download Product Support Pack Direct Download Link : https://support.broadcom.com/web/ecx/solutiondetails?patchId=5338 or Login to the  Broadcom Support Portal. Select "VMware Cloud Foundation" as the product line. Click on "My Downloads" and choose "VMware Aria Universal" or "VMware Aria Suite" Navigate to Solutions, expand the options, and click on Subscription. A list of patches and Product Support Packs will be displayed. Filter to find the appropriate one and click on it to open the download page for that specific Product Support Pack. The syntax to search for a Product Support Pack is always in the format vrslcm-8.16.0-PSPACKx, where x is the Product Support Pack number Based on the above information, the file we need is vrlcm-8.16.0-PSPACK3.pspak Download VMware Aria Automation Binary In the same Broadcom Support Portal, click on My Downloads Click on the product VMware Aria Automation Select the version you would like to download The file you would need to download in order to upgrade VMware Aria Automation from older version to 8.17.0 is VMware Aria Automation 8.17.0 Update Repository Prelude_VA-8.17.0.35214-23831516-updaterepo.iso which is around 12.91 GB Upload and Install Product Support Pack I have an existing VMware Aria Suite Lifecycle 8.16.0 GA where there are no Product Support Packs Installed Click on upload to select the product support pack downloaded previously. Then click on IMPORT Once the import process completes , refresh the page and you should now see 8.16.0 Product Support Pack 3 available for installation Before heading towards installation ensure a snapshot is taken Click on APPLY VERSION to start the process of installing the product support pack As you can see the product specifically asks for snapshot conscent whether you have taken it or not. So take it for sure. Submit the request to begin the installation During PSPACK installation, the important logs to monitor are /var/log/vrlcm/patchcli.log 2024-05-14 10:30:36,859 - __main__ - INFO - Metadata: {"patchInfo":{"name":"VMware Aria Suite Lifecycle, version 8.16.0 Pspack 3","summary":"Cumulative pspack bundle for vRealize Suite Lifecycle Manager","description":"This cumulative pspack bundle provides fixes to issues observed with various VMware Aria Suite Lifecycle components. Refer the associated docUrl for more details.","kbUrl":"https:\/\/docs.vmware.com\/en\/VMware-vRealize-Lifecycle-Manager\/8.16.0\/rn\/vRealize-Lifecycle-Manager-816-Pspack-3.html","eulaFile":"","category":"bugfix","urgency":"critical","releaseType":"pspack","releaseDate":1715332131000,"additionaInfo":{}},"metadataId":"vrlcm-8.16.0-PSPACK3","metadataVersion":"1","patchId":"8fe69f85-5fad-421a-864c-c0e134b557a3","patchBundleCreationDate":1715332131,"selfPatch":true,"product":{"productId":"vrlcm","productName":"VMware Aria Suite Lifecycle","productVersion":"8.16.0","supportedVersions":["8.16.0"],"productBuild":"10689094","productPatchBuild":"","additionaInfo":{"patchInstructions":"mkdir -p \/data\/tmp-pspack-81603\/10318114; cp -r /tmp/10318114/VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak \/data\/tmp-pspack-81603\/10318114; cd \/data\/tmp-pspack-81603\/10318114; unzip VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak; unzip lcm_PSPACK_artifacts.zip; cp -r \/tmp\/10318114\/lcm_pspack_metadata.json \/data\/tmp-pspack-81603\/10318114; sh pre_pspack_instructions.sh; sh pspack_instructions.sh \/data\/tmp-pspack-81603\/10318114 8fe69f85-5fad-421a-864c-c0e134b557a3;"},"patchAlreadyApplied":false},"payload":{"productPatchLevel":"PSPACK3","patchPayloadFilename":"VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak","patchPayloadUri":"","patchPayloadSize":398608505,"sha256sum":"67ab99e5a1cf5f93f111865331d46cc6726bdf34a14fdc19608200b4a2cf4215","productMinorLevel":null},"patchFileName":"vrlcm-8.16.0-PSPACK3.pspak","patchSize":0,"patchSha256sum":"","patchRunningCounter":1,"patchStatus":"ACTIVE","patchDownloadStatus":null,"extract":false,"patchCounter":null} 2024-05-14 10:30:36,859 - __main__ - INFO - Patch File: /tmp/10318114//VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak 2024-05-14 10:30:36,859 - __main__ - INFO - metadata after parsing : 2024-05-14 10:30:36,860 - __main__ - INFO - patch instructions:mkdir -p /data/tmp-pspack-81603/10318114; cp -r /tmp/10318114/VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak /data/tmp-pspack-81603/10318114; cd /data/tmp-pspack-81603/10318114; unzip VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak; unzip lcm_PSPACK_artifacts.zip; cp -r /tmp/10318114/lcm_pspack_metadata.json /data/tmp-pspack-81603/10318114; sh pre_pspack_instructions.sh; sh pspack_instructions.sh /data/tmp-pspack-81603/10318114 8fe69f85-5fad-421a-864c-c0e134b557a3; 2024-05-14 10:30:36,860 - __main__ - INFO - installing patch ... Archive: VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak extracting: lcm_PSPACK_artifacts.zip Archive: lcm_PSPACK_artifacts.zip creating: os/ inflating: vmlcm-service-gui-8.16.0-SNAPSHOT.jar inflating: vmlcm-service-8.16.0-SNAPSHOT.jar inflating: vmware-service-configuration.jar extracting: blackstone.zip inflating: APUAT-8.5.0.18176777.pak inflating: pre_pspack_instructions.sh inflating: pspack_instructions.sh inflating: policy.json inflating: post_patch_instructions.sh inflating: dev-build-upgrade.sh inflating: patchcli.py inflating: patchcliproxy inflating: vlcm-support inflating: vrlcm-server.service 2024-05-14_10:30:42 Pre Product Support Pack vRSLCM 2024-05-14_10:30:42 Cleaning backups from old location... 2024-05-14_10:30:42 Cleaning previous backups... 2024-05-14_10:30:42 Creating new backup file... 2024-05-14_10:30:43 Backup done. 2024-05-14_10:30:43 Copy script to /var/lib/vrlcm 2024-05-14 10:30:49,933 - __main__ - INFO - patch installation process ended. 2024-05-14 10:30:49,933 - __main__ - INFO - patch installation completed. /var/log/vrlcm/bootstrap.log 2024-05-14 10:31:55,251 __main__ - INFO:/var/lib/vrlcm 2024-05-14 10:31:55,251 __main__ - INFO:file removed /var/lib/vrlcm/final/dlfRepo/dlfRepo.zip 2024-05-14 10:31:55,251 __main__ - INFO:zipdir operation 2024-05-14 10:31:55,251 __main__ - INFO:abs_src /var/lib/vrlcm/final/dlfRepo 2024-05-14 10:31:55,252 __main__ - INFO:Adding file to Zip dlfRepo/vssc/8.16.0/dlf/license-vac-80-e9-suite-vrealizeflex-c3-201907.dlf 2024-05-14 10:31:55,252 __main__ - INFO:Adding file to Zip dlfRepo/vssc/8.16.0/dlf/license-vac-80-e5-suite-vrealize-c2-201807.dlf * * * * 2024-05-14 10:35:35,402 __main__ - INFO:delete call is success:http://localhost:8080/lcm/dbservice/api/ischema/properties/webPassword 2024-05-14 10:35:35,415 __main__ - INFO:delete call is success:http://localhost:8080/lcm/dbservice/api/ischema/properties/monitorvRNIWithvROps 2024-05-14 10:35:35,427 __main__ - INFO:delete call is success:http://localhost:8080/lcm/dbservice/api/ischema/properties/monitorvRAWithvROps 2024-05-14 10:35:35,427 __main__ - INFO:file removed /var/lib/vrlcm/final/dlfRepo/dlfRepo.zip 2024-05-14 10:35:35,428 __main__ - INFO:Bootstrap is exit witout any error 2024-05-14 10:35:35,428 __main__ - INFO:schedular api is called /lcm/bootstrap/api/initialize 2024-05-14 10:35:35,515 __main__ - INFO:Response: 2024-05-14 10:35:35,515 __main__ - INFO:Post call is sucessfull url: http://localhost:8080/lcm/bootstrap/api/initialize 2024-05-14 10:35:35,515 __main__ - INFO:lcm schedular started 2024-05-14 10:35:35,515 __main__ - INFO:Error: /tmp/dlfRepo - No such file or directory. 2024-05-14 10:35:35,515 __main__ - INFO:Update Association State Machine is Invoked 2024-05-14 10:35:35,560 __main__ - INFO:Response: 2024-05-14 10:35:35,560 __main__ - INFO:Post call is sucessfull url: http://localhost:8080/lcm/request/api/requests 2024-05-14 10:35:35,560 __main__ - INFO:vmid: eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:35,560 __main__ - INFO:Update License Request:: http://localhost:8080/lcm/request/api/requests/eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:35,586 __main__ - INFO:Response: 2024-05-14 10:35:35,586 __main__ - INFO:Get call is successful url: http://localhost:8080/lcm/request/api/requests/eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:35,587 __main__ - INFO:Update License association request is INPROGRESS 2024-05-14 10:35:35,587 __main__ - INFO:retrying--- Wait for 10 seconds. count: 1 2024-05-14 10:35:45,818 __main__ - INFO:Response: 2024-05-14 10:35:45,818 __main__ - INFO:Get call is successful url: http://localhost:8080/lcm/request/api/requests/eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:45,818 __main__ - INFO:Update License association request COMPLETED 2024-05-14 10:35:45,818 __main__ - INFO:Request either FAILED or is SUCCESS. 2024-05-14 10:35:45,819 __main__ - INFO:file removed /etc/triggerLicenseUpdate 2024-05-14 10:35:45,819 __main__ - INFO:file removed /var/lib/vrlcm/INPROGRESS 2024-05-14 10:35:45,819 __main__ - INFO:Creating SUCCESS file... 2024-05-14 10:35:45,819 __main__ - INFO:SUCCESS file already created... 2024-05-14 10:35:45,819 __main__ - INFO:sucess api count: 3245 failed api count: 0 Above snippets are a success indicators and wait for the services to come back During this process there would be restart of services Once the service is back online, you can see that the product support pack is already installed and we can now map the product binary and we are good to go If you see the policy 8.17.0 version if Automation is present which means either i can install new automation deployment of this version or upgrade an existing old version to automation to this version VMware Aria Automation Upgrade Binary Mapping Downloaded VMware Aria Automation 8.17.0 Upgrade Binary should be mapped in VMware Aria Suite Lifecycle Go to VMware Aria Suite Lifecycle , click on Lifecycle Operations, then browse to SETTINGS and click on Binary Mapping Click on Add Binaries Select Local as i have uploaded to the Suite Lifecycle VA. To upload it to VA, use WINSCP or a FILEZILLA and then copy it to /data folder Select the Binary after it's discovered Then click on ADD The Product Binary Mapping would begin To understand what happens when a product binary is mapped, review this blog post Once the task is completed. Now we are all set to upgrade our existing VMware Aria Automation to 8.17.0 VMware Aria Automation Upgrade Flow ( WORK IN PROGRESS) Ensure Upgrade Binary is mapped You may now see that the upgrade is available on my Automation instance Once you click on upgrade, click on "TRIGGER INVENTORY SYNC" Ensure this completes successfully Inventory Sync is now complete Let's now begin the upgrade. Click on "PROCEED" to start the upgrade flow The repository is already populated Click on NEXT to select Snapshot related options I have selected to Retain the Snapshot taken during upgrade Revert it automatically when a failure occurs , ensuring the application returns to it previous state A log bundle is always collected before it's reverted If GS asks this bundle, go ahead and download it There's a hardware requirement conscent and Run Prechecks Prechecks Succceed and then go ahead with upgrade submission Submit the request to trigger the upgrade Follow the blog which clearly explains what happens in an automation upgrade and what log files to be monitored It is expected to stay on this step for a while as the rpm's are being staged from lcm to automation appliances Upgrade is now completed Just took 1 hour and 8 minutes for a cluster based upgrade This concludes this comprehensive upgrade blog. Hope this helps.