Holodeck 9.1 - Unable to Deploy Site B VCF Installer

[Crivit13]

Attempting to deploy a dual site Holodeck 9.1 instance by following the Holodeck documentation.
Site A deploys successfully.
Site B fails when attempting to deploy VCF Installer appliance with error message: "Error: No network mapping specified. OVF networks..."
Correct 'Site-B' portgroup selected during "New-HoloDeckInstance" run sequence and was assigned successfully to deployed nested Site B ESXi VMs.
Site B config file in /holodeck/config/ within the Site-B > vcf-installer section has the label "network1" set to null - I'd expect this contain the Site-B portgroup name.

[IOVirt]

Having the same issue. Glad to know I'm not the only. Same circumstance as above, Holodeck 9.1 and unable to deploy a site-b successfully due to vcfinstaller failing. I've examined the xxxxx-b.json config file and it looks like it's not getting the settings needed to deploy the vcfinstaller (see excerpt below). After building out the b-side vms, it now wants to deploy the vcfinstaller, doesn't find any settings for network in the json and crashes out. 

      "vcf-installer": {
        "ovaPath": null,
        "rootPassword": "VMware123!VMware123!",
        "localUserPassword": "VMware123!VMware123!",
        "hostname": null,
        "ntp": null,
        "network1": null,
        "ip0": null,
        "netmask0": null,
        "gateway": null,
        "domain": null,
        "searchpath": null,
        "dns": null,
        "depotType": "online",
        "onlineDepotDetails": {
          "depotProxyEnabled": false,
          "depotProxyDetails": {
            "protocol": "HTTPS",
            "ProxyAddress": "",
            "ProxyPort": "",
            "isAuthenticated": false,
            "authDetails": {
              "username": "",
              "password": ""
            }
          }
        },

[IOVirt]

(repost)... I'm having the same issue... Excerpt below is from the xxxxx-site-b.json. It looks like the json doesn't have the details needed to execute on vcfinstaller for site b. So after creating the site-b vms, script crashes because all the settings needed to deploy vcfinstaller are all null.

      "vcf-installer": {
        "ovaPath": null,
        "rootPassword": "VMware123!VMware123!",
        "localUserPassword": "VMware123!VMware123!",
        "hostname": null,
        "ntp": null,
        "network1": null,
        "ip0": null,
        "netmask0": null,
        "gateway": null,
        "domain": null,
        "searchpath": null,
        "dns": null,
        "depotType": "online",
        "onlineDepotDetails": {
          "depotProxyEnabled": false,
          "depotProxyDetails": {
            "protocol": "HTTPS",
            "ProxyAddress": "",
            "ProxyPort": "",
            "isAuthenticated": false,
            "authDetails": {
              "username": "",
              "password": ""
            }
          }
        },

[IOVirt]

(repost)... I'm having the same issue... Excerpt below is from the xxxxx-site-b.json. It looks like the json doesn't have the details needed to execute on vcfinstaller for site b. So after creating the site-b vms, script crashes because all the settings needed to deploy vcfinstaller are all null.

 

      "vcf-installer": {

        "ovaPath": null,

        "rootPassword": "VMware123!VMware123!",

        "localUserPassword": "VMware123!VMware123!",

        "hostname": null,

        "ntp": null,

        "network1": null,

        "ip0": null,

        "netmask0": null,

        "gateway": null,

        "domain": null,

        "searchpath": null,

        "dns": null,

        "depotType": "online",

        "onlineDepotDetails": {

          "depotProxyEnabled": false,

          "depotProxyDetails": {

            "protocol": "HTTPS",

            "ProxyAddress": "",

            "ProxyPort": "",

            "isAuthenticated": false,

            "authDetails": {

              "username": "",

              "password": ""

            }

          }

        },

[Crivit13]

OK thanks. Slightly different from what I'm seeing. 
I've set Site A MasterCIDR to 10.1.0.0/20 & Site B MasterCIDR to 10.2.0.0/20

Post failure of Site B VCF-Installer, the Site B configuration file & VCF-Installer section for Site-B contains all the configuration parameters with the exception of "network1" which designates the VMs portgroup. (Sorry can't post the details I'm on a dark site)
Working around this issue by waiting for the Site B deployment to fail, manually updating the Site B configuration .json file with the correct portgroup name for the VCF-Installer, restarting the Site B deployment via repeating the "New-HoloDeckInstance" command.
So far so good, will update when/if the full deployment completes.