Project

General

Profile

Feature #46182

cephadm should use the same image reference across the cluster

Added by Ken Dreyer 5 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
octopus
Reviewed:
Affected Versions:
Pull request ID:

Description

The documentation has this warning (from https://docs.ceph.com/docs/octopus/install/containers/#containers):

Important Using the :latest tag is discouraged. If you use the :latest tag, there is no guarantee that the same image will be on each of your hosts. Under these conditions, upgrades might not work properly. Remember that :latest is a relative tag, and a moving target.
Instead of the :latest tag, use explicit tags or image IDs. For example:

podman pull ceph/ceph:v15.2.0

This is an administrative burden on the user to always look up and bump the number, and it's an additional human action that can go wrong.

ceph-ansible solved this by resolving the image's floating tag to a sha256 ref one time, and then deploying that same ref to all nodes. cephadm should be able to do something similar.

History

#1 Updated by Sebastian Wagner 4 months ago

  • Project changed from Ceph to Orchestrator

#2 Updated by Sebastian Wagner 4 months ago

  • Tracker changed from Bug to Feature
  • Priority changed from Normal to High

I agree. Users won't get it.

#4 Updated by Sebastian Wagner 4 months ago

  • Status changed from New to In Progress
  • Assignee set to Sebastian Wagner

#5 Updated by Sebastian Wagner 4 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 36432

#6 Updated by Nathan Cutler about 2 months ago

  • Status changed from Fix Under Review to Pending Backport

#7 Updated by Nathan Cutler about 1 month ago

  • Status changed from Pending Backport to Resolved

backported to octopus via https://github.com/ceph/ceph/pull/37436

#8 Updated by Nathan Cutler about 1 month ago

  • Backport set to octopus

Also available in: Atom PDF