Device-domain config option breaks controller operation

[v1shnya]

Use docker-compose-demo.yml. I only removed git checkout commands from Dockerfile-demo to pull the latest code

docker compose -f docker-compose-demo.yml build
docker compose -f docker-compose-demo.yml up

then connect to the controller docker exec -it demo-controller clixon_cli -f /usr/local/etc/clixon/controller.xml

Before opening connection to the devices, add the device-domain option. Connections are established.

nobody@da44d27c592a> show configuration | display cli
set devices device openconfig1
set devices device openconfig1 enabled true
set devices device openconfig1 user noc
set devices device openconfig1 conn-type NETCONF_SSH
set devices device openconfig1 addr r1
set devices device openconfig2
set devices device openconfig2 enabled true
set devices device openconfig2 user noc
set devices device openconfig2 conn-type NETCONF_SSH
set devices device openconfig2 addr r2

nobody@da44d27c592a> configure
nobody@da44d27c592a[/]# set devices device openconfig* device-domain OPENCONFIG
nobody@da44d27c592a[/]# commit local
nobody@da44d27c592a[/]# exit
nobody@da44d27c592a> connection open

nobody@8042b702edde> show connections
Name                    State      Time                   Logmsg
==================================================
openconfig1             OPEN       2026-02-04T17:05:05
openconfig2             OPEN       2026-02-04T17:05:05

Now, it looks like the controller can't identify proper YANG models for the devices

nobody@da44d27c592a> show configuration | display cli
Feb  4 17:00:51.713818: pipe_showas_fn: 310: Netconf error: Parse top file: application unknown-element Failed to find YANG spec of XML node: restconf with parent: config in namespace: http://clicon.org/restconf <bad-element>restconf</bad-element>
cligen_eval_pipe_pre child retval:-1

nobody@8042b702edde> show devices openconfig1 yang
Feb  4 17:10:33.202530: show_yang_revisions: 2428: Netconf error: Get configuration: application operation-failed Failed to find YANG spec of XML node: restconf with parent: config in namespace: http://clicon.org/restconf. Internal error, backend returned invalid XML. <bad-element>restconf</bad-element>
CLI command error

At the same time, the device configurations were successfully pulled from the devices

nobody@8042b702edde> show configuration
<devices xmlns="http://clicon.org/controller">
   <device>
      <name>openconfig1</name>
      <enabled>true</enabled>
      <user>noc</user>
      <conn-type>NETCONF_SSH</conn-type>
      <device-domain>OPENCONFIG</device-domain>
      <addr>r1</addr>
      <config>
         <restconf xmlns="http://clicon.org/restconf">
            <enable>true</enable>
            <auth-type>none</auth-type>
            <debug>0</debug>
            <log-destination>file</log-destination>
            <pretty>false</pretty>
            <socket>
               <namespace>default</namespace>
               <address>0.0.0.0</address>
               <port>80</port>
               <ssl>false</ssl>
            </socket>
         </restconf>
      </config>
   </device>
   <device>
      <name>openconfig2</name>
      <enabled>true</enabled>
      <user>noc</user>
      <conn-type>NETCONF_SSH</conn-type>
      <device-domain>OPENCONFIG</device-domain>
      <addr>r2</addr>
      <config>
         <restconf xmlns="http://clicon.org/restconf">
            <enable>true</enable>
            <auth-type>none</auth-type>
            <debug>0</debug>
            <log-destination>file</log-destination>
            <pretty>false</pretty>
            <socket>
               <namespace>default</namespace>
               <address>0.0.0.0</address>
               <port>80</port>
               <ssl>false</ssl>
            </socket>
         </restconf>
      </config>
   </device>
</devices>

[krihal]

Hi,

I followed your steps and tried to reproduce it:

nobody@2a307a6fd60f> show configuration devices device openconfig* device-domain
<!-- openconfig1: -->
<devices xmlns="http://clicon.org/controller">
   <device>
      <name>openconfig1</name>
      <device-domain>OPENCONFIG</device-domain>
   </device>
</devices>
<!-- openconfig2: -->
<devices xmlns="http://clicon.org/controller">
   <device>
      <name>openconfig2</name>
      <device-domain>OPENCONFIG</device-domain>
   </device>
</devices>
nobody@2a307a6fd60f> show configuration | display cli
set devices device openconfig1
set devices device openconfig1 enabled true
set devices device openconfig1 user noc
set devices device openconfig1 conn-type NETCONF_SSH
set devices device openconfig1 device-domain OPENCONFIG
set devices device openconfig1 addr r1
set devices device openconfig1 config
set devices device openconfig1 config restconf
set devices device openconfig1 config restconf enable true
set devices device openconfig1 config restconf auth-type none
set devices device openconfig1 config restconf debug 0
set devices device openconfig1 config restconf log-destination file
set devices device openconfig1 config restconf pretty false
set devices device openconfig1 config restconf socket default 0.0.0.0 80
set devices device openconfig1 config restconf socket default 0.0.0.0 80 ssl false
set devices device openconfig2
set devices device openconfig2 enabled true
set devices device openconfig2 user noc
set devices device openconfig2 conn-type NETCONF_SSH
set devices device openconfig2 device-domain OPENCONFIG
set devices device openconfig2 addr r2
set devices device openconfig2 config
set devices device openconfig2 config restconf
set devices device openconfig2 config restconf enable true
set devices device openconfig2 config restconf auth-type none
set devices device openconfig2 config restconf debug 0
set devices device openconfig2 config restconf log-destination file
set devices device openconfig2 config restconf pretty false
set devices device openconfig2 config restconf socket default 0.0.0.0 80
set devices device openconfig2 config restconf socket default 0.0.0.0 80 ssl false
nobody@2a307a6fd60f> show configuration | display cli
set devices device openconfig1
set devices device openconfig1 enabled true
set devices device openconfig1 user noc
set devices device openconfig1 conn-type NETCONF_SSH
set devices device openconfig1 device-domain OPENCONFIG
set devices device openconfig1 addr r1
set devices device openconfig1 config
set devices device openconfig1 config restconf
set devices device openconfig1 config restconf enable true
set devices device openconfig1 config restconf auth-type none
set devices device openconfig1 config restconf debug 0
set devices device openconfig1 config restconf log-destination file
set devices device openconfig1 config restconf pretty false
set devices device openconfig1 config restconf socket default 0.0.0.0 80
set devices device openconfig1 config restconf socket default 0.0.0.0 80 ssl false
set devices device openconfig2
set devices device openconfig2 enabled true
set devices device openconfig2 user noc
set devices device openconfig2 conn-type NETCONF_SSH
set devices device openconfig2 device-domain OPENCONFIG
set devices device openconfig2 addr r2
set devices device openconfig2 config
set devices device openconfig2 config restconf
set devices device openconfig2 config restconf enable true
set devices device openconfig2 config restconf auth-type none
set devices device openconfig2 config restconf debug 0
set devices device openconfig2 config restconf log-destination file
set devices device openconfig2 config restconf pretty false
set devices device openconfig2 config restconf socket default 0.0.0.0 80
set devices device openconfig2 config restconf socket default 0.0.0.0 80 ssl false
nobody@2a307a6fd60f>

What versions of each component are you using ("show version")?

[v1shnya]

Hi Kristofer,
thank you for getting back to me query.

Today I can’t reproduce the issue on my laptop. I’m using the same controller image that was built yesterday:

nobody@6c63059467a8> show version
CLIgen: 	7.6.0-1+5+gd279eed
Clixon: 	7.6.0-1+53+g90e170f8
Controller:	1.6.0-1+17+gc65845b
Build:		2026.02.04 15:32 by root on buildkitsandbox

Strange for me, as I've observed situation few times yesterday. This is a bit strange to me, as I observed the issue several times yesterday. I understand that the device-domain option only takes effect after reconnecting to the devices.

So, please, close the case as unreproducible.