The 4.6 CI release contains:
cluster-svcat-apiserver-operator git 954e09cf sha256:882e5ce3ca1e1e18ffe18a872a8a969317e6ea07b617e22732b40da598c4d71b
cluster-svcat-controller-manager-operator git b1168c6c sha256:3ff046a021724da5205c4d97e44acc67ee324593fe1901ff14fcde337da2947d (edited)
But there are no equivalent images in ART. If the images have been removed from ART deliberately, they must be removed from CI and the process of building them and putting them into the 4.6 CI integration stream should be removed as well.
If they were incorrectly removed from ART, they should be added.
https://github.com/openshift/ocp-build-data/commit/f664de17827956e409f558186145bfdd5dec154b restored them to 4.5, if they were incorrectly not restored in 4.6, they must be restored there.
From 4.4 to 4.5, the restore was important, because 4.4 had running operators and we wanted 4.5's cleanup jobs deployed to remove those operators on 4.4 -> 4.5 updates.
From 4.5 to 4.6, we can remove the images if we want. Or keep them around. Doesn't really matter, but good to be consistent about it.
In 4.7, once we get CVO object removal , somebody will need to hand the CVO manifests with deletion annotations to get it to clean up the remaining dangling resources . Doesn't matter to me if you keep the svcat images in the release to use for that purpose, or remove them and add the deletion manifests to some other image which remains part of the release.
Removed from CI for master, release-4.6 and release-4.7.
(In reply to W. Trevor King from comment #2)
> From 4.4 to 4.5, the restore was important, because 4.4 had running
> operators and we wanted 4.5's cleanup jobs deployed to remove those
> operators on 4.4 -> 4.5 updates.
> From 4.5 to 4.6, we can remove the images if we want. Or keep them around.
> Doesn't really matter, but good to be consistent about it.
> In 4.7, once we get CVO object removal , somebody will need to hand the
> CVO manifests with deletion annotations to get it to clean up the remaining
> dangling resources . Doesn't matter to me if you keep the svcat images
> in the release to use for that purpose, or remove them and add the deletion
> manifests to some other image which remains part of the release.
> : https://github.com/openshift/enhancements/pull/419
I can see a few options:
1. keep the svcat operator images around for 4.6 and then update for 4.7 with delete annotation
2. remove both svcat operator images for 4.6 then add a single new image with just the manifests with the delete annotation
3. remove both svcat operator images for 4.6 *and* 4.7, add the manifests with delete annotation to some other place; could the CVO carry these 2 manifests?
The implications of the above are:
1. images carried that aren't really being touched for 4.6. They will end up getting tested but IIRC the CVO won't even run the jobs again if a 4.5 cluster already has the jobs. So keeping the images around seems to just eat cycles
2. This option means the svcat images will be gone. Then for 4.7 a new image that holds just the manifests would be introduced. This means setting up new repos and image configs but might be easier to explain why it exists.
3. this option looks the nicest because the svcat operator images will be gone from both releases and no new image would need to be created. Based on the enhancement proposal seems we only need the 2 svcat job manifests with the delete annotation to be available somewhere. Is there anything that we could carry these manifests in?
Strange, still verify, unit, e2e-aws, e2e-aws-upgrade tests are required for the master branch. See PR: https://github.com/openshift/cluster-svcat-apiserver-operator/pull/95 and screenshot: https://user-images.githubusercontent.com/15416633/92692121-4656b700-f376-11ea-9a05-c4815dac2b9f.png Or am I missing soemthing?
DPTP fixed this on the repo. Looking at your PR it only shows being blocked by tide.
Yes, it looks good now. Verify it. BTW, could you help merge the two PRs? Thanks! It did fix the doc link.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.