SureshKumarMuth's Posts

You can export the VM as ovf template by following the steps given below,  Login to vSphere web client. Click on Hosts & Clusters. Choose the correct Virtual machine which you want to export. Right Click on virtual machine > Template > Export OVF Template. Export OVF Template wizard will open :- First provide the name.

Hi @Arnaud_L  Good to know that the issue is resolved.  Since you are using second nic in VCSA. Could you please if you have any document for reference or steps to configure second nic in VCSA ? I saw someone asked for it in the recent past. I can see many use cases for this and I think still it is a manual process. It would be a great help for others if they have some reference. Currently, I dont have any lab to try that :).  Regards, Suresh

Could you please clarify about the upgrade task ? I upgraded my vCenter Appliance 7 to 8 and since then, i'm not able to backup the configuration anymore (everything else seems to work nicely). The import of the data did fail, but mainly because of the missing 2nd adapter on the new appliance in v8 (which I corrected manually once the upgrade process finished).  -- if the import of the data failed how did the upgrade task completed successfully ? and what is 2nd adapter. you mean NIC ? VCSA by default contains only one NIC.  What did you do to fix it. -- did the prevalidation before upgrade was clear? --after upgrading you got the message as "upgrade completed successfully ". I suspect the upgrade was not fully done. My issue raise when I want to backup my configuration, I got the following error : Invalid vCenter Server Status: All required services are not up! Stopped services: 'updatemgr'. How are you backing up configuration ?  I dont think we can redo the stage 2 alone once the appliance is up on the desired version. You may have to restart the whole process if you have your old 7.x , you can power it on again after shutting down the new VC 8.x and retry the upgrade. Please note that if you try to revert, you may lose some data which was generated after the 8.x VC came into live (example; performance stats, tasks and events etc ...)  

Looks like something is wrong at db level. 2023-06-06T14:08:34.095Z error vmware-vum-server[07441] [Originator@6876 sub=Default] [Vdb::IsRecoverableErrorCode] Unable to recover from 42703:1^M 2023-06-06T14:08:34.095Z error vmware-vum-server[07441] [Originator@6876 sub=Default] [VdbStatement] SQLError was thrown: "ODBC error: (42703) - ERROR: column "bulletin_severity" does not exist;^M --> Error while executing the query" is returned when executing SQL statement "SELECT id, type, title, meta_uid, generic, category, component, service_pack, security_fix, impact, hyperlink, patchconturl, signatureurl, locale, description, vendor, releasedate, downloadtime, path, vendor_uid, bugtraq_uid, cve_uid, deleted, run, exec_platform, release_build, bundle_type, installation_impacts, component_name, code_version, product_version, release, metadataFileId, hidden, recalled, hostupdate_category, bulletin_severity, bulletin_category, bulletin_urgency FROM VCI_UPDATES WHERE deleted ="^M 2023-06-06T14:08:34.095Z error vmware-vum-server[07441] [Originator@6876 sub=VcIntegrity] [vcIntegrity 764] Error in start VUM server^M 2023-06-06T14:08:34.095Z info vmware-vum-server[07441] [Originator@6876 sub=VcIntegrityPlugin] [plugin 270] VcIntegrityPlugin Start^M   a column named  "bulletin_severity" is missing. Not sure if this is a bug. I could not find any KB article for this issue. May be you can raise a ticket with vmware and let them check. I doubt VUM DB reset will help here.

If you have already checked using curl -v then thats fine. Since we are running out of options, I can suggest one thing just to isolate the issue. Check if you can quickly deploy a VCSA 7.x and try to add identity source with same settings. This would help us to conclude if this is due to the version changes ... may be based on the result we can find next course of action. You may also raise a vmware support ticket where they can deep dive into logs.

I am seeing two errors 1. Java exception , unparseable date. Not sure if this is the contributing factor of this issue, in that case code fix might be needed, only vmware can help here 2023-06-06T02:13:13.851Z ERROR ssoAdminServer[141:pool-2-thread-6] [OpId=lgph43x9-1041449-auto-mbl8-h5:70238925] [com.vmware.identity.interop.ldap.OpenLdapClientLibrary] Error when trying to parse validity date java.text.ParseException: Unparseable date: "20530319022108Z" 2. After the above exception, I can still see the process goes on and failed with following error 2023-06-06T02:13:13.868Z WARN ssoAdminServer[141:pool-2-thread-6] [OpId=lgph43x9-1041449-auto-mbl8-h5:70238925] [com.vmware.identity.interop.ldap.LdapErrorChecker] Error received by LDAP client: com.vmware.identity.interop.ldap.OpenLdapClientLibrary, error code: -1 2023-06-06T02:13:13.868Z WARN ssoAdminServer[141:pool-2-thread-6] [OpId=lgph43x9-1041449-auto-mbl8-h5:70238925] [com.vmware.identity.idm.server.ServerUtils] cannot bind connection: [ldaps://ad01dc01.ad1.lab:3269, svc_ldaps@ad1.lab] 2023-06-06T02:13:13.869Z ERROR ssoAdminServer[141:pool-2-thread-6] [OpId=lgph43x9-1041449-auto-mbl8-h5:70238925] [com.vmware.identity.idm.server.ServerUtils] cannot establish ldap connection with URI: [ldaps://ad01dc01.ad1.lab:3269] because [com.vmware.identity.interop.ldap.ServerDownLdapException] with reason [Can't contact LDAP server] therefore will try to attempt to use secondary URIs, if applicable   It looks like a connectivity issue but you have already confirmed no firewall in place and the same machine with ldap works fine. Since it is not working for ldaps connection might be something due to the certs but could not derive anything. Lets check vmware-identity-sts.log to see if we get any messages there. Can you run nc command on VCSA and check if the connections are fine on ports related to ldaps, just to double check. 

Do you have any identity source created already using AD Integrated Windows Authentication ? or this is the first one you are trying to create using ldaps ? If you have IWA type identity source already, then try to remove that and add an ldaps based Identity source.

Strange, do you have the PSOD screenshot, can you provide the screenshot. To my understanding an upgrade should create the missing files. But, looks like it doesn't. Have you tried this upgrade on other nodes in the system ? Just to see if this issue is only with this particular node or all the nodes which are using this custom image.

I just checked a 7.x node and I can see the directory in the ESXi , so this concludes there is no change in the directory structure in the version 7.x. Could you please let me know if you are using VMware image or some custom image ? Is this happening only on one node or all the nodes ?  Have you tried reverting your upgrade after facing this issue ? Do you see the directory in 6.7 version ? 

These messages looks pretty general for me. I dont see any messages related to hostprofile (applying / error message related to HP). Can you please check for the error message which you saw in the webclient in hostd log and share 50 lines before and after the error message or attach the hostd log file in the reply. 

Looks like something messed up at RAID level and volume is not usable.  If the logical volume was erased and new volume was created during the expansion process , then you will not see the data. Before making further changes ,it is better to  contact HPE and get their support to bring the volume back to same state as it was before.  

As you unchecked all the NICs and it works well, so the issue could be related to some configuration parameter related to NICs. Did you get a chance to check the hostd log on the ESXi node ? That will give you more information on why the operation failed with specific errors related to the configuration. This article may not be related to this issue, just a reference for you to check hostd log on the ESXi node  https://kb.vmware.com/s/article/1039148 Hope this helps!! Or you can attach the hostd.log here, I can check if I see any errors related to the operation. Regards, Suresh

Do you see the same when you directly login to ESXi node using host client ? Can you try to access the ESXi host directly and check if you get options to update tool or how does it show there. This will help to isolate the issue. If it is fine at ESXi end then there could be some issues between ESXi and VC in passing the data. Regards, Suresh

Is it happening on one particular VM or all the VMs in the host after upgrading the node to 7.x ? Can you share the vmware.log file and hostd.log file from the ESXi node with VM name and time stamp. I can have a look at the logs to see what is causing this issue.