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

edgeStackCreate returns 500 error when user gives wrong input #10169

Closed
2 tasks done
WaysonWei opened this issue Aug 25, 2023 · 0 comments · Fixed by #8873
Closed
2 tasks done

edgeStackCreate returns 500 error when user gives wrong input #10169

WaysonWei opened this issue Aug 25, 2023 · 0 comments · Fixed by #8873
Labels
Milestone

Comments

@WaysonWei
Copy link
Collaborator

Before you start please confirm the following.

Problem Description

edgeStackCreate returns 500 error when user gives wrong input

Expected Behavior

When a user sends an incorrect edge stack payload to the portainer server then it returns with a 400 error

Actual Behavior

When a user sends an incorrect payload to the portainer server, it returns with a 500 error indicating a server error instead of user error

Steps to Reproduce

1 - Enable edge compute in the settings
2 - Send an API request to the portainer server to create an edge stack
3 - The request needs to contain incorrect outputs i.e using a non existent edge group/incorrect deployment type
4 - See that it comes back with a 500 error instead of 400

Portainer logs or screenshots

No response

Portainer version

2.18.4

Portainer Edition

Business Edition (BE/EE) with 5NF / 3NF license

Platform and Version

Docker 24.0.3

OS and Architecture

ARM64

Browser

No response

What command did you use to deploy Portainer?

No response

Additional Information

No response

@WaysonWei WaysonWei linked a pull request Aug 25, 2023 that will close this issue
@WaysonWei WaysonWei added this to the CE-2.19.0 milestone Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant