Summary: set state_model for HEs at switchover
Review request for Trac Ticket(s): 1789
Peer Reviewer(s): Mathi
Pull request to: Mathi
Affected branch(es): default, 4.7, 4.6
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 6e2cef9d6fd61285c8033b7762e7987637bf4431
Author: Alex Jones <[email protected]>
Date:   Fri, 29 Apr 2016 11:49:23 -0400

        plm: set state_model for HEs at switchover [#1789]

        Apr 29 09:01:38 q50-s1 osafplmd[6482]: ER Invalid state model: 0 Apr 29
        09:01:38 q50-s1 osafplmd[6482]: ER Ent
        safHE=Stirling_Blade_slot_6,safDomain=Q50chassis deactivation failed.

        After switchover PLM does not set the state_model variable in 
PLMS_ENTITY.
        The only time it gets set is when a hotswap event comes up from HPI. At 
this
        point PLM admin operations on HEs without the state_model set all fail 
with
        the above log message.

        Solution is to set the state_model after switchover.


Complete diffstat:
------------------
 osaf/services/saf/plmsv/plms/hpi_intf/plms_hsm.c |  47 
+++++++++++++++++++++++++++++++++++++++++++++++
 osaf/services/saf/plmsv/plms/plms_stdby.c        |  17 +++++++++++++++++
 2 files changed, 64 insertions(+), 0 deletions(-)


Testing Commands:
-----------------
1) lock an HE
2) do middleware si-swap (amf-adm si-swap safSi=SC-2N,safApp=OpenSAF)
3) deactivate the HE

Testing, Expected Results:
--------------------------
1) HE should successfully deactivate


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.


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to