-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting "Error processing requst errors" when building more custom VMs #23
Comments
@marinalf What value were you using for the OS Family for the VM? I can see an error in the logs suggesting this may be a case sensitivity issue. |
Thanks, @philipowen! It is case-sensitive, I switched to LINUX now. The only other pending issues now are:
network_interfaces {
network_uid = "VLAN-PRIMARY" # Need data source support for existing network
name = "Network adapter 1"
mac_address = "00:50:56:97:d7:90"
type = "VIRTUAL_VMXNET_3"
ip_address = "198.18.133.100"
rdp_enabled = false
} |
Glad to hear it worked @marinalf . I beleive there's a fix for the IP issue coming pretty soon. I'm less sure about the first one, though I think is also a known issue and is due to be addressed. |
Hi @marinalf The default network should no longer be created with the topology as per v0.1.15 of the provider, so you should be able to specify that network in your terraform file, and reference it in VMs now, thanks for reporting the issue! The network ID is e.g. resource "dcloud_network" "default_network" {
name = "Default"
description = "The default network"
inventory_network_id = "VLAN-PRIMARY"
topology_uid = dcloud_topology.test_topology.id
} |
Perfect! It is working now, @hughwphamill. I still have to run the plan twice for the VM names to save, everything else is good. |
Thanks for confirming @marinalf The VM Name issue is known and we have TB issue open on the internal code base to track/fix |
Description
Unable to create more custom VMs such as Nexus Dashboard and CML.
For ND, it is already pre-configured with an IP from the default network, but there is no data source to link to the network interface block. The "dcloud_neworks" data source does not accept a filter block to get only the default (primary) network from the outputs. But while creating it in a new network, it sends out this error below. Same for the CML config block.
As a side note, in the case of ND, the VM name in the inventory is "Nexus_dashboard_2.3_node_1" but it does not match the name on the GUI. Same for CML, inventory says "sp_cml2_2.6.0-5_amd64-6" but this does not exist in RTP. I am able to create a windows jump box in the same config/topology and name matches on both the inventory as well as on the GUI.
Thanks for checking.
Affected Version
Steps to Reproduce
Initial code is here.
Checklist
The text was updated successfully, but these errors were encountered: