Unable to edit Openshift recipe machine in dashboard
See original GitHub issueDescription
Attempting to edit an OpenShift recipe-based machine fails, wiping out the recipe on edit.
Reproduction Steps
- Create Che 7 workspace
- Go to config tab, change recipe type to “Openshift”
- Go to machines tab, attempt to edit recipe (change image or memory, etc)
- Upon save: “Failed: Environment should contain at least 1 pod or deployment”
- This is because machine has disappeared from the workspace and so it cannot be saved.
On changing recipe in the edit machine dialog, console errors
TypeError: Recipe should contain at least one OpenShift object
EnvironmentManager: cannot add machine.
TypeError: Recipe should contain at least one OpenShift object
EnvironmentManager: cannot parse recipe.
TypeError: Recipe should contain at least one OpenShift object
EnvironmentManager: cannot parse recipe.
are shown.
OS and version:
Present in 7.0.0-beta-3.0
See also: https://github.com/redhat-developer/rh-che/issues/1381
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Unable to edit subscriptions in Red Hat OpenShift Cluster ...
Issue. It is not possible to edit the Subscription settings for the cluster in Red Hat OpenShift Cluster Manager to change from the...
Read more >Troubleshooting Operator issues - OpenShift Documentation
Disabling the Machine Config Operator from automatically rebooting by using the console. To avoid unwanted disruptions from changes made by the ...
Read more >Troubleshooting GitLab Runner
Docker-machine error: Unable to query docker version: Cannot connect to the docker ... In the GitLab Recipes repository there are web-server configuration ...
Read more >OpenShift Cookbook
Welcome to the OpenShift Cookbook, where you can learn more about how to use OpenShift, one simple recipe at a time.
Read more >Deploy CockroachDB on Red Hat OpenShift
Note: If you cannot access the SQL client, this may be related to your --certs-dir or --host flags. Shell into the client pod...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ibuziuk we are replacing legacy stacks.json with their recipes with devfiles (Dashboard should be adapted as a consequence) hence this should be fixed in the process. cc @ashumilova @evidolob
Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
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.