DS Sync jobs displays 'Running' on the DS page whereas the Job shows 'Passed' - Refresh issue

[mrajora-1]

Description

DS Sync jobs displays 'Running' on the DS page whereas the Job shows 'Passed'

Expected Behavior

Job Status should be consistent on the DS as well as Jobs page

Actual Behavior

DS Sync jobs displays 'Running' on the DS page whereas the Job shows 'Passed'

Steps to Reproduce

• Create a VC, MC, DA, DS
• Do a Sync of the DA
• DA syncs and then DS syncs
• On DS page, Last Job Status, shows 'Running' for a long time, whereas if you check the Jobs page it shows that the Job has Completed and Passed

Additional Information

WORKAROUND - Go to Jobs page and come back to the DS page. The status will show as 'Passed' now. Looks like a refresh issue

Environment

• OSC Version/Build: Version: 1.0.0-SNAPSHOT (Build:144-g9c773e4, 2017-10-27T07:21:25Z)
• Cloud Provider Info:
• Plugin Info:
• Other:

Status

• Reproduced
• In Progress
• Validated => Verified in Version/Build:

securityBroker-DS-keeps-running.log

[arvindn05]

@mrajora-1 Can you make sure the Job wasnt really running at the time you were seeing "running" on the jobs page?

You can open up another window to the jobs page and have them side by side to see if we are really missing an update.

[mrajora-1]

Yes I made sure the job was running and did have 2 windows side by side. The Jobs window displayed 'Passed' whereas the DS windown still displayed 'Running'. If i click on Jobs page from the same DS window and come back, the DS job gets refreshed and displays the correct status.

The screenshots attached are of 2 different windows side by side.

[mrajora-1]

Also wanted to add - Felt something was wrong as it took unusually long time for the DS to pass. On Openstack the appliance instance shows as 'active'. So I checked the Jobs page and there it showed 'passed'. Then come back on DS page the Jobs status is refreshed. But if I open the Jobs page in a separate window, the DS job shows 'passed', but on the the DS page, it still shows 'running'. Looks like a refresh issue.