Inconsistencies between YANG and CLI for router bgp ipv4 address family vrf statement on 16.12 fw

[sebageek]

With V1612_1A_SAP on the asr1k assume the following config present on the device:

router bgp 65148
 !
 address-family ipv4 vrf 7beea201af384c1385fb9b531c73ad95
  redistribute connected
  redistribute static
 exit-address-family

When we remove the config as such

QA-DE-1b-asr11-cp090#conf t
QA-DE-1b-asr11-cp090(config)#router bgp 65148
QA-DE-1b-asr11-cp090(config-router)#no address-family ipv4 vrf 7beea201af384c1385fb9b531c73ad95
QA-DE-1b-asr11-cp090(config-router)#end

we can see that it is no longer present in the cli, but still present when asking for the config in YANG.

# query
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <get>
    <filter>
      <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native" xmlns:ios-bgp="http://cisco.com/ns/yang/Cisco-IOS-XE-bgp">
        <router>
          <ios-bgp:bgp>
            <ios-bgp:id>65148</ios-bgp:id>
          </ios-bgp:bgp>
        </router>
      </native>
    </filter>
  </get>
</rpc>

# result
<rpc-reply message-id="urn:uuid:41dc668e-ffdf-478c-b456-008e8335ed69" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
  <data>
    <native xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-native">
      <router>
        <bgp xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-bgp">
          <id>65148</id>
          <bgp>
            <log-neighbor-changes>true</log-neighbor-changes>
            <router-id>
              <ip-id>10.46.210.16</ip-id>
            </router-id>
          </bgp>
          <address-family>
            <with-vrf>
              <ipv4>
                <af-name>unicast</af-name>
[...]
                <vrf>
                  <name>7beea201af384c1385fb9b531c73ad95</name>
                  <ipv4-unicast>
                    <redistribute-vrf>
                      <connected/>
                      <static/>
                    </redistribute-vrf>
                  </ipv4-unicast>
                </vrf>
[...]
          </address-family>
        </bgp>
      </router>
    </native>
  </data>
</rpc-reply>

On the cli:

QA-DE-1b-asr11-cp090#show run | inc address-family ipv4 vrf 7beea201af384c1385fb9b531c73ad95
QA-DE-1b-asr11-cp090#

This leads to our bgp config not being synced onto the device, as both the driver and the yang-stack assume that everything is okay.