>>> Kadlecsik József <kadlecsik.joz...@wigner.hu> schrieb am 17.08.2020 um 12:12 in Nachricht <alpine.deb.2.23.453.2008171134050.25...@blackhole.kfki.hu>: > Hello, > > At upgrading a corosync/pacemaker/libvirt/KVM cluster from Debian stretch > to buster, all the node utilization attributes were erased from the > configuration. However, the same attributes were kept at the VirtualDomain > resources. This resulted that all resources with utilization attributes > were stopped. > > The documentation says: "You can name utilization attributes according to > your preferences and define as many name/value pairs as your configuration > needs.", so one assumes utilization attributes are kept during upgrades, > for nodes and resources as well.
Now that you mention it, I think we had it in the past with SLES, too. > > The corosync incompatibility made the upgrade more stressful anyway and > the stopping of the resources came out of the blue. The resources could > not be started of course ‑ and there were no log warning/error messages > that the resources are not started because the utilization constrains > could not be satisfied. Pacemaker logs a lot (from admin point of view it > is too much), but in this case there was no indication why the resources > could not be started (or we were unable to find it in the logs?). So we > wasted a lot of time with debugging the VirtualDomain agent. Also true: It's not very obvious when resources are not started due to utilization constraints. > > Currently we run the cluster with the placement‑strategy set to default. > > In my opinion node attributes should be kept and preserved during an > upgrade. Also, it should be logged when a resource must be stopped/cannot > be started because the utilization constrains cannot be satisfied. +1 > > Best regards, > Jozsef > ‑‑ > E‑mail : kadlecsik.joz...@wigner.hu > PGP key: https://wigner.hu/~kadlec/pgp_public_key.txt > Address: Wigner Research Centre for Physics > H‑1525 Budapest 114, POB. 49, Hungary > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/