'VLAN MA' detected the 'warning' condition 'The interface is invalid (no VLAN IDB)'

[dave_stern]

Just wanted to share that we found a bug where the model cleared but we were unable to commit a sub-interface to an existing interface on IOS-XR 6.1.2 (submitted case 681760171)

commit-reply

<?xml version="1.0"?>

<rpc-reply message-id="urn:uuid:00f97ce8-f526-4677-83b1-0380491c8744" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">

<rpc-error>

  <error-type>application</error-type>

  <error-tag>operation-failed</error-tag>

  <error-severity>error</error-severity>

  <error-path xmlns:ns2="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg" xmlns:ns1="http://cisco.com/ns/yang/Cisco-IOS-XR-l2-eth-infra-cfg">ns2:interface-configurations/ns2:interface-configuration[active = 'act' and interface-name = 'GigabitEthernet0/0/0/19.444']/ns1:vlan-sub-configuration/ns1:vlan-identifier/ns1:first-tag</error-path>

  <error-message xml:lang="en">'VLAN MA' detected the 'warning' condition 'The interface is invalid (no VLAN IDB)'</error-message>

</rpc-error>

</rpc-reply>

In order to solve this: it was found that

interface_configuration.interface_mode_non_physical = xr_ifmgr_cfg.InterfaceModeEnumEnum.default

needed to be added to code for the interface we were adding the sub interface to work around the issue.

Thanks for the assist guys!!!

[saalvare · Accepted solution]

Thanks for the confirming the workaround.  For future readers, let me clarify that this is an XR defect.  It's not related to YDK or even the model specification.  XR defect is CSCvd05692.