Just upgraded to Foreman 3.14/Katello 4.16 and noticed and I am hosting quite a few docker image repositories. What I can see is that after the upgrade the name of the repo changes when a new image is added.
Name before:
<organization>-<product>-<repo name>
Name changed to:
<organization>/<product>/<repo name>
ex.
dummy-docker_hub-postgres became dummy/docker_hub/postgres
Tried to find anything in the release notes or changes about this but failed to see anything.
Perhaps just a new naming schema to deal with?
Just a little annoying since it started to break some docker installations that started to fail to find the images from the repo.
Thanks for the referens, I suspected as much.
Just trying to find the best way to deal with the change since the repo names only change when a new image is added.
Would have preferred to change all names at the same time and inform users before of the coming change. I guess it will just be a slow moving change that depends on if a new image has been added after the upgrade or not.
If you want to avoid the new container naming scheme, you can change it back to the old default via Lifecycle Environments → Your LCE → Registry Naming Pattern. Old repositories should remain the same, it should just be the new names that follow the default.
I agree though, the release note docs should mention it. We can add it as an upgrade warning retroactively.
