Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Error screen on job FAIL status

Description

Overview:
In some scenarios , the FAIL job status is not populated with either user details (may be because it failed to fetch user details, or some other issue), the job execution record will look as below:

In such scenarios, the screen errors out with the attached error Message, This scenario needs to be handled on UI

Steps to Reproduce:

  • Observed when mod-data-export was running in HA in one of the environments

Expected Results:
Job is shown on UI with FAIL status

Actual Results: Error screen

Interested parties: Everyone

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Magda Zacharska June 18, 2020 at 9:09 PM

Setting the release to Q2 2020 so it can be tested in bugfest environment.

Yevhenii Maltsev June 17, 2020 at 12:06 PM

If UI covers all fields, it means that the backend can send an empty object and UI should display an empty line. I think, this behavior is not applicable for this UI and we should display the needed information. So I covered by the additional check only the user information.

Kruthi Vuppala June 12, 2020 at 1:46 PM
Edited

How can it be reproduced on the environment? It seems, it's needed for the verification.

To reproduce data-export needs to be running 2 copies of the backend service, I doubt if we can do it in the reference environment., If this story makes it to the release. I can get it tested in bugfest.

user information should be handled in scope of this story. Are there any other fields that should be checked?

I think all the fields displayed on the UI should have a check

Yevhenii Maltsev June 11, 2020 at 3:15 PM

Please, could you clarify some information:

  • How can it be reproduced on the environment? It seems, it's needed for the verification.

  • As far as I understand, user information should be handled in scope of this story. Are there any other fields that should be checked?

Kruthi Vuppala May 28, 2020 at 12:48 PM

HA is high availability. However, the backend doesn't support this yet

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Concorde

Fix versions

Release

Q2 2020

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 21, 2020 at 5:23 PM
Updated June 25, 2021 at 4:28 PM
Resolved June 18, 2020 at 9:09 PM
TestRail: Cases
TestRail: Runs