Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devfile schema validation failed due to unexpected type for the persistVolumes field #20153

Closed
RomanNikitenko opened this issue Jul 20, 2021 · 2 comments
Labels
area/doc Issues related to documentation kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@RomanNikitenko
Copy link
Member

RomanNikitenko commented Jul 20, 2021

Describe the bug

It's impossible to start a workspace when persistVolumes value is boolean type.
The error is:

Failed to resolve a devfile. Error occurred during creation a workspace from devfile located at `https://raw.githubusercontent.com/chepullreq4/pr-check-files/master/che-theia/pr-1049/simple/che-theia-nodejs-devfile.yaml`. Cause: Devfile schema validation failed. Error: (/attributes/persistVolumes):The value must be of string type, but actual type is boolean.

According to the doc it should work well for the boolean type

Che version

nightly

Steps to reproduce

  1. Try to start a workspace from the devfile https://raw.githubusercontent.com/chepullreq4/pr-check-files/master/che-theia/pr-1049/simple/che-theia-nodejs-devfile.yaml

Screenshots

try_it_buttons_errors

Environment

Dev Sandbox (workspaces.openshift.com)

@RomanNikitenko RomanNikitenko added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 20, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jul 20, 2021
@sparkoo sparkoo added severity/P2 Has a minor but important impact to the usage or development of the system. area/doc Issues related to documentation and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 20, 2021
@che-bot
Copy link
Contributor

che-bot commented Jan 16, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 16, 2022
@che-bot che-bot closed this as completed Jan 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants