Loading...
Loading...
New functionality introduced with Upgrade Center in Paris and new Upgrade Monitor attempts to provide an estimation on duration of the upgrade that is ongoing or scheduled based on upgrade of similar instances. By default platform will try to connect to instances used as active update set sources and retrieve information on similar upgrades duration. It has been observed that upgrade monitor page and user session may become unresponsive during this process if it attempts to connect to an unexpected URL. Observed localhost entries (URLs are anonymized): 2020-12-08 09:37:01 (798) http-36 New transaction B473E4D4DBC120104848622DCA9619CF #4873 /$upgrade_monitor.do 2020-12-08 09:37:01 (837) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 #4873 /$upgrade_monitor.do Parameters ------------------------- 2020-12-08 09:37:01 (838) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 *** Start #4873 /$upgrade_monitor.do, user: CLL05_admin 2020-12-08 09:37:01 (938) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 [0:00:00.096] getRealForm 2020-12-08 09:45:04 (717) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 OUTBOUND_HTTP: protocol=HTTP/1.1 response_status=-1 response_time=480561 request_length=367 response_length=-1 app_scope=global session_id=B473E4D4DBC120104848622DCA9619CF transaction_name="#4873 /$upgrade_monitor.do" transaction_id=5e736050dbc120104848622dca96198d user_name=admin= source_table=plugin://com.glide.upgrade_center/ui.jforms/$upgrade_monitor.xml source_record=3 system_id=app123456.sjc000.service-now.com:instance000 method=POST log_level=Basic scheme=http hostname=10.10.10.10 path=/sys_upgrade_history.do url=http://10.10.10.10:3000/sys_upgrade_history.do response_body="[ERROR CODE: -1 ] The server 10.10.10.10 failed to respond" 2020-12-08 09:45:04 (727) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 WARNING *** WARNING *** No response from host 2020-12-08 09:45:04 (727) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 SEVERE *** ERROR *** getRecords failed (No response from host) 2020-12-08 09:45:05 (467) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 OUTBOUND_HTTP: protocol=HTTP/1.1 response_status=401 response_time=716 request_length=367 response_length=0 app_scope=global session_id=B473E4D4DBC120104848622DCA9619CF transaction_name="#4873 /$upgrade_monitor.do" transaction_id=5e736050dbc120104848622dca96198d user_name=admin= source_table=plugin://com.glide.upgrade_center/ui.jforms/$upgrade_monitor.xml source_record=3 system_id=app123456.sjc000.service-now.com:instance000 method=POST log_level=Basic scheme=https hostname=instance.service-now.com path=/sys_upgrade_history.do url=https://instance.service-now.com/sys_upgrade_history.do 2020-12-08 09:45:05 (469) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 WARNING *** WARNING *** Method failed: (https://instance.service-now.com/sys_upgrade_history.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 401 Unauthorized with code: 401 2020-12-08 09:45:05 (471) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 SEVERE *** ERROR *** getRecords failed (Method failed: (https://instance.service-now.com/sys_upgrade_history.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 401 Unauthorized with code: 401) 2020-12-08 09:45:06 (017) Default-thread-5 B473E4D4DBC120104848622DCA9619CF txid=5e736050dbc1 OUTBOUND_HTTP: protocol=HTTP/1.1 response_status=200 response_time=539 request_length=367 response_length=222 app_scope=global session_id=B473E4D4DBC120104848622DCA9619CF transaction_name="#4873 /$upgrade_monitor.do" transaction_id=5e736050dbc120104848622dca96198d user_name=admin= source_table=plugin://com.glide.upgrade_center/ui.jforms/$upgrade_monitor.xml source_record=3 system_id=app123456.sjc000.service-now.com:instance000 method=POST log_level=Basic scheme=https hostname=instance2.service-now.com path=/sys_upgrade_history.do url=https://instance2.service-now.com/sys_upgrade_history.do Steps to Reproduce 1) Provision instance pre Paris 2). Define an updates set source that is external - non cloud hosted instance. 3) Upgrade instance 4) Access instance during upgrade as admin or user having admin role. You will be automatically redirected to upgrade monitor page. 5) Notice that user session becomes unresponsive. Expected behavior: Instance will be usable and session will not become unresponsive.
When the admin session is stuck on /$upgrade_monitor.do a. Cancel your transaction by manually loading the following URL https://<InstanceName>/cancel_my_transaction.do b. From there, manually navigating to below URL allows to browse the instance. https://<InstanceName>/nav_to.do?uri=/home.do One of the below workarounds can be applied to avoid this issue: 1. (Temporarily) Disable the update set source record by setting the active flag to false. https://<InstanceName>/sys_update_set_source_list.do 2. Specify a valid source based on its sys_id via the property - glide.upgrade.preview.duration.instance.id This is how you can find an instance's sys_id: - navigate to the sys_update_set_source table - open a record - right click on header -> Show XML - view the "instance_id" value
PRB1458912
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.