Actions
Story #5134
closedStory #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io
Fix pulp-operator CI w/ Ansible Molecule
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.)
Updated by fao89 over 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee changed from mdepaulo@redhat.com to fao89
Updated by pulpbot over 4 years ago
- Status changed from ASSIGNED to POST
Added by Fabricio Aguiar over 4 years ago
Updated by fao89 over 4 years ago
- Category set to Operator - Moved to Github Issues
Updated by Anonymous over 4 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp-operator|3680e945940bdbac07f773ea65b58966faaa413f.
Updated by daviddavis about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Enabling molecule tests
https://pulp.plan.io/issues/5134 closes #5134