OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[RELENG-46] Failed to create Carbon staging repo https://jira.opendaylight.org/browse/RELENG-46 releng <p>The Carbon Autorelease build is failing to generate a staging repo. See:</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/249/archives/deploy-staged-repository.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/249/archives/deploy-staged-repository.log.gz</a></p> <p>One theory is this might be related to our max file size limit of 500 MB in Nexus.</p> <p>Operating System: All<br/> Platform: All</p> RELENG-46

Failed to create Carbon staging repo

Bug Resolved Done Unassigned Thanh Ha (zxiiro) Thu, 20 Apr 2017 17:23:52 +0000 Thu, 19 Oct 2017 21:29:17 +0000 Wed, 7 Jun 2017 15:53:15 +0000 unspecified Autorelease 0 3 <p>Submitted patch <a href="https://git.opendaylight.org/gerrit/55751" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/55751</a> which should create a log of files that are larger than 200 MB so that we can inspect file sizes.</p> <p>Colin suggests we archive the last build in Jenkins to unblock testing.</p> <p>Submitted a patch to archive 1 copy of artifacts from the last successful build.</p> <p><a href="https://git.opendaylight.org/gerrit/55757" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/55757</a></p> <p>In the interest in checking the file sizes log I started a build with -DskipTests=true to see if we can have a quick copy of that log file to inspect today.</p> <p>Largest file appears to be about 300MB so the issue must be something else. I'm not sure what else it could be at the moment. We need to bring up a VM to troubleshoot.</p> <p>210456576 /w/workspace/autorelease-release-carbon/hide/from/pom/files/m2repo/org/opendaylight/bier/bier-karaf/0.1.0-Carbon/bier-karaf-0.1.0-Carbon.tar.gz<br/> 212033536 /w/workspace/autorelease-release-carbon/hide/from/pom/files/m2repo/org/opendaylight/bier/bier-karaf/0.1.0-Carbon/bier-karaf-0.1.0-Carbon.zip<br/> 315871232 /w/workspace/autorelease-release-carbon/hide/from/pom/files/m2repo/org/opendaylight/integration/distribution-karaf/0.6.0-Carbon/distribution-karaf-0.6.0-Carbon.tar.gz<br/> 318402560 /w/workspace/autorelease-release-carbon/hide/from/pom/files/m2repo/org/opendaylight/integration/distribution-karaf/0.6.0-Carbon/distribution-karaf-0.6.0-Carbon.zip<br/> 213438464 /w/workspace/autorelease-release-carbon/hide/from/pom/files/m2repo/org/opendaylight/vtn/distribution.vtn-manager.karaf/0.6.0-Carbon/distribution.vtn-manager.karaf-0.6.0-Carbon.tar.gz<br/> 215134208 /w/workspace/autorelease-release-carbon/hide/from/pom/files/m2repo/org/opendaylight/vtn/distribution.vtn-manager.karaf/0.6.0-Carbon/distribution.vtn-manager.karaf-0.6.0-Carbon.zip</p> <p>So it turns out with -DskipTests the build actually successfully deploys.</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/253/archives/deploy-staged-repository.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/253/archives/deploy-staged-repository.log.gz</a></p> <p>So the only difference between this build #253 and the build from #249 is that:</p> <p>1) We ran with -DskipTests<br/> 2) We removed tsdr & cardinal from the build</p> <p>I am unsure if this is related to the issue in question, but we see several fatal errors in console logs of carbon build #249 and #247 in <span class="error">[3.]</span> & <span class="error">[4.]</span> which is not seen in #253 (where the artifacts are uploaded onto nexus successfully with the tests skipped)</p> <p>2017-04-18 23:55:16.840642: <span class="error">[23193]</span>: FATAL: Creating Database Handler Failed!! <br/> 2017-04-18 23:55:16.840819: <span class="error">[23193]</span>: FATAL: Creating Database Handler Failed!! <br/> 2017-04-18 23:55:16.840893: <span class="error">[23193]</span>: FATAL: Creating Database Handler Failed!!<br/> ...</p> <p>Not sure, if this is the cause the issue ?</p> <p><span class="error">[3.]</span> <a href="https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/249/console.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/249/console.log.gz</a><br/> <span class="error">[4.]</span> <a href="https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/247/console.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/247/console.log.gz</a></p> <p>(In reply to Thanh Ha from comment #6)<br/> > So it turns out with -DskipTests the build actually successfully deploys.<br/> > <br/> > <a href="https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/</a><br/> > 253/archives/deploy-staged-repository.log.gz<br/> > <br/> > <br/> > So the only difference between this build #253 and the build from #249 is<br/> > that:<br/> > <br/> > 1) We ran with -DskipTests<br/> > 2) We removed tsdr & cardinal from the build</p> <p>Given this and the number of sporadic/timing issues we're seeing, e.g.,:<br/> <a href="https://lists.opendaylight.org/pipermail/release/2017-April/010290.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/release/2017-April/010290.html</a></p> <p>Maybe we should run autorelease-carbon with -DskipTests first, then publish artifacts, then run it normally. How hard would that be?</p> <p>It would be straightforward to create a separate job "autorelease-release-carbon-notests" job (temporarily) with the `-Dskiptest` enabled instead of incorporating both into the same job. This is because the any failures in the builder section would not allow the job to continue the next builder section.</p> <p>Uploading artifacts to nexus is no longer reproducible, therefore this should no longer be a blocker bug. I am presently reducing the priority to normal.</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/autorelease-release-notests-carbon/1/archives/deploy-staged-repository.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/autorelease-release-notests-carbon/1/archives/deploy-staged-repository.log.gz</a></p> <p>Atrifacts for the build: <a href="https://nexus.opendaylight.org/content/repositories/autorelease-1765/org/opendaylight/integration/distribution-karaf/0.6.0-Carbon/" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/autorelease-1765/org/opendaylight/integration/distribution-karaf/0.6.0-Carbon/</a></p> <p>Anil, if you believe this is fixed. You can close it. We can always reopen it later.</p> Development External issue ID 8265 External issue URL Rank 0|i01m7r: