Project

Profile

Help

Story #5134

closed

Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io

Fix pulp-operator CI w/ Ansible Molecule

Added by mdepaulo@redhat.com over 5 years ago. Updated about 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Operator - Moved to Github Issues
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Sprint 77
Quarter:

Description

Ever since I inherited pulp-operator from ehelms, the CI has not been working.

This is impeding our productivity on developing pulp-operator.

Conversations on the CoreOS slack channel ansible-operator suggest this is a bug in the Ansible Operator framework (the Go Operator is more mature.)

Actions #1

Updated by fao89 about 5 years ago

  • Tags CI/CD added
Actions #2

Updated by fao89 over 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee changed from mdepaulo@redhat.com to fao89
Actions #3

Updated by pulpbot over 4 years ago

  • Status changed from ASSIGNED to POST
Actions #4

Updated by fao89 over 4 years ago

  • Sprint set to Sprint 76

Added by Fabricio Aguiar over 4 years ago

Revision 3680e945 | View on GitHub

Enabling molecule tests

https://pulp.plan.io/issues/5134 closes #5134

Actions #5

Updated by fao89 over 4 years ago

  • Category set to Operator - Moved to Github Issues
Actions #6

Updated by rchan over 4 years ago

  • Sprint changed from Sprint 76 to Sprint 77
Actions #7

Updated by Anonymous over 4 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #8

Updated by daviddavis about 4 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF