Viya 4 Scheduling Tab under Jobs and Flows of Environment Manager does not display the built in Jobs

[alko13]

Good Day!

,

We have a fresh install of Viya 4. Installation seems completed sucessfully, all pods are in Running/Completed State. However while navigating EVM, Have noticed that the Scheduling tab under Jobs and Flows are displaying 0 jobs. Have compared this into a lab environment that is fresh installed as well and the jobs can be displayed from there. May I know what items to check to solve this? I checked the logs of the sas-scheduler pod and seems no error/abnormality there.

Actual Environment (No jobs being displayed):

Lab Environment (With Jobs)

Please advise,

Thanks in advance

[gwootton]

Look at the network trace in your browser's developer tools to see if any calls are failing with 401/403 errors, and make sure there are no rules that have been added or modified limiting your access to those endpoints.

That tab is populated by calls to /jobFlowScheduling/schedulers, /jobExecution/jobRequests, /scheduler/jobs and /jobFlowScheduling/flows.

Usage Note 60268: Using the web browser developer tools to investigate issues in SAS® Web Applications
https://support.sas.com/kb/60/268.html

[alko13]

Hi @gwootton 

We see these 404 messages in network trace of chrome. Anything needs to be checked further?

[gwootton]

The network tab rather than the console tab will show all the requests and responses more clearly. What you've shared shows you are getting a 404 when looking for one specific job definition: d08d41da-2f03-4129-9043-196eba8b92bb. I'm not sure what that is related to, but I would not expect it to prevent all the jobs from not being displayed.

[alko13]

@gwootton for the network tab these 404 appear for a specific job.

Accessing the job url also leads to 404 error 

I intend to  delete the problematic job using sas-viya cli. however, even the cli is unable to detect this job

Got idea how can can delete this job outputting 404 error? Seems to be a corrupted job

Thanks!

[gwootton]

I suspect the issue here is you have some job of id X that is referencing the (non-existent) job definition of id Y. We need to delete the job X but we don't have that ID yet, only the ID Y that doesn't exist.

So I think you'd want to call for example the URL:
/jobExecution/jobs?filter=contains(jobDefinitionUri,'d08d41da-2f03-4129-9043-196eba8b92bb')

Which should return any jobs that reference the already deleted job definition's ID. You could then use that ID to delete through the sas-viya CLI.

[alko13]

Hi @gwootton 

Managed to delete the problematic jobs using cli.

Now no more error 404 in Network Tab

But still scheduled jobs does not show.

Are there other things that can be explored on?

Thanks!

[gwootton]

Are you able to create a new job and have it show up in the list?

[alko13]

@gwootton 

Creation of job is okay, However also not showing on the list.

After creating Job Flow:

[gwootton]

I would suspect then the issue is with rules applied to the endpoints I mentioned. Have the default rules been modified or added to for:
/jobFlowScheduling/schedulers, /jobExecution/jobRequests, /scheduler/jobs and /jobFlowScheduling/flows