<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:05 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-1259] Error messages and logs missing for this or other RPC failures.</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1259</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;This is related to &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1258&quot; title=&quot;Clustering: RPC failing in clustering data store integration tests&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1258&quot;&gt;&lt;del&gt;CONTROLLER-1258&lt;/del&gt;&lt;/a&gt;. In addition to the problem encountered in the bug, it lacked a useful error message and log entry. This bug should be fixed first, since the other bug is needed to reproduce it.&lt;/p&gt;

&lt;p&gt;I&apos;m encountered this running /suites/clustering/datastore/020_crud_on_leader.txt.&lt;/p&gt;

&lt;p&gt;The Keywords that are failing are:&lt;/p&gt;

&lt;p&gt;Purchase cars on Leader&lt;br/&gt;
Purchase cars on Follower1&lt;br/&gt;
Purchase cars on Follower2&lt;/p&gt;

&lt;p&gt;What&apos;s happening is that the RPCs to &quot;buy a car&quot; only work when executed against one of the three controllers. Strangely it&apos;s not even the car-people shard leader.&lt;/p&gt;

&lt;p&gt;Tom Pantelis is running these test in Brocade&apos;s lab on Helium and they are passing. This bug is unique to Lithium.&lt;/p&gt;

&lt;p&gt;Other than the fact that these keywords are failing, this bug addresses the issue that the error messages and log entries are missing when the &quot;buy a car&quot; RPCs are used.&lt;/p&gt;

&lt;p&gt;Procedure:&lt;/p&gt;

&lt;p&gt;Pull the latest stable Lithium Release. I pulled distribution-karaf-0.3.0-20150414.220637-1140.zip&lt;/p&gt;

&lt;p&gt;Use the python cluster deploy script.&lt;/p&gt;

&lt;p&gt;Let the test run. The shards configured themselves in this way:&lt;/p&gt;

&lt;p&gt;car shard&lt;/p&gt;
{&apos;member1&apos;: &apos;Follower&apos;,
&apos;member2&apos;: &apos;Leader&apos;,
&apos;member3&apos;: &apos;Follower&apos;}
&lt;p&gt;people shard&lt;/p&gt;
{&apos;member1&apos;: &apos;Follower&apos;,
&apos;member2&apos;: &apos;Follower&apos;,
&apos;member3&apos;: &apos;Leader&apos;}
&lt;p&gt;car-people shard&lt;/p&gt;
{&apos;member1&apos;: &apos;Leader&apos;,
&apos;member2&apos;: &apos;Follower&apos;,
&apos;member3&apos;: &apos;Follower&apos;}


&lt;p&gt;After the test completes, use ReST RPCs to purchase a car on member1, member2, and member2. &lt;/p&gt;

&lt;p&gt;URL:&lt;br/&gt;
&lt;a href=&quot;http://member1:8181/restconf/operations/car-purchase:buy-car&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://member1:8181/restconf/operations/car-purchase:buy-car&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;JSON:&lt;br/&gt;
 { &quot;input&quot; : &lt;/p&gt;
  	{ 
      &quot;car-purchase:person&quot; : &quot;/people:people/people:person[people:id=&apos;user9&apos;]&quot;, 
      &quot;car-purchase:person-id&quot; : &quot;user9&quot;, 
      &quot;car-purchase:car-id&quot; : &quot;9&quot; 
    } 
&lt;p&gt; }&lt;/p&gt;

&lt;p&gt;For the first two members, there will be a 500 error in Postman, and nothing in the karaf log. Member3 gets a nice &#8220;200 OK&#8221; in Postman and I see an acknowledgement of the car purchase in the karaf log.&lt;/p&gt;

&lt;p&gt;The 500 error should contain some text (or even a stack trace - if that&apos;s not a security issue) describing the reason for the error. In this case the 500 error has no text.&lt;/p&gt;

&lt;p&gt;To observe the log files connect to the terminal on all three controllers.&lt;/p&gt;

&lt;p&gt;ssh karaf@member1 -p 8101&lt;br/&gt;
ssh karaf@member2 -p 8101&lt;br/&gt;
ssh karaf@member3 -p 8101&lt;/p&gt;


&lt;p&gt;If you try the &quot;buy a car&quot; RPCs, you will see nothing from the failures on member1 and member2, but you will see a acknowledgement message for the successful RPC on member3.&lt;/p&gt;

&lt;p&gt;The failures should produce both errors in the RPC ReST call and in the karaf log.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25813">CONTROLLER-1259</key>
            <summary>Error messages and logs missing for this or other RPC failures.</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <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="10000">Done</resolution>
                                        <assignee username="vdemcak@cisco.com">Vaclav Demcak</assignee>
                                    <reporter username="phillip.shea@hp.com">Phillip Shea</reporter>
                        <labels>
                    </labels>
                <created>Fri, 17 Apr 2015 18:55:05 +0000</created>
                <updated>Thu, 28 May 2015 13:46:20 +0000</updated>
                            <resolved>Thu, 28 May 2015 13:46:20 +0000</resolved>
                                    <version>Post-Helium</version>
                                                    <component>restconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="50448" author="tpantelis" created="Fri, 17 Apr 2015 20:07:58 +0000"  >&lt;p&gt;This is about reporting detailed error info on rpc failure. The error message just says something &quot;The operation encountered an unexpected error while executing.&quot; with no other info:&lt;/p&gt;

&lt;p&gt;{&lt;br/&gt;
  &quot;errors&quot;:{&lt;br/&gt;
    &quot;error&quot;:[&lt;/p&gt;
{
      &quot;error-type&quot;:&quot;application&quot;,
      &quot;error-tag&quot;:&quot;operation-failed&quot;,
      &quot;error-message&quot;:&quot;The operation encountered an unexpected error while executing.&quot;
}]}

&lt;p&gt;The error-info tag should be included with the detailed error cause, preferably including the stack trace. As I recall, it used to include this. &lt;/p&gt;

&lt;p&gt;As long as we return the detailed error info, I don&apos;t think we need to log it as warn or error in the karaf log.&lt;/p&gt;</comment>
                            <comment id="50449" author="vdemcak@cisco.com" created="Fri, 15 May 2015 07:32:17 +0000"  >&lt;p&gt;Restconf doesn&apos;t contain logs for more functionality (not only RPC)&lt;br/&gt;
so next patch adds better logging for Restconf (BrokerFacade and RestconfImpl)&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/19712/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/19712/&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                    <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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3017</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=3017]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10383"><![CDATA[Lithium-RC1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02pgv:</customfieldvalue>

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