Bug #9795

1.3.0 clients does not discover 1.3.1 servers

Added by Adam Gibbins 8 months ago. Updated 6 months ago.

Status:Closed Start date:09/29/2011
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Keywords: Affected mCollective version:
Branch:
Votes: 0

Description

I’ve just upgraded my MCollective Client to 1.3.1 and am finding that mc-find-hosts does not report 1.3.0 servers.

All machines are running Ubuntu Linux. The 1.3.1 client running Natty, the 1.3.0 client running Lucid along with both servers.

I run “mc-find-hosts” on a 1.3.1 client and the 1.3.0 server logs:

D, [2011-09-29T11:47:04.813560 #9748] DEBUG -- : runnerstats.rb:42:in `received' Incrementing total stat
D, [2011-09-29T11:47:04.813697 #9748] DEBUG -- : ssl.rb:171:in `deserialize' De-Serializing using marshal
D, [2011-09-29T11:47:04.813790 #9748] DEBUG -- : ssl.rb:126:in `validrequest?' Validating request from cert=agibbins-public
D, [2011-09-29T11:47:04.814064 #9748] DEBUG -- : runnerstats.rb:31:in `validated' Incrementing validated stat
D, [2011-09-29T11:47:04.814139 #9748] DEBUG -- : ssl.rb:171:in `deserialize' De-Serializing using marshal
D, [2011-09-29T11:47:04.814237 #9748] DEBUG -- : base.rb:117:in `validate_filter?' Message failed the filter checks
D, [2011-09-29T11:47:04.814303 #9748] DEBUG -- : runnerstats.rb:25:in `filtered' Incrementing filtered stat
D, [2011-09-29T11:47:04.814385 #9748] DEBUG -- : runner.rb:87:in `run' Message does not pass filters, ignoring
D, [2011-09-29T11:47:04.814452 #9748] DEBUG -- : stomp.rb:134:in `receive' Waiting for a message from Stomp

Yet I run “mc-inventory foobar” on a 1.3.1 client and the 1.3.0 server reports successfully:

Inventory for foobar:
Server Statistics:
Version: 1.3.0
Start Time: Thu Sep 29 11:46:16 +0100 2011
Config File: /etc/mcollective/server.cfg
Collectives: mcollective
Main Collective: mcollective
Process ID: 9748
Total Messages: 21
Messages Passed Filters: 3
Messages Filtered: 18
Replies Sent: 2
Total Processor Time: 0.19 seconds
System Time: 0.1 seconds
<snip>

Running “mc-find-hosts” on a 1.3.0 client experiences the same problem against a 1.3.1 server. Again, mc-inventory works.

All machines are running the discovery agent.

History

Updated by R.I. Pienaar 8 months ago

  • Subject changed from 1.3.0 mc-find-hosts seems unable to talk to 1.3.1 servers to 1.3.0 clients does not discover 1.3.1 servers

Updated by R.I. Pienaar 6 months ago

  • Status changed from Unreviewed to Closed

Looked into this, not much to be done about – especially since 1.3.2 is again not compatible with 1.3.1 so going to close it. This kind of thing is to be expected in dev releases its unfortunate I didnt know about this to point it out in the rel notes though – this is made clear in 1.3.2 notes.

Also available in: Atom PDF