Notice resource-agents and resource-agents-extra are in the remove list. It's a common action from users to accept the removal after d-r-u.
After reboot:
ubuntu@pgsrv02:~$ dpkg -l | grep -i resource-agent
ii pacemaker-resource-agents 2.1.2-1ubuntu3.1 all cluster resource manager general resource agents
rc resource-agents 1:4.7.0-1ubuntu7 all Transitional package for the resource-agents
ii resource-agents-base 1:4.7.0-1ubuntu7 all Cluster Resource Agents curated by Ubuntu
ii resource-agents-common 1:4.7.0-1ubuntu7 amd64 Common files used by the Cluster Resource Agents
And now there is no resource-agents-extra, and the Pacemaker cluster is broken.
For what I see, the issue is that pacemaker-resource-agents has moved from:
Hi Lucas,
About the -proposed, you're right - I added only the universe repository.
Regarding the original issue, here is what happens:
The resource-agents package was installed as a dependency for pacemaker:
Before d-r-u:
ubuntu@pgsrv02:~$ dpkg -l | grep -i resource-agent resource- agents 2.0.3-3ubuntu4.3 all cluster resource manager general resource agents
ii pacemaker-
ii resource-agents 1:4.5.0-2ubuntu2.2 amd64 Cluster Resource Agents
Running d-r-u:
ubuntu@pgsrv02:~$ sudo do-release-upgrade
...
81 packages are going to be removed.
Continue [yN] Details [d]
Remove (was auto installed) accountsservice alsa-topology-conf gsettings- backend dconf-service gcc-10-base glib-networking networking- common glib-networking -services desktop- schemas language- selector- common rvice0 libasound2 libasound2-data libcanberra0 8-minimal libpython3.8-stdlib libqb0 libreadline5 headers- 5.4.0-109 linux-headers- 5.4.0-109- generic headers- 5.4.0-148 linux-headers- 5.4.0-148- generic image-5. 4.0-109- generic linux-modules- 5.4.0-109- generic contest python3-entrypoints python3- requests- unixsocket simplejson python3.8 python3.8-minimal resource-agents agents- extra session-migration sound-theme- freedesktop
alsa-ucm-conf at bsdmainutils cluster-glue cryptsetup-run
dconf-
glib-
gsettings-
libaccountsse
libcbor0.6 libdconf1 libdns-export1109 libevent-2.1-7 libfl2
libfuse2 libhogweed5 libjson-c4 liblrm2 libmpdec2 libmysqlclient21
libnettle7 libntfs-3g883 libogg0 libopenhpi3 libopenipmi0
libperl5.30 libplumbgpl2 libproxy1v5 libpython3.8
libpython3.
libsepol1 libsnmp-base libsnmp35 libsnmp40 libsoup2.4-1
libsoup2.4-common libstonith1 libtdb1 libtimedate-perl liburcu6
libvorbis0a libvorbisfile3 libxml2-utils libxmlb1
linux-
linux-
linux-
ltrace lz4 mysql-common ncal net-tools openhpid perl-modules-5.30
popularity-
python3-
resource-
Notice resource-agents and resource- agents- extra are in the remove list. It's a common action from users to accept the removal after d-r-u.
After reboot: resource- agents 2.1.2-1ubuntu3.1 all cluster resource manager general resource agents agents- base 1:4.7.0-1ubuntu7 all Cluster Resource Agents curated by Ubuntu agents- common 1:4.7.0-1ubuntu7 amd64 Common files used by the Cluster Resource Agents
ubuntu@pgsrv02:~$ dpkg -l | grep -i resource-agent
ii pacemaker-
rc resource-agents 1:4.7.0-1ubuntu7 all Transitional package for the resource-agents
ii resource-
ii resource-
And now there is no resource- agents- extra, and the Pacemaker cluster is broken.
For what I see, the issue is that pacemaker- resource- agents has moved from:
Version: 2.0.3-3ubuntu4.3
Depends: procps, resource-agents
To:
Version: 2.1.2-1ubuntu3.1 agents- base agents- extra
Depends: procps, resource-
Suggests: resource-
So the -extra packages is not required, but some of its content was part of the resources-agents previously (at least the pgsql).
This is a different bug from the one reported here but related. Any suggestions on how to handle this?