I would suggest to wait for LP: #1740892 SRU to be completed first since it affects package upgrade (corosync/pacemaker relation).
Additionally, IMHO, it may be "safer" to not introduce too much change in one SRU, especially considering LP: #1740892 mark as Critical.
1) Please keep monitoring LP: #1740892 and let's wait for the SRU to turn "Fix Released" for Trusty.
2) Then let's start LP: #1316970 SRU right after using either "STS-Sponsor" or "Ubuntu Sponsors Team"
Seyeong,
The SRU for LP: #1740892 is not started yet, but base on nacc's comment, It should start soon : /bugs.launchpad .net/charm- hacluster/ +bug/1740892/ comments/ 47
https:/
I would suggest to wait for LP: #1740892 SRU to be completed first since it affects package upgrade (corosync/pacemaker relation).
Additionally, IMHO, it may be "safer" to not introduce too much change in one SRU, especially considering LP: #1740892 mark as Critical.
1) Please keep monitoring LP: #1740892 and let's wait for the SRU to turn "Fix Released" for Trusty.
2) Then let's start LP: #1316970 SRU right after using either "STS-Sponsor" or "Ubuntu Sponsors Team"
- Eric