Project

General

Profile

Actions

Bug #45162

closed

cephadm: iscsi should use the correct container image

Added by Ricardo Marques about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Category:
cephadm
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I've used "registry/ceph/ceph:latest" to bootstrap my cluster, but when I add an iSCSI gateway I see that "docker.io/ceph/ceph:v15" is used for the gateway:


# ceph orch daemon add iscsi rbd --placement node1

node1:~ # ceph orch ls
NAME         RUNNING  REFRESHED  AGE  PLACEMENT    IMAGE NAME                                                               IMAGE ID      
iscsi.iscsi      1/1  4m ago     26m  node2        docker.io/ceph/ceph:v15                                                  bc83a388465f  
mgr.mgr          1/0  4m ago     -    <unmanaged>  registry/ceph/ceph:latest  f5dd3c91a8e2  
mon.mon          1/0  4m ago     -    <unmanaged>  registry/ceph/ceph:latest  f5dd3c91a8e2

I'd expect that, in this scenario, iSCSI gateway uses "registry/ceph:latest" image too.

Actions #1

Updated by Sebastian Wagner about 4 years ago

  • Description updated (diff)
Actions #2

Updated by Dimitri Savineau about 4 years ago

docker.io/ceph/ceph:v15 is the default cephadm container image so if you're using a different container image via the ceph orch command then you need to modify the container_image global variable.

ceph config set global container_image registry/ceph/ceph:latest
Actions #3

Updated by Michael Fritch about 4 years ago

  • Status changed from New to Fix Under Review
  • Assignee set to Michael Fritch
  • Pull request ID set to 34695
Actions #4

Updated by Sebastian Wagner about 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #5

Updated by Sebastian Wagner almost 4 years ago

  • Status changed from Pending Backport to Resolved
  • Target version changed from v16.0.0 to v15.2.3
Actions

Also available in: Atom PDF