Bug 1877713 - Block upgrade with non-sha256 oauth token, broken apart from MSTR-997
Summary: Block upgrade with non-sha256 oauth token, broken apart from MSTR-997
Keywords:
Status: CLOSED DUPLICATE of bug 1949941
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oauth-apiserver
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.8.0
Assignee: Standa Laznicka
QA Contact: pmali
URL:
Whiteboard: LifecycleReset
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-10 09:25 UTC by Stefan Schimanski
Modified: 2021-04-16 10:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-16 10:54:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Stefan Schimanski 2020-09-10 09:25:56 UTC 
Description of problem:

In 4.7 we want to be able to assume that there is no non-sha256 oauth token in the system. For that we will add an Upgradable:false condition to 4.6z before we ship 4.7.
Comment 1 Michal Fojtik 2020-10-10 10:20:57 UTC 
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Comment 2 Michal Fojtik 2021-02-26 14:07:13 UTC 
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Comment 3 Michal Fojtik 2021-03-01 08:07:18 UTC 
The LifecycleStale keyword was removed because the needinfo? flag was reset.
The bug assignee was notified.
Comment 5 Standa Laznicka 2021-04-16 10:53:50 UTC 
Closing in favour of #1949941. With the past experience in mind, we decided to allow upgrades, even though the old-format tokens will not work at all. We'll create an informational alert in 4.7 in case there still are some of the old-format tokens.
Comment 6 Standa Laznicka 2021-04-16 10:54:05 UTC 

*** This bug has been marked as a duplicate of bug 1949941 ***
Note You need to log in before you can comment on or make changes to this bug.