Conflicts with no priority after upgrade

[RicRigon]

We have just upgraded our DEV environment from Tokyo to Vancouver and in the upgrade conflicts list we found that we have more than 2000 entries with no priority.

Has anyone seen this already and knows how we should handle them?

If it can make any difference, we are on an on-prem instance hosted by our ServiceNow provider.

Thanks for any insight!

Ric

[Dr Atul G- LNG]

Hi @RicRigon 

That should be a reason, is it your 1st upgrade after on prem or earlier also did. Better log a now support case.

[RicRigon]

Actually we upgraded several times in the past and it's the first time we had this situation.

Another unexpected behavior is that we did not find any Upgrade Task for the conflicts resolution. None were created for our conflicts.

The upgrade was from Tokyo patch 10 HF2b to Vancouver patch 7 HF 1

[Dr Atul G- LNG · Accepted solution]

Hi @RicRigon 

Better to log a Now support case.

[RicRigon]

Eventually we resolved with the help of ServiceNow support.

The root cause has been found in the finalization script of the upgrade failing due to records in the sys_metadata with empty field "sys_class_name".

we fixed by running the following scripts to adjust the sys_metadata table:

var gr = new GlideRecord("sys_metadata");
gr.addEncodedQuery("sys_class_name=^sys_updated_on!=NULL^sys_update_nameSTARTSWITHbsm_action_^sys_scopeISEMPTY^ORsys_scope=global");
gr.query();
gs.print("Updating " + gr.getRowCount() + "records to sys_class_name = bsm_action");
gr.setValue("sys_class_name", "bsm_action");
gr.updateMultiple();

var gr = new GlideRecord("sys_metadata");
gr.addEncodedQuery("sys_class_name=^sys_updated_on!=NULL^sys_update_nameSTARTSWITHsys_translated_^sys_scopeISEMPTY^ORsys_scope=global");
gr.query();
gs.print("Updating " + gr.getRowCount() + "records to sys_class_name = sys_translated");
gr.setValue("sys_class_name", "sys_translated");
gr.updateMultiple();

var gr = new GlideRecord("sys_metadata");
gr.addEncodedQuery("sys_class_name=^sys_updated_on!=NULL^sys_update_nameSTARTSWITHsys_ui_message^sys_scopeISEMPTY^ORsys_scope=global");
gr.query();
gs.print("Updating " + gr.getRowCount() + "records to sys_class_name = sys_ui_message");
gr.setValue("sys_class_name", "sys_ui_message");
gr.updateMultiple();

var gr = new GlideRecord("sys_metadata");
gr.addEncodedQuery("sys_class_name=^sys_updated_on!=NULL^sys_update_nameSTARTSWITHsys_documentation_^sys_scopeISEMPTY^ORsys_scope=global");
gr.query();
gs.print("Updating " + gr.getRowCount() + "records to sys_class_name = sys_documentation");
gr.setValue("sys_class_name", "sys_documentation");
gr.updateMultiple();

and once the sys_metadata table was fixed, we executed again the upgradeSummary:

var logger = new SNC.UpgradeSummary("5a5f85724b210210d4d9d68dbce0582e"); logger.getAllDescriptions();

This correctly prioritized our conflicts and generated the upgrate tasks