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

[Test failure] <TC_AUTHOR_69>: <LTI Consumer isn't working and giving 502 bad gateway error> #340

Closed
fayyazahmed66 opened this issue Feb 19, 2024 · 4 comments
Labels
needs triage release testing Affects the upcoming release (attention needed)
Milestone

Comments

@fayyazahmed66
Copy link

Release

quince

Expected behavior

User should be able to update LTI consumer urls and it should save without giving errors.

Actual behavior

Getting 502 bad gateway.

Steps to reproduce

  1. Go to studio
  2. add LTI consumer and try to save it after giving the correct urls
  3. click on save button

Additional information

link: https://studio.sandbox.openedx.edly.io/container/block-v1:edX+DemoX+Demo_Course+type@vertical+block@b01aa2c53b064c579812ba446299d812

Image :
Uploading Screenshot 2024-02-19 at 12.27.52 PM.png…

@mariajgrimaldi
Copy link
Member

Hello there! Thanks for the report. Have you tried this in a different environment? Or locally?

@mariajgrimaldi mariajgrimaldi modified the milestones: Quince.3, Redwood.1 Apr 26, 2024
@mariajgrimaldi
Copy link
Member

@DonatoBD will try to reproduce this issue in the Sandbox. Please, let us know what you find!

@mariajgrimaldi mariajgrimaldi added the release testing Affects the upcoming release (attention needed) label May 9, 2024
@DonatoBD
Copy link

DonatoBD commented May 9, 2024

Hi @fayyazahmed66, I did a test last week in https://studio.sandbox.openedx.edly.io/ using this page to test the LTI component and as you can see I had no problems

Screenshot from 2024-05-02 20-35-22

Screenshot from 2024-05-02 20-35-10

Screenshot from 2024-05-02 20-34-58

Screenshot from 2024-05-02 20-34-48

I also tested it locally and could not replicate what you reported. Is there any special condition needed to replicate it or it was already solved?

@mariajgrimaldi
Copy link
Member

I believe this was environment-related, so I'll be closing this now. If any other issue arises during Redwood testing, we'll take care of it separately. Thank you both!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage release testing Affects the upcoming release (attention needed)
Projects
Development

No branches or pull requests

3 participants