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

Not all error messages being returned correctly #340

Open
5 of 8 tasks
SColson82 opened this issue Oct 18, 2024 · 2 comments
Open
5 of 8 tasks

Not all error messages being returned correctly #340

SColson82 opened this issue Oct 18, 2024 · 2 comments
Assignees

Comments

@SColson82
Copy link

SColson82 commented Oct 18, 2024

In the POST, the only error message that I am receiving, regardless of the error issue is:
Failed to create L2VPN. Status code: 400: Request does not have a valid JSON or body is incomplete/incorrect

The following error messages are in the SPEC and don't appear to be supported:

  • 201: L2VPN Service Created
  • 400: Request does not have a valid JSON or body is incomplete/incorrect
  • 410: Can't fulfill the strict QoS requirements
  • 402: Request not compatible (For instance, when a L2VPN P2MP is requested but only L2VPN P2P is supported)
  • 409: L2VPN Service already exists.
    ------------------------------------ To be addressed in next release.
  • 401: Not Authorized
  • 411: Scheduling not possible
  • 422: Attribute not supported by the SDX-LC/OXPO
@congwang09
Copy link
Contributor

This is mostly updated. Will address 401, 411 and 422 in later PR.

@congwang09
Copy link
Contributor

402 code is for "Payment Required", we probably shouldn't use it for Request not compatible case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants