Re: [OpenDaylight Discuss] NETCONF RPC XML remove namespace of sub-tree element

Wed, 28 Nov 2018 05:52:48 -0800

Attached the request I’m sending.

Alexis

curl -X POST \
  
http://localhost:8080/restconf/operations/network-topology:network-topology/topology/topology-netconf/node/alex/yang-ext:mount/ietf-netconf:edit-config
 \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic YWRtaW46YWRtaW4=' \
  -H 'Content-Type: application/xml' \
  -d '<?xml version="1.0" encoding="UTF-8"?>
<input xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   <target>
      <candidate />
   </target>
   <default-operation>none</default-operation>
   <config>
         <interface-configurations 
xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg";>
            <interface-configuration 
xmlns:a="urn:ietf:params:xml:ns:netconf:base:1.0" a:operation="replace">
               <interface-name>TenGigE0/0/0/0.111</interface-name>
               <active>act</active>
               <ipv4-network 
xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ipv4-io-cfg";>
                  <addresses>
                     <primary>
                        <netmask>255.255.255.254</netmask>
                        <address>10.15.56.98</address>
                     </primary>
                  </addresses>
               </ipv4-network>
               <mtus>
                  <mtu>
                     <owner>sub_vlan</owner>
                     <mtu>4484</mtu>
                  </mtu>
               </mtus>
               
<interface-mode-non-physical>default</interface-mode-non-physical>
               <description>test</description>
               <vlan-sub-configuration 
xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-l2-eth-infra-cfg";>
                  <vlan-identifier>
                     <first-tag>111</first-tag>
                     <vlan-type>vlan-type-dot1q</vlan-type>
                  </vlan-identifier>
               </vlan-sub-configuration>
            </interface-configuration>
         </interface-configurations>
   </config>
</input>'


curl -X PUT \
  
http://localhost:8080/restconf/config/network-topology:network-topology/topology/topology-netconf/node/alex/yang-ext:mount/Cisco-IOS-XR-ifmgr-cfg:interface-configurations/interface-configuration/act/TenGigE0%2F0%2F0%2F0.111
 \
  -H 'Content-Type: application/xml' \
  -d '    <interface-configuration 
xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg";>
      <active>act</active>
      <interface-name>TenGigE0/0/0/0.111</interface-name>
      <vlan-sub-configuration 
xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-l2-eth-infra-cfg";>
        <vlan-identifier 
xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-l2-eth-infra-cfg";>
          <vlan-type>vlan-type-dot1q</vlan-type>
          <first-tag>111</first-tag>
        </vlan-identifier>
      </vlan-sub-configuration>
      <mtus>
        <mtu>
          <owner>sub_vlan</owner>
          <mtu>4484</mtu>
        </mtu>
      </mtus>
      <interface-mode-non-physical>default</interface-mode-non-physical>
      <description>test</description>
      <ipv4-network xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ipv4-io-cfg";>
        <addresses xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ipv4-io-cfg";>
          <primary>
            <address>10.15.56.98</address>
            <netmask>255.255.255.254</netmask>
          </primary>
        </addresses>
      </ipv4-network>
    </interface-configuration>'


On Nov 28, 2018, at 8:48 AM, Alexis de Talhouët <[email protected]> wrote:

Robert,

Starting version 0.7.0 onward it’s broken...

I’m sending the request through RESTCONF, yes.

When sending RPC ietf-netconf:edit-config, device namespace get stripped out the edit-config payload; URI: http://localhost:8080/restconf/operations/network-topology:network-topology/topology/topology-netconf/node/alex/yang-ext:mount/ietf-netconf:edit-config


Attached logs for both scenarios.

Regards,
Alexis

<odl-issue.txt>


On Nov 27, 2018, at 7:31 PM, Robert Varga <[email protected]> wrote:



On 28/11/2018 01:24, Robert Varga wrote:
As you can see, the namespace has been stripped out, hence device is
unable to recognize the element I’m trying to configure.

Is this a know issue? It is a very critical regression to me.
Looks like a bug. Can you narrow down the versions? How does Oxygen
SR3/Fluorine GA look like?

Also, how do you send that request down? RESTCONF?

Regards,
Robert



_______________________________________________
Discuss mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/discuss

Reply via email to