Job definition for reset-admin-password doesn't propagate image pull policy
Maintainers usually reply within 4 days
Nobody has claimed this yet.
- #1631 by @zombiecalypse — closed without merging
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- infrastructure
Research direction
Start with the proposed fix commit 2131e13e146d77a2425a120860be8251fed0bacf, then inspect the reset-admin-password job definition and how spec.image_pull_policy is propagated. Done means the job uses the configured policy, including Never, and the reproduction no longer fails with an image-pull error.
Written by the indexing model from the issue text.
Description
Version: Found in pulp-operator version: 2.0.0-20260317, though likely other versions are affected as well.
Describe the bug When setting a non-default spec.image_pull_policy, such as Never, the job reset-admin-password will still use Always.
To Reproduce
Basic:
- Run pulp operator, e.g. on minikube or just as a local service
- Send a CRD that uses
spec.image_pull_policy=Never(example - Generated job
reset-admin-passworduses wrong image pull policy
How a user might encounter it:
- Run pulp operator on minikube
- Create custom pulp image (simulated here by simple copy of default tag):
docker pull pulp/pulp-minimal && \
docker tag pulp/pulp-minimal:stable foo/bar:baz && \
minikube image load foo/bar:baz
- Apply CRD with
image_pull_policy: Never: https://gist.github.com/zombiecalypse/3d16a7d01ae7dd8a95b29ea9d2091845 - job reset-admin-password fails to start with image pull error
Expected behavior Job uses the same image_pull_policy as the rest of the deployment.
Additional context Proposed fix: https://github.com/pulp/pulp-operator/commit/2131e13e146d77a2425a120860be8251fed0bacf
- Dominant language
- Go
- Stars
- 88
- Forks
- 68
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pulp/pulp-operator
-
settings.py flaps between reconciles: needsMigrationSetting depends on map iteration orderPossibly taken @fontaineajulien claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pulp/pulp-operator#1691 ·
Maintainers usually reply within 4 days
-
Documentation for metadata signing (APT/RPM) removed but still relevantMay be free again A pull request for this issue was closed without being merged. OpenIssue Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pulp/pulp-operator#1644 ·
Maintainers usually reply within 4 days
-
Issue Triage-Needed
Difficulty 3/5 1-2 days Newbie friendliness 74/100
pulp/pulp-operator#1685 ·
Maintainers usually reply within 4 days
-
Feature Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 35/100
pulp/pulp-operator#1682 ·
Maintainers usually reply within 4 days
-
Issue Triage-Needed
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pulp/pulp-operator#1647 ·
Maintainers usually reply within 4 days
All issues in pulp/pulp-operator
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
vanderheijden86/b9s#20 ·
-
go-battery needs an ndsctl on PATH: TestPurchaseSessionGuardHoldsThroughTheOutcomeUnknownWindow fails on bare hosts (passes with stub)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenTollGate/tollgate-module-basic-go#726 ·
Maintainers usually reply within 1 day
-
ux waiting for feedback
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
evcc-io/evcc#34527 · 1 comment ·
Maintainers usually reply within 1 day
-
phase:v3 type:harness
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day