Broken Packetcable CSIT since 10/17

Kevin Kershaw <K.Kershaw@...>

Hi –


A couple of weeks ago I noticed that the Packetcable CSIT jobs have been failing in Jenkins since October 17 – when all of our CSIT tests began failing.  The failure occurs across Carbon, Nitrogen, & Oxygen releases.  The log message that’s associated with the failure is:


19:25:35 Add CCAP :: Add Single CCAP                                           | FAIL |

19:25:35 Parent suite setup failed:

19:25:35 No keyword with name 'BuildIn.Set Suite Variable' found. Did you mean:

19:25:35     BuiltIn.Set Suite Variable

19:25:35     BuiltIn.Set Test Variable




In the autorelease-carbon job, there’s a failure that looks related with this set of log entries:


04:58:30 [ERROR] The build could not read 1 project -> [Help 1]
04:58:30 [ERROR]   
04:58:30 [ERROR]   The project org.opendaylight.packetcable:packetcable:1.5.3 (/w/workspace/packetcable-validate-autorelease-carbon/packetcable/pom.xml) has 1 error
04:58:30 [ERROR]     Non-resolvable parent POM for org.opendaylight.packetcable:packetcable:1.5.3: Could not find artifact org.opendaylight.odlparent:odlparent:pom:1.8.3 in opendaylight-mirror ( and 'parent.relativePath' points at wrong local POM @ line 5, column 13 -> [Help 2]
04:58:30 [ERROR] 
04:58:30 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
04:58:30 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
04:58:30 [ERROR] 
04:58:30 [ERROR] For more information about the errors and possible solutions, please read the following articles:
04:58:30 [ERROR] [Help 1]
04:58:30 [ERROR] [Help 2]
04:58:30 Build step 'Invoke top-level Maven targets' marked build as failure


A change was applied by the jenkins-releng team (Anil Belur) on the 17th that looks implicated.  Change:  has this description:  “Bump versions by x.y.(z+1)”


There were build failures on this change/patch but it looks like the change was merged anyway.   

One thing that looks fishy is that the updated pom files are referencing component versions in Nexus that are not there (for example, odlparent 1.8.3 or Packetcable 1.5.3).


Can someone help me identify the problem and get our CSIT back on track? 




Kevin Kershaw