This really goes deeper than the agent, and I'm not sure that delays as proposed would be a good path forward here (as it would likely create some form of impact to use cases not affected by this).  

Ultimately this is a problem with clvmd, in that it can't handle a request when there is a member which hasn't started yet.  Having the agent need to accommodate this behavior doesn't seem like the best target.  

It is an unfortunate timing window for sure, but do we have the ability to work around this with timings or delays elsewhere?  Something that delays the node joining for the amount of time needed to get everything recovered elsewhere?

As we're looking at 6.10 planning, it would be great if we could find a way to eliminate this from consideration, as it would have minimal impact to our overall customer base and could be too invasive for prod-phase 3.

Let us know if we can pursue these other angles.

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days