[Pacemaker] Pacemaker 0.6.3 (progress report)

Andrew Beekhof abeekhof at suse.de
Thu Apr 17 02:55:56 EDT 2008

Hi All,

Just wanted to let people know about the progress of 0.6.3 which is  
due about now.
Unfortunately my cluster hardware isn't co-operating and its taking a  
little while to get to the point where I can do the release testing.

Hopefully it wont be much longer.  See below for the current list of  


   * Update source tarball to revision: be12cb83cd2d
   * Statistics:
       Changesets:       68
       Diff:          329 files changed, 16312 insertions(+), 10799  

   * Changes since Pacemaker-0.6.2
   + High: Admin: Bug LF:1848 - crm_resource - Pass set name and id to  
delete_resource_attr() in the correct order
   + High: Build: SNMP has been moved to the management/pygui project
   + High: crmd: Bug LF1837 - Unmanaged resources prevent crmd from  
shutting down
   + High: PE: Anti-colocation with slave shouldn't prevent master  
   + High: PE: Bug LF 1768 - Wait more often for STONITH ops to  
complete before starting resources
   + High: PE: Bug LF1836 - Allow is-managed-default=false to be  
overridden by individual resources
   + High: PE: Bug LF185 - Prevent pointless master/slave instance  
shuffling by ignoring the master-pref of stopped instances
   + High: PE: Bug N-191176 - Implement interleaved ordering for clone- 
to-clone scenarios
   + High: PE: Bug N-347004 - Ensure clone notifications are always  
sent when an instance is stopped/started
   + High: PE: Bug N-347004 - Include notification ordering is correct  
for interleaved clones
   + High: PE: Bug PM-11 - Directly link probe_complete to starting  
clone instances
   + High: PE: Bug PM1 - Fix setting failcounts when applied to  
complex resources
   + High: PE: Bug PM12, LF1648 - Extensive revision of group ordering
   + High: PE: Bug PM7 - Ensure masters are always demoted before they  
are stopped
   + High: PE: Create probes after allocation to allow smarter  
handling of anonymous clones
   + High: PE: Don't prioritize clone instances that must be moved
   + High: TE: Repair failcount updates
   + High: TE: Use the correct offset when updating failcount
   + Medium: Build: Make configure fail if bz2 or libxml2 are not  
   + Medium: Build: Re-instate a better default for LCRSODIR
   + Medium: CIB: Bug LF-1861 - Filter irrelvant error status from  
synchronous CIB clients
   + Medium: Core: Bug 1849 - Invalid conversion of ordinal leap year  
to gregorian date
   + Medium: Core: Disable compataibility code for 2.0.4 and 2.0.5  
   + Medium: crmd: Bug LF-1860 - Automatically cancel recurring ops  
before demote and promote operations (not only stops)
   + Medium: PE: Bug LF:1866 - Fix version check when applying  
compatability handling for failed start operations
   + Medium: PE: Bug LF:1866 - Restore the ability to have start  
failures not be fatal
   + Medium: PE: Bug PM1 - Failcount applies to all instances of non- 
unique clone
   + Medium: PE: Correctly set the state of partially active master/ 
slave groups
   + Medium: PE: Don't claim to be stopping an already stopped orphan
   + Medium: PE: Ensure implies_left ordering constraints are always  
   + Medium: PE: Reprocess the current action if it changed (so that  
any prior dependancies are updated)
   + Medium: snmp: Reference the correct internal header
   + Medium: TE: Bug LF-1859 - Wait for fail-count updates to complete  
before terminating the transition
   + Medium: TE: Bug LF:1859 - Don't abort graphs due to our own  
failcount updates
   + Medium: TE: Bug LF:1859 - Prevent the TE from interupting itself

More information about the Pacemaker mailing list