Linux server pattern fails step 3.2.83 - 'Filter route interface'

[Mark Todorov]

Dear Community,

I am observing the following error on step 3.2.83 of Linux server pattern (Filter router interface) for some of the targeted Linux devices:

Test failed: JAVASCRIPT_CODE_FAILURE: TypeError: Cannot convert null to an object. (ad_hoc:EvalClosure-Filter route interfaces-705444873; line 11)

While checking the previous step which is 'Set dest_ip_network for each route' I am observing the following:

There is a 3rd result at the bottom without any value in it. This is not observed with servers that we are already updating successfully. 

Any suggestion from where or why I am receiving the empty value and how to address the issue further?

Thanks in advance! 

Mark

[SiD2]

Hi @Mark Todorov 

Yes, it looks like some data is missing, but first, you need to ensure that we miss getting the data from the server itself or, if missed in b/w the pattern steps, and accordingly, you need to take action.

So first, I suggest you back-trace the steps and see from where the data is coming to this table by doing pattern debugging, and then you should get some idea.

[Canjura]

Hi Mark, 

Did you find a solution for this, I'm having the same issue.

Did you recently update to Utah? I'm wondering if that's a release-related issue. 

It seems to work fine in my old "Tokyo" instance.

Thanks.

[Mark Todorov]

Hi Canjura,

I am not sure that the issue is connected with release. Some servers were not experiencing it, and some were. 

This will definitely be addressed to ServiceNow support. 

Here is how I updated that step and the issue was resolved for all the servers.  

I've addressed the empty route interface values to the relevant Linux teams, it may be to configuration from their end, but for now I don't know more. 

Hope this helps.

Mark

[Canjura]

Hi Mark, 

I was comparing the Linux Server pattern between Tokyo and Utah, and yes, it has been updated.

3.2.64. Failover: Get the routes and gateway for IPv6

• This step doesn’t exist in Tokyo.
• Sometimes this step generates the “$route_table_ss_v6” as an empty table

3.2.65. Merge IPv4 and IPv6 route_table_ss

• This step then merges $route_table_ss with $route_table_ss_v6 into $route_table_ss
• The resulting $route_table_ss includes the previous values PLUS the empty row

I guess is either fix that step that creates the empty table or applying a filter like the one you’re using will work.

Thanks for your reply.