4 thoughts on - Yum Update Pulls In Lvm-cluster On 7.3

• Hello, which command did you execute, exactly?
  I have only experience with RHEL and not CentOS for what regards lvm2-cluster; in my opinion it is correct that it is included in “Resilient Storage” group. So that if you already had this group installed but not lvm2-cluster rpm package, it was a problem before, not now….

  Eg, in a CentOS 7.2 vm of mine I have:

  [root@manageiq ~]# rpm -q lvm2-cluster package lvm2-cluster is not installed
  [root@manageiq ~]#

  [root@manageiq ~]# rpm -q lvm2
  lvm2-2.02.130-5.el7.x86_64
  [root@manageiq ~]#

  [root@manageiq ~]# yum update
  . . . CentOS-release x86_64 7-3.1611.el7.CentOS
  base 23 k
  . . . lvm2 x86_64 7:2.02.166-1.el7_3.1
  updates 1.1 M
  . . . but no lvm2-cluster package proposed

  but correctly if I run

  [root@manageiq ~]# yum groupinstall “Resilient Storage”
  … Dependencies Resolved

  =================================================================================================== Package Arch Version
  Repository Size
  ===================================================================================================Installing for group install “Resilient Storage”:
  dlm x86_64 4.0.6-1.el7
  base 89 k gfs2-utils x86_64 3.1.9-3.el7
  base 302 k lvm2-cluster x86_64 7:2.02.166-1.el7_3.1
  updates 663 k Installing for dependencies:
  corosync x86_64 2.4.0-4.el7
  base 213 k corosynclib x86_64 2.4.0-4.el7
  base 125 k dlm-lib x86_64 4.0.6-1.el7
  base 24 k libqb x86_64 1.0-1.el7
  base 92 k resource-agents x86_64 3.9.5-82.el7_3.1
  updates 360 k Updating for dependencies:
  device-mapper x86_64 7:1.02.135-1.el7_3.1
  updates 269 k device-mapper-event x86_64 7:1.02.135-1.el7_3.1
  updates 177 k device-mapper-event-libs x86_64 7:1.02.135-1.el7_3.1
  updates 177 k device-mapper-libs x86_64 7:1.02.135-1.el7_3.1
  updates 333 k device-mapper-persistent-data x86_64 0.6.3-1.el7
  base 368 k lvm2 x86_64 7:2.02.166-1.el7_3.1
  updates 1.1 M
  lvm2-libs x86_64 7:2.02.166-1.el7_3.1
  updates 984 k

  Transaction Summary
  ===================================================================================================Install 3 Packages (+5 Dependent packages)
  Upgrade ( 7 Dependent packages)

  So it seems ok to me. It pulls the update of lvm2 package itself and also the lvm2-cluster package (correctly pulled from the “updates” repo)

  HIH, Gianluca

• Hi,

  Sorry for the delayed response.

  Below is the whole transaction:

  (shadow pts3) # yum clean metadata ; yum update Loaded plugins: changelog, fastestmirror, langpacks, priorities Cleaning repos: base cr extras updates
  10 metadata files removed
  8 sqlite files removed
  0 metadata files removed Loaded plugins: changelog, fastestmirror, langpacks, priorities base | 3.6 kB 00:00:00
  cr | 3.3 kB 00:00:00
  extras | 3.4 kB 00:00:00
  updates | 3.4 kB 00:00:00
  (1/5): cr/7/x86_64/primary_db | 1.2 kB 00:00:00
  (2/5): base/7/x86_64/group_gz | 155 kB 00:00:00
  (3/5): extras/7/x86_64/primary_db | 183 kB 00:00:00
  (4/5): updates/7/x86_64/primary_db | 1.2 MB 00:00:00
  (5/5): base/7/x86_64/primary_db | 5.6 MB 00:00:00
  Loading mirror speeds from cached hostfile Resolving Dependencies
  –> Running transaction check
  —> Package lvm2-cluster.x86_64 7:2.02.166-1.el7_3.1 will be installed
  –> Processing Dependency: resource-agents >= 3.9.5-25 for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: dlm >= 3.99.1-1 for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: corosync >= 1.99.9-1 for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: libquorum.so.5(COROSYNC_QUORUM_1.0)(64bit) for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: libcpg.so.4(COROSYNC_CPG_1.0)(64bit) for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: libcmap.so.4(COROSYNC_CMAP_1.0)(64bit) for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: libquorum.so.5()(64bit) for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: libdlm.so.3()(64bit) for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: libcpg.so.4()(64bit) for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Processing Dependency: libcmap.so.4()(64bit) for package: 7:lvm2-cluster-2.02.166-1.el7_3.1.x86_64
  –> Running transaction check
  —> Package corosync.x86_64 0:2.4.0-4.el7 will be installed
  –> Processing Dependency: libqb.so.0()(64bit) for package: corosync-2.4.0-4.el7.x86_64
  —> Package corosynclib.x86_64 0:2.4.0-4.el7 will be installed
  —> Package dlm.x86_64 0:4.0.6-1.el7 will be installed
  —> Package dlm-lib.x86_64 0:4.0.6-1.el7 will be installed
  —> Package resource-agents.x86_64 0:3.9.5-82.el7_3.3 will be installed
  –> Running transaction check
  —> Package libqb.x86_64 0:1.0-1.el7 will be installed
  –> Finished Dependency Resolution

  Dependencies Resolved

  ================================================================================================================================================================================================================== Package Arch Version Repository Size
  ==================================================================================================================================================================================================================Installing for group upgrade “Resilient Storage”:
  lvm2-cluster x86_64 7:2.02.166-1.el7_3.1 updates 663 k Installing for dependencies:
  corosync x86_64 2.4.0-4.el7 base 213 k
  corosynclib x86_64 2.4.0-4.el7 base 125 k
  dlm x86_64 4.0.6-1.el7 base 89 k
  dlm-lib x86_64 4.0.6-1.el7 base 24 k
  libqb x86_64 1.0-1.el7 base 92 k
  resource-agents x86_64 3.9.5-82.el7_3.3 updates 361 k

  Transaction Summary
  ==================================================================================================================================================================================================================Install 1 Package (+6 Dependent packages)

  Total download size: 1.5 M
  Installed size: 3.5 M
  Is this ok [y/d/N]:
  Exiting on user command Your transaction was saved, rerun it with:
  yum load-transaction /tmp/yum_save_tx.2017-01-04.00-16.SQFChS.yumtx
  (shadow pts3) #

  (shadow pts2) # rpm -q lvm2-cluster package lvm2-cluster is not installed
  (shadow pts2) #

  Hummm, According to the changelog your version of lvm2 is over a year old.

  (shadow pts2) # rpm -q lvm2
  lvm2-2.02.166-1.el7_3.1.x86_64
  (shadow pts2) #

  This is the latest from the CentOS repo. I do not however think this is a problem, it is just an observation.

  If I run yum groupinstall “Resilient Storage” I get the essentially same results as you do.

  So I guess what I am trying to figure out is what is pulling in the Resilient Storage group.

  Suggestions?

  Regards,

• No problem

  Yes, it was a test vm server not recently updated.

  question: your .repo files under /etc/yum.repos.d contain official CentOS
  mirrors or anything customized that could have broken repodata information?

  question: why are you using priorities plugin?
  See here for related files, in case:
  https://wiki.CentOS.org/PackageManagement/Yum/Priorities

  What I would test/try in order is:

  – check all enabled contents in .repo files and verify it is correct in respect with a standard CentOS 7 system

  – yum update –disablerepo=cr and see if anything changes

  – it could be related with priorities plugin too, I would try yum update –disableplugin=priorities and/or yum update –disableplugin=priorities –disablerepo=cr

  – I never used changelog plugin and it should pop-in only if changelog option has been given in yum command, anyway I would try yum update –disableplugin=changelog and/or yum update –disableplugin=changelog –disablerepo=cr

  – try running yum command with debug option enabled and see if anything pops up yum update -d 5

  HIH, Gianluca

• …
  …

  I don’t see how the above output could be much more clear. It wants to upgrade the installed group of packages named “Resilient Storage” and the included packages have new dependencies.

  Options:
  * realise you don’t want the group and remove it
  * live with its new dependencies even though you wont use all of them
  (this is of course the situation more many other packages on your
  machine already)
  * hold off on the update

  /Peter K