Strange behavior of yum-cron / yum-update / softwarecenter in cockpit and old GUI

NethServer Version: 7.7.1809
Module: softwarecenter / yum

Hi there,

I noticed differences in updates between softwarecenter of old gui and cockpit and yum-cron mail report.
3 different reports with 4 different methods???

  1. yum-cron mail report:
    yum-cron only reports 1 package

  2. old GUI softwarecenter:
    here are 9 packages reported

  3. cockpit reports this:

    BUT: POP3 connector / Roundcube and Webtop are not installed on this machine!

  4. yum ceck-updates reports:

    nethserver-cockpit.noarch 1.4.2-1.ns7 sb-nethserver-updates
    nethserver-cockpit-lib.noarch 1.4.2-1.ns7 sb-nethserver-updates
    nethserver-evebox.noarch 1.2.1-1.ns7 sb-nethserver-updates
    nethserver-fail2ban.noarch 1.3.6-1.ns7 sb-nethserver-updates
    nethserver-mail-common.noarch 2.11.3-1.ns7 sb-nethserver-updates
    nethserver-mail-disclaimer.noarch 2.11.3-1.ns7 sb-nethserver-updates
    nethserver-mail-server.noarch 2.11.3-1.ns7 sb-nethserver-updates
    nethserver-mail-smarthost.noarch 2.11.3-1.ns7 sb-nethserver-updates
    python2-future.noarch 0.18.2-2.el7 sb-epel

Which is the same as old GUI.

After update with cockpit-softwarecenter the yum.log reports:

Feb 17 09:12:29 Updated: nethserver-cockpit-lib-1.4.2-1.ns7.noarch
Feb 17 09:12:29 Updated: nethserver-mail-smarthost-2.11.3-1.ns7.noarch
Feb 17 09:12:30 Updated: nethserver-mail-common-2.11.3-1.ns7.noarch
Feb 17 09:12:37 Installed: geolite2-city-20180605-1.el7.noarch
Feb 17 09:12:37 Updated: nethserver-evebox-1.2.1-1.ns7.noarch
Feb 17 09:12:37 Updated: nethserver-mail-server-2.11.3-1.ns7.noarch
Feb 17 09:12:38 Updated: nethserver-mail-disclaimer-2.11.3-1.ns7.noarch
Feb 17 09:12:38 Updated: nethserver-cockpit-1.4.2-1.ns7.noarch
Feb 17 09:12:38 Updated: nethserver-fail2ban-1.3.6-1.ns7.noarch
Feb 17 09:12:39 Updated: python2-future-0.18.2-2.el7.noarch

Which is the same as yum check-updates showed.

Has anybody else noticed this strange behavior??
How can this be?

TIA Ralf

Hi Ralph, you are right, there are some differences because they refer to different things. I try to clarify some aspects, feel free to ask for more information.

You have a subscription (sb-epel says that).

yum-cron runs during the night and fetches the RPMs from the autoupdates/ repositories. They are synchronized to their upstream counterparts about one time per week. If you wait a few days, you’ll see the other packages too!

You are applying a “manual” update. Here you see the packages from the stable/ repositories. They are synchronized every day at 21.00 UTC with their upstream counterparts. Manual updates with a subscription could be useful

  1. when you install new packages
  2. when you immediately want a new package version (e.g. a bug fix)

I guess in Details you can see the same RPMs. However the list tries to group them under the “Application” that requires at least one of them. I might ask @giacomo and @edoardo_spadoni to shed more light about this.

This is the expected behavior.

Hi @davidep,
thank you for your answer and your try to clarify.

Yes, I have a subscription.
But I’m still a little bit confused. :blush:

I understand the part with autoupdates/ and stable/ repos, even when I don’t get why and how there are 2 different repos configured. In /etc/yum.repos.d there is only the subscsrition.repo enabled.

BUT shouldn’t old GUI and cockpit report the same?
Why are there applications reported when they are not installed at all?
And why in Details you can see rpms of other application than in the main page?
That doesn’t make sense to me. :thinking:
Please don’t get me wrong, but i my eyes this is more a bug than a special behavior.

1 Like