{}USER STORY:{}

The assisted installer should be able to use CAPI-based vsphere installs without requiring access to vcenter.

{}DESCRIPTION:{}

The installer makes calls to vcenter to determine the networks, which are required for CAPI based installs, but vcenter access is not guaranteed in the assisted installer.

See:

https://github.com/openshift/installer/pull/7962/commits/2bfb3d193d375286d80e36e0e7ba81bb74559a9d#diff-c8a93a8c9fb0e5dbfa50e3a8aa1fbd253dd324fb981a01a69f6bf843305117cbR267

https://github.com/openshift/installer/pull/7962/commits/2bfb3d193d375286d80e36e0e7ba81bb74559a9d#diff-42f3fb5184e7ed95dc5efdff5ca11cb2b713ac266322a99c03978106c0984f22R127

which were lovingly lifted from this slack thread.

{}Required:{}

In cases where the installer calls vcenter to obtain values to populate manifests, the installer should leave empty fields (or a default value) if it is unable to access vcenter. It should produce partial manifests, rather than throw an error.

{}Nice to have:{}

...

{}ACCEPTANCE CRITERIA:{}

Continued compatibility with agent installer, particularly producing capi manifests when access to vcenter fails.

{}ENGINEERING DETAILS:{}

<!--

Any additional information that might be useful for engineers: related
repositories or pull requests, related email threads, GitHub issues or
other online discussions, how to set up any required accounts and/or
environments if applicable, and so on.

-->