1 2 Previous Next 16 Replies Latest reply on Dec 17, 2018 8:08 AM by broberts1974

    vSAN Build Recommendation Engine Health

    alainrussell Enthusiast

      We're seeing an error on our VSAN cluster after upgrading from 6.5 to 6.7. Error is "Unexpected VMware Update Manager (VUM)baseline creation failure. Please check vSAN and VUM logs for details", we've reset the VUM database and checked the logs but nothing sticks out.

       

      Has anyone seen (and resolved) something similar?

        • 1. Re: vSAN Build Recommendation Engine Health
          alainrussell Enthusiast

          This appeared to come right overnight after an update to the latest 6.7b VCSA.

          • 3. Re: vSAN Build Recommendation Engine Health
            Neilly Enthusiast

            We are seeing the same issue - we also upgraded from v6.5U2 to v6.7U1. I've opened an SR (just 5 minutes ago). I have found several ssues after the upgrade:

            1. The VSAN health check has three warnings under the vsan build recommendation test

                 1.1 vsan build recommendation engine health

                 1.2 vsan build recommendation

                 1.3 vsan release catalog up-to-date

            2. VUM system managed baseline group host patch for the vsan cluster is stuck at v6.5U2 - it should be updated to v6.7u1

            3. VUM system managed baseline only has v6.5U2 and does not have v6.7U1

             

            The fundamental issue seems to be the system's inability to download the current release catalog db file. When this error occurs an option is made available to upload the file manually. Of course there is no information as to where that file is located - even the docs are silent on where the file is located, well except for the exceedingly vague "VMWare cloud". I eventually found a link in a very new KB 58891 - VMware Knowledge Base - which points to this location for the release catalog db file :

            https://vcsa.vmware.com/ph/api/v1/results?deploymentId=tba4919b-2dce-f4585-9556-a780bb9ac060&collectorId=VsanCloudHealth…

             

            I noticed with some concern that the url, and the file itself, contains "6_5" - maybe the newer v6.7 of vcenter/vum/vsan are looking in the wrong location? Regardless saving the file locally and uploading it to the vcenter server resolved the issue of the release catalog not being up-to-date. However a new issue then arose - the vsan build recommendation engine health check has a warning that there is an "Unexpected VUM baseline creation failure. Check the vsan and vum logs".

             

            Checking the logs indicates that the problem is that the release catalog db file does not contain up-to-date version information for v6.7U1 as the build number it has for v6.7.0 (8169922) is not the same as v6.7.0 U1 (10302608) which I downloaded from vmware and imported to vum as an "ESXi Image" and then used for a Custom baseline so I could upgrade my ESXi vsan hosts.

             

            Here is the error from the log :

            vmware-vsan-health-service-2.log.gz:2018-10-31T17:13:50.659Z INFO vsan-mgmt[Thread-1219] [VsanVumConnection::RemediateVsanClusterInVum opID=noOpId] build = {'release': {'vcVersion': ['6.7.0'], 'profileName': 'ESXi-6.7.0-8169922-standard', 'baselineName': 'VMware ESXi 6.7.0 (build 8169922)', 'isoDisplayName': 'VMware ESXi Release  6.7.0, Build 8169922', 'depotInfo': {'params': '%7B%22sourcefilesize%22%3A%22346359808%22%2C%22dlgcode%22%3A%22ESXI670%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%22f4fa9947-85e7-4ffd-8287-9519bf903eb8%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.7.0%22%7D', 'downloadurl': 'https://download2.vmware.com/software/esx/67/VMware-VMvisor-Installer-6.7.0-8169922.x86_64.iso', 'familyversion': '6.7', 'productfamily': 'VMware vSphere'}, 'bldnum': 8169922}}

             

            So if vmware can get the release catalog db file into the right location (and/or name) and updated with the most recent build info then everything should start working again.

             

            Cheers,

             

            Ron

            • 4. Re: vSAN Build Recommendation Engine Health
              Stom2015 Lurker

              Hi Ron,

               

              Anything news here? Did you get a fix?

               

              Best Regards,

              Marcus

              • 5. Re: vSAN Build Recommendation Engine Health
                Kambrosia Lurker

                Same problem here...

                did you get a fix ?

                • 6. Re: vSAN Build Recommendation Engine Health
                  Neilly Enthusiast

                  Hi,

                   

                  I've received three emails and two voicemails but haven't received a fix. I did recheck the kb with the links to the downloadable json file (kb 58891) to see if they silently updated the file. And they have updated it! But all they did was remove any references to the current release - ie removed v6.7 U1. This is a bit of a step forward in that now the release version and build number are correctly correlated. All they have to do now is add in the current release version and build number (v6.7 U1, 10302608).

                   

                  Just for completeness sake - and to ensure proper historical documentation - here are the two "content" sections of the json file for comparison.

                   

                  A) Previous version, and what I initially downloaded :

                  arrivalDate1540942175000
                  processedDate1540967375000
                  content"{\"releasePreferenceOrder\": [\"ESXi 6.7 U1\", \"ESXi 6.7\", \"ESXi 6.5 U2\", \"ESXi 6.5 U1\", \"vSAN 6.6\", \"ESXi 6.5\", \"ESXi 6.0 U3\", \"ESXi 6.0 U2\", \"ESXi 6.0 U1\", \"ESXi 6.0\", \"ESXi 5.5\"], \"timestamp\": 1540893530, \"version\": \"1.0.9\", \"releaseInfo\": {\"ESXi 6.5 U1\": {\"release\": {\"vcVersion\": [\"6.5.0\"], \"depotInfo\": {\"familyversion\": \"6.5\"}}}, \"ESXi 6.5 U2\": {\"release\": {\"baselineName\": \"VMware ESXi 6.5.0 U2 (build 8294253)\", \"isoDisplayName\": \"VMware ESXi Release 6.5.0, Build 8294253\", \"depotInfo\": {\"downloadurl\": \"https://download2.vmware.com/software/esx/65/VMware-VMvisor-Installer-6.5.0.update02-8294253.x86_64.iso\", \"productfamily\": \"VMware vSphere\", \"params\": \"%7B%22sourcefilesize%22%3A%22354357248%22%2C%22dlgcode%22%3A%22ESXI65U2%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%22cbf49b96-694a-4052-8904-85bf67a14515%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.5.0+U2%22%7D\", \"familyversion\": \"6.5\"}, \"bldnum\": 8294253, \"vcVersion\": [\"6.5.0\"], \"patchids\": [\"ESXi650-Update02\"], \"profileName\": \"ESXi-6.5.0-20180502001-standard\", \"patchDisplayName\": \"VMware ESXi 6.5.0 U2 (vSAN 6.6.1 Update 2, build 8294253)\"}}, \"ESXi 6.5\": {\"release\": {\"vcVersion\": [\"6.5.0\"], \"depotInfo\": {\"familyversion\": \"6.5\"}}}, \"ESXi 6.7\": {\"release\": {\"baselineName\": \"VMware ESXi 6.7.0 (build 8169922)\", \"isoDisplayName\": \"VMware ESXi Release 6.7.0, Build 8169922\", \"depotInfo\": {\"downloadurl\": \"https://download2.vmware.com/software/esx/67/VMware-VMvisor-Installer-6.7.0-8169922.x86_64.iso\", \"productfamily\": \"VMware vSphere\", \"params\": \"%7B%22sourcefilesize%22%3A%22346359808%22%2C%22dlgcode%22%3A%22ESXI670%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%22f4fa9947-85e7-4ffd-8287-9519bf903eb8%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.7.0%22%7D\", \"familyversion\": \"6.7\"}, \"bldnum\": 8169922, \"vcVersion\": [\"6.7.0\"], \"profileName\": \"ESXi-6.7.0-8169922-standard\"}}, \"ESXi 6.0 U1\": {\"release\": {\"vcVersion\": [\"6.0.0\"], \"depotInfo\": {\"familyversion\": \"6.0\"}}}, \"ESXi 6.7 U1\": {\"release\": {\"baselineName\": \"VMware ESXi 6.7.0 (build 8169922)\", \"isoDisplayName\": \"VMware ESXi Release 6.7.0, Build 8169922\", \"depotInfo\": {\"downloadurl\": \"https://download2.vmware.com/software/esx/67/VMware-VMvisor-Installer-6.7.0-8169922.x86_64.iso\", \"productfamily\": \"VMware vSphere\", \"params\": \"%7B%22sourcefilesize%22%3A%22346359808%22%2C%22dlgcode%22%3A%22ESXI670%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%22f4fa9947-85e7-4ffd-8287-9519bf903eb8%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.7.0%22%7D\", \"familyversion\": \"6.7\"}, \"bldnum\": 8169922, \"vcVersion\": [\"6.7.0\"], \"profileName\": \"ESXi-6.7.0-8169922-standard\"}}, \"ESXi 6.0 U3\": {\"release\": {\"baselineName\": \"VMware ESXi 6.0.0 U3 (build 5050593)\", \"isoDisplayName\": \"VMware ESXi Release 6.0.0, Build 5050593\", \"depotInfo\": {\"downloadurl\": \"https://download2.vmware.com/software/vi/60/VMware-VMvisor-Installer-6.0.0.update03-5050593.x86_64.iso\", \"productfamily\": \"VMware vSphere\", \"params\": \"%7B%22sourcefilesize%22%3A%22378443776%22%2C%22dlgcode%22%3A%22ESXI60U3%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%2228e9acbf-0df5-4a31-b75c-55344db36598%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.0U3%22%7D\", \"familyversion\": \"6.0\"}, \"bldnum\": 5050593, \"vcVersion\": [\"6.0.0\"], \"patchids\": [\"ESXi600-Update03\"], \"profileName\": \"ESXi-6.0.0-20170202001-standard\", \"patchDisplayName\": \"VMware ESXi 6.0.0 U3 (vSAN 6.2, build 5050593)\"}}, \"ESXi 6.0 U2\": {\"release\": {\"vcVersion\": [\"6.0.0\"], \"depotInfo\": {\"familyversion\": \"6.0\"}}}, \"vSAN 6.6\": {\"release\": {\"vcVersion\": [\"6.5.0\"], \"depotInfo\": {\"familyversion\": \"6.5\"}}}, \"ESXi 5.5\": {\"release\": {\"vcVersion\": [\"5.5.0\"], \"depotInfo\": {\"familyversion\": \"5.5\"}}}, \"ESXi 6.0\": {\"release\": {\"vcVersion\": [\"6.0.0\"], \"depotInfo\": {\"familyversion\": \"6.0\"}}}}, \"patchRecommendation\": {\"ESXi 6.5 U1\": [], \"ESXi 6.5 U2\": [\"ESXi650-201810401-BG\"], \"ESXi 6.5\": [], \"ESXi 6.7\": [\"ESXi670-201810401-BG\"], \"ESXi 6.0 U1\": [], \"ESXi 6.7 U1\": [], \"ESXi 6.0 U3\": [\"ESXi600-201807401-BG\"], \"ESXi 6.0 U2\": [], \"vSAN 6.6\": [], \"ESXi 5.5\": [], \"ESXi 6.0\": []}, \"knownReleasesMapping\": {\"2718056\": \"beta\", \"4600945\": \"beta\", \"4179636\": \"beta\", \"2615706\": \"beta\", \"3074370\": \"beta\", \"1746972\": \"beta\", \"5146855\": \"beta\", \"3380126\": \"beta\", \"5224590\": \"beta\", \"5050594\": \"beta\", \"1474529\": \"beta\", \"5230636\": \"beta\", \"5224936\": \"beta\", \"2143828\": \"beta\", \"3825890\": \"beta\", \"2809294\": \"beta\", \"4192242\": \"beta\", \"3029759\": \"beta\", \"2403254\": \"beta\", \"4345814\": \"beta\", \"3030015\": \"beta\", \"1892725\": \"beta\", \"4724148\": \"beta\", \"1623379\": \"beta\", \"5572662\": \"beta\", \"4564108\": \"beta\", \"3343346\": \"beta\", \"3566909\": \"beta\", \"2638310\": \"beta\", \"2069601\": \"beta\", \"4510823\": \"beta\", \"3620773\": \"beta\", \"2494575\": \"beta\", \"1882254\": \"beta\", \"3247721\": \"beta\", \"5310539\": \"beta\", \"1746027\": \"beta\", \"4887373\": \"beta\", \"2456378\": \"beta\", \"2302652\": \"beta\", \"3568723\": \"beta\", \"2715442\": \"beta\", \"3116896\": \"beta\"}}"

                   

                  B) Current version, grabbed Nov 7, 2018 at 4:50PM PST

                  arrivalDate1541372979000
                  processedDate1541401779000
                  content"{\"releasePreferenceOrder\": [\"ESXi 6.7\", \"ESXi 6.5 U2\", \"ESXi 6.5 U1\", \"vSAN 6.6\", \"ESXi 6.5\", \"ESXi 6.0 U3\", \"ESXi 6.0 U2\", \"ESXi 6.0 U1\", \"ESXi 6.0\", \"ESXi 5.5\"], \"timestamp\": 1540548184, \"version\": \"1.0.9\", \"releaseInfo\": {\"ESXi 6.5 U1\": {\"release\": {\"vcVersion\": [\"6.5.0\"], \"depotInfo\": {\"familyversion\": \"6.5\"}}}, \"ESXi 6.5 U2\": {\"release\": {\"baselineName\": \"VMware ESXi 6.5.0 U2 (build 8294253)\", \"isoDisplayName\": \"VMware ESXi Release 6.5.0, Build 8294253\", \"depotInfo\": {\"downloadurl\": \"https://download2.vmware.com/software/esx/65/VMware-VMvisor-Installer-6.5.0.update02-8294253.x86_64.iso\", \"productfamily\": \"VMware vSphere\", \"params\": \"%7B%22sourcefilesize%22%3A%22354357248%22%2C%22dlgcode%22%3A%22ESXI65U2%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%22cbf49b96-694a-4052-8904-85bf67a14515%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.5.0+U2%22%7D\", \"familyversion\": \"6.5\"}, \"bldnum\": 8294253, \"vcVersion\": [\"6.5.0\"], \"patchids\": [\"ESXi650-Update02\"], \"profileName\": \"ESXi-6.5.0-20180502001-standard\", \"patchDisplayName\": \"VMware ESXi 6.5.0 U2 (vSAN 6.6.1 Update 2, build 8294253)\"}}, \"ESXi 6.5\": {\"release\": {\"vcVersion\": [\"6.5.0\"], \"depotInfo\": {\"familyversion\": \"6.5\"}}}, \"ESXi 6.7\": {\"release\": {\"baselineName\": \"VMware ESXi 6.7.0 (build 8169922)\", \"isoDisplayName\": \"VMware ESXi Release 6.7.0, Build 8169922\", \"depotInfo\": {\"downloadurl\": \"https://download2.vmware.com/software/esx/67/VMware-VMvisor-Installer-6.7.0-8169922.x86_64.iso\", \"productfamily\": \"VMware vSphere\", \"params\": \"%7B%22sourcefilesize%22%3A%22346359808%22%2C%22dlgcode%22%3A%22ESXI670%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%22f4fa9947-85e7-4ffd-8287-9519bf903eb8%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.7.0%22%7D\", \"familyversion\": \"6.7\"}, \"bldnum\": 8169922, \"vcVersion\": [\"6.7.0\"], \"profileName\": \"ESXi-6.7.0-8169922-standard\"}}, \"ESXi 6.0 U1\": {\"release\": {\"vcVersion\": [\"6.0.0\"], \"depotInfo\": {\"familyversion\": \"6.0\"}}}, \"ESXi 6.0\": {\"release\": {\"vcVersion\": [\"6.0.0\"], \"depotInfo\": {\"familyversion\": \"6.0\"}}}, \"ESXi 6.0 U3\": {\"release\": {\"baselineName\": \"VMware ESXi 6.0.0 U3 (build 5050593)\", \"isoDisplayName\": \"VMware ESXi Release 6.0.0, Build 5050593\", \"depotInfo\": {\"downloadurl\": \"https://download2.vmware.com/software/vi/60/VMware-VMvisor-Installer-6.0.0.update03-5050593.x86_64.iso\", \"productfamily\": \"VMware vSphere\", \"params\": \"%7B%22sourcefilesize%22%3A%22378443776%22%2C%22dlgcode%22%3A%22ESXI60U3%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%2228e9acbf-0df5-4a31-b75c-55344db36598%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Product+Binaries%22%2C%22productversion%22%3A%226.0U3%22%7D\", \"familyversion\": \"6.0\"}, \"bldnum\": 5050593, \"vcVersion\": [\"6.0.0\"], \"patchids\": [\"ESXi600-Update03\"], \"profileName\": \"ESXi-6.0.0-20170202001-standard\", \"patchDisplayName\": \"VMware ESXi 6.0.0 U3 (vSAN 6.2, build 5050593)\"}}, \"ESXi 6.0 U2\": {\"release\": {\"vcVersion\": [\"6.0.0\"], \"depotInfo\": {\"familyversion\": \"6.0\"}}}, \"vSAN 6.6\": {\"release\": {\"vcVersion\": [\"6.5.0\"], \"depotInfo\": {\"familyversion\": \"6.5\"}}}, \"ESXi 5.5\": {\"release\": {\"vcVersion\": [\"5.5.0\"], \"depotInfo\": {\"familyversion\": \"5.5\"}}}}, \"patchRecommendation\": {\"ESXi 6.5 U1\": [], \"ESXi 6.5 U2\": [\"ESXi650-201810401-BG\"], \"ESXi 6.5\": [], \"ESXi 6.7\": [\"ESXi670-201810401-BG\"], \"ESXi 6.0 U1\": [], \"ESXi 6.0\": [], \"ESXi 6.0 U3\": [\"ESXi600-201807401-BG\"], \"ESXi 6.0 U2\": [], \"vSAN 6.6\": [], \"ESXi 5.5\": []}, \"knownReleasesMapping\": {\"2718056\": \"beta\", \"4600945\": \"beta\", \"4179636\": \"beta\", \"2615706\": \"beta\", \"3074370\": \"beta\", \"1746972\": \"beta\", \"5146855\": \"beta\", \"3380126\": \"beta\", \"5224590\": \"beta\", \"5050594\": \"beta\", \"1474529\": \"beta\", \"5230636\": \"beta\", \"5224936\": \"beta\", \"2143828\": \"beta\", \"3825890\": \"beta\", \"2809294\": \"beta\", \"4192242\": \"beta\", \"3029759\": \"beta\", \"2403254\": \"beta\", \"4345814\": \"beta\", \"3030015\": \"beta\", \"1892725\": \"beta\", \"4724148\": \"beta\", \"1623379\": \"beta\", \"5572662\": \"beta\", \"4564108\": \"beta\", \"3343346\": \"beta\", \"3566909\": \"beta\", \"2638310\": \"beta\", \"2069601\": \"beta\", \"4510823\": \"beta\", \"3620773\": \"beta\", \"2494575\": \"beta\", \"1882254\": \"beta\", \"3247721\": \"beta\", \"5310539\": \"beta\", \"1746027\": \"beta\", \"4887373\": \"beta\", \"2456378\": \"beta\", \"2302652\": \"beta\", \"3568723\": \"beta\", \"2715442\": \"beta\", \"3116896\": \"beta\"}}"

                   

                  Cheers,

                   

                  Ron

                  • 7. Re: vSAN Build Recommendation Engine Health
                    Stom2015 Lurker

                    ...

                    should be fixed in U2 (Q1/2019).

                     

                    Best Regards,

                    Marcus

                    • 8. Re: vSAN Build Recommendation Engine Health
                      Neilly Enthusiast

                      Hi,

                       

                      Update - finally was able to connect with the vmware tech support today. Over the course of about an hour of poking around on the vcenter server (stopping services, starting services, checking the vsan health log, etc.) he came to the decision to reset the VUM database. This wipes out any custom baselines, but we only had two, one of which was for the upgrade to v6.7U1. So no problem. Unfortunately this does not seem to have corrected the problem since the vsan health check is still showing an alert.

                       

                      Actually this does not surprise me since my own digging points to the vsan release catalog being the problem and the VUM db reset does not touch the vsan release catalog. I am expecting a call back from vmware tomorrow to see how things went and determine next steps.

                       

                      Cheers,

                       

                      Ron

                      • 9. Re: vSAN Build Recommendation Engine Health
                        HFMudd Novice

                        I'm stuck in the same boat after upgrading to 6.7u1 - vSAN support finally punted to VUM support. I'm waiting to hear back from them. I'm thinking the same thing you are, curious to hear if that is really where things resolve.

                        • 10. Re: vSAN Build Recommendation Engine Health
                          Neilly Enthusiast

                          Worked with vmware support today. The tech suggested that we could workaround the issues by "silencing" the health check alarm and creating a custom baseline in VUM based on importing the ESXi ISO image file. I responded by pointing out that the workaround does not address the issue of the vsan release catalog db file being populated with invalid data and that we should first fix that before attempting any workarounds. After all I had previously already done just that so I could upgrade from 6.5 to 6.7U1. He checked with someone at vmware and decided to check internally with his team to see if a new json file with the correct and current ESXi version/build number data is going to be released any time soon.

                           

                          For those that are talking to vmware tech support feel free to reference my support ticket : 18973209311. Also please submit feedback on the kb 58891 to encourage them to update the release catalog db file with current release versions and build numbers.

                           

                          Cheers,

                           

                          Ron

                          • 11. Re: vSAN Build Recommendation Engine Health
                            Neilly Enthusiast

                            VMware has updated the release catalog db file as of Monday Nov 26 2018. It now contains the correct data for ESXi 6.7 U1.

                             

                            After downloading the file via the link in vmware kb 58891 I manually uploaded the file to the VSAN system which cleared the error on the vSAN Build Recommendation health checks and also fixed the VUM Baselines which were stuck at a prior version and did not include the baseline group for the vSAN Cluster.

                             

                            To manually upload the release catalog db file you will need to use the HTML client as the Flash client has no method to do this:

                                 1. Go to Hosts/Clusters

                                 2. Select your vsan cluster

                                 3. Go to Monitor

                                 4. Go to vSAN/Health

                                 5. Expand the "vSAN Build Recommendation health" check

                                 6. Select the "vSAN release catalog up-to-date" sub check

                                 7. Click the link "Update From File" and browse to / select the json file you previously downloaded from kb 58891.

                             

                            Things that are still wrong:

                                 1. The date/time stamp for the "Local release DB copy last updated" is not correct, mine says  2018-10-16 21:00:00  whereas it should be either the time I updated the file (2018-11-27) or it should be the time that vmware updated the file (2018-11-26).

                             

                            Cheers,

                             

                            Ron

                            • 12. Re: vSAN Build Recommendation Engine Health
                              rickolson2018 Lurker

                              Last week I also got the 'Unexpected VUM baseline creation failure' warning.  However, I haven't updated to 6.7.  My environment is all still 6.5.  Seems pretty strange - I'm going to take a look at the KB you linked here, but just thought I'd toss this out in case anyone else is on ESXi 6.5 and also experiencing this issue.

                              • 13. Re: vSAN Build Recommendation Engine Health
                                Neilly Enthusiast

                                Final update from vmware - they are working on documenting the fix in a new kb. While that is being done here is the rest of the fix - after updating the release catalog db file manually :

                                 

                                If vcenter has internet connectivity
                                Open an SSH session to the vCenter Appliance that is only managing the vSAN 6.7 U1 cluster.
                                Edit the /etc/vmware-vsan-health/config.conf file to add vSAN release catalog entry with keyword defaultmetadataurl. vSAN's config.conf has section for VumIntegration with enabled flag as True. Add new entry to the same section.
                                After update config.conf VumIntegration sectio should look like:

                                [VumIntegration]
                                enabled = True
                                defaultmetadataurl = https://vcsa.vmware.com/ph/api/v1/results?deploymentId=2d02e861-7e93-4954-9a73-b08692a330d1&collectorId=VsanCloudHealth.6_5&objectId=0c3e9009-ba5d-4e5f6-bae8-f25ec506d219&type=vsan-updates-json
                                Restart the vSAN management service
                                In the vSphere Web Client, browse to:
                                Administration > Deployment > System Configuration > Services > vSAN Health Service > Actions > Restart).
                                From the VCSA CLI, run this command: /usr/lib/vmware-vmon/vmon-cli -r vsan-health



                                It seems to me that the fix points to a new (different) url from whatever is built-in as a default. For whatever reason they are not updating the catalog file at the default url and instead are providing the fixed catalog file at a new url location.

                                 

                                Cheers,

                                 

                                Ron

                                2 people found this helpful
                                • 14. Re: vSAN Build Recommendation Engine Health
                                  Nocturne Novice

                                  Is it possible, that this issue also exist in a 6.5 U2 environment? We see the same behavior in our installation since 1-2 weeks.

                                  1 2 Previous Next