Bug #50502
cephadm pull doesn't get latest image
Status:
Closed
Priority:
Low
Assignee:
-
Category:
cephadm
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
I tried to do a "cephadm pull" this morning on my mini-cluster and it got v16.2.0. Dockerhub has v16.2.1 currently though. Sebastian says that it's using infer_image for command_pull, which it probably shouldn't do. Fix it to get the latest one.
This command worked around the issue:
$ sudo CEPHADM_IMAGE=ceph/ceph:v16.2.1 ./cephadm pull
Related issues
History
#1 Updated by Sebastian Wagner almost 3 years ago
This is a tricky one!
Imagine you set
ceph config set global container_image my-local-trusted-registry/myceph:latest
You expect cephadm pull to pull the configured container, not docker.io/ceph/ceph
#2 Updated by Sebastian Wagner almost 3 years ago
- Related to Bug #46561: cephadm: monitoring services adoption doesn't honor the container image added
#3 Updated by Sebastian Wagner almost 3 years ago
- Related to Feature #47274: cephadm: make the container_image setting available to the cephadm binary independent of any deployed daemons (maybe ceph.conf?) added
#4 Updated by Sebastian Wagner almost 3 years ago
https://github.com/ceph/ceph/pull/39058 caused a subtle behavior change.
Previously, if we used a non-stable tag, it pulled the latest version of that tag
Now we're always pulling a consistent repo_digest.
#5 Updated by Sebastian Wagner almost 3 years ago
- Priority changed from Normal to Low
#6 Updated by Sebastian Wagner about 2 years ago
- Status changed from New to Closed