Yum updates e-mail and software center show different

The e-mails I started getting a couple of days ago show 5 updates.

Updating:
 microcode_ctl          x86_64 2:2.1-47.5.el7_6     sb-updates            2.0 M
 nethserver-base        noarch 3.7.3-1.ns7          sb-nethserver-updates 247 k
 nethserver-cockpit     noarch 0.9.3-1.ns7          sb-nethserver-updates 2.1 M
 nethserver-cockpit-lib noarch 0.9.3-1.ns7          sb-nethserver-updates  31 k
 vim-minimal            x86_64 2:7.4.160-6.el7_6    sb-updates            437 k

However, going into Software Center I see a whole slew more:

|Name|Version|Release|
| --- | --- | --- |
|certbot|0.35.1|1.el7|
|device-mapper|1.02.149|10.el7_6.8|
|device-mapper-event|1.02.149|10.el7_6.8|
|device-mapper-event-libs|1.02.149|10.el7_6.8|
|device-mapper-libs|1.02.149|10.el7_6.8|
|glibc|2.17|260.el7_6.6|
|glibc|2.17|260.el7_6.6|
|glibc-common|2.17|260.el7_6.6|
|glibc-devel|2.17|260.el7_6.6|
|glibc-headers|2.17|260.el7_6.6|
|libgudev1|219|62.el7_6.7|
|libteam|1.27|6.el7_6.1|
|lvm2|2.02.180|10.el7_6.8|
|lvm2-libs|2.02.180|10.el7_6.8|
|microcode_ctl|2.1|47.5.el7_6|
|nethserver-base|3.7.3|1.ns7|
|nethserver-cgp|2.1.4|1.ns7|
|nethserver-cockpit|0.9.3|1.ns7|
|nethserver-cockpit-lib|0.9.3|1.ns7|
|nethserver-mail-common|2.6.6|1.ns7|
|nethserver-mail-filter|2.6.6|1.ns7|
|nethserver-mail-p3scan|2.6.6|1.ns7|
|nethserver-mail-server|2.6.6|1.ns7|
|nethserver-mail-smarthost|2.6.6|1.ns7|
|nethserver-vpn-ui|1.0.1|1.ns7|
|pulledpork|0.7.3|5.ns7|
|python2-acme|0.35.1|1.el7|
|python2-certbot|0.35.1|1.el7|
|systemd|219|62.el7_6.7|
|systemd-libs|219|62.el7_6.7|
|systemd-libs|219|62.el7_6.7|
|systemd-python|219|62.el7_6.7|
|systemd-sysv|219|62.el7_6.7|
|teamd|1.27|6.el7_6.1|
|vim-minimal|7.4.160|6.el7_6|

Updates CHANGELOG

Why are all these not showing in the e-mails.

Cheers.

Could you post your settings under Software Center > Configure ?

image

Cheers.

It’s a normal condition with #subscription updates. Manual updates always point to latest stable releases, whilst automated updates are rolled out gradually.

Really. :astonished:

Then why are (most of) this snapshot not showing in the e-mail, as they come from the same libraries:

image

I thought one of the advantages with a subscription is that I would only see stable updates. Also, how do I apply just the stable ones given this scenario.

Cheers.

They’ll be available in a few days!

I thought the subscription libraries were different and the updates were only rolled in later than they hit the regular ones.

image

So why is vim-minimal in the e-mail, but systemd-sysv not, as they are from the same library.

Similarly nethserver-base and nethserver-cockpit-lib is, but nethserver-cgp and nethserver-vpn-ui aren’t.

[root@Nethserver ~]# yum repolist -v
Loading "changelog" plugin
Loading "fastestmirror" plugin
Loading "nethserver_events" plugin
Config time: 0.015
Yum version: 3.4.3
Loading mirror speeds from cached hostfile
 * sb-base: u2.nethserver.com
 * sb-centos-sclo-rh: u2.nethserver.com
 * sb-centos-sclo-sclo: u2.nethserver.com
 * sb-epel: u2.nethserver.com
 * sb-extras: u2.nethserver.com
 * sb-nethserver-base: u2.nethserver.com
 * sb-nethserver-updates: u2.nethserver.com
 * sb-updates: u2.nethserver.com
Setting up Package Sacks
pkgsack time: 0.010
Repo-id      : sb-base/x86_64
Repo-name    : Stable mirror: CentOS Base 7
Repo-revision: 1543161601
Repo-updated : Sun Nov 25 08:00:34 2018
Repo-pkgs    : 10,019
Repo-size    : 9.4 G
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=base&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/base/x86_64/ (1 more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:04 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

Repo-id      : sb-centos-sclo-rh/x86_64
Repo-name    : Stable mirror: SCLo rh 7
Repo-revision: 1562597140
Repo-updated : Mon Jul  8 07:47:55 2019
Repo-pkgs    : 8,366
Repo-size    : 7.3 G
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=centos-sclo-rh&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/centos-sclo-rh/x86_64/
             : (1 more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:05 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

Repo-id      : sb-centos-sclo-sclo/x86_64
Repo-name    : Stable mirror: SCLo sclo 7
Repo-revision: 1561390845
Repo-updated : Mon Jun 24 08:40:50 2019
Repo-pkgs    : 780
Repo-size    : 237 M
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=centos-sclo-sclo&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/centos-sclo-sclo/x86_64/
             : (1 more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:05 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

Repo-id      : sb-epel/x86_64
Repo-name    : Stable mirror: EPEL 7
Repo-revision: 1562807525
Repo-updated : Wed Jul 10 18:14:20 2019
Repo-pkgs    : 13,297
Repo-size    : 15 G
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=epel&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/epel/x86_64/ (1 more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:06 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

Repo-id      : sb-extras/x86_64
Repo-name    : Stable mirror: CentOS Extras 7
Repo-revision: 1560955949
Repo-updated : Wed Jun 19 07:55:32 2019
Repo-pkgs    : 419
Repo-size    : 588 M
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=extras&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/extras/x86_64/ (1 more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:07 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

Repo-id      : sb-nethserver-base/x86_64
Repo-name    : Stable mirror: NethServer Base 7
Repo-revision: 1544698988
Repo-updated : Thu Dec 13 03:03:18 2018
Repo-pkgs    : 322
Repo-size    : 1.0 G
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=nethserver-base&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/nethserver-base/x86_64/
             : (1 more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:07 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

Repo-id      : sb-nethserver-updates/x86_64
Repo-name    : Stable mirror: NethServer Updates 7
Repo-revision: 1562748942
Repo-updated : Wed Jul 10 01:56:04 2019
Repo-pkgs    : 407
Repo-size    : 1.6 G
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=nethserver-updates&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/nethserver-updates/x86_64/
             : (1 more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:08 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

Repo-id      : sb-updates/x86_64
Repo-name    : Stable mirror: CentOS Updates 7
Repo-revision: 1562188294
Repo-updated : Wed Jul  3 14:25:02 2019
Repo-pkgs    : 2,231
Repo-size    : 11 G
Repo-mirrors : https://mirrorlist.nethserver.com/?repo=updates&arch=x86_64&nsversion=7.6.1810&usetier=$YUM0
Repo-baseurl : https://u2.nethserver.com/stable/7.6.1810/updates/x86_64/ (1
             : more)
Repo-expire  : 7,200 second(s) (last: Mon Jul 15 07:05:09 2019)
  Filter     : read-only:present
Repo-filename: /etc/yum.repos.d/subscription.repo

repolist: 35,841
[root@Nethserver ~]#

Cheers.

I guess because during the daily yum-cron task the repositories are different. You can try by yourself:

yum clean all
YUM0=yes yum repolist -v

Compared to

yum clean all
yum repolist -v

The difference should be in

  • https://u2.nethserver.com/autoupdate/7.6.1810 hit by yum-cron (YUM0=yes)
  • https://u2.nethserver.com/stable/7.6.1810 hit by software center and console

To answer your question, provided that either with or without “YUM0” here mean “stable” , you can run

yum clean all
YUM0=yes yum update

Interesting. Before I saw the above post, I ran a “yum update” in the console:

image

The updates that are in the e-mail are the ones that yum highlighted. Not sure what that highlighting means ?? ??

Cheers.

The files are already downloaded and present in YUM local cache dir.

Gottcha.

Can I suggest that the 2 processes are aligned, based on subscription status to avoid the confusion. And (maybe) the possibility of applying “untrusted” updates, which in this case it’s obvious there are differences. But if there were many trusted updates and only 1 untrusted one, it could be overlooked in scanning the software center list.

Cheers.