-
Bug
-
Resolution: Done
-
Highest
-
None
-
None
-
None
-
None
RESTCONF initialization fails with exception (see attached log file) when global schema context contains yang models using deviations.
Reproduction steps:
- clean compile transportpce project `mvn clean install`
- start karaf with transportpce project: `cd karaf/target/assembly/bin; ./karaf`
- check feature activation, after ~15s after karaf is started, RESTCONF init fails with exception in attached log.
The problem is in the following yang models, containing deviations , that we re introduced with OpenRoadm Network model 4.1
transportpce/ordmodels/network/src/main/yang/org-openroadm-otn-network-topology@2018-11-30.yang
transportpce/ordmodels/network/src/main/yang/org-openroadm-network-topology@2018-11-30.yang
transportpce/ordmodels/network/src/main/yang/org-openroadm-network@2018-11-30.yang
When deviations are removed inside the models above , TransportPCE project starts just fine.
When deviations are kept, tranpost PCE karaf features are failing to start with exception: RestconfDocumentedException: errors: [RestconfError [error-type: application, error-tag: operation-failed, error-message: name doesn't exist.]]
which means that RESTCONF feature activation fails.
However, it does not seem to affect the functional tests.
So the problem is not blocking for the TransportPCE official karaf distribution, but it affects the lighty.io build process as reported by Juraj.
Since the first fix 82505 has been merged, E2E functests UT are now failing.
There was an error in Revision mapping of Deviations in Restconf.
The patch for this issue is already prepared and awaiting review. https://git.opendaylight.org/gerrit/#/c/netconf/+/83679/
- blocks
-
TRNSPRTPCE-127 lighty.io build support
- Verified