<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:22:55 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[NETVIRT-974] karaf process killed by OS due to OOM condition</title>
                <link>https://jira.opendaylight.org/browse/NETVIRT-974</link>
                <project id="10144" key="NETVIRT">netvirt</project>
                    <description>&lt;p&gt;since aprox 10/20/2017 we have seen our nitrogen and oxygen CSIT jobs fail&lt;br/&gt;
because the karaf process is using so much memory that the OS has to kill it:&lt;/p&gt;

&lt;p&gt;the karaf console gets a message like this:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;/tmp/karaf-0.8.0-SNAPSHOT/bin/karaf: line 422: 11539 Killed                  
${KARAF_EXEC} &quot;${JAVA}&quot; ${JAVA_OPTS} &quot;$NON_BLOCKING_PRNG&quot; -Djava.endorsed.dirs=&quot;${JAVA_ENDORSED_DIRS}&quot; -Djava.ext.dirs=&quot;${JAVA_EXT_DIRS}&quot; -Dkaraf.instances=&quot;${KARAF_HOME}/instances&quot; -Dkaraf.home=&quot;${KARAF_HOME}&quot; -Dkaraf.base=&quot;${KARAF_BASE}&quot; -Dkaraf.data=&quot;${KARAF_DATA}&quot; -Dkaraf.etc=&quot;${KARAF_ETC}&quot; -Dkaraf.restart.jvm.supported=true -Djava.io.tmpdir=&quot;${KARAF_DATA}/tmp&quot; -Djava.util.logging.config.file=&quot;${KARAF_BASE}/etc/java.util.logging.properties&quot; ${KARAF_SYSTEM_OPTS} ${KARAF_OPTS} ${OPTS} &quot;$@&quot; -classpath &quot;${CLASSPATH}&quot; ${MAIN}&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;


&lt;p&gt;During a live debug session, we witnessed the java process consuming arpox 1.6G&lt;br/&gt;
of memory. (xmx is set to 2G and the host system has 4G). At some point, in a manner&lt;br/&gt;
of 5-10s the mem usage jumped up near 3.5G and the process was killed. It was very&lt;br/&gt;
sudden.&lt;/p&gt;</description>
                <environment></environment>
        <key id="28680">NETVIRT-974</key>
            <summary>karaf process killed by OS due to OOM condition</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="10004" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Verified</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="vorburger">Michael Vorburger</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                            <label>csit:failures</label>
                    </labels>
                <created>Thu, 2 Nov 2017 20:23:09 +0000</created>
                <updated>Tue, 7 Nov 2017 09:00:16 +0000</updated>
                                                            <fixVersion>Nitrogen-SR1</fixVersion>
                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                                                            <comments>
                            <comment id="59895" author="vorburger" created="Thu, 2 Nov 2017 21:03:22 +0000"  >&lt;p&gt;we should have a hs_err_pid*.log file and &lt;b&gt;have&lt;/b&gt; to have an *.hprof file to know where and find a fix for an OOM...&lt;/p&gt;

&lt;p&gt;have you been able to re-double-check if these files are&apos;t already produced somewhere? How about just doing a dumb:&lt;/p&gt;

&lt;p&gt;sudo find / -name &quot;hs_err_pid*.log&quot;&lt;br/&gt;
sudo find / -name &quot;*.hprof&quot;&lt;/p&gt;

&lt;p&gt;the hprof should be produced by I can see that in $ODL/bin/karaf we already have &quot;-XX:+HeapDumpOnOutOfMemoryError&quot; on DEFAULT_JAVA_OPTS...&lt;/p&gt;

&lt;p&gt;to fix the folder where it would write the HPROF into, you could add: -XX:HeapDumpPath=/a/folder/you/can/recover &lt;/p&gt;</comment>
                            <comment id="59896" author="vorburger" created="Thu, 2 Nov 2017 23:05:09 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=jluhrsen&quot; class=&quot;user-hover&quot; rel=&quot;jluhrsen&quot;&gt;jluhrsen&lt;/a&gt; clarified that there is no hs_err_pid*.log or *.hprof - OS kills JVM before that&apos;s produced.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://lists.opendaylight.org/pipermail/controller-dev/2017-November/014034.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lists.opendaylight.org/pipermail/controller-dev/2017-November/014034.html&lt;/a&gt; lists some ideas how that possible.&lt;/p&gt;

&lt;p&gt;Attached &lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/attachment/14211/14211_ThreadExplosion.java&quot; title=&quot;ThreadExplosion.java attached to NETVIRT-974&quot;&gt;ThreadExplosion.java&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;https://jira.opendaylight.org/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt; is a quick test I wrote to convince myself that a big Thread bug should not lead to this behaviour. &lt;/p&gt;

&lt;p&gt;So then my best bet currently then is on some JNI crap or &quot;off heap allocation&quot; (ByteBuffers) - this is going to be fun to figure out.&lt;/p&gt;

&lt;p&gt;Best next step I can think of is to figure out how to get an OS (not JVM) level coredump kind of file when it gets killed, and then get help analyzing that.&lt;/p&gt;</comment>
                            <comment id="59941" author="jluhrsen" created="Mon, 6 Nov 2017 19:30:01 +0000"  >&lt;p&gt;well, it&apos;s looking more and more like something to do with the host os and how it interacts with whatever is&lt;br/&gt;
different in nitro/oxy vs carbon.&lt;/p&gt;

&lt;p&gt;I have some tests in the sandbox that show the crash is coming with the host image as is. Another job that&lt;br/&gt;
uses a host image from the past (these are updated periodically. think &quot;yum update -y&quot;) that is not seeing&lt;br/&gt;
the crash. Also, another job using the troublesome image but first doing a &quot;yum update -y&quot; before running&lt;br/&gt;
the CSIT suites and the crash is not seen.&lt;/p&gt;

&lt;p&gt;for completeness, the image label with the problem is:&lt;br/&gt;
  java-builder - 20171020-0130      (Oct. 20, 2017)&lt;/p&gt;

&lt;p&gt;the older image without the problem has a label of:&lt;br/&gt;
  java-builder - 20170807-2145     (Aug 7, 2017)&lt;/p&gt;


&lt;p&gt;Further, there was some very odd SFT failures we saw in the past and seemed like they could be explained&lt;br/&gt;
by crashing VMs or java processes just dying. I think the java-builder images used in those jobs was also&lt;br/&gt;
updated recently and the problem went away. If needed, we can dig in to that and see if the same image&lt;br/&gt;
label was used there. Maybe we just hit some corner case bug related to java and some host os software/lib&lt;br/&gt;
which is now fixed.&lt;/p&gt;

&lt;p&gt;what should we do next?&lt;/p&gt;</comment>
                            <comment id="59942" author="vorburger" created="Mon, 6 Nov 2017 19:54:13 +0000"  >&lt;p&gt;&amp;gt; but first doing a &quot;yum update -y&quot; before running the CSIT suites and the crash is not seen.&lt;/p&gt;

&lt;p&gt;can you detail which packages get updated from what (bad) version to which (good) versions? If only for future &quot;ah that was...&quot;.&lt;/p&gt;

&lt;p&gt;&amp;gt; what should we do next?&lt;/p&gt;

&lt;p&gt;In an ideal world with unlimited resources, it would be interesting to understand what was wrong here. Back in the real world, if I read this right (please confirm if I did get this right..), then basically the summary of what you&apos;re saying is that with current &quot;latest everything&quot;, we&apos;re good? If so, then my vote is &lt;em&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=J5Xu9UcOdj0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;fuhgeddaboudit&lt;/a&gt; ...&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;PS:  If we ever hit this kind of Kernel OOM killer hitting ODL again, the sub tasks on this issue now have steps which may be useful if something like this ever has to be investigated again another time.&lt;/p&gt;</comment>
                            <comment id="59943" author="klou" created="Mon, 6 Nov 2017 20:43:36 +0000"  >&lt;p&gt;This is no longer a blocker for Nitrogen-SR1 - correct?  &lt;/p&gt;

&lt;p&gt;Should we downgrade severity and move Fix Version/s value to Nitrogen-SR2?&lt;/p&gt;</comment>
                            <comment id="59946" author="jluhrsen" created="Mon, 6 Nov 2017 20:57:02 +0000"  >&lt;p&gt;I&apos;ve attached the full output of &quot;yum list installed&quot; before and after and including the &quot;yum update -y&quot;&lt;/p&gt;

&lt;p&gt;below is the diff of the packages that are listed in &quot;yum list installed&quot; before and after the &quot;yum update -y&quot;. Maybe there&lt;br/&gt;
is some difference in packages that will give a clue. maybe not. Maybe it&apos;s the java upgrade itself (from 144-0.b01 to 151-1.b12)&lt;br/&gt;
BTW, the older image (Aug 20) has java version 141-b16&lt;/p&gt;

&lt;p&gt;12:53 $ diff /tmp/beforeyumupdate /tmp/afteryumupdate &lt;br/&gt;
4,9c4,9&lt;br/&gt;
&amp;lt; NetworkManager.x86_64                 1:1.8.0-9.el7                   @base     &lt;br/&gt;
&amp;lt; NetworkManager-libnm.x86_64           1:1.8.0-9.el7                   @base     &lt;br/&gt;
&amp;lt; NetworkManager-ppp.x86_64             1:1.8.0-9.el7                   @base     &lt;br/&gt;
&amp;lt; NetworkManager-team.x86_64            1:1.8.0-9.el7                   @base     &lt;br/&gt;
&amp;lt; NetworkManager-tui.x86_64             1:1.8.0-9.el7                   @base     &lt;br/&gt;
&amp;lt; NetworkManager-wifi.x86_64            1:1.8.0-9.el7                   @base     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; NetworkManager.x86_64                 1:1.8.0-11.el7_4                @updates  &lt;br/&gt;
&amp;gt; NetworkManager-libnm.x86_64           1:1.8.0-11.el7_4                @updates  &lt;br/&gt;
&amp;gt; NetworkManager-ppp.x86_64             1:1.8.0-11.el7_4                @updates  &lt;br/&gt;
&amp;gt; NetworkManager-team.x86_64            1:1.8.0-11.el7_4                @updates  &lt;br/&gt;
&amp;gt; NetworkManager-tui.x86_64             1:1.8.0-11.el7_4                @updates  &lt;br/&gt;
&amp;gt; NetworkManager-wifi.x86_64            1:1.8.0-11.el7_4                @updates  &lt;br/&gt;
40c40&lt;br/&gt;
&amp;lt; augeas-libs.x86_64                    1.4.0-2.el7_4.1                 @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; augeas-libs.x86_64                    1.4.0-2.el7_4.2                 @updates  &lt;br/&gt;
214c214&lt;br/&gt;
&amp;lt; epel-release.noarch                   7-10                            @epel     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; epel-release.noarch                   7-11                            @epel     &lt;br/&gt;
304,311c304,310&lt;br/&gt;
&amp;lt; grub2.x86_64                          1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;lt; grub2-common.noarch                   1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;lt; grub2-pc.x86_64                       1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;lt; grub2-pc-modules.noarch               1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;lt; grub2-tools.x86_64                    1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;lt; grub2-tools-efi.x86_64                1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;lt; grub2-tools-extra.x86_64              1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;lt; grub2-tools-minimal.x86_64            1:2.02-0.64.el7.centos          @base     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; grub2.x86_64                          1:2.02-0.65.el7.centos.2        @updates  &lt;br/&gt;
&amp;gt; grub2-common.noarch                   1:2.02-0.65.el7.centos.2        @updates  &lt;br/&gt;
&amp;gt; grub2-pc.x86_64                       1:2.02-0.65.el7.centos.2        @updates  &lt;br/&gt;
&amp;gt; grub2-pc-modules.noarch               1:2.02-0.65.el7.centos.2        @updates  &lt;br/&gt;
&amp;gt; grub2-tools.x86_64                    1:2.02-0.65.el7.centos.2        @updates  &lt;br/&gt;
&amp;gt; grub2-tools-extra.x86_64              1:2.02-0.65.el7.centos.2        @updates  &lt;br/&gt;
&amp;gt; grub2-tools-minimal.x86_64            1:2.02-0.65.el7.centos.2        @updates  &lt;br/&gt;
341,342c340,341&lt;br/&gt;
&amp;lt; iptables.x86_64                       1.4.21-18.0.1.el7.centos        @base     &lt;br/&gt;
&amp;lt; iptables-services.x86_64              1.4.21-18.0.1.el7.centos        @base     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; iptables.x86_64                       1.4.21-18.2.el7_4               @updates  &lt;br/&gt;
&amp;gt; iptables-services.x86_64              1.4.21-18.2.el7_4               @updates  &lt;br/&gt;
371,373c370,372&lt;br/&gt;
&amp;lt; java-1.8.0-openjdk.x86_64             1:1.8.0.144-0.b01.el7_4         @updates  &lt;br/&gt;
&amp;lt; java-1.8.0-openjdk-devel.x86_64       1:1.8.0.144-0.b01.el7_4         @updates  &lt;br/&gt;
&amp;lt; java-1.8.0-openjdk-headless.x86_64    1:1.8.0.144-0.b01.el7_4         @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; java-1.8.0-openjdk.x86_64             1:1.8.0.151-1.b12.el7_4         @updates  &lt;br/&gt;
&amp;gt; java-1.8.0-openjdk-devel.x86_64       1:1.8.0.151-1.b12.el7_4         @updates  &lt;br/&gt;
&amp;gt; java-1.8.0-openjdk-headless.x86_64    1:1.8.0.151-1.b12.el7_4         @updates  &lt;br/&gt;
385,389c384,389&lt;br/&gt;
&amp;lt; kernel-debug-devel.x86_64             3.10.0-693.2.2.el7              @updates  &lt;br/&gt;
&amp;lt; kernel-headers.x86_64                 3.10.0-693.2.2.el7              @updates  &lt;br/&gt;
&amp;lt; kernel-tools.x86_64                   3.10.0-693.2.2.el7              @updates  &lt;br/&gt;
&amp;lt; kernel-tools-libs.x86_64              3.10.0-693.2.2.el7              @updates  &lt;br/&gt;
&amp;lt; kexec-tools.x86_64                    2.0.14-17.el7                   @base     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; kernel.x86_64                         3.10.0-693.5.2.el7              @updates  &lt;br/&gt;
&amp;gt; kernel-debug-devel.x86_64             3.10.0-693.5.2.el7              @updates  &lt;br/&gt;
&amp;gt; kernel-headers.x86_64                 3.10.0-693.5.2.el7              @updates  &lt;br/&gt;
&amp;gt; kernel-tools.x86_64                   3.10.0-693.5.2.el7              @updates  &lt;br/&gt;
&amp;gt; kernel-tools-libs.x86_64              3.10.0-693.5.2.el7              @updates  &lt;br/&gt;
&amp;gt; kexec-tools.x86_64                    2.0.14-17.2.el7                 @updates  &lt;br/&gt;
392,394c392,394&lt;br/&gt;
&amp;lt; kmod.x86_64                           20-15.el7_4.2                   @updates  &lt;br/&gt;
&amp;lt; kmod-libs.x86_64                      20-15.el7_4.2                   @updates  &lt;br/&gt;
&amp;lt; koji.noarch                           1.13.0-3.el7                    @epel     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; kmod.x86_64                           20-15.el7_4.4                   @updates  &lt;br/&gt;
&amp;gt; kmod-libs.x86_64                      20-15.el7_4.4                   @updates  &lt;br/&gt;
&amp;gt; koji.noarch                           1.14.0-1.el7                    @epel     &lt;br/&gt;
479c479&lt;br/&gt;
&amp;lt; libgudev1.x86_64                      219-42.el7_4.1                  @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; libgudev1.x86_64                      219-42.el7_4.4                  @updates  &lt;br/&gt;
542,543c542,543&lt;br/&gt;
&amp;lt; libsss_idmap.x86_64                   1.15.2-50.el7_4.2               @updates  &lt;br/&gt;
&amp;lt; libsss_nss_idmap.x86_64               1.15.2-50.el7_4.2               @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; libsss_idmap.x86_64                   1.15.2-50.el7_4.6               @updates  &lt;br/&gt;
&amp;gt; libsss_nss_idmap.x86_64               1.15.2-50.el7_4.6               @updates  &lt;br/&gt;
645c645&lt;br/&gt;
&amp;lt; nss.x86_64                            3.28.4-12.el7_4                 @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; nss.x86_64                            3.28.4-15.el7_4                 @updates  &lt;br/&gt;
650,651c650,651&lt;br/&gt;
&amp;lt; nss-sysinit.x86_64                    3.28.4-12.el7_4                 @updates  &lt;br/&gt;
&amp;lt; nss-tools.x86_64                      3.28.4-12.el7_4                 @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; nss-sysinit.x86_64                    3.28.4-15.el7_4                 @updates  &lt;br/&gt;
&amp;gt; nss-tools.x86_64                      3.28.4-15.el7_4                 @updates  &lt;br/&gt;
661,663c661,663&lt;br/&gt;
&amp;lt; openssh.x86_64                        7.4p1-12.el7_4                  @updates  &lt;br/&gt;
&amp;lt; openssh-clients.x86_64                7.4p1-12.el7_4                  @updates  &lt;br/&gt;
&amp;lt; openssh-server.x86_64                 7.4p1-12.el7_4                  @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; openssh.x86_64                        7.4p1-13.el7_4                  @updates  &lt;br/&gt;
&amp;gt; openssh-clients.x86_64                7.4p1-13.el7_4                  @updates  &lt;br/&gt;
&amp;gt; openssh-server.x86_64                 7.4p1-13.el7_4                  @updates  &lt;br/&gt;
675c675&lt;br/&gt;
&amp;lt; parallel.noarch                       20150522-1.el7.cern             installed &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; parallel.noarch                       20160222-1.el7                  @epel     &lt;br/&gt;
800c800&lt;br/&gt;
&amp;lt; python-perf.x86_64                    3.10.0-693.2.2.el7              @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; python-perf.x86_64                    3.10.0-693.5.2.el7              @updates  &lt;br/&gt;
829c829&lt;br/&gt;
&amp;lt; python2-koji.noarch                   1.13.0-3.el7                    @epel     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; python2-koji.noarch                   1.14.0-1.el7                    @epel     &lt;br/&gt;
884,885c884,885&lt;br/&gt;
&amp;lt; selinux-policy.noarch                 3.13.1-166.el7_4.4              @updates  &lt;br/&gt;
&amp;lt; selinux-policy-targeted.noarch        3.13.1-166.el7_4.4              @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; selinux-policy.noarch                 3.13.1-166.el7_4.5              @updates  &lt;br/&gt;
&amp;gt; selinux-policy-targeted.noarch        3.13.1-166.el7_4.5              @updates  &lt;br/&gt;
900c900&lt;br/&gt;
&amp;lt; sssd-client.x86_64                    1.15.2-50.el7_4.2               @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; sssd-client.x86_64                    1.15.2-50.el7_4.6               @updates  &lt;br/&gt;
907,911c907,911&lt;br/&gt;
&amp;lt; systemd.x86_64                        219-42.el7_4.1                  @updates  &lt;br/&gt;
&amp;lt; systemd-libs.i686                     219-42.el7_4.1                  @updates  &lt;br/&gt;
&amp;lt; systemd-libs.x86_64                   219-42.el7_4.1                  @updates  &lt;br/&gt;
&amp;lt; systemd-python.x86_64                 219-42.el7_4.1                  @updates  &lt;br/&gt;
&amp;lt; systemd-sysv.x86_64                   219-42.el7_4.1                  @updates  &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; systemd.x86_64                        219-42.el7_4.4                  @updates  &lt;br/&gt;
&amp;gt; systemd-libs.i686                     219-42.el7_4.4                  @updates  &lt;br/&gt;
&amp;gt; systemd-libs.x86_64                   219-42.el7_4.4                  @updates  &lt;br/&gt;
&amp;gt; systemd-python.x86_64                 219-42.el7_4.4                  @updates  &lt;br/&gt;
&amp;gt; systemd-sysv.x86_64                   219-42.el7_4.4                  @updates  &lt;br/&gt;
930,931c930,931&lt;br/&gt;
&amp;lt; tzdata.noarch                         2017b-1.el7                     @base     &lt;br/&gt;
&amp;lt; tzdata-java.noarch                    2017b-1.el7                     @base     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; tzdata.noarch                         2017c-1.el7                     @updates  &lt;br/&gt;
&amp;gt; tzdata-java.noarch                    2017c-1.el7                     @updates  &lt;br/&gt;
947c947&lt;br/&gt;
&amp;lt; wget.x86_64                           1.14-15.el7                     @base     &lt;br/&gt;
&amp;#8212;&lt;br/&gt;
&amp;gt; wget.x86_64                           1.14-15.el7_4.1                 @updates  &lt;br/&gt;
980,983d979&lt;/p&gt;
</comment>
                            <comment id="59947" author="jluhrsen" created="Mon, 6 Nov 2017 21:00:36 +0000"  >&lt;p&gt;Kit, I moved this to Medium and Major instead of Critical and Blocker&lt;/p&gt;</comment>
                            <comment id="59948" author="askb" created="Mon, 6 Nov 2017 21:00:54 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=jluhrsen&quot; class=&quot;user-hover&quot; rel=&quot;jluhrsen&quot;&gt;jluhrsen&lt;/a&gt; Could you check with the below recently updated java-builder image, if the issue is still reproducible. &lt;/p&gt;

&lt;p&gt;The SFT test which has OOM with the earlier builds is no longer seen with this image. &lt;/p&gt;

&lt;p&gt;&quot;88569cec-33d3-4fae-a749-da64fd9c9c5c&quot;&lt;br/&gt;
&quot;CentOS 7 - java-builder - 20171030-1039&quot;&lt;/p&gt;</comment>
                            <comment id="59949" author="jluhrsen" created="Mon, 6 Nov 2017 21:09:52 +0000"  >&lt;p&gt;hopefully this fixes us:&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/65231&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/65231&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="59962" author="skitt@redhat.com" created="Tue, 7 Nov 2017 09:00:16 +0000"  >&lt;p&gt;Funny that, I&#8217;d mentioned to Michael that the 151 Java 8 update listed a few OOM fixes in its changelog; perhaps that&#8217;s what&#8217;s helping us here...&lt;/p&gt;

&lt;p&gt;(I do suspect however that we&#8217;ve just moved the goalposts a little.)&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="14211" name="ThreadExplosion.java" size="1175" author="vorburger" created="Thu, 2 Nov 2017 23:02:37 +0000"/>
                            <attachment id="14207" name="dmesg.log.txt" size="50212" author="jluhrsen" created="Thu, 2 Nov 2017 20:25:14 +0000"/>
                            <attachment id="14208" name="journalctl.log.txt" size="830630" author="jluhrsen" created="Thu, 2 Nov 2017 20:25:44 +0000"/>
                            <attachment id="14210" name="odl1_karaf.log.txt" size="3748832" author="jluhrsen" created="Thu, 2 Nov 2017 20:26:52 +0000"/>
                            <attachment id="14209" name="odl1_karaf_console.log.txt" size="1528" author="jluhrsen" created="Thu, 2 Nov 2017 20:26:52 +0000"/>
                            <attachment id="14215" name="yumupdate" size="217237" author="jluhrsen" created="Mon, 6 Nov 2017 20:58:05 +0000"/>
                    </attachments>
                <subtasks>
                            <subtask id="28684">NETVIRT-975</subtask>
                            <subtask id="28691">NETVIRT-979</subtask>
                            <subtask id="28690">NETVIRT-978</subtask>
                            <subtask id="28685">NETVIRT-976</subtask>
                            <subtask id="28686">NETVIRT-977</subtask>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0375z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>