https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/VTN-117 vtn <p>The CSIT for Beryllium VTN Manager failed.<br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/63/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/63/</a></p> <p>On the build 63 of the "vtn-csit-1node-manager-all-beryllium" job, all test cases failed.</p> <p>This is not happened always.<br/> Actually, this was the first and only case in which the "vtn-csit-1node-manager-all-beryllium" failed.</p> <p>Operating System: All<br/> Platform: All</p> VTN-117

All test cases failed in the CSIT for Beryllium VTN Manager.

Bug Resolved Done Unassigned Hideyuki Tai Wed, 10 Feb 2016 20:14:42 +0000 Thu, 19 Oct 2017 21:25:09 +0000 Fri, 12 Feb 2016 00:01:54 +0000 unspecified VTN Manager 0 2 <p>On the failure build (#63), many RESTCONF requests to VTN Manager failed on 404 errors.<br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/63/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/63/</a></p> <p>I've checked the karaf log file on the failure build (#63).<br/> Then, I've found out that the initialization of the VTN Manager was not completed even in 3 minutes after the controller started up.<br/> It seems to me that ODL controller was busy on something wrong so that it didn't reach to the initialization process of the VTN Manager yet.<br/> I think that's why all test cases failed.</p> <p>That being said, I'm still not sure why the ODL controller took such a lot of time to just install features.</p> <p>Jamo has gave us his investigation result on the ML.</p> <p><a href="https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001294.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001294.html</a></p> <p>"I tested locally and found this:<br/> with RC2.1, there is a &gt; 7m lag between when I see AAA Initialized and<br/> when vtn sees it's config-pusher Succcessful log message. My assumption<br/> here is that if AAA is Initialized, that's aprox when I'll see a 200<br/> back from /restconf/modules. This appears to be consistent and repeatable."</p> <p>This means AAA is initialized. You would see 401 or 404 otherwise. This isn't a AAA issue.</p> <p>Additional Jamo's comment:<br/> "to double check, I ran two more test jobs.<br/> #65 with RC1.2 which fails again.<br/> #66 with latest stable/Be available and it passes.<br/> I think something is broken just in RC2.1."</p> <p><a href="https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001302.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001302.html</a></p> <p>#65 build (CSIT): <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/65/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/65/</a><br/> #66 build (CSIT): <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/66/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/66/</a></p> <p>Luis's comment on the issue:</p> <p>"<br/> Hi Jamo, I am looking at the karaf log for fail/pass runs, and in both cases the controller is not full up when the test starts, so regardless any other issue, I think we should patch our test code to increase the sleep when we load all compatible features. Something like 3 minutes instead of 1:</p> <ul class="alternate" type="square"> <li>single feature test: 1 min (already there)</li> <li>all compatible features test: 3 mins (new patch)</li> <li>all features test: 5 mins (already there)</li> </ul> <p>BR/Luis<br/> "</p> <p>Reference: <a href="https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001306.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001306.html</a></p> <p>(In reply to Hideyuki Tai from comment #5)<br/> &gt; Luis's comment on the issue:<br/> &gt; <br/> &gt; "<br/> &gt; Hi Jamo, I am looking at the karaf log for fail/pass runs, and in both cases<br/> &gt; the controller is not full up when the test starts, so regardless any other<br/> &gt; issue, I think we should patch our test code to increase the sleep when we<br/> &gt; load all compatible features. Something like 3 minutes instead of 1:<br/> &gt; <br/> &gt; - single feature test: 1 min (already there)<br/> &gt; - all compatible features test: 3 mins (new patch)<br/> &gt; - all features test: 5 mins (already there)<br/> &gt; <br/> &gt; BR/Luis<br/> &gt; "<br/> &gt; <br/> &gt; Reference:<br/> &gt; <a href="https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001306.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/vtn-dev/2016-February/001306.html</a></p> <p>Closing this bug. The RC2.2 distro did not see this issue. I have added a <br/> patch <span class="error">&#91;0&#93;</span> that will give more time for features to come up to prevent false<br/> failures in the future.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/34525/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34525/</a></p> <p>RC2.2 test:<br/> <a href="https://jenkins.opendaylight.org/releng/job/vtn-csit-1node-manager-all-beryllium/69/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/vtn-csit-1node-manager-all-beryllium/69/</a></p> Development External issue ID 5305 External issue URL Rank 0|i02tov: