Majic Projects
Majic Ansible Roles
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Majic Ansible Roles / Closed Bug report MAR-184 Python requirements update checks produce unnecessary warning e-mails
Go to the next issue (open or closed)
Go to the next open issue
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Bug report
  • Category
    General
  • Targetted for
    7.0.0
  • Status
    Closed
  • Progress
  • Priority
    Must fix before next release
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (1)
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    4 hours
  • Time spent
    2 hours
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
  • Reproducability
    Always
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Show / hide more details »
Description

When using the mechanism for checking for available package updates for Python requirements files, the relevant script will send out notifications to system administrator that contain no package update notifications, and instead contain a number of warnings about deprecations in the pip-tools package.

This produces excess mail that will also have tendency to reduce ability to catch actionable items.

The following should be done:

  • Update the common role.
    • Use the --resolver backtracking option when invoking the pip-compile for Python requirements update checks.
  • Update role reference documentation.
  • Update release notes.
Steps to reproduce this issue

Reproduction steps:

  1. Set-up a server using the common role.

  2. Wait for server to perform package updates checks (usually one day).

  3. Verify that mail notification has been sent with available package updates for requirements-checking virtual environment itself.

  4. Update the pip_check_requirements and pip_check_requirements_py3 common role parameters with reported updates and deploy changes to server.

  5. Wait for server to perform package updates checks (usually one day).

  6. Verify that no mail notification has been sent with available package updates for requirements-checking virtual environment itself.

Expected results:

  1. Mail with package update notifications is sent in step (3).

  2. Mail with package update notifications is not sent in step (6).

Actual results:

  1. Mail with package update notifications is sent in step (3).

  2. Mail with package update notifications is sent in step (6). The mail contains only warnings about deprecation happening in the pip-tools package.

Todos (0 / 0)
Options
There are no comments