group.of.nepali.translators team mailing list archive

[Lucas Albuquerque Medeiros de Moura <1924766@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

[Impact]
When ESM Apps goes into production we want to be able to advertise it to our users through MOTD.
Currently, update-notifier apt-check does not take into consideration the exclusive packages of ESM Apps, which is a problem.

[Test case]

To reproduce the issue, you can:

1. Launch a xenial vm
2. Install the latest version of uaclient from the stable ppa:
   https://launchpad.net/~ua-client/+archive/ubuntu/stable/
3. Change the following line on `/etc/ubuntu-advantage/uaclient.conf` from
   
   contract_url: 'https://contracts.canonical.com'

   To:

   contract_url: 'https://contracts.staging.canonical.com'

4. Attach a staging token to uaclient thorough:

    ua attach YOUR_STAGING_TOKEN

5. Run /usr/lib/update-notifier/apt-check --human-readable
6. Verify that no mention to ESM Apps is made and that update-notifier puts all of the ESM packages in the same bucket


To verify that the error is fixed:

1.Perform all the stages above until step 4
2 Install the new update-notifier from this ppa:
  https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa
3. Verify now that ESM Apps is reflected in the message

[Where problems could occur]

The changes in this package should only be seen when MOTD is getting a
new message. If that script fails for some reason, it seems that MOTD
will only not present the message, which is doesn't seem to be a system
critical issue.

[Discussion]

With ESM Apps going to production soon, we have decided to update the
messages delivered by update-notifier apt-check to address the package
count of ESM Apps and the possibility of installing more upgrades if the
user has ESM Apps disabled.

We are also updating other parts of the messaging as well. First, we only display ESM Infra status
on ESM distros. However, we will keep showing the ESM Infra package count on all of them.

For ESM Apps, we are only performing the alerts (For example, that you
might have x packages updates if ESM Apps is installed) if the user is
on a LTS distro.

Finally, we are also addressing this bug here:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1883315

Where we were incorrectly counting ESM packages even if the user did not
have access to those services.

== Changelog ==

  + data/apt-check
    - Make distinction of ESM Apps and ESM Infra when doing package count
    - Only count ESM packages if the user has access to the service (LP #1883315)
    - Only display ESM Infra alerts if the distro is ESM

** Affects: update-notifier (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: update-notifier (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Also affects: update-notifier (Ubuntu Xenial)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1924766

Title:
  update-notifier does not handle ESM Apps in the apt-check script

Status in update-notifier package in Ubuntu:
  New
Status in update-notifier source package in Xenial:
  New

Bug description:
  [Impact]
  When ESM Apps goes into production we want to be able to advertise it to our users through MOTD.
  Currently, update-notifier apt-check does not take into consideration the exclusive packages of ESM Apps, which is a problem.

  [Test case]

  To reproduce the issue, you can:

  1. Launch a xenial vm
  2. Install the latest version of uaclient from the stable ppa:
     https://launchpad.net/~ua-client/+archive/ubuntu/stable/
  3. Change the following line on `/etc/ubuntu-advantage/uaclient.conf` from
     
     contract_url: 'https://contracts.canonical.com'

     To:

     contract_url: 'https://contracts.staging.canonical.com'

  4. Attach a staging token to uaclient thorough:

      ua attach YOUR_STAGING_TOKEN

  5. Run /usr/lib/update-notifier/apt-check --human-readable
  6. Verify that no mention to ESM Apps is made and that update-notifier puts all of the ESM packages in the same bucket

  
  To verify that the error is fixed:

  1.Perform all the stages above until step 4
  2 Install the new update-notifier from this ppa:
    https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa
  3. Verify now that ESM Apps is reflected in the message

  [Where problems could occur]

  The changes in this package should only be seen when MOTD is getting a
  new message. If that script fails for some reason, it seems that MOTD
  will only not present the message, which is doesn't seem to be a
  system critical issue.

  [Discussion]

  With ESM Apps going to production soon, we have decided to update the
  messages delivered by update-notifier apt-check to address the package
  count of ESM Apps and the possibility of installing more upgrades if
  the user has ESM Apps disabled.

  We are also updating other parts of the messaging as well. First, we only display ESM Infra status
  on ESM distros. However, we will keep showing the ESM Infra package count on all of them.

  For ESM Apps, we are only performing the alerts (For example, that you
  might have x packages updates if ESM Apps is installed) if the user is
  on a LTS distro.

  Finally, we are also addressing this bug here:
  https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1883315

  Where we were incorrectly counting ESM packages even if the user did
  not have access to those services.

  == Changelog ==

    + data/apt-check
      - Make distinction of ESM Apps and ESM Infra when doing package count
      - Only count ESM packages if the user has access to the service (LP #1883315)
      - Only display ESM Infra alerts if the distro is ESM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1924766/+subscriptions