[NETCONF-487] netconf features broken when used in int/dist compatible with all feature set Created: 22/Nov/17  Updated: 16/Feb/22  Resolved: 16/Feb/22

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Jamo Luhrsen Assignee: Ivan Martiniak
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File [NETCONF-487] Steps to reproduce.odt     File karaf.log    

 Description   

email discussion https://lists.opendaylight.org/pipermail/netconf-dev/2017-November/001502.html

the distribution-version feature was broken sometime between the first Nitrogen
release and our efforts to release Nitrogen SR1. This is a regression, in that sense,
and regressions are normally considered blockers.

when installing the integration projects compatible-with-all feature set, the problem
is seen. If only the individual features are installed, the version feature works. This may
be enough of a workaround to downgrade from blocker status, but not enough is known
yet as to the root problem.

 Comments   
Comment by Luis Gomez [ 22/Nov/17 ]

Here is a patch that as a minimum fixes the netconf features incompatibilities in CSIT by moving all netconf dependent features to not compatible:

https://git.opendaylight.org/gerrit/#/c/65844

netconf test result: https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-nitrogen/234/

Here is an extra patch that fixes the version test when many features are loaded together:

https://git.opendaylight.org/gerrit/#/c/65854

distribution test result: https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-csit-1node-userfeatures-all-nitrogen/237/

BR/Luis

Comment by Jamo Luhrsen [ 23/Nov/17 ]

Thanks for the digging Luis.

More info:

This is not a regression and also existed in the first nitrogen release. The reason we did not see the failure
then was that our compatible-with-all feature installation was broken during that release. This was a breakage
on the deployment side, not anything internal to an OpenDaylight project. We fixed that deployment issue
around Oct 2nd, and that's when the failure first started showing up. I have tested the original Nitrogen release
with the fixed deployment job and the failure is there.

Luis did investigate deep enough to realize that the feature is indeed broken when it's loaded with our
test feature set "compatible-with-all". We can leave this issue open for that reason. His patch to move
netconf features out of compatible-with-all is just a workaround. Someone needs to figure out what is
really broken.

I have removed the elevated states (blocker/crtical) of this bug.

Comment by Ivan Martiniak [ 26/Jan/22 ]

Hello jluhrsen, can you please let us know if issue is present in current Phosphorus release? 

Generated at Wed Feb 07 20:15:09 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.