Summary: plm: log entity paths for failed HPI calls
Review request for Trac Ticket(s): 2109
Peer Reviewer(s): Mathi
Pull request to:
Affected branch(es): default, 5.1, 5.0
Development branch:
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services y
OpenSAF services n
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
changeset 83f40abde765f9acce4b167a935386efe4cfbab7
Author: Alex Jones <ajo...@genband.com>
Date: Mon, 10 Oct 2016 14:20:22 -0400
plm: log entity paths for failed HPI calls [#2109]
Sep 27 00:34:10 q50-s2 osafplmd[10184]: ER failed to get resource id:
-1011
When an HPI call fails for a specific resource id or entity path, the
resource id or entity path is not always printed out.
Print out the resource id or entity path if the HPI call fails.
Complete diffstat:
------------------
osaf/libs/common/plmsv/include/plms_hsm.h | 4 +++-
osaf/services/saf/plmsv/plms/hpi_intf/plms_epath_util.c | 32
++++++++++++++++++++++++++++----
osaf/services/saf/plmsv/plms/hpi_intf/plms_hrb.c | 7 ++++++-
osaf/services/saf/plmsv/plms/hpi_intf/plms_hsm.c | 54
++++++++++++++++++++++++++++++++++++++++--------------
4 files changed, 77 insertions(+), 20 deletions(-)
Testing Commands:
-----------------
Difficult to test because there must be an error condition with hardware.
Testing, Expected Results:
--------------------------
entity path or resource id gets printed out
Conditions of Submission:
-------------------------
<<HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC>>
Arch Built Started Linux distro
-------------------------------------------
mips n n
mips64 n n
x86 n n
x86_64 y y
powerpc n n
powerpc64 n n
Reviewer Checklist:
-------------------
[Submitters: make sure that your review doesn't trigger any checkmarks!]
Your checkin has not passed review because (see checked entries):
___ Your RR template is generally incomplete; it has too many blank entries
that need proper data filled in.
___ You have failed to nominate the proper persons for review and push.
___ Your patches do not have proper short+long header
___ You have grammar/spelling in your header that is unacceptable.
___ You have exceeded a sensible line length in your headers/comments/text.
___ You have failed to put in a proper Trac Ticket # into your commits.
___ You have incorrectly put/left internal data in your comments/files
(i.e. internal bug tracking tool IDs, product names etc)
___ You have not given any evidence of testing beyond basic build tests.
Demonstrate some level of runtime or other sanity testing.
___ You have ^M present in some of your files. These have to be removed.
___ You have needlessly changed whitespace or added whitespace crimes
like trailing spaces, or spaces before tabs.
___ You have mixed real technical changes with whitespace and other
cosmetic code cleanup changes. These have to be separate commits.
___ You need to refactor your submission into logical chunks; there is
too much content into a single commit.
___ You have extraneous garbage in your review (merge commits etc)
___ You have giant attachments which should never have been sent;
Instead you should place your content in a public tree to be pulled.
___ You have too many commits attached to an e-mail; resend as threaded
commits, or place in a public tree for a pull.
___ You have resent this content multiple times without a clear indication
of what has changed between each re-send.
___ You have failed to adequately and individually address all of the
comments and change requests that were proposed in the initial review.
___ You have a misconfigured ~/.hgrc file (i.e. username, email etc)
___ Your computer have a badly configured date and time; confusing the
the threaded patch review.
___ Your changes affect IPC mechanism, and you don't present any results
for in-service upgradability test.
___ Your changes affect user manual and documentation, your patch series
do not contain the patch that updates the Doxygen manual.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
