Hi Sathwik, We have merged the below patch and it should fix this issue. https://git.opendaylight.org/gerrit/#/c/69657/
Regards, Arun From: [email protected] [mailto:[email protected]] On Behalf Of Michael Vorburger Sent: Tuesday, March 20, 2018 6:36 PM To: B Sathwik <[email protected]>; [email protected] Cc: [email protected]; [email protected] Subject: Re: [openflowplugin-dev] [genius-dev] Openflow Service ERROR state in Fluorine +infrautils-dev: On Tue, Mar 20, 2018 at 1:33 PM, B Sathwik <[email protected]<mailto:[email protected]>> wrote: I have raised a bug for this. Here is the JIRA link https://jira.opendaylight.org/browse/OPNFLWPLUG-988 Regards Sathwik From: B Sathwik Sent: Tuesday, March 20, 2018 12:34 PM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Openflow Service ERROR state in Fluorine Hi Genius CSIT for fluorine is failing because Openflow service is in ERROR state in diag status CLI output, where as it is passing for Oxygen. https://jenkins.opendaylight.org/releng/view/genius/job/genius-csit-1node-upstream-all-fluorine/ I tried it locally with fluorine distribution. Here is the output opendaylight-user@root> opendaylight-user@root>showSvcStatus Timestamp: Tue Mar 20 11:53:31 IST 2018 Node IP Address: 127.0.0.1 System ready state: ACTIVE OPENFLOW : ERROR IFM : OPERATIONAL ITM : OPERATIONAL DATASTORE : OPERATIONAL opendaylight-user@root> opendaylight-user@root> seeing this gives me an idea for an Enhancement, in the infrautils diagstatus code: What I think one would ideally want to see in this output, both on the CLI as well as when used e.g. from a CSIT script via JMX, to avoid having to dig through logs, is WHY something is in Error... so ideally, it should probably be possible to DiagStatusService report() not just a ServiceState in a ServiceDescriptor, but a Throwable to diagstatus, which would set the status to ERROR - and then the CLI/JMX/etc. could include that Throwable as more detailed background about the failure. The code catching exceptions and setting an ERROR ServiceState would then pass that Throwable to the ServiceDescriptor. In this particular case, the NPE that was apparently fixed by c/69657 would then show up there - which would probably help, in the future, to see the real problem more immediately. Would anyone be motivated to work on this? A new JIRA in the infrautils project would be a good start. Tx, M. -- Michael Vorburger, Red Hat [email protected]<mailto:[email protected]> | IRC: vorburger @freenode | ~ = http://vorburger.ch<http://vorburger.ch/> Can someone from openflowplugin team look into this issue? Best Regards Sathwik _______________________________________________ genius-dev mailing list [email protected]<mailto:[email protected]> https://lists.opendaylight.org/mailman/listinfo/genius-dev
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
