Scoped applications missing default update set in the update set picker after Paris upgrade

[Rashid Yakhyaev]

Hi guys!

We just upgraded our on-prem DEV instance from New York to Paris patch 3, and we are experiencing some problems with scoped applications/ default update sets. 

The default update set is there when we are in global scope.

But when we switch to a scoped application, there is no default update set. Below you can see an example of a scoped application where all of the three update sets have the field Default set set to false. Still I can't see the default update set in the update-set-picker. 

The list below (sys_update_set table) shows 4 current update sets in the scoped application. All of these are "Automatically created by the system" as it states in their description field. The default update set is the only update set out of these 4 that has the field Default set set to true. See the example below:

I tried to set the Default update set as my current but the system does not let me, it automatically sets the previous update set as the current. See the images below

Have any of you guys experienced this issue? All help is appreciated!

Edit: Disabling the glide.ui.vcs.collision_avoidance property fixed the problem. 

[Ankur Bawiskar]

@Rashid Yakhyaev 

If this issue came after the upgrade and was working fine previously please raise a HI ticket

Regards
Ankur

[Ankur Bawiskar]

@Rashid Yakhyaev 

Thanks for marking my response as helpful.

Let me know if I have answered your question.

If so, please mark appropriate response as correct & helpful so that this thread can be closed and others can be benefited by this.

Regards
Ankur

[Rashid Yakhyaev · Accepted solution]

Edit: Disabling the glide.ui.vcs.collision_avoidance property fixed the problem. 

[Hristo Ivanov]

Hey Rashid, 

Do you have any guide or a KB that you followed for upgrading an on-prem instance cause I am about to do one and can't find anything?

Thanks in advance!