VMware Cloud Foundation

 View Only

  • 1.  VCF 5.2 import fails with the following error - Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address failed

    Posted Jan 28, 2025 02:50 PM

    Hello,

    Performing convert workflow using VCF 5.2 brownfield import option. The storage in this case is NFS (there is no vSAN). However the convert operation fails with the following error message - 

    [2025-01-28 15:54:04,932] [INFO] vcf_brownfield:374: Brownfield Import main version: 5.2.1.0-24307788
    [2025-01-28 15:54:13,486] [INFO] sddc_manager_helper:382: Generating SDDC Manager public API token
    [2025-01-28 15:54:13,743] [INFO] request_helper:22: Response status from SDDC Manager token generation: 200
    [2025-01-28 15:54:13,869] [INFO] request_helper:22: Response status from retrieving domain: 200
    [2025-01-28 15:54:13,870] [INFO] sddc_manager_helper:427: Retrieving SDDC Manager version
    [2025-01-28 15:54:13,872] [INFO] sddc_manager_helper:440: Discovered SDDC Manager version: 5.2.1.0
    [2025-01-28 15:54:13,874] [INFO] sddc_manager_helper:382: Generating SDDC Manager public API token
    [2025-01-28 15:54:13,957] [INFO] request_helper:22: Response status from SDDC Manager token generation: 200
    [2025-01-28 15:54:13,958] [DEBUG] sddc_validator:41: Successfully fetched SDDC Manager token
    [2025-01-28 15:54:13,958] [INFO] sddc_manager_helper:382: Generating SDDC Manager public API token
    [2025-01-28 15:54:14,042] [INFO] request_helper:22: Response status from SDDC Manager token generation: 200
    [2025-01-28 15:54:14,067] [INFO] request_helper:22: Response status from retrieving domain: 200
    [2025-01-28 15:54:14,068] [INFO] sddc_manager_helper:403: Using cached SDDC Manager token header
    [2025-01-28 15:54:14,089] [INFO] request_helper:22: Response status from retrieving domain: 200
    [2025-01-28 15:54:14,089] [DEBUG] sddc_validator:56: Domain name 'domain-wklda-vcsa' presence is as expected: is_present = False
    [2025-01-28 15:54:14,090] [INFO] sddc_manager_helper:276: Retrieving SDDC Manager trusted certificates
    [2025-01-28 15:54:14,090] [INFO] sddc_manager_helper:382: Generating SDDC Manager public API token
    [2025-01-28 15:54:14,192] [INFO] request_helper:22: Response status from SDDC Manager token generation: 200
    [2025-01-28 15:54:14,224] [INFO] request_helper:22: Response status from retrieving trusted certificates: 200
    [2025-01-28 15:54:14,298] [DEBUG] security_utils:37: wklda-xxx.xxxx.com is not trusted
    [2025-01-28 15:54:14,360] [INFO] trust_vcenter:36: Retrieved server wklda-xxx.xxxx.com thumbprint (SHA256): 7B:5E:94:FF:19:DC:EC:64:92:E3:7B:DB:05:13:2A:8A:6E:0C:7D:B2:A0:D7:0A:91:BF:6B:6D:15:C6:32:23:99
    [2025-01-28 15:56:01,618] [INFO] vcenter_rest_api_helper:39: Generating session to vCenter: wklda-xxx.xxxx.com
    [2025-01-28 15:56:01,728] [INFO] request_helper:22: Response status from vCenter session authentication: 201
    [2025-01-28 15:56:01,728] [DEBUG] vcenter_rest_api_helper:47: Generated vCenter session token: 36eca79283e6596f03efe6a427469f56
    [2025-01-28 15:56:01,728] [INFO] vcenter_rest_api_helper:82: Retrieving trusted root CA chain IDs of vCenter: wklda-xxx.xxxx.com
    [2025-01-28 15:56:05,227] [INFO] request_helper:22: Response status from vCenter trusted root CA chain IDs retrieval: 200
    [2025-01-28 15:56:05,227] [INFO] vcenter_rest_api_helper:64: Retrieving trusted root CA chain with id: 6EF55F4D2541FD3FC241C7F2578674F1F2A455B4 of vCenter: wklda-xxx.xxxx.com
    [2025-01-28 15:56:05,449] [INFO] request_helper:22: Response status from vCenter trusted root CA chain retrieval: 200
    [2025-01-28 15:56:05,450] [DEBUG] vcenter_certificate_util:16: Discovered certificate chain for chain_id: 6EF55F4D2541FD3FC241C7F2578674F1F2A455B4
    [2025-01-28 15:56:05,450] [INFO] sddc_manager_helper:276: Retrieving SDDC Manager trusted certificates
    [2025-01-28 15:56:05,451] [INFO] sddc_manager_helper:382: Generating SDDC Manager public API token
    [2025-01-28 15:56:05,537] [INFO] request_helper:22: Response status from SDDC Manager token generation: 200
    [2025-01-28 15:56:05,557] [INFO] request_helper:22: Response status from retrieving trusted certificates: 200
    [2025-01-28 15:56:05,571] [INFO] sddc_manager_certificate_util:29: Adding new trusted certificate for alias: 6ef55f4d2541fd3fc241c7f2578674f1f2a455b4 with thumbprint: BD:B7:9C:DF:6D:47:85:56:69:72:D9:B4:FB:96:30:00:69:2D:BC:05:E9:E2:DB:29:E4:5A:92:09:5F:1C:86:D6
    [2025-01-28 15:56:05,571] [INFO] sddc_manager_certificate_util:29: Adding new trusted certificate for alias: wklda-xxx.xxxx.com with thumbprint: 7B:5E:94:FF:19:DC:EC:64:92:E3:7B:DB:05:13:2A:8A:6E:0C:7D:B2:A0:D7:0A:91:BF:6B:6D:15:C6:32:23:99
    [2025-01-28 15:56:05,572] [INFO] sddc_manager_helper:325: Importing trusted certificates to SDDC Manager trust store
    [2025-01-28 15:56:05,572] [DEBUG] sddc_manager_helper:327: Certificates payload contains 2 entries
    [2025-01-28 15:56:06,840] [INFO] request_helper:22: Response status from certificates import: 200
    [2025-01-28 15:56:07,378] [INFO] request_helper:22: Response status from certificates refresh: 200
    [2025-01-28 15:56:07,379] [INFO] sddc_manager_helper:276: Retrieving SDDC Manager trusted certificates
    [2025-01-28 15:56:07,379] [INFO] sddc_manager_helper:403: Using cached SDDC Manager token header
    [2025-01-28 15:56:07,399] [INFO] request_helper:22: Response status from retrieving trusted certificates: 200
    [2025-01-28 15:56:07,404] [INFO] vcf_brownfield:523: Going to check vCenter wklda-xxx.xxxx.com
    [2025-01-28 15:56:07,404] [INFO] sddc_manager_helper:448: Retrieving SDDC Manager controller info
    [2025-01-28 15:56:07,404] [INFO] sddc_manager_helper:382: Generating SDDC Manager public API token
    [2025-01-28 15:56:07,486] [INFO] request_helper:22: Response status from SDDC Manager token generation: 200
    [2025-01-28 15:56:07,513] [ERROR] request_helper:28: Result status code from SDDC Manager controller info retrieval: 404
    [2025-01-28 15:56:07,513] [INFO] sddc_manager_helper:834: Setting pre-check engine datasource
    [2025-01-28 15:56:07,513] [DEBUG] sddc_manager_helper:835: Set datasource payload: {'type': 'SDDC_MANAGER', 'authType': 'INTERNAL_MIXED', 'endpoint': {'address': ''}}
    [2025-01-28 15:56:07,858] [ERROR] request_helper:28: Result status code from set datasource: 400
    [2025-01-28 15:56:07,858] [INFO] sddc_manager_helper:846: Could not configure datasoure
    [2025-01-28 15:56:07,859] [DEBUG] sddc_manager_helper:847: b'{"errorCode":"BASELINER_DATASOURCE_VALIDATION_FAILED","arguments":["INTERNAL_MIXED_SDDC_MANAGER",""],"context":{"orchestrator.error.retriable":"false"},"message":"Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address  failed.","referenceToken":"3R676H"}'
    [2025-01-28 15:56:07,859] [DEBUG] sddc_manager_helper:849: Response from set datasource: b'{"errorCode":"BASELINER_DATASOURCE_VALIDATION_FAILED","arguments":["INTERNAL_MIXED_SDDC_MANAGER",""],"context":{"orchestrator.error.retriable":"false"},"message":"Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address  failed.","referenceToken":"3R676H"}'
    [2025-01-28 15:56:07,860] [INFO] sddc_manager_helper:403: Using cached SDDC Manager token header
    [2025-01-28 15:56:07,892] [INFO] request_helper:22: Response status from retrieving domain: 200
    [2025-01-28 15:56:08,633] [INFO] request_helper:22: Response status from trigger import guardrails: 202
    [2025-01-28 15:56:08,633] [DEBUG] sddc_manager_helper:869: Response from trigger import guardrails: b'{"id":"587857e8-4a31-46ed-8fa0-e515aea615ae","link":null,"taskId":"587857e8-4a31-46ed-8fa0-e515aea615ae","resourceId":"e852b08f-de0b-43fc-b1f6-0ce5cf80d1f7","resourceType":"BASELINER_DISCOVERY","state":"IN_PROGRESS","description":"Discover SDDC","errors":null,"timestamp":1738079768012,"completionTimestamp":null}'
    [2025-01-28 15:56:09,074] [INFO] sddc_manager_helper:901: monitor import guardrails - IN_PROGRESS
    [2025-01-28 15:56:24,214] [INFO] sddc_manager_helper:901: monitor import guardrails - IN_PROGRESS
    [2025-01-28 15:56:39,425] [INFO] sddc_manager_helper:901: monitor import guardrails - COMPLETED
    [2025-01-28 15:56:39,484] [INFO] check_domain_reporter:47: Total checks: 96, Successful checks: 88, Failed checks: 8, Internal errors: 0
    [2025-01-28 15:56:39,485] [INFO] check_domain:164: For more details, please, check:
        Failed guardrails YML: /home/vcf/vcf-brownfield-import-5.2.1.0-24307788/vcf-brownfield-toolset/output/guardrails_report_wklda-xxx.xxxx.com.yml
        Failed guardrails CSV: /home/vcf/vcf-brownfield-import-5.2.1.0-24307788/vcf-brownfield-toolset/output/guardrails_report_wklda-xxx.xxxx.com.csv
        All guardrails CSV: /home/vcf/vcf-brownfield-import-5.2.1.0-24307788/vcf-brownfield-toolset/output/guardrails_report_wklda-xxx.xxxx.com_all.csv

    Any pointers are much appreciated.



  • 2.  RE: VCF 5.2 import fails with the following error - Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address failed

    Posted Jan 29, 2025 01:36 AM

    Hello nimo1983,

    what is in the /home/vcf/vcf-brownfield-import-5.2.1.0-24307788/vcf-brownfield-toolset/output/guardrails_report_wklda-xxx.xxxx.com.yml file?


    Original Message


  • 3.  RE: VCF 5.2 import fails with the following error - Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address failed

    Posted Jan 29, 2025 04:57 AM

    by the way, I have the same error message in SDDC manager AFTER converting a brownfield environment. can be found in UI and /var/log/vmware/vcf/operatiosmanager/operatiosmanager.log


    Original Message


  • 4.  RE: VCF 5.2 import fails with the following error - Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address failed

    Broadcom Employee
    Posted Jan 29, 2025 07:41 AM
    Edited by Marek Zdrojewski Jan 29, 2025 07:41 AM

    As mentioned above, please post the "failed guardrails" for the details.

    Thanks!


    Original Message


  • 5.  RE: VCF 5.2 import fails with the following error - Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address failed

    Posted Jan 29, 2025 07:53 AM
    Edited by idefix90 Jan 29, 2025 07:55 AM

    maybe it is a DNS problem

    there must be a DNS A and PTR Record for each component, also for the SDDC manager appliance.


    Original Message


  • 6.  RE: VCF 5.2 import fails with the following error - Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address failed

    Posted Jan 30, 2025 09:56 AM

    Hi all, 

    nimo1983 i  see you used version 5.2.1.0 of the VCF import tool, it has been revamped in 5.2.1.1 and now there is already 5.2.1.2 available for download so,

    i recommend re-download the latest and try again.

    VCF Import Tool 5.2.1.2

    vcf-brownfield-import-5.2.1.2-24494579.tar.gz(9.16 MB)

    Build Number: 24494579


    Original Message


  • 7.  RE: VCF 5.2 import fails with the following error - Validation of data source of type INTERNAL_MIXED_SDDC_MANAGER and address failed

    Posted Jan 30, 2025 09:56 AM

    In addition to the new VCF Import Tool 5.2.1.2 vcf-brownfield-import-5.2.1.2-24494579.tar.gz (9.16 MB) Jan 21, 2025

    There is a new VCF-SDDC-Manager-Appliance-5.2.1.1-24397777.ova (4.44 GB) - Dec 12, 2024

    And we learn from Considerations Before Converting or Importing Existing vSphere Environments into VMware Cloud Foundation that they both works best together, so download them both and try again.


    Original Message