Openshift : Same pvc might cause problems for different blueprints
Open
backend
bug
- Dominant language
- Python
- Stars
- 8
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The contents of a new course might overwrite the stuff that has been present in the persistent volume before.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the OpenShift persistent-volume and blueprint handling, then trace how a new course is mapped to an existing volume. Done means separate blueprints cannot overwrite one another's persistent-volume contents, with a regression test covering the scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100