bugcrmsh - Bugs: bug #38036, crm shell doesn't recognize valid...

 
 

bug #38036: crm shell doesn't recognize valid hosts in #uname rules

Submitter:  Alan Robertson <ossalanr>
Submitted:  Mon 07 Jan 2013 04:27:42 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Works For Me
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 15 Mar 2013 07:32:44 PM UTC, comment #1: 

Cannot reproduce. Please try with the latest crmsh version.

Dejan Muhamedagic <dejanm>
Group administrator
Mon 07 Jan 2013 04:27:42 PM UTC, original submission:  

I have a series of clusters with 4 or more nodes in them.   There is an IPMI STONITH
resource for each node.  Each STONITH resource is constrained to NOT run on
the machine it is STONITHing -- since that doesn't work.


When I save the configuration, I get these messages:

foo-db01: WARNING: 4: stonith_foo-db01-loc: referenced node foo-db01 does not exist
foo-db01: WARNING: 4: stonith_foo-db02-loc: referenced node foo-db02 does not exist
foo-db01: WARNING: 4: stonith_foo-pn01-loc: referenced node foo-pn01 does not exist
foo-db01: WARNING: 4: stonith_foo-pn02-loc: referenced node foo-pn02 does not exist
foo-db01: WARNING: 4: stonith_foo-pn03-loc: referenced node foo-pn03 does not exist
foo-db01: WARNING: 4: stonith_foo-pn04-loc: referenced node foo-pn04 does not exist
foo-db01: WARNING: 4: stonith_foo-pn05-loc: referenced node foo-pn05 does not exist
foo-db01: WARNING: 4: stonith_foo-pn06-loc: referenced node foo-pn06 does not exist

Everything works exactly as it should, except for getting these bogus messages.

These system names are all correct and are all in the configuration.
Amusingly enough, the machine foo-db01 is complaining that even it doesn't exist.

The rules are created by a script that configures all the machines in the configuration.
The text in the here document that creates it looks like this:

location stonith_${node}-loc stonith_$node \\
    rule \$id="ST_${node}_loc_R" -inf: #uname eq ${node}

or more concretely:
location stonith_foo-db01-loc stonith_foo-db01 \
    rule $id="ST_foo-db01_loc_R" -inf: #uname eq foo-db01

These rules all work exactly like they should - but our customer doesn't like the bogus warnings.  Please note that I cannot provide you the exact or complete configuration because our customer  would not allow that. I can assure you that if I remove those constraints that the warnings
go away, and if I leave them in I get these warnings.

Alan Robertson <ossalanr>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by dejanm (Posted a comment)
  • -email is unavailable- added by ossalanr (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-03-15 dejanm StatusNone Works For Me
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-bb6a.
    Corresponding source code