Bug 2107513
| Summary: | [SSO] 1.0.1 csv is pulling in secondary-scheduler-operator-container-v1.1-5 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | RamaKasturi <knarra> |
| Component: | kube-scheduler | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED ERRATA | QA Contact: | RamaKasturi <knarra> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.10 | CC: | jchaloup, mfojtik |
| Target Milestone: | --- | ||
| Target Release: | 4.12.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-01-17 19:52:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
RamaKasturi
2022-07-15 10:26:40 UTC
Setting blocker ? as with the current state 1.0.1 cannot be shipped !! Not a blocker for 4.11 We release async. Also, osso 1.0.0 release is expected to be functioning properly in 4.11. @jan i remember we discussed that we cannot install 1.0.0 release on 4.11, is that not true ? Am i missing something ? 1.0.0 can be installed on every OCP release as there's no OCP version restriction enforced. The maximum OCP version has been annotated in 1.0.1 [1]. I recall we had a discussion in which I incorrectly stated 1.0.1 can be installed only in 4.10. 4.11 is the only OCP version where we can install both 1.0.1 and 1.1.0. Also the OCP version in which we expect the osso to be automatically and transparently updated from 1.0.1 to 1.1.0. [1] https://github.com/openshift/secondary-scheduler-operator/blob/release-4.10/manifests/cluster-secondary-scheduler-operator.clusterserviceversion.yaml#L38 @jan does that mean that user installing 1.0.0 on 4.11 will be able to go from 1.0.1 to 1.1.0 but user installing 1.0.0 on ocp 4.10 will be able to go only till 1.0.1 until he upgrades the system to 4.11. Am i correct ? > user installing 1.0.0 on 4.11 will be able to go from 1.0.1 to 1.1.0 Correct > user installing 1.0.0 on ocp 4.10 will be able to go only till 1.0.1 until he upgrades the system to 4.11. 1.0.0 is not restricted in 4.10 so the same as above applies. User can either upgrade 1.0.0 -> 1.0.1, 1.0.0 -> 1.1.0 or also 1.0.0 -> 1.0.1 -> 1.1.0 Moving this bug to verified state as i see that 1.0.1 does not pull in 1.1.0 operator and everything works fine.
[knarra@knarra verification-tests]$ oc get csv -n openshift-secondary-scheduler-operator
NAME DISPLAY VERSION REPLACES PHASE
elasticsearch-operator.5.4.3 OpenShift Elasticsearch Operator 5.4.3 Succeeded
secondaryscheduleroperator.v1.0.1 Secondary Scheduler Operator for Red Hat OpenShift 1.0.1 secondaryscheduleroperator.v1.0.0 Succeeded
Do not see securitycontext added as well
[knarra@knarra verification-tests]$ oc get deployment secondary-scheduler -o yaml -n openshift-secondary-scheduler-operator| grep "securityContext"
securityContext: {}
securityContext: {}
Normal Pulling 32s kubelet Pulling image "registry.redhat.io/openshift-secondary-scheduler-operator/secondary-scheduler-operator-rhel8@sha256:dc1fbcd07505646a2ed0bb900def7536c23d7af7ab9e02fce469a5372ff2cde5"
Based on the above moving bug to verified state.
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 (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:7399 |