[Debian-ha-maintainers] Bug#847295: Bug#847295: pcs: cluster auth does not generate tokens file & hangs on find

[Valentin Vidic]

On Thu, Dec 08, 2016 at 11:12:00PM -0200, Rafael David Tinoco wrote:
> Wasn't aware of that, my bad here. Somehow I assumed that it could only
> manage a cluster configured by it from the beginning, I should have 
> tested this more carefully. 

Yes, crmsh was the cluster configuration tool released in previous Debian
versions.  pcs will be included in included in stretch for the first time
so it is quite possible that people will install it on their clusters in
addition to the existing crmsh package.  Both configuration tools can be
active at the same time as the resource configuration is stored in
pacemaker CIB.

> APT::Install-Recommends "false" in apt.conf does that. Pacemaker is declared 
> as "Recommended" and it should be as "Dependency":
> 
> https://www.debian.org/doc/debian-policy/ch-relationships.html
> " The Depends field should be used if the depended-on package is required 
> for the depending package to provide a significant amount of functionality."
> 
> I choose to put corosync only as a Dependency. Maybe its better to have 
> Pacemaker instead.

We can review this dependency but the default setup that we support on
Debian is with APT::Install-Recommends "true".  Users can disable this
but need to handle possible problems too.

> Definitely. For LP: #1640923 the key is:
> 
> "sudo pcs cluster destroy" before moving on. 
> 
> It clears /etc/corosync and /var/lib/corosync/ (I just realized my upstream 
> commit was wrong, just fixed it into:https://github.com/ClusterLabs/pcs/pull/120
> 
> With that said, sorry to bother and thank you much for reviewing this for me.
> I'll make sure patches are good for Xenial/Yakkety and propose the debdiffs.
> 
> No change is needed in Debian. Should I close this case ? 
> (Would you use it for changing recommends/depends ?)

I think it can be closed and I will try to document these
findings for the next package release. 

-- 
Valentin