Bug 2097618 - PipelineRun creation from the GUI for a Pipeline with 2 workspaces hardcode the PVC storageclass
Summary: PipelineRun creation from the GUI for a Pipeline with 2 workspaces hardcode t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.9.z
Assignee: Mohammed Saud
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On: 2092140
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-16 07:27 UTC by OpenShift BugZilla Robot
Modified: 2022-07-05 22:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Pipeline start form was always using a hardcoded value (gp2) as the default storageclass. Consequence: The gp2 storageclass was always used, even if it did not exist on the cluster. Fix: Use the default specified storageclass name instead of a hardcoded value. Result: Starting a pipeline with VolumeClaimTemplate uses the correct default storageclass.
Clone Of:
Environment:
Last Closed: 2022-07-05 22:04:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11716 0 None open [release-4.9] Bug 2097618: Avoid using 'gp2' hardcoded storage class 2022-06-20 07:21:52 UTC
Red Hat Product Errata RHBA-2022:5434 0 None None None 2022-07-05 22:04:31 UTC

Comment 5 spathak@redhat.com 2022-07-01 13:00:45 UTC
Verified on build version: 4.9.41
Browser version: Chrome 101

Comment 7 errata-xmlrpc 2022-07-05 22:04:15 UTC
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.9.41 bug fix 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/RHBA-2022:5434


Note You need to log in before you can comment on or make changes to this bug.