search

CloudGenix / cloudgenix_config

Configuration exporting and Continuous Integration (CI) capable configuration importing for the CloudGenix Cloud Controller.
MIT License
12 stars 22 forks source link

Failure to apply network_context_id on subinterface #84

Closed rpollard00 closed 2 years ago

rpollard00 commented 2 years ago

Appears to be an issue with applying a network context on subinterfaces.

A site pulled with pull_site.py correctly shows the subinterface by its friendly name:

wan 1lan 1.2042:
... #config omitted
  network_context_id: Guest

On application of do_site.py, the network_context_id is removed from the subinterface.

Log output, do_site.py when applying already configured friendly network_context_id name:

DEBUG: INTERFACE DIFF: ipv4_config->ethernet_port->sub_interface :
 -  network_context_id  :  15156366995910130
 +  network_context_id  :  Guest

The above context id and friendly name refer to the same thing, so it should not even attempt to change it, in this instance. When I look at the subinterface configuration after this, the network_context_id is not set.

If I change the network_context_id in the template to its numeric identifier, then it correctly preserves (if already configured), or sets(if not configured) the context on the subinterface.

e.g. This correctly sets the network_context to the "Guest" context:

wan 1lan 1.2042:
...
  network_context_id: "15156366995910130"
ktanushree commented 2 years ago

Hi @rpollard00, we've fixed this bug in 1.7.0b2.