cfgtable.get(key=...) Ignoring multiple key-fields. (semantics error in factory.cfgtable_encode_namekey)

[xerotolerance]

Walkthrough

1. Table objects are created by FactoryCfgTable(table_name, data_dict), w/ data_dict containing the sections of the YAML spec. Ex (note the dict key 'key-field'):

{'set': 'routing-options/static/route', 'key-field': ['dest', 'next_hop'], 'view': <class '...StaticRouteView'>}

2. FactoryCfgTable sets

new_cls.DEFINE = deepcopy(data_dict)  #(line 23)

3. CfgTable's constructor sets

self._data_dict = self.DEFINE #(line 22)

4. Eventually, cfgtable.get() calls

self._encode_namekey(get_cmd, dot, named_item) #line 504

5. PROBLEM: _encode_namekey(...) calls self._data_dict.get("key","name") instead of "key-field" causing the default field, name, to be checked every time regardless of whether the YAML definition specifies multiple key-fields.

    def _encode_namekey(self, get_cmd, dot, namekey_value):
        """
        encodes the specific namekey_value into the get command so that the
        returned XML configuration is the complete hierarchy of data.
        """
        namekey_xpath = self._data_dict.get("key", "name")    # line 339 is the problem: "key" should be "key-field"
        keylist_xml = self._grindkey(namekey_xpath, namekey_value)
        for _add in keylist_xml:
            dot.append(_add)

[rahkumar651991]

Can you share the netconf logs for this example. Need full configuration to replicate the scenario and verify it.

Refer here -https://www.juniper.net/documentation/us/en/software/junos/junos-xml-protocol/topics/example/netconf-traceoptions-configuring.html

[dineshbaburam91]

@xerotolerance Kindly share the table/view YAML data to replicate the scenario and verify it.