Project

Profile

Help

Story #6584

closed

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 over 4 years ago. Updated about 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

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.)


Sub-issues 4 (0 open4 closed)

Task #6585: Show the status page in pulp_installer CICLOSED - WONTFIXmdepaulo@redhat.com

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

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

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

Actions

Related issues

Blocked by Pulp - Issue #6586: pulpcore-api.service fails to start on containers running systemdCLOSED - CURRENTRELEASEmdepaulo@redhat.comActions

Also available in: Atom PDF