Question

Your team maintains a network automation pipeline that spins up a CML topology from a versioned topology.yaml file during the 'test' stage. After a colleague edited the topology file, the pipeline's CML import job fails with an error indicating the referenced node type cannot be resolved on the CML server. The topology previously imported successfully. Inspecting the diff, you notice the 'node_definition' field for a router node was changed from 'iosv' to 'csr1000v'. What is the MOST likely cause of the failure?

Accepted Answer

The CML server does not have the 'csr1000v' node definition and its associated image installed, so the referenced node type cannot be resolved during import.

Answer

CML topology files only accept the 'iosv' node definition; all other router types must be defined through the API after import.

Answer

The GitLab runner lacks the Docker-in-Docker service required to translate node definitions before uploading the topology.

Answer

Changing node_definition invalidates the topology file's YAML schema version, which must be manually incremented on every node edit.