Bug 1888220
| Summary: | [Feature:Marketplace] Marketplace resources with labels provider displayName [Top Level] [Feature:Marketplace] Marketplace resources with labels provider displayName [ocp-21728] create opsrc with labels [Serial] | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Lukasz Szaszkiewicz <lszaszki> | |
| Component: | OLM | Assignee: | Evan Cordell <ecordell> | |
| OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> | |
| Status: | CLOSED DUPLICATE | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | astoycos, bparees, krizza, nhale | |
| Version: | 4.4 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.7.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1894998 (view as bug list) | Environment: |
[Feature:Marketplace] Marketplace resources with labels provider displayName [Top Level] [Feature:Marketplace] Marketplace resources with labels provider displayName [ocp-21728] create opsrc with labels [Serial]
|
|
| Last Closed: | 2020-11-09 18:40:22 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1894998, 1894999, 1895000 | |||
|
Description
Lukasz Szaszkiewicz
2020-10-14 12:46:20 UTC
Still needs to be investigated, marking target release as 4.7.0 for now. > Andrew, I'm going to clone this back to 4.4 now, but it seems like an issue in and of itself that sippy cannot infer existing bugs exist at higher release versions to accommodate the existing github-based backport process (open bugs one release at a time as we backport).
it's not that sippy cannot, it's that sippy deliberately does not. The fact that you have a bug targeted at 4.7 is no guarantee you are aware the issue exists in 4.4 or are intending to fix it there. The only thing that makes that intent clear is you creating the clone and targeting it to that release.
For that reason, sippy only acknowledges bugs that are targeted at the same release that the issue is showing up in.
And I do not see that the 4.4 clone has been created. Adding a needs info in lieu of an "action required" to create the clone, as this is still showing up as a high failure on 4.4 (passing at 56%)
it also looks like this bug is the main reason we have no accepted 4.4-ci payloads in the last 7 days: https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/dashboards/overview#4.5.0-0.nightly so i think this should be considered for raising severity/priority. link above should have been to https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/dashboards/overview#4.4.0-0.ci > The impetus for the comment was that there's a set of manual steps involved when targetRelease > version, like creating bugs on [version, targetRelease] to verify the issue in that range. Since this process should be the same across components, could it be automated? i believe dptp does have tooling for creating BZ clones for you: https://bugs.ci.openshift.org/clones?ID=1888220 (use the "Create clone" button) Closing this as it is a duplicate of 1895019, which at the time was not cloned from the parent 4.5.z bug. *** This bug has been marked as a duplicate of bug 1895019 *** |