On 25.02.22 17:24, Adam King wrote:
I don't know for sure, but it's possibly a result of the centos 8 EOL
stuff from a few weeks ago (they removed seom repos and a lot of our
build stuff broke). I think we had to update some of our container
images to deal with that.
IMHO container image
I don't know for sure, but it's possibly a result of the centos 8 EOL stuff
from a few weeks ago (they removed seom repos and a lot of our build stuff
broke). I think we had to update some of our container images to deal with
that.
- Adam King
On Fri, Feb 25, 2022 at 10:55 AM Robert Sander
On 25.02.22 16:43, Adam King wrote:
ceph config set mgr mgr/cephadm/use_repo_digest false
Nice to know.
The other question is: Why is the digest changing for a released Ceph
image with a specific version tag?
What changes are made to the container image that are not in the release
notes?
Thank you very much :)
ceph config set global container_image was the solution to
get the new node to deploy fully,
and with ceph config set mgr mgr/cephadm/use_repo_digest true/false it
will hopefully never repeat
now lets hope the recovery is without further trouble
Greetings,
Kai
On
For the last question, cephadm has a config option for whether or not it
tries to convert image tags to repo digest (ceph config set mgr
mgr/cephadm/use_repo_digest true/false). I'm not sure if setting it to
false helps if the tag has already been converted though.
In terms of getting the cluster
