<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:50 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>[CONTROLLER-1944] persisted data not restored in controller CSIT</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1944</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;example:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-1node-akka1-all-aluminium/97/robot-plugin/log.html.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-1node-akka1-all-aluminium/97/robot-plugin/log.html.gz&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;This is a stable test with magnesium.&lt;/p&gt;

&lt;p&gt;The failure is seen by a 409&#160; when trying a GET on /restconf/config/cars:cars&lt;/p&gt;

&lt;p&gt;This test is using the wildcard *journal to move the segmented-journal to the&lt;br/&gt;
new ODL instance that should recover the persisted data. The&#160;&lt;a href=&quot;https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-1node-akka1-all-aluminium/97/odl_1/odl1_karaf.log.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;karaf log &lt;/a&gt;&lt;br/&gt;
does have some mentions of journal data recovery. There is one exception in the&lt;br/&gt;
persistence area, but no idea if it&apos;s related or not:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
2020-06-08T03:08:11,487 | ERROR | opendaylight-cluster-data-akka.actor.&lt;span class=&quot;code-keyword&quot;&gt;default&lt;/span&gt;-dispatcher-19 | AbstractMXBean                   | 295 - org.opendaylight.controller.sal-common-util - 2.0.1 | registration failed
javax.management.InstanceAlreadyExistsException: org.opendaylight.controller:type=RemoteRpcBroker,name=RemoteRpcRegistry
	at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:436) ~[?:?]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1855) ~[?:?]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:955) ~[?:?]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:890) ~[?:?]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:320) ~[?:?]
	at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) ~[?:?]
	at org.opendaylight.controller.md.sal.common.util.jmx.AbstractMXBean.registerMBean(AbstractMXBean.java:107) [bundleFile:?]
	at org.opendaylight.controller.remote.rpc.registry.mbeans.AbstractRegistryMXBean.&amp;lt;init&amp;gt;(AbstractRegistryMXBean.java:43) [bundleFile:?]
	at org.opendaylight.controller.remote.rpc.registry.mbeans.RemoteRpcRegistryMXBeanImpl.&amp;lt;init&amp;gt;(RemoteRpcRegistryMXBeanImpl.java:25) [bundleFile:?]
	at org.opendaylight.controller.remote.rpc.registry.RpcRegistry.preStart(RpcRegistry.java:70) [bundleFile:?]
	at akka.actor.Actor.aroundPreStart(Actor.scala:550) [bundleFile:2.5.31]
	at akka.actor.Actor.aroundPreStart$(Actor.scala:550) [bundleFile:2.5.31]
	at akka.persistence.AbstractPersistentActor.akka$persistence$Eventsourced$$&lt;span class=&quot;code-keyword&quot;&gt;super&lt;/span&gt;$aroundPreStart(PersistentActor.scala:455) [bundleFile:2.5.31]
	at akka.persistence.Eventsourced.aroundPreStart(Eventsourced.scala:261) [bundleFile:2.5.31]
	at akka.persistence.Eventsourced.aroundPreStart$(Eventsourced.scala:253) [bundleFile:2.5.31]
	at akka.persistence.AbstractPersistentActor.aroundPreStart(PersistentActor.scala:455) [bundleFile:2.5.31]
	at akka.actor.ActorCell.create(ActorCell.scala:678) [bundleFile:2.5.31]
	at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:549) [bundleFile:2.5.31]
	at akka.actor.ActorCell.systemInvoke(ActorCell.scala:571) [bundleFile:2.5.31]
	at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:293) [bundleFile:2.5.31]
	at akka.dispatch.Mailbox.run(Mailbox.scala:228) [bundleFile:2.5.31]
	at akka.dispatch.Mailbox.exec(Mailbox.scala:241) [bundleFile:2.5.31]
	at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) [bundleFile:2.5.31]
	at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) [bundleFile:2.5.31]
	at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) [bundleFile:2.5.31]
	at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) [bundleFile:2.5.31]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="32739">CONTROLLER-1944</key>
            <summary>persisted data not restored in controller CSIT</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="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10002">Duplicate</resolution>
                                        <assignee username="jluhrsen">Jamo Luhrsen</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                    </labels>
                <created>Mon, 8 Jun 2020 23:51:00 +0000</created>
                <updated>Fri, 12 Jun 2020 10:54:49 +0000</updated>
                            <resolved>Fri, 12 Jun 2020 10:54:49 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="68190" author="rovarga" created="Tue, 9 Jun 2020 08:26:48 +0000"  >&lt;p&gt;The stack trace is completely unrelated and is fixed in &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1943&quot; title=&quot;InstanceAlreadyExistsException is reported during sal-remoterpc-connector startup&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1943&quot;&gt;&lt;del&gt;CONTROLLER-1943&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="68205" author="rovarga" created="Thu, 11 Jun 2020 08:46:13 +0000"  >&lt;p&gt;This is the upgrade scenario, where the journal comes from a previous version. Given that we are switching journal plugins, the old distro will be using leveldb, the new distro will be using segmented-journal &#8211; hence the data is not recovered (as the journal will be missing).&lt;/p&gt;

&lt;p&gt;To make this pass on Aluminium, the test should trigger a snapshot before shutting down the old instance (hence journal will be empty, hence it should not matter that we are using a different plugin).&lt;/p&gt;</comment>
                            <comment id="68206" author="rovarga" created="Thu, 11 Jun 2020 08:47:25 +0000"  >&lt;p&gt;This is specific to Mg-&amp;gt;Al transition. Future releases should work fine, as should previous ones.&lt;/p&gt;</comment>
                            <comment id="68215" author="tcere" created="Fri, 12 Jun 2020 10:15:05 +0000"  >&lt;p&gt;The issue for updating the tests related to Mg -&amp;gt; Al transition is already reported here: &lt;a href=&quot;https://jira.opendaylight.org/browse/INTTEST-95&quot; title=&quot;Jobs that transfer journal from old versions to new ones need to be updated due to segmented journal&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INTTEST-95&quot;&gt;INTTEST-95&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="68219" author="rovarga" created="Fri, 12 Jun 2020 10:54:49 +0000"  >&lt;p&gt;Let&apos;s track this in &lt;a href=&quot;https://jira.opendaylight.org/browse/INTTEST-95&quot; title=&quot;Jobs that transfer journal from old versions to new ones need to be updated due to segmented journal&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INTTEST-95&quot;&gt;INTTEST-95&lt;/a&gt; then.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="32689">INTTEST-95</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </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|i03swv:</customfieldvalue>

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