Project

Profile

Help

Story #6584

Story #5762: [Epic] CI Improvements

As a pulp_installer CI user, I see verification that pulp functions and was installed correctly at the end

Added by mdepaulo@redhat.com 6 months ago. Updated 2 months ago.

Status:
NEW
Priority:
Normal
Category:
Installer
Sprint/Milestone:
-
Start date:
Due date:
% Done:

50%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

Currently, we only verify that no module tasks fail, and that most are idempotent.

We should be running some tests like:

  1. Checking the status page.
  2. Confirming that the correct versions are installed; they were not overwritten.
  3. Run some functional tests.
  4. Verifying the firewall is actually open.

Some of these may belong the in the installer itself so that users will have them run, the rest belong in ansible molecule's verify.yml (assuming we are using ansible as the molecule verifier. testinfra is another.)


Subtasks

Task #6585: Show the status page in pulp_installer CINEWmdepaulo@redhat.com

Actions
Task #6588: Verify our systemd unit files in pulp_installer CINEWmdepaulo@redhat.com

Actions
Story #7259: As a user, the pulp_installer will verify that the Pulp Services are up & listeningMODIFIEDfao89

Actions
Story #7272: As a pulp_installer CI user, some verification tests are run at the endMODIFIEDmdepaulo@redhat.com

Actions

Related issues

Blocked by Pulp - Issue #6586: pulpcore-api.service fails to start on containers running systemdMODIFIED<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by bmbouter 5 months ago

  • Category set to Installer
  • Tags deleted (Pulp 3 installer)

#2 Updated by mdepaulo@redhat.com 3 months ago

  • Blocked by Issue #6586: pulpcore-api.service fails to start on containers running systemd added

Please register to edit this issue

Also available in: Atom PDF