On Tue, Jan 16, 2018 at 8:21 PM, Brady Johnson <[email protected]> wrote:
> For the SFC version bump patch [0] I need to merge this patch [1] first, > but its failing [2] with this: > > > *00:46:35* [ERROR] Failed to execute goal > org.opendaylight.odlparent:karaf-plugin:2.0.5:populate-local-repo > (populate-local-repo) on project karaf: Failed to execute: Invalid path. > Syntax mvn:[repository_url!]groupId/artifactId[/[version]/[type]] -> [Help > 1]*00:46:35* [ERROR] *00:46:35* [ERROR] To see the full stack trace of the > errors, re-run Maven with the -e switch.*00:46:35* [ERROR] Re-run Maven using > the -X switch to enable full debug logging.*00:46:35* [ERROR] *00:46:35* > [ERROR] For more information about the errors and possible solutions, please > read the following articles:*00:46:35* [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException*00:46:35* > [ERROR] *00:46:35* [ERROR] After correcting the problems, you can resume the > build with the command*00:46:35* [ERROR] mvn <goals> -rf :karaf > > > > Does anyone know anything about this failure?? > distribution jobs will continue to fail until the bump is complete across all projects. As long as the verify job succeeds, you can force merge it (ie remove jenkins-releng from Reviewers and manually +1 Verify). > > > [0] https://git.opendaylight.org/gerrit/#/c/66513/ > [1] https://git.opendaylight.org/gerrit/#/c/67219/ > [2] https://jenkins.opendaylight.org/releng/job/ > sfc-distribution-check-oxygen/300/console > > > Regards, > > *Brady Johnson* > [email protected] > > <https://twitter.com/inocybetech> <http://www.inocybe.com/> > <https://www.linkedin.com/company/2661537?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A2661537%2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe> > [image: > Screenshot 2017-02-14 at 10.43.55 AM.png] > <https://www.youtube.com/channel/UC9uUWABdPR0Je9Du_15FCkw> > > > > On Tue, Jan 16, 2018 at 6:35 PM, Faseela K <[email protected]> wrote: > >> Hi, >> >> If there was an option to do such major impact changes on a different >> branch, and then get it merged to main branch when things are stable >> enough.(given that such a version bump-up is happening almost at the same >> time as we are going to do a branch cut), would have been far better. >> >> But would like to tell that some of the issues we had with the >> previous versions seem to go off once we got a stable genius >> distribution(eg : ssh related problems as sshd got upgraded). >> >> Thanks, >> >> Faseela >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Luis Gomez >> *Sent:* Wednesday, January 17, 2018 5:58 AM >> *To:* Jamo Luhrsen <[email protected]> >> *Cc:* Stephen Kitt <[email protected]>; OpenDaylight Discuss < >> [email protected]>; Release ([email protected]) >> <[email protected]>; tsc <[email protected]> >> *Subject:* Re: [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 >> migration >> >> >> >> FYI I am trying this patch in sandbox for the issue you observed in CSIT: >> >> >> >> https://git.opendaylight.org/gerrit/#/c/67224/ >> >> >> >> BR/Luis >> >> >> >> >> >> On Jan 16, 2018, at 1:56 PM, Jamo Luhrsen <[email protected]> wrote: >> >> >> >> good idea Sam. I'll try that. >> >> btw, you could do a curl on restconf/modules and get a 200 right? >> >> JamO >> >> On 01/16/2018 01:55 PM, Sam Hague wrote: >> >> I loaded that distro locally and did feature:install >> odl-netvirt-openstack. That worked fine. Maybe we can use the patch you >> added recently to not use the bootfeatures? >> >> On Jan 16, 2018 4:02 PM, "Jamo Luhrsen" <[email protected] < >> mailto:[email protected] <[email protected]>>> wrote: >> >> Thanks Luis, >> >> that fixed it, and I ran new jobs already. ODL did not come "UP", so >> we have something to fix still. >> >> I'll be debugging, but something weird ended up in the features cfg >> file. >> there is an UUID in the featuresBoot and featuresRepositories lines >> >> https://jenkins.opendaylight.org/releng/user/jluhrsen/my- >> views/view/netvirt%20csit/job/netvirt-csit-1node-openstack- >> ocata-gate-stateful-oxygen/638/ >> <https://jenkins.opendaylight.org/releng/user/jluhrsen/ >> my-views/view/netvirt%20csit/job/netvirt-csit-1node- >> openstack-ocata-gate-stateful-oxygen/638/> >> >> JamO >> >> >> >> On 01/16/2018 12:38 PM, Luis Gomez wrote: >> >> I mean the format of the URL so that script can take it :) >> >> Just add 2 folders (/karaf/0.8.0-SNAPSHOT) in you HTTP server and it >> should work, for example: >> >> http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/kar >> af-0.8.0-SNAPSHOT.zip >> <http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/ka >> raf-0.8.0-SNAPSHOT.zip> >> >> >> >> On Jan 16, 2018, at 12:35 PM, Jamo Luhrsen <[email protected] < >> mailto:[email protected] <[email protected]>>> wrote: >> >> >> >> On 01/16/2018 12:27 PM, Luis Gomez wrote: >> >> I think you have to use something like this in the >> BUNDLE_URL: http://www.luhrsenlounge.net/odl/*karaf/0.8.0-SNAPSHOT*/kara >> f-0.8.0-SNAPSHOT.zip >> >> <http://www.luhrsenlounge.net/odl/*karaf/0.8.0-SNAPSHOT*/ >> karaf-0.8.0-SNAPSHOT.zip> >> >> >> hmmm... the BUNDLE_URL is right, but our deployment script is having >> trouble using >> it. I'm looking. >> >> >> On Jan 16, 2018, at 11:51 AM, Jamo Luhrsen <[email protected] < >> mailto:[email protected] <[email protected]>> >> >> <mailto:[email protected] <[email protected]> < >> mailto:[email protected] <[email protected]>>>> wrote: >> >> >> Sam built a local distro with the remaining unmerged patches >> and I am trying some netvirt CSIT with that: >> >> https://jenkins.opendaylight.org/releng/user/jluhrsen/my- >> views/view/netvirt%20csit/job/netvirt-csit-1node-openstack- >> ocata-gate-stateful-oxygen/637 >> <https://jenkins.opendaylight.org/releng/user/jluhrsen/ >> my-views/view/netvirt%20csit/job/netvirt-csit-1node- >> openstack-ocata-gate-stateful-oxygen/637> >> >> >> >> https://jenkins.opendaylight.org/releng/user/jluhrsen/my- >> views/view/netvirt%20csit/job/netvirt-csit-1node-openstack- >> ocata-gate-stateful-snat-conntrack-oxygen/38 >> <https://jenkins.opendaylight.org/releng/user/jluhrsen/ >> my-views/view/netvirt%20csit/job/netvirt-csit-1node- >> openstack-ocata-gate-stateful-snat-conntrack-oxygen/38> >> >> >> >> JamO >> >> >> >> On 01/16/2018 11:07 AM, Michael Vorburger wrote: >> >> On Tue, Jan 16, 2018 at 7:29 PM, Brady Johnson <[email protected] < >> mailto:[email protected] <[email protected]>> >> >> <mailto:[email protected] <[email protected]> < >> mailto:[email protected] <[email protected]>>>> wrote: >> >> >> We have indeed made good progress and it looks like we're close. >> Should we at least give it until the end of the >> >> day today? >> >> >> Related to this, since the merges started I havent been able to build >> SFC since Friday when I sent this email >> >> [0] and I >> >> still cant today. So this is something we need to resolve soon to >> avoid schedule slips. >> >> [0] https://lists.opendaylight.org/pipermail/release/2018-Januar >> y/013337.html >> >> <https://lists.opendaylight.org/pipermail/release/2018- >> January/013337.html> >> >> <https://lists.opendaylight.org/pipermail/release/2018-Janua >> ry/013337.html >> >> <https://lists.opendaylight.org/pipermail/release/2018- >> January/013337.html>> >> >> >> >> Regards, >> >> *Brady Johnson* >> [email protected] <mailto:[email protected] <[email protected]>> >> <mailto:[email protected] <[email protected]> < >> mailto:[email protected] <[email protected]>>> >> >> <https://twitter.com/inocybetech <https://twitter.com/inocybetech>>< >> http://www.inocybe.com/ >> >> <http://www.inocybe.com/>><https://www.linkedin.com/compa >> ny/2661537?trk=tyah&trkInfo=clickedVertical%3Acompany% >> 2CclickedEntityId%3A2661537%2Cidx%3A1-1-1%2CtarId% >> 3A1441300264767%2Ctas%3Ainocybe >> <https://www.linkedin.com/company/2661537?trk=tyah&trkInf >> o=clickedVertical%3Acompany%2CclickedEntityId%3A2661537% >> 2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe>>Screenshot >> >> 2017-02-14 at 10.43.55 AM.png <https://www.youtube.com/chann >> el/UC9uUWABdPR0Je9Du_15FCkw >> >> <https://www.youtube.com/channel/UC9uUWABdPR0Je9Du_15FCkw>> >> >> >> >> >> On Tue, Jan 16, 2018 at 8:31 AM, Stephen Kitt <[email protected] < >> mailto:[email protected] <[email protected]>> >> >> <mailto:[email protected] <[email protected]> <mailto:[email protected] >> <[email protected]>>>> wrote: >> >> >> Hi, >> >> In last week’s TSC call we agreed to move forward with merging the >> odlparent 3 / yangtools 2 migration patches, with a timebox — we >> were >> supposed to be able to run NetVirt CSIT yesterday. Obviously that >> deadline has gone whizzing past and we’re still some way away from >> running NetVirt CSIT; I’m not sure how far away... Strictly >> speaking, >> all the NetVirt dependencies now pass verify (thanks to lots of >> work by >> Tom, Robert and Michael on Neutron in particular), so we could >> give it >> a shot once the patches are merged, but I also knows that OVSDB >> fails >> its IT so I expect NetVirt CSIT won’t pass. >> >> So the question now is what do we do. Following the agreed plan, >> we >> should start reverting the patches (hopefully without messing up >> the >> follow-up fixes). We could formulate alternative plans, but I’m >> not >> sure what the community feels about that! >> >> Anyway, I’m not trying to suggest a concrete solution with this >> email, >> I want to start the discussion. >> >> >> my personal view is that the sane thing to do would be to revert and >> finish this up on a branch in parallel, to unblock >> folks, because the timeline proposed in https://lists.opendaylight.org >> /pipermail/release/2018-January/013336.html >> >> <https://lists.opendaylight.org/pipermail/release/2018- >> January/013336.html> was missed, >> >> and IMHO it's likely at least several more days until things fully >> stabilize. Through all the various 3rd party >> >> upgrades and >> >> yangtools changes etc. that went into this big bump, as of right there >> still has never been a full netvirt CSIT >> >> successfully >> >> run proving non-regression, yet; that's going to happen in the coming >> days. >> >> But I believe this view is not widely shared... ;-) Part of the reasons >> for that seem to include issues such as >> >> that the >> >> multipatch job apparently doesn't work, so it is hard to test change >> accross projects easily. I'm not sure that >> >> "let's just >> >> merge and figure it out as we go along" is the best answer to that >> problem.. but if others don't have a problem >> >> with the >> >> "broken world" for a number of days, then so be it! >> >> >> Regards, >> >> -- >> Stephen Kitt >> Principal Software Engineer, Office of the CTO >> Red Hat >> >> _______________________________________________ >> release mailing list >> [email protected] <mailto:[email protected] >> ight.org <[email protected]>> >> >> <mailto:[email protected] >> <[email protected]> <mailto:[email protected] >> <[email protected]>>> >> >> https://lists.opendaylight.org/mailman/listinfo/release >> >> <https://lists.opendaylight.org/mailman/listinfo/release> < >> https://lists.opendaylight.org/mailman/listinfo/release >> <https://lists.opendaylight.org/mailman/listinfo/release>> >> >> >> >> >> _______________________________________________ >> TSC mailing list >> [email protected] <mailto:[email protected] >> <[email protected]>> <mailto:[email protected] >> <[email protected]> >> >> <mailto:[email protected] <[email protected]>>> >> >> https://lists.opendaylight.org/mailman/listinfo/tsc < >> https://lists.opendaylight.org/mailman/listinfo/tsc> >> >> <https://lists.opendaylight.org/mailman/listinfo/tsc < >> https://lists.opendaylight.org/mailman/listinfo/tsc>> >> >> >> >> >> >> _______________________________________________ >> release mailing list >> [email protected] <mailto:[email protected] >> <[email protected]>> >> https://lists.opendaylight.org/mailman/listinfo/release < >> https://lists.opendaylight.org/mailman/listinfo/release> >> >> _______________________________________________ >> TSC mailing list >> [email protected] <mailto:[email protected] >> <[email protected]>> >> https://lists.opendaylight.org/mailman/listinfo/tsc < >> https://lists.opendaylight.org/mailman/listinfo/tsc> >> >> >> >> >> >> _______________________________________________ >> TSC mailing list >> [email protected] <mailto:[email protected] >> <[email protected]>> >> https://lists.opendaylight.org/mailman/listinfo/tsc < >> https://lists.opendaylight.org/mailman/listinfo/tsc> >> >> >> >> _______________________________________________ >> release mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/release >> >> > > _______________________________________________ > release mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/release > >
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
