© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
It looks like this problem is still persistent in 5.0.x branch. This sometimes happens when applied diff is empty, e.g. when there is no difference between pacemaker config being applied. On the second run of the same command diff applies cleanly and everything is ok. So it looks like we need to catch this exception and simply retry.