[ODLPARENT-12] SingleFeatureTest : Can it verify also requirements from config files? Created: 10/Mar/15  Updated: 24/Jan/18  Resolved: 08/May/17

Status: Resolved
Project: odlparent
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 2811

 Description   

https://bugs.opendaylight.org/show_bug.cgi?id=2795
documents a bug where bundle dependencies are satisfied, but config file requires service defined by (otherwise independent) feature.

Would it be possible for SingleFeatureTest to detect such issues?
Description of the following bug illustrates that currently it does not detect that (passes on the feature guilty of BGPCEP-189).
https://bugs.opendaylight.org/show_bug.cgi?id=2810



 Comments   
Comment by Robert Varga [ 31/Aug/15 ]

Just to clarify what is being asked. The problem is that the features and config files are structurally valid, but the configuration activation fails because a component required for the config file to succeed is not being pulled in. Is that correct?

Comment by Vratko Polak [ 03/Sep/15 ]

Yes, that is correct.

Comment by Robert Varga [ 09/Feb/16 ]

This feature is already present in controller's integration test prototype (config-it-base)

Comment by Vratko Polak [ 18/Feb/16 ]

> (config-it-base)

Great! Is there a documentation on how to use it?
So that committers on integration/distribution can point to that when giving -1 to integration feature candidates.

The most recent project in need of such tests is Netconf, as evidenced by NETCONF-149.

Comment by Michael Vorburger [ 08/May/17 ]

> config files are structurally valid

just FYI, in order to validate if clustered-app-config files are structurally valid, there is https://git.opendaylight.org/gerrit/#/c/56027/

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