Search Results

Recently , worked on a case where user had challenges in creating a webhook for git We were hitting an exception stating 400 Bad Request from POST http://identity-service-prelide-sb.cluster.local:8000/csp/gateway/am/api/auth/api-tokens/authorize When we fill all the information needed to save / create the webhook , we hit above exception. So what's happening in the background . We will find all the information w.r.t this error in codestream logs -------------------------------------------------------------------------------------------------------------------------- When an API call is made to authorize -------------------------------------------------------------------------------------------------------------------------- 2022-05-24T02:13:15.501Z DEBUG codestream [host='codestream-app-74cd595686-6vxfc' thread='parallel-9' user='' org='' trace='' parent='' span=''] o.s.w.r.f.client.ExchangeFunctions.traceDebug:119 - [4baaf594] HTTP POST http://identity-service.prelude.svc.cluster.local:8000/csp/gateway/am/api/auth/api-tokens/authorize -------------------------------------------------------------------------------------------------------------------------- This returns a 400 response stating invalid refresh token -------------------------------------------------------------------------------------------------------------------------- 2022-05-24T02:13:15.895Z INFO identity-service [host='identity-service-app-7857cb8674-4v5nq' thread='pool-3-thread-1' user='' org='' trace=''] com.vmware.identity.rest.RestClient.lambda$logRequest$1:74 - POST https://sso.iaas.nz.service.test/SAAS/API/1.0/oauth2/token?grant_type=refresh_token 2022-05-24T02:13:15.916Z ERROR identity-service [host='identity-service-app-7857cb8674-4v5nq' thread='reactor-http-epoll-3' user='' org='' trace=''] c.v.i.c.RestResponseEntityExceptionHandler.logBriefError:213 - Handling bad request exception: java.lang.IllegalArgumentException: REST error received: { "error": "invalid_grant", "error_description": "Invalid refresh token: Njg3MDIxNjg2MjI0OmsuDq93TLejOHGxNc0uR5eMuskn" }, status code: 400 BAD_REQUEST thrown at com.vmware.identity.common.util.WebClientUtil.handleException:36 2022-05-24T02:13:15.916Z INFO identity-service [host='identity-service-app-7857cb8674-4v5nq' thread='reactor-http-epoll-1' user='' org='' trace=''] reactor.netty.http.server.AccessLog.info:270 - 10.244.0.76 - - [24/May/2022:02:13:15 +0000] "POST /csp/gateway/am/api/auth/api-tokens/authorize HTTP/1.1" 400 303 8080 414 ms -------------------------------------------------------------------------------------------------------------------------- After exception in identity-service, codestream throws the same exception -------------------------------------------------------------------------------------------------------------------------- 2022-05-24T02:13:15.916Z DEBUG codestream [host='codestream-app-74cd595686-6vxfc' thread='reactor-http-epoll-12' user='' org='' trace='' parent='' span=''] o.s.w.r.f.client.ExchangeFunctions.traceDebug:119 - [4baaf594] [166c65f5-1] Response 400 BAD_REQUEST 2022-05-24T02:13:15.918Z INFO codestream [host='codestream-app-74cd595686-6vxfc' thread='reactor-http-epoll-10' user='' org='' trace='' parent='' span='] reactor.netty.http.server.AccessLog.info:270 - 10.244.0.63 - - [24/May/2022:02:13:15 +0000] "POST /codestream/api/git-webhooks HTTP/1.1" 400 330 8000 438 ms The reason for exception is that there is a section called API Token in WebHooks. This API token is the refresh token generated from vRA This token has to be valid Once this was changed and a valid token was provided , we were able to save the webhook or create it. One more method to verify if the token is expired is through the API response The Expires HTTP header contains the date/time after which the response is considered expired. Invalid expiration dates with value 0 represent a date in the past and mean that the resource is already expired

vIDM DB partition is full or nearly out of space. To validate the DB partition is using most of the space run the following commands: du -sh /db/elasticsearch du -sh /db/rabbitmq du -sh /db/data This will allow to see that /db/data taking most of the space. If it is one of the other disk trees, please see other KBs (ie audit data). Apply the following steps to clean up the bloated DB table Step:1 Take Product Snapshot Step:2 Stop Services service horizon-workspace stop Step:3 Fetch the Password to connect with postgres database cat /usr/local/horizon/conf/db.pwd If you do not want to expose the password then use below command as it is. It will export the password into PGPASSWORD export PGPASSWORD=`cat /usr/local/horizon/conf/db.pwd` example snippet root@idm [ /opt/vmware/horizon/workspace/logs ]# export PGPASSWORD=`cat /usr/local/horizon/conf/db.pwd` root@idm [ /opt/vmware/horizon/workspace/logs ]# /opt/vmware/vpostgres/current/bin/psql -U postgres saas psql.bin (9.6.21 (VMware Postgres 9.6.21.0-18007711 release)) Type "help" for help. saas=# \q root@idm [ /opt/vmware/horizon/workspace/logs ]# When you execute below Step:4 command to login then it will not prompt you for password again Step:4 Connect to Postgres database using below command. Output snippet shown below too. Remember the password shown below is from my lab. Don't use it in your environment /opt/vmware/vpostgres/current/bin/psql -U postgres saas example snippet: root@idm [ ~ ]# cat /usr/local/horizon/conf/db.pwd X9cEZskwwWRdeqP8hPE30TB_KKYx_Lq2 root@idm [ ~ ]# /opt/vmware/vpostgres/current/bin/psql -U postgres saas Password for user postgres: psql.bin (9.6.21 (VMware Postgres 9.6.21.0-18007711 release)) Type "help" for help. saas=# Step:5 Fetch the table sizes using below query SELECT nspname || '.' || relname AS "relation", pg_size_pretty(pg_total_relation_size(C.oid)) AS "total_size" FROM pg_class C LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace) WHERE nspname NOT IN ('pg_catalog', 'information_schema') AND C.relkind <> 'i' AND nspname !~ '^pg_toast' ORDER BY pg_total_relation_size(C.oid) DESC LIMIT 20; Step:6 Truncate the table as shown below using command truncate table "OAuth2RefreshToken" CASCADE; Step:7 Check the row count for three tables select count(*) from "OAuth2RefreshToken"; select count(*) from "OAuth2AccessToken"; select count(*) from "SuiteTokenCache"; Step:8 Execute Full Vacuum using below command vacuum full verbose; Output would be sometime like below saas=# vacuum full verbose; INFO: vacuuming "saas.databasechangelog" INFO: "databasechangelog": found 0 removable, 1368 nonremovable row versions in 47 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.07 sec. INFO: vacuuming "saas.databasechangeloglock" INFO: "databasechangeloglock": found 18 removable, 1 nonremovable row versions in 1 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.00 sec. INFO: vacuuming "saas.ForbiddenTenantName" INFO: "ForbiddenTenantName": found 0 removable, 0 nonremovable row versions in 0 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.00 sec. INFO: vacuuming "saas.MasterKey" INFO: "MasterKey": found 0 removable, 0 nonremovable row versions in 0 pages * * * * INFO: vacuuming "saas.ResourceTypeRegistry" INFO: "ResourceTypeRegistry": found 2 removable, 3 nonremovable row versions in 1 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.02 sec. INFO: vacuuming "saas.EndUserCatalogStorage" INFO: "EndUserCatalogStorage": found 0 removable, 0 nonremovable row versions in 0 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.00 sec. VACUUM saas=# Step:9 Re-Index table OAuth2RefreshToken and perform full vacuum again To ReIndex reindex table "OAuth2RefreshToken"; Full Vacuum vacuum full verbose; example snippets saas=# vacuum full verbose; INFO: vacuuming "saas.databasechangelog" INFO: "databasechangelog": found 0 removable, 1368 nonremovable row versions in 47 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.07 sec. INFO: vacuuming "saas.databasechangeloglock" INFO: "databasechangeloglock": found 18 removable, 1 nonremovable row versions in 1 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.00 sec. INFO: vacuuming "saas.ForbiddenTenantName" INFO: "ForbiddenTenantName": found 0 removable, 0 nonremovable row versions in 0 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.00 sec. INFO: vacuuming "saas.MasterKey" INFO: "MasterKey": found 0 removable, 0 nonremovable row versions in 0 pages * * * * INFO: vacuuming "information_schema.sql_features" INFO: "sql_features": found 0 removable, 671 nonremovable row versions in 7 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.01 sec. INFO: vacuuming "saas.ResourceProfileMapping" INFO: "ResourceProfileMapping": found 0 removable, 0 nonremovable row versions in 0 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.00 sec. INFO: vacuuming "saas.IDPOrgNetwork" INFO: "IDPOrgNetwork": found 0 removable, 2 nonremovable row versions in 1 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 0.00s/0.00u sec elapsed 0.00 sec. VACUUM Step:10 Exit Database \q Step:11 Execute a Postgres Service Restart root@idm [ ~ ]# service vpostgres restart root@idm [ ~ ]# Step:12 Start Horizon Application service horizon-workspace start Step:13 Wait for the application to completely initialize Log Location: /opt/vmware/horizon/workspace/logs Initially you would see information being logged under workspace.log , then connector.log and horizon.log Monitor for any exceptions Step:14 Once the whole application is initialized you may perform check on the table again by logging into database as shown below Also perform table size check if needed Step:15 Check the disk space now and perform a health check to see if everything is working as expected

Let me show an example of how we can identify version of vRA through API Request As a first step we need to fetch the authentication token API: POST {{vraurl}}/csp/gateway/am/api/login?{{access_token}} Headers: Content-Type: application/json Body: { "username": "{{username}}", "password": "{{password}}" } Tests: var data=JSON.parse(responseBody); postman.setEnvironmentVariable("access_token", data.cspAuthToken); Params {{access_token}} Response { "cspAuthToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6IjMxMzk2MzUxOTA5ODI4MzAxNjUifQ.eyJpc3MiOiJDTj1QcmVsdWRlIElkZW50aXR5IFNlcnZpY2UsT1U9Q01CVSxPPVZNd2FyZSxMPVNvZmlhLFNUPVNvZmlhLEM9QkciLCJpYXQiOjE2NDkyNDg0ODEsImV4cCI6MTY0OTI3NzI4MSwianRpIjoiNWI0OGFjMmUtMTExMi00YTZmLWJmZmUtYzc2OThiOTY2MDJiIiwiY29udGV4dCI6Ilt7XCJtdGRcIjpcInVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDphYzpjbGFzc2VzOlBhc3N3b3JkUHJvdGVjdGVkVHJhbnNwb3J0XCIsXCJpYXRcIjoxNjQ5MjQ4NDgxLFwiaWRcIjoxNX1dIiwiYXpwIjoicHJlbHVkZS11c2VyLWVsa2xpOVRSWUYiLCJzdWIiOiJjYXAub3JnOjkxZmIyM2ZkLTZjZTEtNGY2OS1hNTU2LWNlMmNlZmZiZWY0YSIsImRvbWFpbiI6ImNhcC5vcmciLCJ1c2VybmFtZSI6ImFydW4iLCJwZXJtcyI6WyJjc3A6b3JnX293bmVyIiwiZXh0ZXJuYWwvNTZiOTZjNDAtMjMxNC00MGI5LTk4YWUtZDM3M2M4NTk4ZjEwL29yY2hlc3RyYXRpb246YWRtaW4iLCJleHRlcm5hbC8zMzFmMDQwZC01NzNlLTQ1ODQtOGRmZi1mZmQ3MGFlMDE1MmIvQ29kZVN0cmVhbTphZG1pbmlzdHJhdG9yIiwiZXh0ZXJuYWwvZTJmMjA3N2ItNjE1Yy00YmY1LTg1MjQtMTIwMGRlMzEzZjQzL2NhdGFsb2c6YWRtaW4iLCJleHRlcm5hbC8yN2RjZmI0My1iODBlLTQzYWItODVhMi05ODBiNzliOWYyNzcvbWlncmF0aW9uOmFkbWluIiwiZXh0ZXJuYWwvYjgwMDJkZTAtMWI2MS00NWMwLWI4NGItMjdlZTc4ZTVmOTAyL3NhbHRzdGFjazphZG1pbiIsImV4dGVybmFsLzI3ZGNmYjQzLWI4MGUtNDNhYi04NWEyLTk4MGI3OWI5ZjI3Ny9hdXRvbWF0aW9uc2VydmljZTpjbG91ZF9hZG1pbiJdLCJjb250ZXh0X25hbWUiOiJjMmVhZTY3YS1mZjZkLTRkYWUtOWZkMy02NTk0MzUyYTFmOGEiLCJhY2N0IjoiYXJ1biJ9.uGIvog_oQ_cl-LeP9h_NcuBUmlqJDmFRkKxfU7YZXaRhlmJW9HC6ycTGjKW8yNJ83v6HMAEMz2PiVNgT09JMUHysrzQJUGnkcBGYnwD1T5SfvVvsFNsjdvq1vZ4tDc_wnZuX_VnHrgRP9QpMvNrU0KXvRNb23tAdfx8bVuvDCpmNQ3jUQZDpS5gvIqw3jS-vLhzAO-Mo0gE4am9h-zHvNg_UKyrfz2gMpWdyKYPw4ARHS8CDFuFcKimakPdbzE1AWeTtVWXfZwbNgaoQ-oGqw2N4MgQSy4Ov6oi6mPfz5YY1hGkwKEM5z8sX25VZC7lxwIRkkoLLmo9Yckic0v0vvQ" } Once we execute you would be fetching an authentication token. Replace the variables with appropriate values Request Create an API to fetch version API: GET {{vraurl}}/config.json Authorization: {{access_token}} Response { "applicationVersion": "dlJlYWxpemUgQXV0b21hdGlvbiA4LjcuMC4yMTE2OSAoMTk1MDg1MDUpCg==", "vac": { "tableName": "symphony_tango_ui", "collectorId": "vRA_ui.8_7", "endpointEnv": "production" }, "disableTelemetry": true, "disablePendo": true, "cloudFront": false, "deployment": "onprem", "featureFlags": { "ENABLE_SEGMENT_IO": false, "ENABLE_REQUEST_FORM_CUSTOMIZATION": true, "ADMIN_MENU_ENABLED": true, "DISABLE_WORKFLOW_ENUMERATION": true, "ENABLE_MIGRATION": true, "ENABLE_STANDALONE_ASSESSMENT": false, "ENABLE_V2T_MIGRATION": true, "QUICKSTART_TILE_ENABLED": true } } We will now use the applicationVersion base64 value , decode it to get version of vRealize Automation Login into https://www.base64decode.org/ Copy the string from the previous step dlJlYWxpemUgQXV0b21hdGlvbiA4LjcuMC4yMTE2OSAoMTk1MDg1MDUpCg==

I wanted to explore what really happens in the background and understand the whole flow during upgrade and product support pack implementation. This is the most comprehensive guide ever written for vRSLCM in terms of upgrade So , I decided to deploy a vRSLCM 8.6.2 and then upgrade it to 8.8. After that's successful , i would then apply 8.8.0.1 Policy that's PSPAK1 Here's the link to the whole documentation , download the pdf which has compete steps and snippets Attaching mind map here just for reference. This is present in the pdf too. Snippets in the document explains what log you need to check on each phase of the upgrade

When you perform an upgrade to latest version of vRSLCM that's 8.8.2.3 and you perform a "Check for Upgrade" it would throw a red banner which looks like an exception with no message This is a cosmetic issue and has no impact of product functionality Ideally , when your on latest version of vRSLCM , then you perform a system upgrade check you would be returned that there is no upgrade available. This is still the behavior in the background. Due to a known issue instead of a message we get an exception. This behavior is being fixed in upcoming release of vRSLCM From logs perspective , when you click on "check for upgrade" this is what happens in the background Reference: vmware_vrlcm.log ## checks if it's a vcf based env, it's not ## 2022-08-11 08:29:17.676 INFO [http-nio-8080-exec-4] c.v.v.l.l.c.DeploymentsController - -- is vcF user ::false ## executes update check command ## 2022-08-11 08:29:17.677 INFO [http-nio-8080-exec-4] c.v.v.l.u.ShellExecutor - -- Executing shell command: /opt/vmware/bin/vamicli update --check 2022-08-11 08:29:17.679 INFO [http-nio-8080-exec-4] c.v.v.l.u.ProcessUtil - -- Execute /opt/vmware/bin/vamicli ## result returned is absolutely right. There are no further upgrades available for 8.8.2 ## 2022-08-11 08:29:18.582 INFO [http-nio-8080-exec-4] c.v.v.l.u.ShellExecutor - -- Result: [Checking for available updates, this process can take a few minutes... . Available Updates - No available updates found]. 2022-08-11 08:29:18.583 INFO [http-nio-8080-exec-4] c.v.v.l.u.u.LCMUpgradeUtil - -- Output of update check : Checking for available updates, this process can take a few minutes... . Available Updates - No available updates found 2022-08-11 08:29:18.583 INFO [http-nio-8080-exec-4] c.v.v.l.l.c.DeploymentsController - -- Authentication object is not null org.springframework.security.authentication.UsernamePasswordAuthenticationToken@fe908ae6: YXYXYXYX org.springframework.security.core.userdetails.User@c220133a: Username: admin@local; Password: YXYXYXYX Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: LCM_ADMIN; Credentials: [PROTECTED]; Authenticated: true; Details: org.springframework.security.web.authentication.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Granted Authorities: LCM_ADMIN ## Ideally or in the previous versions following message would be displayed in UI stating "No upgrade available" 2022-08-11 08:29:18.583 INFO [http-nio-8080-exec-4] c.v.v.l.l.c.DeploymentsController - -- is vcF user ::false 2022-08-11 08:29:18.583 INFO [http-nio-8080-exec-4] c.v.v.l.u.u.LCMUpgradeUtil - -- No upgrade available. ## Now we get a banner with an incomplete error which ideally should not be the case due to this below error ## 2022-08-11 08:29:18.583 ERROR [http-nio-8080-exec-4] c.v.v.l.l.c.InputValidationExceptionHandlingController - -- Handling InvalidInputException with error message: null

Pre-Requisite Ensure vRSLCM 8.10 PSPACK 1 is implemented Download / Upload the product binary Click here for vRSLCM 8.10 PSPACK 1 Release Notes Click here for vRNI 6.8 Release Notes Select the product from the Environment Pane and click on Upgrade Trigger Inventory Sync . Ensure it's completed. Then click on Upgrade Ensure appropriate binary or upgrade bundle is selected Take a Product Snapshot , if you want to retrain the snapshot after upgrade you may do so Run Precheck What Prechecks are performed ? vRNI healthy platform check vRNI SSH status check on platform vRNI SSH status check on collector vRNI version check vRNI number of VMs check Submit upgrade request Upgrade Workflow is now started Different states in the upgrade are as below Stage:1 Shutting down Guest OS Stage:2 Shutting down Guest OS Stage:3 Creating Node Snapshot (Platform and Collector) Stage:4 Power On VM Stage:5 Power On VM Stage:6 productHealthCheck Stage:7 Create snapshot Inventory Stage:8 upgradevrni Stage:9 deleteNodeSnapshot Stage:10 productupgradeinventoryupdate Let's inspect Stage:8 in detail Inside stage 8 we have Start VRNI Upload Upgrade Bundle VRNI Upgrade Bundle Status Upgrade Precheck Upgrade Precheck Status VRNI Online Upgrade Check Upgrade Status VRNI VCF Watermark Configuration On VRNI VCF Watermark Configuration Success Product Patch Upgrade Notification Modification Modify Notification Scheduler Final Deep Dive on Stage:8 will be updated soon.... This concludes the upgrade. Remember to perofrm inventory sycn for sure before you upgrade vRNI. This is very important.

Attaching a pdf which has same information Author ARUN NUKULA Environment vROps Source Version: 8.6.2 Target Version : 8.6.4 vRSLCM 8.8.2 PSPACK 2 Note: This blog does not contain any customer facing data. It's performed in a lab environment whic has been destroyed Procedure These are the different environments in my vRSLCM. Upgrade would be performed on tvrops environment It's a single node vROps instance Took a snapshot before beginning any sort of a task on the product Logging into the product , i have three integrations all of those adapters are in functional state vCenter 8.x LogInsight NSXT Logged into vRSLCM , then performed inventory sync Once that's successful , go ahead and then click on upgrade Then we would be prompted with the repository url There would be an APUAT test performed. Once the APUAT test is completed , we can download the report or view it by clicking on view report When we click on download report , it would download a zip file with following contents Opt for a snapshot even though i've taken one just before the upgrade manually You may open index.html using browser which would show you the report Its pretty much a new system so there is nothing really in it. Hence the report is blank Then the services check would happen Once prechecks are done , you can download the report if one want's to use it as an articfact for upgrade and then click on next Validate all inputs for uprgade and click on submit to trigger uprgade The moment we click on submit upgrade is iniitiated There are 10 stages for this upgrade ( stages will vary if it is a cluster ) Stage 1: Clusteronlineofflineconfiguration 1. Start 2. Configure Cluster Init 3. Configure Cluster Online Offline State 4. Check Cluster Online Offline State 5. Final Stage 2: Shutting down Guest OS 1. Start 2. Shutdown Guest OS 3. Final Stage 3: Creating Node Snapshot 1. Start 2. Get vMoid of the virtual machine using name 3. Virtual machine using vMoid 4. Final Stage: 4 Power On VM 1. Start 2. Get vMoid of the virtual machine using name 3. Power On Virtual Machine 4. Final Stage: 5 vRealize Operations Manager Service Check 1. Start 2. vRealize Operations Manager Services Status Check task 3. Final Stage: 6 Clusteronlineofflineconfiguration 1. Start 2. Configure Cluster Init 3. Configure Cluster Online Offline State 4. Check Cluster Online Offline State 5. Final Stage: 7 Create Snapshot Inventory 1. Start 2. Product Snapshot Inventory create 3. On Environment Snapshot Complete Stage: 8 vROps Upgrade 1. Start 2. Start Upgrade 3. Find healthy adapters before upgrade 4. Install vROps uprgade pak 5. Check cluster status 6. vRealize Operations Manager SDDC Manager Watermark 7. Final Stage: 9 Delete Node Snapshot 1. Start 2. Get VMID delete snapshot 3. Delete Node Snapshot 4. Final Stage: 10 Product Upgrade Inventory update 1. Start 2. Product Upgrade Inventory Upgrade 3. Final After all of the above stages vROps upgrade is now complete What happens during Stage 8 : vROps Upgrade vROps Upgrade is started 2022-09-16 05:29:57.733 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- State to find :: com.vmware.vrealize.lcm.plugin.core.vrops.tasks.StartUpgradeTask Deepdive into various phases of the upgrade 1. FindHealthyAdapterTask is triggered 2022-09-16 05:29:57.733 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- State to find :: com.vmware.vrealize.lcm.plugin.core.vrops.tasks.FindHealthyAdapterTask 2022-09-16 05:29:57.755 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- Invoking Task :: com.vmware.vrealize.lcm.plugin.core.vrops.tasks.FindHealthyAdapterTask 2. Adapter response is logged 2022-09-16 05:30:00.976 INFO [pool-3-thread-39] c.v.v.l.p.c.v.t.FindHealthyAdapterTask - -- adapters response message {"adapterInstancesInfoDto":[{"resourceKey":{"name":"nsxt","adapterKindKey":"NSXTAdapter","resourceKindKey":"NSXTAdapterInstance","resourceIdentifiers":[{"identifierType":{"name":"AUTO_DISCOVERY","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"NSXTHOST","dataType":"STRING","isPartOfUniqueness":true},"value":"nsxtm.cap.org"},{"identifierType":{"name":"UNMONITORED_SERVICES","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"vmc_config_limits_file_name","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"VMEntityVCID","dataType":"STRING","isPartOfUniqueness":false},"value":""}]},"description":"","collectorId":1,"collectorGroupId":"9659e5d0-d36a-45c0-b7c0-11ef73d04363","credentialInstanceId":"35621c3f-bc32-4e26-95d4-98c24e3274e9","monitoringInterval":5,"numberOfMetricsCollected":1648,"numberOfResourcesCollected":110,"lastHeartbeat":1663306196138,"lastCollected":1663306155060,"messageFromAdapterInstance":"","links":[{"href":"/suite-api/api/adapters/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/credentials/35621c3f-bc32-4e26-95d4-98c24e3274e9","rel":"RELATED","name":"linkToCredential"}],"id":"2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9"},{"resourceKey":{"name":"vRealizeOpsMgrAPI (vRealize Operations Manager Collector-tvrops)","adapterKindKey":"vRealizeOpsMgrAPI","resourceKindKey":"vRealizeOpsMgrAPI Adapter Instance","resourceIdentifiers":[]},"collectorId":1,"monitoringInterval":1,"numberOfMetricsCollected":0,"numberOfResourcesCollected":0,"lastHeartbeat":1663306196138,"lastCollected":1663306182865,"messageFromAdapterInstance":"","links":[{"href":"/suite-api/api/adapters/c7fd85d1-1537-4513-a63d-9b443913bee5","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"linkToCredential"}],"id":"c7fd85d1-1537-4513-a63d-9b443913bee5"},{"resourceKey":{"name":"vc8","adapterKindKey":"VMWARE","resourceKindKey":"VMwareAdapter Instance","resourceIdentifiers":[{"identifierType":{"name":"AUTODISCOVERY","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"CLOUD_TYPE","dataType":"STRING","isPartOfUniqueness":false},"value":"PRIVATE_CLOUD"},{"identifierType":{"name":"DV_PORT_GROUP_DISABLED","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"DVS_DISABLED","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"ENABLE_ACTIONS","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"GFS_SKIP_PATTERNS","dataType":"STRING","isPartOfUniqueness":false},"value":"docker/devicemapper/mnt"},{"identifierType":{"name":"IS_REAL_TIME_MONITORING_ENABLED","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"PDRS_STATS_PROVIDER","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"PROCESSCHANGEEVENTS","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"VCURL","dataType":"STRING","isPartOfUniqueness":true},"value":"vc8.cap.org"},{"identifierType":{"name":"VM_FOLDER_DISABLED","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"VM_LIMIT","dataType":"STRING","isPartOfUniqueness":false},"value":"2000000000"},{"identifierType":{"name":"VMC_CONFIG_LIMITS_FILE_NAME","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"VMEntityVCID","dataType":"STRING","isPartOfUniqueness":false},"value":"0d0a4688-0836-448b-a97d-0910ba336f61"}]},"description":"","collectorId":1,"collectorGroupId":"9659e5d0-d36a-45c0-b7c0-11ef73d04363","credentialInstanceId":"0f88a896-0de5-4225-b268-4d736e1aabda","monitoringInterval":5,"numberOfMetricsCollected":64,"numberOfResourcesCollected":4,"lastHeartbeat":1663306196138,"lastCollected":1663306126082,"messageFromAdapterInstance":"","links":[{"href":"/suite-api/api/adapters/78b711a1-4f09-4080-aaab-81d9a12a0c72","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/credentials/0f88a896-0de5-4225-b268-4d736e1aabda","rel":"RELATED","name":"linkToCredential"}],"id":"78b711a1-4f09-4080-aaab-81d9a12a0c72"},{"resourceKey":{"name":"Container","adapterKindKey":"Container","resourceKindKey":"ContainerAdapterInstance","resourceIdentifiers":[{"identifierType":{"name":"ClusterId","dataType":"STRING","isPartOfUniqueness":true},"value":"tvrops"}]},"collectorId":1,"collectorGroupId":"9659e5d0-d36a-45c0-b7c0-11ef73d04363","monitoringInterval":1,"numberOfMetricsCollected":0,"numberOfResourcesCollected":0,"lastHeartbeat":1663306196138,"lastCollected":1663306182864,"messageFromAdapterInstance":"","links":[{"href":"/suite-api/api/adapters/bbb977cd-648b-49fa-84f3-02a720b1f780","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"linkToCredential"}],"id":"bbb977cd-648b-49fa-84f3-02a720b1f780"},{"resourceKey":{"name":"li","adapterKindKey":"LogInsightAdapter","resourceKindKey":"LoginSight Adapter Instance","resourceIdentifiers":[{"identifierType":{"name":"IS_SINGLETON","dataType":"STRING","isPartOfUniqueness":true},"value":""},{"identifierType":{"name":"LOGINSIGHTURL","dataType":"STRING","isPartOfUniqueness":false},"value":"li.cap.org"}]},"description":"","collectorId":1,"collectorGroupId":"9659e5d0-d36a-45c0-b7c0-11ef73d04363","monitoringInterval":5,"numberOfMetricsCollected":0,"numberOfResourcesCollected":0,"lastHeartbeat":1663306196138,"lastCollected":1663306122860,"messageFromAdapterInstance":"","links":[{"href":"/suite-api/api/adapters/fc977e44-9ab1-4b30-badb-031878cef5c6","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"linkToCredential"}],"id":"fc977e44-9ab1-4b30-badb-031878cef5c6"},{"resourceKey":{"name":"vRealize Operations Manager Adapter - tvrops","adapterKindKey":"vCenter Operations Adapter","resourceKindKey":"vCenter Operations Adapter Instance","resourceIdentifiers":[{"identifierType":{"name":"ClusterId","dataType":"STRING","isPartOfUniqueness":true},"value":"tvrops"},{"identifierType":{"name":"COLLECTORID","dataType":"STRING","isPartOfUniqueness":false},"value":"1"},{"identifierType":{"name":"NODEID","dataType":"STRING","isPartOfUniqueness":true},"value":"24127062-16cc-48cb-81de-1249e3c8a722"}]},"collectorId":1,"monitoringInterval":5,"numberOfMetricsCollected":9940,"numberOfResourcesCollected":11,"lastHeartbeat":1663306196138,"lastCollected":1663306133374,"messageFromAdapterInstance":"","links":[{"href":"/suite-api/api/adapters/5a1812aa-c575-4aa2-9074-4a313572ef79","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"linkToCredential"}],"id":"5a1812aa-c575-4aa2-9074-4a313572ef79"}]} 3. Formatting above json we get following list of adapters NSXTM vc8 vRealizeOpsMgrAPI Container li vRealize Operations Manager Adapter 4. Fetches the id's 2022-09-16 05:30:00.983 INFO [pool-3-thread-39] c.v.v.l.p.c.v.t.FindHealthyAdapterTask - -- adapterIds : [2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9, c7fd85d1-1537-4513-a63d-9b443913bee5, 78b711a1-4f09-4080-aaab-81d9a12a0c72, bbb977cd-648b-49fa-84f3-02a720b1f780, fc977e44-9ab1-4b30-badb-031878cef5c6, 5a1812aa-c575-4aa2-9074-4a313572ef79] 5. Goes and connects to each adapter to check its status ******************************************************* ### nsxt adapter response as a whole as an example ### ******************************************************* 2022-09-16 05:30:00.984 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9 2022-09-16 05:30:00.985 INFO [pool-3-thread-39] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 05:30:01.061 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9: 200 200 2022-09-16 05:30:01.061 INFO [pool-3-thread-39] c.v.v.l.p.c.v.t.FindHealthyAdapterTask - -- adapter resource response :: Response{statusCode=200, responseMessage='200', responseData='{"description":"","creationTime":1663301784638,"resourceKey":{"name":"nsxt","adapterKindKey":"NSXTAdapter","resourceKindKey":"NSXTAdapterInstance","resourceIdentifiers":[{"identifierType":{"name":"AUTO_DISCOVERY","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"NSXTHOST","dataType":"STRING","isPartOfUniqueness":true},"value":"nsxtm.cap.org"},{"identifierType":{"name":"UNMONITORED_SERVICES","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"vmc_config_limits_file_name","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"VMEntityVCID","dataType":"STRING","isPartOfUniqueness":false},"value":""}]},"credentialInstanceId":"35621c3f-bc32-4e26-95d4-98c24e3274e9","resourceStatusStates":[{"adapterInstanceId":"2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":5,"badges":[{"type":"COMPLIANCE","color":"GREY","score":-1.0},{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/35621c3f-bc32-4e26-95d4-98c24e3274e9","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9"}', responseDataBytes=[123, 34, ****** 34, 125], headers={Transfer-Encoding=[chunked], Keep-Alive=[timeout=15, max=100], null=[HTTP/1.1 200 200], Server=[Apache], Access-Control-Allow-Origin=[*], X-Request-ID=[DQ4uW0p6ZuEfKZdR02H9FCSyztsyRT0p], X-Content-Type-Options=[nosniff], Connection=[Keep-Alive], Pragma=[no-cache], Date=[Fri, 16 Sep 2022 05:30:00 GMT], X-Frame-Options=[SAMEORIGIN], Strict-Transport-Security=[max-age=31536000; includeSubDomains], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Content-Security-Policy=[default-src https: wss: data: 'unsafe-inline' 'unsafe-eval'; child-src *; worker-src 'self' blob:], Vary=[User-Agent], Expires=[0], X-XSS-Protection=[1; mode=block], Content-Type=[application/json;charset=UTF-8]}} 2022-09-16 05:30:01.074 INFO [pool-3-thread-39] c.v.v.l.p.c.v.t.FindHealthyAdapterTask - -- adapter resource response :: {"description":"","creationTime":1663301784638,"resourceKey":{"name":"nsxt","adapterKindKey":"NSXTAdapter","resourceKindKey":"NSXTAdapterInstance","resourceIdentifiers":[{"identifierType":{"name":"AUTO_DISCOVERY","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"NSXTHOST","dataType":"STRING","isPartOfUniqueness":true},"value":"nsxtm.cap.org"},{"identifierType":{"name":"UNMONITORED_SERVICES","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"vmc_config_limits_file_name","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"VMEntityVCID","dataType":"STRING","isPartOfUniqueness":false},"value":""}]},"credentialInstanceId":"35621c3f-bc32-4e26-95d4-98c24e3274e9","resourceStatusStates":[{"adapterInstanceId":"2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":5,"badges":[{"type":"COMPLIANCE","color":"GREY","score":-1.0},{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/35621c3f-bc32-4e26-95d4-98c24e3274e9","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9"} 6. In the same way it connects to all other adapters too 2022-09-16 05:30:01.079 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5 2022-09-16 05:30:01.079 INFO [pool-3-thread-39] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 05:30:01.120 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5: 200 200 2022-09-16 05:30:01.136 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72 2022-09-16 05:30:01.137 INFO [pool-3-thread-39] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 05:30:01.209 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72: 200 200 2022-09-16 05:30:01.237 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780 2022-09-16 05:30:01.237 INFO [pool-3-thread-39] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 05:30:01.274 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780: 200 200 2022-09-16 05:30:01.293 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6 2022-09-16 05:30:01.295 INFO [pool-3-thread-39] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 05:30:01.342 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6: 200 200 2022-09-16 05:30:01.361 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79 2022-09-16 05:30:01.362 INFO [pool-3-thread-39] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 05:30:01.403 INFO [pool-3-thread-39] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79: 200 200 7. Once we fetch all adapter data , validates everything is good. pak file installation is triggered 2022-09-16 05:30:01.424 INFO [pool-3-thread-39] c.v.v.l.p.c.v.t.FindHealthyAdapterTask - -- healthyAdapters : ["2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","78b711a1-4f09-4080-aaab-81d9a12a0c72","bbb977cd-648b-49fa-84f3-02a720b1f780","5a1812aa-c575-4aa2-9074-4a313572ef79","fc977e44-9ab1-4b30-badb-031878cef5c6","c7fd85d1-1537-4513-a63d-9b443913bee5"] 2022-09-16 05:30:01.424 INFO [pool-3-thread-39] c.v.v.l.p.c.v.t.FindHealthyAdapterTask - -- Upgrade Start: Executing Product Pak Installation 8. Takes around 45 minutes to complete the upgrade 2022-09-16 06:15:41.621 INFO [pool-3-thread-42] c.v.v.l.p.c.v.t.InstallvROpsProductUpgradePakTask - -- Product Pak installtion completed 2022-09-16 06:15:41.621 INFO [pool-3-thread-42] c.v.v.l.p.a.s.Task - -- Injecting Edge :: OnInstallvROpsProductUpgradePakCompleted 9. Starts cluster status check and completes it 2022-09-16 06:15:42.500 INFO [pool-3-thread-49] c.v.v.l.p.c.v.t.VropsClusterStatusCheckTask - -- Starting VropsClusterStatusCheckTask 2022-09-16 06:15:52.452 INFO [pool-3-thread-49] c.v.v.l.d.v.VropsEndpoint - -- returned data 200 :::: {"cluster_name":"tvrops","installation_state":"DONE","ha_state":"DISABLED","ca_state":"DISABLED","remove_node_state":"NONE","initialization_state":"NONE","online_state":"ONLINE","online_state_time":1663308803575,"online_state_reason_info":{"online_state_reason":"online_state.change_reason.upgrade_successful","last_status_date":"1663308803575"},"out_of_diskspace_slice":"","is_pak_installation_active":false,"is_pak_uninstall_active":false,"migration_state":null,"is_shrinking":false,"fail_going_offline":false} 2022-09-16 06:15:52.453 INFO [pool-3-thread-49] c.v.v.l.p.c.v.t.VropsClusterStatusCheckTask - -- cluster state :ONLINE 2022-09-16 06:15:52.453 INFO [pool-3-thread-49] c.v.v.l.p.a.s.Task - -- Injecting Edge :: OnVropsClusterStatusCheckSuccess 10. After OnVropsClusterStatusCheckSuccess , VropsCheckAdapterInstancesStateTask is triggered 2022-09-16 06:15:53.421 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- Responding for Edge :: OnVropsClusterStatusCheckSuccess 2022-09-16 06:15:53.422 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- State to find :: com.vmware.vrealize.lcm.plugin.core.vrops.tasks.VropsClusterStatusCheckTask 2022-09-16 06:15:53.422 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- State to find :: com.vmware.vrealize.lcm.plugin.core.vrops.tasks.VropsCheckAdapterInstancesStateTask 2022-09-16 06:15:53.452 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- Invoking Task :: com.vmware.vrealize.lcm.plugin.core.vrops.tasks.VropsCheckAdapterInstancesStateTask 11. This is where all adapters are verified post upgrade or application of the pak file 2022-09-16 06:15:55.944 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- Check adapter instance, repeat count : 1 2022-09-16 06:15:55.944 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- logging healthyAdapters ["2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","78b711a1-4f09-4080-aaab-81d9a12a0c72","bbb977cd-648b-49fa-84f3-02a720b1f780","5a1812aa-c575-4aa2-9074-4a313572ef79","fc977e44-9ab1-4b30-badb-031878cef5c6","c7fd85d1-1537-4513-a63d-9b443913bee5"] 2022-09-16 06:15:55.946 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9 2022-09-16 06:15:55.948 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:55.989 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9: 401 401 2022-09-16 06:15:55.989 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/auth/token/acquire 2022-09-16 06:15:55.990 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:56.092 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- POST /suite-api/api/auth/token/acquire: 200 200 2022-09-16 06:15:56.093 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9 2022-09-16 06:15:56.095 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:56.161 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9: 200 200 2022-09-16 06:15:56.162 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- adapter resource response :: {"description":"","creationTime":1663301784638,"resourceKey":{"name":"nsxt","adapterKindKey":"NSXTAdapter","resourceKindKey":"NSXTAdapterInstance","resourceIdentifiers":[{"identifierType":{"name":"AUTO_DISCOVERY","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"NSXTHOST","dataType":"STRING","isPartOfUniqueness":true},"value":"nsxtm.cap.org"},{"identifierType":{"name":"UNMONITORED_SERVICES","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"vmc_config_limits_file_name","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"VMEntityVCID","dataType":"STRING","isPartOfUniqueness":false},"value":""}]},"credentialInstanceId":"35621c3f-bc32-4e26-95d4-98c24e3274e9","resourceStatusStates":[{"adapterInstanceId":"2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":5,"badges":[{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"COMPLIANCE","color":"GREY","score":-1.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/35621c3f-bc32-4e26-95d4-98c24e3274e9","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"2dbdcd2c-bd1d-47be-9092-8ff59a7e03c9"} 2022-09-16 06:15:56.171 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72 2022-09-16 06:15:56.172 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:56.237 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72: 200 200 2022-09-16 06:15:56.238 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- adapter resource response :: {"description":"","creationTime":1663302194599,"resourceKey":{"name":"vc8","adapterKindKey":"VMWARE","resourceKindKey":"VMwareAdapter Instance","resourceIdentifiers":[{"identifierType":{"name":"AUTODISCOVERY","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"CLOUD_TYPE","dataType":"STRING","isPartOfUniqueness":false},"value":"PRIVATE_CLOUD"},{"identifierType":{"name":"DV_PORT_GROUP_DISABLED","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"DVS_DISABLED","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"ENABLE_ACTIONS","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"GFS_SKIP_PATTERNS","dataType":"STRING","isPartOfUniqueness":false},"value":"docker/devicemapper/mnt"},{"identifierType":{"name":"IS_REAL_TIME_MONITORING_ENABLED","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"PDRS_STATS_PROVIDER","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"PROCESSCHANGEEVENTS","dataType":"STRING","isPartOfUniqueness":false},"value":"true"},{"identifierType":{"name":"VCURL","dataType":"STRING","isPartOfUniqueness":true},"value":"vc8.cap.org"},{"identifierType":{"name":"VM_FOLDER_DISABLED","dataType":"STRING","isPartOfUniqueness":false},"value":"false"},{"identifierType":{"name":"VM_LIMIT","dataType":"STRING","isPartOfUniqueness":false},"value":"2000000000"},{"identifierType":{"name":"VMC_CONFIG_LIMITS_FILE_NAME","dataType":"STRING","isPartOfUniqueness":false},"value":""},{"identifierType":{"name":"VMEntityVCID","dataType":"STRING","isPartOfUniqueness":false},"value":"0d0a4688-0836-448b-a97d-0910ba336f61"}]},"credentialInstanceId":"0f88a896-0de5-4225-b268-4d736e1aabda","resourceStatusStates":[{"adapterInstanceId":"78b711a1-4f09-4080-aaab-81d9a12a0c72","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":5,"badges":[{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"COMPLIANCE","color":"GREY","score":-1.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=78b711a1-4f09-4080-aaab-81d9a12a0c72","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=78b711a1-4f09-4080-aaab-81d9a12a0c72","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/78b711a1-4f09-4080-aaab-81d9a12a0c72/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/0f88a896-0de5-4225-b268-4d736e1aabda","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"78b711a1-4f09-4080-aaab-81d9a12a0c72"} 2022-09-16 06:15:56.241 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780 2022-09-16 06:15:56.248 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:56.290 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780: 200 200 2022-09-16 06:15:56.291 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- adapter resource response :: {"creationTime":1663298162604,"resourceKey":{"name":"Container","adapterKindKey":"Container","resourceKindKey":"ContainerAdapterInstance","resourceIdentifiers":[{"identifierType":{"name":"ClusterId","dataType":"STRING","isPartOfUniqueness":true},"value":"tvrops"}]},"resourceStatusStates":[{"adapterInstanceId":"bbb977cd-648b-49fa-84f3-02a720b1f780","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":1,"badges":[{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=bbb977cd-648b-49fa-84f3-02a720b1f780","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=bbb977cd-648b-49fa-84f3-02a720b1f780","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/bbb977cd-648b-49fa-84f3-02a720b1f780/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"bbb977cd-648b-49fa-84f3-02a720b1f780"} 2022-09-16 06:15:56.298 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79 2022-09-16 06:15:56.299 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:56.336 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79: 200 200 2022-09-16 06:15:56.337 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- adapter resource response :: {"creationTime":1663298161446,"resourceKey":{"name":"vRealize Operations Manager Adapter - tvrops","adapterKindKey":"vCenter Operations Adapter","resourceKindKey":"vCenter Operations Adapter Instance","resourceIdentifiers":[{"identifierType":{"name":"ClusterId","dataType":"STRING","isPartOfUniqueness":true},"value":"tvrops"},{"identifierType":{"name":"COLLECTORID","dataType":"STRING","isPartOfUniqueness":false},"value":"1"},{"identifierType":{"name":"NODEID","dataType":"STRING","isPartOfUniqueness":true},"value":"24127062-16cc-48cb-81de-1249e3c8a722"}]},"resourceStatusStates":[{"adapterInstanceId":"5a1812aa-c575-4aa2-9074-4a313572ef79","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":5,"badges":[{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=5a1812aa-c575-4aa2-9074-4a313572ef79","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=5a1812aa-c575-4aa2-9074-4a313572ef79","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/5a1812aa-c575-4aa2-9074-4a313572ef79/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"5a1812aa-c575-4aa2-9074-4a313572ef79"} 2022-09-16 06:15:56.344 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6 2022-09-16 06:15:56.345 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:56.383 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6: 200 200 2022-09-16 06:15:56.384 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- adapter resource response :: {"description":"","creationTime":1663302105758,"resourceKey":{"name":"li","adapterKindKey":"LogInsightAdapter","resourceKindKey":"LoginSight Adapter Instance","resourceIdentifiers":[{"identifierType":{"name":"IS_SINGLETON","dataType":"STRING","isPartOfUniqueness":true},"value":""},{"identifierType":{"name":"LOGINSIGHTURL","dataType":"STRING","isPartOfUniqueness":false},"value":"li.cap.org"}]},"resourceStatusStates":[{"adapterInstanceId":"fc977e44-9ab1-4b30-badb-031878cef5c6","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":5,"badges":[{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=fc977e44-9ab1-4b30-badb-031878cef5c6","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=fc977e44-9ab1-4b30-badb-031878cef5c6","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/fc977e44-9ab1-4b30-badb-031878cef5c6/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"fc977e44-9ab1-4b30-badb-031878cef5c6"} 2022-09-16 06:15:56.391 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- url to connect https://tvrops.cap.org/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5 2022-09-16 06:15:56.392 INFO [pool-3-thread-22] c.v.v.l.u.SSLUtil - -- Disabled SNI for SSL socket. 2022-09-16 06:15:56.426 INFO [pool-3-thread-22] c.v.v.l.d.v.VropsConnector - -- GET /suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5: 200 200 2022-09-16 06:15:56.426 INFO [pool-3-thread-22] c.v.v.l.p.c.v.t.VropsCheckAdapterInstancesStateTask - -- adapter resource response :: {"creationTime":1663298393242,"resourceKey":{"name":"vRealizeOpsMgrAPI (vRealize Operations Manager Collector-tvrops)","adapterKindKey":"vRealizeOpsMgrAPI","resourceKindKey":"vRealizeOpsMgrAPI Adapter Instance","resourceIdentifiers":[]},"resourceStatusStates":[{"adapterInstanceId":"c7fd85d1-1537-4513-a63d-9b443913bee5","resourceStatus":"DATA_RECEIVING","resourceState":"STARTED","statusMessage":""}],"resourceHealth":"GREEN","resourceHealthValue":100.0,"dtEnabled":true,"monitoringInterval":1,"badges":[{"type":"EFFICIENCY","color":"GREEN","score":100.0},{"type":"RISK","color":"GREEN","score":0.0},{"type":"HEALTH","color":"GREEN","score":100.0}],"relatedResources":[],"links":[{"href":"/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5","rel":"SELF","name":"linkToSelf"},{"href":"/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5/relationships","rel":"RELATED","name":"relationsOfResource"},{"href":"/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5/properties","rel":"RELATED","name":"propertiesOfResource"},{"href":"/suite-api/api/alerts?resourceId=c7fd85d1-1537-4513-a63d-9b443913bee5","rel":"RELATED","name":"alertsOfResource"},{"href":"/suite-api/api/symptoms?resourceId=c7fd85d1-1537-4513-a63d-9b443913bee5","rel":"RELATED","name":"symptomsOfResource"},{"href":"/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5/statkeys","rel":"RELATED","name":"statKeysOfResource"},{"href":"/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5/stats/latest","rel":"RELATED","name":"latestStatsOfResource"},{"href":"/suite-api/api/resources/c7fd85d1-1537-4513-a63d-9b443913bee5/properties","rel":"RELATED","name":"latestPropertiesOfResource"},{"href":"/suite-api/api/credentials/","rel":"RELATED","name":"credentialsOfResource"}],"identifier":"c7fd85d1-1537-4513-a63d-9b443913bee5"} 12. Post this the watermark task is triggred 2022-09-16 06:15:58.463 INFO [pool-3-thread-6] c.v.v.l.p.c.v.t.VropsUpgradeVcfWaterMarkingTask - -- SDDC Manager Water mark configurations are skipped as it is not SDDC Manager user 2022-09-16 06:15:58.464 INFO [pool-3-thread-6] c.v.v.l.p.a.s.Task - -- Injecting Edge :: OnWaterMarkConfigurationsCompleted 13. Upgrade eventually completes If we detect that theree are adapter instances which were logged successfully before upgrade and not post upgrade then we thrown an error stating You may continue finishing your upgrade by clicking on RETRY and select skip option to be true and move on This should conclude your upgrade Note: This Post Upgrade adapter check has been removed from vROps upgrade flow in vRSLCM 8.10. Hence this issue will not ben seen anymore. There are health checks which can be enabled and disabled on environment level which would cater to this requirement.

PDF document Demo vRSLCM 8.10 bring 2 major features on the table with respect to vRealize Automation 1. Enable / Disable Pendo in vRA 8.x through vRSLCM 2. Auto Revert Feature when there's an upgrade failure in vRA 8.x In this blog, we will discuss Pendo Integration and how it works through vRSLCM 8.x Pendo integration for vRA in vRSLCM What's Pendo and Why is it used? Pendo is a product-analytics app built to help software companies develop products that resonate with customers. The tool is used for collecting page clicks, feature clicks, providing in-app guides, and producing various kinds of reports, which are based on tagged pages and features When was it introduced in vRealize Automation 8.x? vRealize Automation participates in VMware's original Customer Experience Improvement Program (CEIP) and also the Pendo Customer Experience Program (Pendo CEIP) for vRealize applications. Pendo CEIP was introduced in vRA 8.8 verison. You can separately join or leave the VMware original Customer Experience Improvement Program (CEIP) and the Pendo Customer Experience Program (Pendo CEIP). Each program collects somewhat different types of customer interaction data, as described below. Original CEIP The original CEIP provides VMware with information that enables designers and engineers to improve products and services, fix problems, and advise you on how best to deploy and use VMware products and services. It collects usage and runtime data to help gauge system stability and the consumption levels of different features. This information also helps VMware designers and engineers determine what to build next based on which use-cases and features are being used or not used. You can join this CEIP when you install vRealize Automation with the vRealize Lifecycle Manager (LCM). After installation, vRealize Automation administrators and enabled users can also join or leave the program by using vracli ceip command line options. Pendo CEIP Pendo is an integrated third-party tool that collects user activities and provides analytics to vRealize Automation product development. The Pendo CEIP collects workflow data based on your interaction with the user interface. This information helps VMware designers and engineers develop data-driven improvements to the usability of products and services. You can join or leave the Pendo CEIP by using vracli ceip pendo command line options. Enabled users can also join or leave the Pendo CEIP by using options in their vRealize Automation user interface. How was Pendo being enabled till now on vRA 8.x? Command Line Method One can join, leave, or verify the Pendo Customer Experience Improvement Program (Pendo CEIP) for vRealize services as follows. Join Log in to the vRealize Automation appliance command line as root. Run the vracli ceip pendo on command. Restart vRealize Automation services by running the /opt/scripts/deploy.sh command. Leave Log in to the vRealize Automation appliance command line as root. Run the vracli ceip pendo off command. Restart vRealize Automation services by running the /opt/scripts/deploy.sh command. Verify Log in to the vRealize Automation appliance command line as root. Run the vracli ceip pendo status command. UI Method You can join or leave the Pendo CEIP for vRealize services by using the following on-screen interaction sequence in vRealize Automation. From the active vRealize Automation service, click the question mark Help toggle (?) in the upper right area of the screen. Alternately and if visible, you can click Cookie Usage in the Cookie banner. If you clicked the ? icon, click Cookie Usage in the lower right area of the subsequent Help page. Review cookie usage and how to opt-out ocntent on subsequent page What's new with Pendo Integration with vRA using vRSLCM 8.10 then ? vRSLCM 8.10 now provides option to toggle pendo settings as a day-2 action on vRealize Automation product. Select the Environment , then the product vRealize Automation. Click on the three dots where you have list of day-2 actions available for the product. There would be an option called "Toggle Pendo Setting" When we click on "Toggle Pendo Setting" , we do get a dialogue box stating when you perofrm toggle operation whether it's "ON" or "OFF" , there would be service restart hence downtime is expected. If it's a clustered environment then the downtime could increase a bit compared to single node. Let's understand what happens when you enable pendo and check it's flow when you disable as well. Enabling Pendo Click on the three dots and then in the drop down select " Toggle Pendo Setting " Took a snapshot before changing as a precautionary measure. Not really needed but does not harm either. Default option is "OFF" , we will change it to "ON" The moment we click submit a request is generated with 2 stages Stage 1: Toggle pendo setting on vRealize Automation Host 1. Start 2. Start toggle pendo on vRealize Automation Host 3. Toggle pendo on vRealize Automation Host initiated 4. Restarting services on vRealize Automation host 5. Check Pendo status on vRealize Automation host 6. Final Stage 2 Update Environment Details 1. Start 2. Update Environment Details 3. Final Request State Machine After it's complete , the property is set to true From logs perspective Reference: vmware_vrlcm.log #### Request is processed ### 2022-10-13 12:47:06.318 INFO [scheduling-1] c.v.v.l.r.c.p.ToggleVraPendoSettingPlanner - -- Processing toggling of vRA Pendo setting request. 2022-10-13 12:47:06.319 INFO [scheduling-1] c.v.v.l.r.c.p.ToggleVraPendoSettingPlanner - -- Processing request - toggleVraPendoSetting for environment cf8ac4ce-a7a7-4958-8401-50efdf4f1489 ### Request is being set to IN PROGRESS### 2022-10-13 12:47:06.511 INFO [scheduling-1] c.v.v.l.r.c.RequestProcessor - -- Processing request with ID : d5ef03d5-7821-4755-bd7a-b1a6db3bb5d9 with request type TOGGLE_VRA_PENDO_SETTING with request state INPROGRESS. ### Task is now started ### 2022-10-13 12:47:08.658 INFO [scheduling-1] c.v.v.l.c.u.EventExecutionTelemetryUtil - -- Start Instrumenting EventMetadata. 2022-10-13 12:47:08.658 INFO [scheduling-1] c.v.v.l.c.u.EventExecutionTelemetryUtil - -- Stop Instrumenting EventMetadata. 2022-10-13 12:47:08.667 INFO [pool-3-thread-26] c.v.v.l.p.c.v.t.VraVaTogglePendoSettingTask - -- Starting :: vRealize Automation toggle Pendo Setting Task 2022-10-13 12:47:08.669 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- PRELUDE ENDPOINT HOST :: vra.cap.org ### pendo status is verified to begin with ### 2022-10-13 12:47:08.669 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- COMMAND :: vracli ceip pendo status 2022-10-13 12:47:08.884 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- Executing command --> vracli ceip pendo status 2022-10-13 12:47:10.430 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- exit-status: 0 2022-10-13 12:47:10.431 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- Command executed sucessfully ### Response is that it's disabled ### 2022-10-13 12:47:10.443 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- Command execution response: { "exitStatus" : 0, "outputData" : "Pendo is disabled.\n", "errorData" : null, "commandTimedOut" : false } 2022-10-13 12:47:10.443 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Command Status code :: 0 2022-10-13 12:47:10.443 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Output Stream :: 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Pendo is disabled. 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Error Stream :: 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- null 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.p.c.v.t.VraVaTogglePendoSettingTask - -- vRA Pendo status output : Pendo is disabled. 2022-10-13 12:47:10.444 INFO [pool-3-thread-26] c.v.v.l.p.c.v.t.VraVaTogglePendoSettingTask - -- Pendo is in disabled state on the vRealize Automation host: vra.cap.org ### Command to enable is sent ### 2022-10-13 12:47:10.445 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- PRELUDE ENDPOINT HOST :: vra.cap.org 2022-10-13 12:47:10.445 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- COMMAND :: vracli ceip pendo on 2022-10-13 12:47:10.542 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- Executing command --> vracli ceip pendo on 2022-10-13 12:47:12.594 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- exit-status: 0 2022-10-13 12:47:12.594 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- Command executed sucessfully ### After the command is successfully executed , there is a restart of services which needs to be done ### 2022-10-13 12:47:12.595 INFO [pool-3-thread-26] c.v.v.l.u.SshUtils - -- Command execution response: { "exitStatus" : 0, "outputData" : "Pendo data collection was successfully turned on. Restart the services for command to take effect.\n", "errorData" : null, "commandTimedOut" : false } 2022-10-13 12:47:12.596 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Command Status code :: 0 2022-10-13 12:47:12.596 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:12.597 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Output Stream :: 2022-10-13 12:47:12.597 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:12.597 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Pendo data collection was successfully turned on. Restart the services for command to take effect. 2022-10-13 12:47:12.597 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:12.598 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- Error Stream :: 2022-10-13 12:47:12.598 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:12.598 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- null 2022-10-13 12:47:12.598 INFO [pool-3-thread-26] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- ==================================================== 2022-10-13 12:47:12.598 INFO [pool-3-thread-26] c.v.v.l.p.c.v.t.VraVaTogglePendoSettingTask - -- Enabled Pendo on the vRealize Automation host: vra.cap.org 2022-10-13 12:47:12.598 INFO [pool-3-thread-26] c.v.v.l.p.a.s.Task - -- Injecting Edge :: OnVraVaTogglePendoSuccess * * * 2022-10-13 12:47:12.894 INFO [pool-3-thread-24] c.v.v.l.p.c.v.t.VraVaStartServicesTask - -- Starting :: vRA VA Start Services Task 2022-10-13 12:47:12.895 INFO [pool-3-thread-24] c.v.v.l.p.c.v.t.VraVaStartServicesTask - -- isCavaDeployment :false deployOptions: null 2022-10-13 12:47:12.897 INFO [pool-3-thread-24] c.v.v.l.p.c.v.t.VraVaStartServicesTask - -- Running Deploy Script on vRA VA : vra.cap.org 2022-10-13 12:47:12.899 INFO [pool-3-thread-24] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- PRELUDE ENDPOINT HOST :: vra.cap.org ### Service restart command is executed and then it's complete #### 2022-10-13 12:47:12.899 INFO [pool-3-thread-24] c.v.v.l.d.v.h.VraPreludeInstallHelper - -- COMMAND :: /opt/scripts/deploy.sh 2022-10-13 12:47:13.016 INFO [pool-3-thread-24] c.v.v.l.u.SshUtils - -- Executing command --> /opt/scripts/deploy.sh * * * 2022-10-13 13:08:40.866 INFO [pool-3-thread-24] c.v.v.l.p.a.s.Task - -- Injecting Edge :: OnVraVaStartServicesSuccess Even when you toggle it back to OFF state , the flow would remain same Opt In & Opt Out When the user logs in When you click on COOKIE USAGE , you will be presented following pane where you have disclaimer and notes on how to opt out Looking at the previous screenshot user called "arun" is sending data . He has an option to "OPT OUT" I just click on "OPT OUT" and then it does not send any data anymore. Another click on "OPT IN" starts sending the data Again , this is per user basis. Arun might have opted out but a user called harsha can still stay by opting in. Remember , if PENDO is not enabled , this page would just look as below

VMware released vRealize Suite Lifecycle Manager 8.10 on 11th October 2022. This release comes with lot's of exciting features. In this video , we will discuss one such feature introduced in this version which would provide integration between vRealize Suite products With vRealize Log Insight, you can now perform log forwarding configuration from other vRealize Suite products to vRealize Log Insight. Similarly, with vRealize Operations Manager, you can now perform management pack configuration of other vRealize products in vRealize Operations Manager. With this info let's get into the lab and explore how this works PDF Demo Procedure Creating an environment named "Staging" which would consists of following products vRealize Automation vRealize Operations vRealize LogInsight vRealize SaltStack Config Accept EULA Assign licenses will be associated with the products being deployed Certificate has already been created inside locker , so it's just time to use it now Select the infrastructure properties The next step is to configure product properties. This is the place where you implement inter integrations Starting with vRealize Automation , we would fill all of the product properties needed for a successful install We have a new option to check a box which would enable vRLI Log Forwarding Configuration and Monitoring with vROps In the same manner, for vRealize LogInsight as well you have an option to monitor with vROps. That's just a check box which needs to be addressed One difference for vROps is that it needs management pack to be installed. The pak files can be uploaded to /data partition of vRSLCM. Then click on the box which says "EDIT ADAPTER FILES SELECTION" There are three management packs 1. Management pack for vRO 2. Management pack for SDDC Health 3. Management Pack for VMware Identity Manager Adapter Mention the path where the pak files are stored. that's /data which is recommended. Then when we click on "DISCOVER" all the pak files available will be displayed. Based on the previous selection , respective pak files will be installed and then configured during installation We also have an option to select what log entities to be pushed to vRLI from vROps Saltstack product properties page Now that we have all of the parameters needed entered , we will now go ahead and click next to perform prechecks Since all validations are now good , we will submit the request so that environment deployment can start Based on the number of products , number of stages would vary Finally installation completed. Took around 1 hour and 52 minutes to deploy all 4 products As discussed we did select vROps and vRA to push logs to vRLI during it's deployment itself. That's what we see in the below screenshot which shows 2 sources who are injecting the logs. Even with vROps the adapter configuration is done automatically and management packs are installed. Staging environment is just deployed so the health information should be available pretty soon Remember , there are Day-2 actions available for Log Forwarding and Management Pack installation on respective products This concludes the blog. Happy Learning

This blog post explains the procedure on how to review the password of a stored locker object using API method Assumptions {{lcmurl}} is vRSLCM FQDN example: https://lcm.domain.example Authentication Aquire LCM Auth Token (admin@local) Request Method: POSTRequest: {{lcmurl}}/lcm/authzn/api/login Authorization: Basic Auth username: admin@local password: ****** Response A cookie is created and response code is 200 Fetch Passwords Request Method: GET URL: {{lcmurl}}/lcm/locker/api/v2/passwords Response { "page": 0, "total": 1, "passwords": [ { "vmid": "0704babb-5b6c-474f-9d03-c92dffb9ca59", "tenant": "default", "alias": "0", "userName": "", "password": "PASSWORD****", "passwordDescription": "", "createdOn": 1665126022437, "lastUpdatedOn": 1665126022437, "referenced": false } ] } View Passwords To view password , one has to enter {{lcmurl}} , then the vmid of the locker object captured in the previous request as shown above. Also , the body of the post request should contain lcm's root password Request Method: POST URL: {{lcmurl}}/lcm/locker/api/passwords/view/{{locker_vmid}} Authorization: Inherit from Parent Body: { "rootPassword": "{{lcmrootpassword}}" } Response { "passwordVmid": "0704babb-5b6c-474f-9d03-c92dffb9ca59", "password": "VMware123!" } The response would contain the password vmid along with the password in plain text Note: Password being displayed here is an example

In this blog we shall discuss methods or process needed to change passwords of managed products by vRSLCM using locker API's In all below API calls where mentioned {{idmurl}} is the VMware Identity Manager's hostname (e.g idm.domain.example) {{lcmurl}} is the vRealize Suite Lifecycle Manager's hostname (e.g https://lcm.domain.example) Aquire Session Token ( vIDM ) Request Method: POST Request: {{vidmurl}}/SAAS/API/1.0/REST/auth/system/login Headers: Content-Type: application/json Accept: application/json Request body: { "username": "configadmin", "password": "configadmin_password", "issueToken": "true" } Response false eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJqdGkiOiIwN2VlNDQ0My0yYzYzLTRkNmQtODk4ZC1kY2UzZjQzNDZkYWYiLCJwcm4iOiJjb25maWdhZG1pbkBJRE0iLCJkb21haW4iOiJTeXN0ZW0gRG9tY**********3_qehterCBvH60n_ecUx4tweMj6byOorhEcFBfgCgG5LxDUDKH5Da9XaPmBsOF5qcozCz9YWdJciuwGtCGUxdow2zhdwfVGb-uNk71QyUET6fSh1G-JQCn41K_8rJ4tgtRX8ETm--BGLY9fy5g A cookie is set in this case as well This session token has been placed under environment details as variable Aquire LCM Auth Token (admin@local) Request Method: POST Request: {{lcmurl}}/lcm/authzn/api/login Authorization: Basic Auth username: admin@local password: ****** Response A cookie is created and response code is 200 As one can see there are two cookies set , one for idm based authentication and the other for lcm local auth Fetch Environment Details We shall use this API to fetch environment details in which the product is present Request Method: GET Request: {{lcmurl}}/lcm/lcops/api/v2/environments?status=COMPLETED Response [ { "environmentId": "globalenvironment", "environmentName": "globalenvironment", "environmentDescription": "", "environmentHealth": null, "logHistory": "[ {\n \"logGeneratedTime\" : 1657682435109,\n \"logLocation\" : \"https://lcm.cap.org/repo/logBundleRepo/environment/globalenvironment/log-globalenvironment-1657682435109.tar.gz\"\n} ]", "environmentStatus": "COMPLETED", "infrastructure": { "properties": { } }, "products": [ { "id": "vidm", "version": "3.3.6", "patchHistory": null, "snapshotHistory": null, "logHistory": null, "clusterVIP": null, "nodes": [ { "type": "vidm-primary", "properties": { "hostName": "********", "cluster": "********", "esxHost": "********", "memory": "**", "diskMode": "***", "vCenterHost": "******", "storage": "****", "network": "*****", "capacity": "***", "vidmRootPassword": "locker:password:b1ed53c1-c6c2-4422-ba3c-68f39b33a04a:dummyalias", "vidmSystemAdminPassword": "locker:password:17e1d72f-2a2d-4105-ba13-ba26b62473ee:installerPassword", "enableTelemetry": "false", "affinityRules": null, "__vMoid": "vm-43", } }, { "type": "vidm-connector", "properties": { } } ], "collectorGroups": null, "properties": { * * "vidmAdminPassword": "locker:password:17e1d72f-2a2d-4105-ba13-ba26b62473ee:installerPassword", "enableTelemetry": "false", "defaultConfigurationPassword": "locker:password:17e1d72f-2a2d-4105-ba13-ba26b62473ee:installerPassword", * * * "certificate": "locker:certificate:6d7a83c9-40c6-42f8-9d6b-af75227b3689:idm" } } ], "metaData": { "isCloudProxyEnvironment": "false" } }, You will get a json response with all the environment and product data. Look at the screenshot for more information. Based on the environment and the product you have selected to change specific account passwords , those data can be aquired from this response Get the root password from the product As an example in this blog , we will choose to change root password of vIDM Based on the above response we got the the environments api , we will collect current root password of vIDM and keep it aside So that would be "vidmRootPassword": "locker:password:b1ed53c1-c6c2-4422-ba3c-68f39b33a04a:dummyalias" We can confirm that from UI too If you look at the syntax on how it's stored "vidmRootPassword": "locker:password:vmid:locker_alias" "vidmRootPassword": "locker:password:b1ed53c1-c6c2-4422-ba3c-68f39b33a04a:dummyalias" Get the Password using VMID Now let's get the details of the password using the extracted vmid by using following API Request Method: GET Request: {{lcmurl}}/lcm/locker/api/v2/passwords/details/ Response { "vmid": "b1ed53c1-c6c2-4422-ba3c-68f39b33a04a", "tenant": "default", "alias": "dummyalias", "userName": "dummy", "password": "PASSWORD****", "passwordDescription": "dummypassword", "createdOn": 1664436058965, "lastUpdatedOn": 1664436058965 } View Password To view the password use the below URL Request Method: POST Request: {{lcmurl}}/lcm/locker/api/v2/passwords/details/ Response { "passwordVmid": "b1ed53c1-c6c2-4422-ba3c-68f39b33a04a", "password": "Dummy123!" } Create New Password object in Locker Here's the API to create an object in locker. It's a post call. In the response your returned with the vmid of the password object which has been created Request Method: POST Request: {{lcmurl}}/lcm/locker/api/v2/passwords Response { "vmid": "deab31fa-ea7a-452b-a0ad-a5daa5bb4126", "tenant": "default", "alias": "vidmroot071022", "userName": "root", "password": "PASSWORD****", "passwordDescription": "vidmroot071022", "createdOn": 1665147383168, "lastUpdatedOn": 1665147383168 } We can check the new password in the UI as well Update Password As an example , we shall consider root password of vIDM to be changed Request Method: PUT Request:{{lcmurl}}/lcm/lcops/api/v2/environments/{{envid}}/products/{{idmprodid}}/nodes/{{nodetype}} Note: the above request url should be properly replaced by appropriate values This URL is used to change root password for vIDM node {{envid}}: "globalenvironment" {{idmprodid}}: "vidm" {{nodetype}}: "vidm-primary" We need to compile body of the request Remeber from the previous API , we've collected the current password and also stored the vmid of the new password onject we created to apply as a new root password { "currentPassword": "locker:password:b1ed53c1-c6c2-4422-ba3c-68f39b33a04a:dummyalias", "hostName": "{{nodehostname}}", "newPassword": "locker:password:deab31fa-ea7a-452b-a0ad-a5daa5bb4126:vidmroot071022", "userNameToUpdate": "root" } Remember the {{nodehostname}} is the node for which the password is being changed. If it's a cluster , this has to be executed thrice on each node to maintain consistency Once we submit the request , as a response a request id is sent which can be tracked too The request id can be polled using following API Request Method: PUT Request:{{lcmurl}}/lcm/request/api/v2/requests/ Response In the UI you may see the request to update password is now complete for root In similar manner if you want to change admin password of vIDM then you have to do following. Remeber the API would change it's not going to be same Request Method: PUT Request: {{lcmurl}}/lcm/lcops/api/v2/environments/{{envid}}/products/{{idmprodid}}/admin-password Note: the above request url should be properly replaced by appropriate values This URL is used to change root password for vIDM node {{envid}}: "globalenvironment" {{idmprodid}}: "vidm" {{nodetype}}: "vidm-primary" Request Body { "adminPassword": "locker:password:deab31fa-ea7a-452b-a0ad-a5daa5bb4126:vidmroot071022", "currentAdminPassword": "locker:password:17e1d72f-2a2d-4105-ba13-ba26b62473ee:installerPassword" } I will replace the values in the body with appropriate values Then execute the API If you poll the request you can see whole lot of details. If it's a failure then stop polling You may now see the request created and completed in UI . Delete Password To delete the password , one can use the following API Request Method: DELETE Request: {{lcmurl}}/lcm/locker/api/v2/passwords/ I'll get the vmid from the url or from the api as shown before Response { "vmid": "b1ed53c1-c6c2-4422-ba3c-68f39b33a04a", "tenant": "default", "alias": "dummyalias", "userName": "dummy", "password": "Dummy123!", "passwordDescription": "dummypassword", "createdOn": 1664436058965, "lastUpdatedOn": 1664436058965 } In this manner if you know the API's and appropriate values to substitute you should be able to programatically change passwords on any products managed by vRSLCM 8.x

Have a usecase to increase size of vRSLCM appliance's data partition Current settings of the partitions on appliance root@dlcm [ ~ ]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 2.9G 0 2.9G 0% /dev tmpfs 3.0G 20K 3.0G 1% /dev/shm tmpfs 3.0G 1.1M 3.0G 1% /run tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup /dev/sda4 8.7G 2.1G 6.2G 26% / tmpfs 3.0G 8.4M 2.9G 1% /tmp /dev/sda2 119M 28M 85M 25% /boot /dev/mapper/stroage_vg-storage 9.8G 95M 9.2G 2% /storage /dev/mapper/data_vg-data 148G 23G 119G 16% /data tmpfs 595M 0 595M 0% /run/user/0 From vCenter PVDISPLAY output root@dlcm [ ~ ]# pvdisplay --- Physical volume --- PV Name /dev/sdc VG Name stroage_vg PV Size <10.00 GiB / not usable 0 Allocatable yes (but full) PE Size 4.00 MiB Total PE 2559 Free PE 0 Allocated PE 2559 PV UUID 1FzPjT-ESCV-7HMn-OdXG-Sbof-d2HM-ChEzXg --- Physical volume --- PV Name /dev/sdb VG Name data_vg PV Size <150.00 GiB / not usable 0 Allocatable yes (but full) PE Size 4.00 MiB Total PE 38399 Free PE 0 Allocated PE 38399 PV UUID 3xS6lh-0rjq-1HV5-kO9y-Tc5m-AYVR-uWDdpW --- Physical volume --- PV Name /dev/sdd VG Name swap_vg PV Size <8.00 GiB / not usable 0 Allocatable yes (but full) PE Size 4.00 MiB Total PE 2047 Free PE 0 Allocated PE 2047 PV UUID XHQmv4-yaGc-tBbE-qg9r-Jyto-HREF-1bPNsy Here's the /etc/fstab data for partitions. Since we are only concerned for /data , we will only work with #system mnt-pt type options,nosuid,nodev dump fsck /dev/sda4 / ext3 defaults 1 1 /dev/sda3 swap swap defaults 0 0 /dev/sda2 /boot ext3 defaults,nosuid,noacl,nodev,noexec 1 2 /dev/cdrom /mnt/cdrom iso9660 ro,noauto,nosuid,nodev 0 0 /dev/data_vg/data /data ext3 rw,nosuid,nodev,exec,auto,nouser,async 0 1 /dev/stroage_vg/storage /storage ext3 rw,nosuid,nodev,exec,auto,nouser,async 0 1 /dev/swap_vg/swap1 none swap sw 0 0 Increased disk size of hard disk 2 from 150GB to 200GB Now that the disk size is increased on the appliance level reboot appliance The moment appliance is back online or responding over network ssh and execute below command " df -h " root@dlcm [ ~ ]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 2.9G 0 2.9G 0% /dev tmpfs 3.0G 20K 3.0G 1% /dev/shm tmpfs 3.0G 1.1M 3.0G 1% /run tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup /dev/sda4 8.7G 2.1G 6.2G 26% / tmpfs 3.0G 72K 3.0G 1% /tmp /dev/sda2 119M 28M 85M 25% /boot /dev/mapper/stroage_vg-storage 9.8G 95M 9.2G 2% /storage /dev/mapper/data_vg-data 197G 23G 166G 12% /data tmpfs 595M 0 595M 0% /run/user/0 As one can see it was 150G before and the current state is 200G How does this work ? Below snippets are taken from journalctl -x When you reboot after increasing the space during every reboot everyboot scripts are triggered Sep 16 07:33:56 dlcm.cap.org vaos[959]: This script is executed on all boots, except the first one. Sep 16 07:33:56 dlcm.cap.org vaos[959]: ++ basename /usr/lib/bootstrap/everyboot Sep 16 07:33:56 dlcm.cap.org vaos[959]: + NAME=everyboot Sep 16 07:33:56 dlcm.cap.org vaos[959]: + BOOTSTRAP_DIR=/etc/bootstrap/everyboot.d Sep 16 07:33:56 dlcm.cap.org vaos[959]: + BOOTSTRAP_LOG=/var/log/bootstrap/everyboot.log Sep 16 07:33:56 dlcm.cap.org vaos[959]: + tee -a /var/log/bootstrap/everyboot.log Sep 16 07:33:56 dlcm.cap.org vaos[959]: + set -eu Sep 16 07:33:56 dlcm.cap.org vaos[959]: + set -x Sep 16 07:33:56 dlcm.cap.org vaos[959]: + log 'main bootstrap everyboot started' Sep 16 07:33:56 dlcm.cap.org vaos[959]: ++ date '+%Y-%m-%d %H:%M:%S' Sep 16 07:33:56 dlcm.cap.org vaos[959]: + echo '2022-09-16 07:33:56 main bootstrap everyboot started' Sep 16 07:33:56 dlcm.cap.org vaos[959]: 2022-09-16 07:33:56 main bootstrap everyboot started Sep 16 07:33:56 dlcm.cap.org vaos[959]: + for script in "${BOOTSTRAP_DIR}"/* Sep 16 07:33:56 dlcm.cap.org vaos[959]: + echo Sep 16 07:33:56 dlcm.cap.org vaos[959]: + '[' '!' -e /etc/bootstrap/everyboot.d/20-autogrow-disk ']' Sep 16 07:33:56 dlcm.cap.org vaos[959]: + '[' '!' -x /etc/bootstrap/everyboot.d/20-autogrow-disk ']' Sep 16 07:33:56 dlcm.cap.org vaos[959]: + log '/etc/bootstrap/everyboot.d/20-autogrow-disk starting' Sep 16 07:33:56 dlcm.cap.org vaos[959]: ++ date '+%Y-%m-%d %H:%M:%S' Sep 16 07:33:56 dlcm.cap.org vaos[959]: + echo '2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting' Sep 16 07:33:56 dlcm.cap.org vaos[959]: 2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting Sep 16 07:33:56 dlcm.cap.org vaos[959]: + /etc/bootstrap/everyboot.d/20-autogrow-disk Sep 16 07:33:56 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:56 UTC 2022 Disk Util: INFO: Scanning Hard disk sizes Sep 16 07:33:56 dlcm.cap.org rsyslogd[712]: imjournal: journal files changed, reloading... [v8.2202.0 try https://www.rsyslog.com/e/0 ] Sep 16 07:33:56 dlcm.cap.org vaos[959]: Syncing file systems Sep 16 07:33:56 dlcm.cap.org vaos[959]: which: no multipath in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/vmware/bin) Sep 16 07:33:56 dlcm.cap.org vaos[959]: Scanning SCSI subsystem for new devices and remove devices that have disappeared Sep 16 07:33:56 dlcm.cap.org vaos[959]: Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs Sep 16 07:33:57 dlcm.cap.org vaos[959]: [65B blob data] Sep 16 07:33:57 dlcm.cap.org vaos[959]: OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Sep 16 07:33:57 dlcm.cap.org vaos[959]: Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00 Sep 16 07:33:57 dlcm.cap.org vaos[959]: Type: CD-ROM ANSI SCSI revision: 05 Sep 16 07:33:58 dlcm.cap.org vaos[959]: [182B blob data] Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00 Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: CD-ROM ANSI SCSI revision: 05 Sep 16 07:33:58 dlcm.cap.org vaos[959]: Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs Sep 16 07:33:58 dlcm.cap.org vaos[959]: Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs Sep 16 07:33:58 dlcm.cap.org vaos[959]: [65B blob data] Sep 16 07:33:58 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:58 dlcm.cap.org vaos[959]: [53B blob data] Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:58 dlcm.cap.org vaos[959]: [65B blob data] Sep 16 07:33:58 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00 Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:59 dlcm.cap.org vaos[959]: [53B blob data] Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:59 dlcm.cap.org vaos[959]: [65B blob data] Sep 16 07:33:59 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 02 Lun: 00 Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:59 dlcm.cap.org vaos[959]: [53B blob data] Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:59 dlcm.cap.org vaos[959]: [65B blob data] Sep 16 07:33:59 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 03 Lun: 00 Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:59 dlcm.cap.org vaos[959]: [53B blob data] Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0 Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02 Sep 16 07:33:59 dlcm.cap.org vaos[959]: 0 new or changed device(s) found. Sep 16 07:33:59 dlcm.cap.org vaos[959]: 0 remapped or resized device(s) found. Sep 16 07:33:59 dlcm.cap.org vaos[959]: 0 device(s) removed. Sep 16 07:33:59 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sda Sep 16 07:33:59 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdb Sep 16 07:33:59 dlcm.cap.org vaos[959]: Physical volume "/dev/sdb" changed Sep 16 07:33:59 dlcm.cap.org vaos[959]: 1 physical volume(s) resized or updated / 0 physical volume(s) not resized Sep 16 07:33:59 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdc Sep 16 07:34:00 dlcm.cap.org vaos[959]: Physical volume "/dev/sdc" changed Sep 16 07:34:00 dlcm.cap.org vaos[959]: 1 physical volume(s) resized or updated / 0 physical volume(s) not resized Sep 16 07:34:00 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdd Sep 16 07:34:00 dlcm.cap.org vaos[959]: Physical volume "/dev/sdd" changed Sep 16 07:34:00 dlcm.cap.org vaos[959]: 1 physical volume(s) resized or updated / 0 physical volume(s) not resized Sep 16 07:34:00 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/stroage_vg/storage Sep 16 07:34:00 dlcm.cap.org vaos[959]: Size of logical volume stroage_vg/storage unchanged from <10.00 GiB (2559 extents). Sep 16 07:34:00 dlcm.cap.org vaos[959]: Logical volume stroage_vg/storage successfully resized. Sep 16 07:34:00 dlcm.cap.org vaos[959]: resize2fs 1.45.5 (07-Jan-2020) Sep 16 07:34:00 dlcm.cap.org vaos[959]: The filesystem is already 2620416 (4k) blocks long. Nothing to do! Sep 16 07:34:00 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/data_vg/data Sep 16 07:34:00 dlcm.cap.org vaos[959]: Size of logical volume data_vg/data changed from <150.00 GiB (38399 extents) to <200.00 GiB (51199 extents). Sep 16 07:34:01 dlcm.cap.org vaos[959]: Logical volume data_vg/data successfully resized. Sep 16 07:34:01 dlcm.cap.org vaos[959]: resize2fs 1.45.5 (07-Jan-2020) Sep 16 07:34:01 dlcm.cap.org kernel: EXT4-fs (dm-1): resizing filesystem from 39320576 to 52427776 blocks Sep 16 07:34:01 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:01,289 main ERROR Unable to locate appender "MaskedLogs" for logger config "root" Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:05,233 main ERROR Unable to locate appender "MaskedLogs" for logger config "root" Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: . ____ _ __ _ _ Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: \\/ ___)| |_)| | | | | || (_| | ) ) ) ) Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: ' |____| .__|_| |_|_| |_\__, | / / / / Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: =========|_|==============|___/=/_/_/_/ Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: :: Spring Boot :: (v2.1.16.RELEASE) Sep 16 07:34:06 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:06.313 INFO dlcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStarting] : Start> Sep 16 07:34:06 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:06.368 DEBUG dlcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStarting] : Runni> Sep 16 07:34:06 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:06.369 INFO dlcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStartupProfileInf> Sep 16 07:34:07 dlcm.cap.org systemd-resolved[1403]: Using degraded feature set (UDP+EDNS0) for DNS server 10.109.44.132. Sep 16 07:34:11 dlcm.cap.org kernel: EXT4-fs (dm-1): resized to 46792704 blocks Sep 16 07:34:11 dlcm.cap.org vlcm-service[1098]: [2022-09-16 07:34:11.274] [INFO ][main] org.spr.con.sup.PostProcessorRegistrationDelegate$BeanPostProcessorChecker: -- Bean 'configuratio> Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: [2022-09-16 07:34:12.102] [INFO ][main] com.vmw.vre.lcm.com.log.MaskingPrintStream: -- * SYSOUT/SYSERR CAPTURED: -- Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: ___ ___ _ ___ __ __ Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: __ __ | _ \ / __| | | / __| | \/ | Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: \ V / | / \__ \ | |__ | (__ | |\/| | Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _\_/_ |_|_\ |___/ |____| \___| |_| |_| Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _|"""""| _|"""""| _|"""""| _|"""""| _|"""""| _|"""""| Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: * -- Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: ___ ___ _ ___ __ __ Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: __ __ | _ \ / __| | | / __| | \/ | Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: \ V / | / \__ \ | |__ | (__ | |\/| | Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _\_/_ |_|_\ |___/ |____| \___| |_| |_| Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _|"""""| _|"""""| _|"""""| _|"""""| _|"""""| _|"""""| Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: [2022-09-16 07:34:12.156] [INFO ][main] org.spr.boo.SpringApplication: -- The following profiles are active: apiignore Sep 16 07:34:15 dlcm.cap.org launch-blackstone-spring[1099]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". Sep 16 07:34:15 dlcm.cap.org launch-blackstone-spring[1099]: SLF4J: Defaulting to no-operation (NOP) logger implementation Sep 16 07:34:15 dlcm.cap.org launch-blackstone-spring[1099]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Sep 16 07:34:17 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:17.856 INFO dlcm.cap.org --- [ main] trationDelegate$BeanPostProcessorChecker [postProcessAfterInit> Sep 16 07:34:19 dlcm.cap.org kernel: EXT4-fs (dm-1): resized filesystem to 52427776 Sep 16 07:34:19 dlcm.cap.org vaos[959]: Filesystem at /dev/mapper/data_vg-data is mounted on /data; on-line resizing required Sep 16 07:34:19 dlcm.cap.org vaos[959]: old_desc_blocks = 10, new_desc_blocks = 13 Sep 16 07:34:19 dlcm.cap.org vaos[959]: The filesystem on /dev/mapper/data_vg-data is now 52427776 (4k) blocks long. Sep 16 07:34:19 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:19 UTC 2022 Disk Util: INFO: LV Resizing /dev/swap_vg/swap1 Sep 16 07:34:19 dlcm.cap.org vaos[959]: fsadm: Filesystem "swap" on device "/dev/mapper/swap_vg-swap1" is not supported by this tool. Sep 16 07:34:19 dlcm.cap.org vaos[959]: Filesystem check failed. Sep 16 07:34:20 dlcm.cap.org vaos[959]: + RES=0 Sep 16 07:34:20 dlcm.cap.org vaos[959]: + log '/etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0' Sep 16 07:34:20 dlcm.cap.org vaos[959]: ++ date '+%Y-%m-%d %H:%M:%S' Sep 16 07:34:20 dlcm.cap.org vaos[959]: + echo '2022-09-16 07:34:20 /etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0' Sep 16 07:34:20 dlcm.cap.org vaos[959]: 2022-09-16 07:34:20 /etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0 This is the script where it's located Log Snippet from everyboot.log under /var/log/bootstrap/ + echo '2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting' 2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting + /etc/bootstrap/everyboot.d/20-autogrow-disk Fri Sep 16 07:33:56 UTC 2022 Disk Util: INFO: Scanning Hard disk sizes Syncing file systems which: no multipath in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/vmware/bin) Scanning SCSI subsystem for new devices and remove devices that have disappeared Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs Scanning for device 0 0 0 0 ...^M Scanning for device 0 0 0 0 ... OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 05 .0:0:0:0 sg0 (1) ESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[D ESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[D ESC[D^MESC[AESC[AESC[AOLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 05 Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs Scanning for device 2 0 0 0 ...^M Scanning for device 2 0 0 0 ... OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 ^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 Scanning for device 2 0 1 0 ...^M Scanning for device 2 0 1 0 ... OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 ^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 Scanning for device 2 0 2 0 ...^M Scanning for device 2 0 2 0 ... OLD: Host: scsi2 Channel: 00 Id: 02 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 ^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 02 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 Scanning for device 2 0 3 0 ...^M Scanning for device 2 0 3 0 ... OLD: Host: scsi2 Channel: 00 Id: 03 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 ^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 03 Lun: 00 Vendor: VMware Model: Virtual disk Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 02 0 new or changed device(s) found. 0 remapped or resized device(s) found. 0 device(s) removed. Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sda Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdb Physical volume "/dev/sdb" changed 1 physical volume(s) resized or updated / 0 physical volume(s) not resized Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdc Physical volume "/dev/sdc" changed 1 physical volume(s) resized or updated / 0 physical volume(s) not resized Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdd Physical volume "/dev/sdd" changed 1 physical volume(s) resized or updated / 0 physical volume(s) not resized Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/stroage_vg/storage Size of logical volume stroage_vg/storage unchanged from <10.00 GiB (2559 extents). Logical volume stroage_vg/storage successfully resized. resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 2620416 (4k) blocks long. Nothing to do! Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/data_vg/data Size of logical volume data_vg/data changed from <150.00 GiB (38399 extents) to <200.00 GiB (51199 extents). Logical volume data_vg/data successfully resized. resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/mapper/data_vg-data is mounted on /data; on-line resizing required old_desc_blocks = 10, new_desc_blocks = 13