Project

Profile

Help

Story #5134

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 about 1 year ago. Updated 2 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
Operator
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.)

Associated revisions

Revision 3680e945 View on GitHub
Added by Fabricio Aguiar 3 months ago

Enabling molecule tests

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

History

#1 Updated by fao89 10 months ago

  • Tags CI/CD added

#2 Updated by fao89 3 months ago

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

#3 Updated by pulpbot 3 months ago

  • Status changed from ASSIGNED to POST

#4 Updated by fao89 3 months ago

  • Sprint set to Sprint 76

#5 Updated by fao89 3 months ago

  • Category set to Operator

#6 Updated by rchan 3 months ago

  • Sprint changed from Sprint 76 to Sprint 77

#7 Updated by Anonymous 2 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF