Uploaded image for project: 'controller'
  1. controller
  2. CONTROLLER-1201

netconf client check base1.1 capability wrong

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • None
    • Helium
    • netconf
    • None
    • Operating System: All
      Platform: All

    • 2837

      I have a netconf server that does not advertise urn:ietf:params:netconf:base:1.1
      . but advertise a private capability "urn:com:xxx:yyy:ebase:1.1.1"

      In the following method, it only check capability with string base:1.1. and get a wrong capability to make ODL sending the base1.1 separators in RPC messages.

      private boolean containsBase11Capability(final Document doc) {
      final NodeList nList = doc.getElementsByTagName("capability");
      for (int i = 0; i < nList.getLength(); i++) {
      if (nList.item.getTextContent().contains("base:1.1"))

      { return true; }

      }
      return false;
      }

      I think the the check should use full capability string "urn:ietf:params:netconf:base:1.1"

            mmarsale@cisco.com Maros Marsalek
            bo.l.li@ericsson.com Bo Li
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: