Project

General

Profile

Bug #21463

Frontend upgrade is failing if it is unable to determine the version of the Factory

Added by Marco Mambelli over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
11/29/2018
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

The Frontend is failing an upgrade if it is nunable to connect to the Factory and fetch its version to verify the configuration is compatible w/ it

[root@fermicloud309 llobato]# /usr/sbin/gwms-frontend upgrade
Using default frontend config file: /etc/gwms-frontend/frontend.xml
Traceback (most recent call last):
  File "/sbin/reconfig_frontend", line 183, in <module>
    msg = check_config_frontend.main(xml)
  File "/usr/lib/python2.7/site-packages/glideinwms/creation/lib/check_config_frontend.py", line 87, in main
    f_version = get_factory_version(fc)
  File "/usr/lib/python2.7/site-packages/glideinwms/creation/lib/check_config_frontend.py", line 27, in get_factory_version
    return results[0]['GlideinWMSVersion']
IndexError: list index out of range
Upgrading the frontend                                     [FAILED]

It is not good to have an exception.
A preferred behavior would be to print a warning but still allow a reconfig of the frontend

History

#1 Updated by Marco Mambelli over 1 year ago

  • Status changed from New to Feedback
  • Assignee changed from Marco Mambelli to Lorena Lobato Pardavila

Changes are in v35/21463

#2 Updated by Lorena Lobato Pardavila over 1 year ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Lorena Lobato Pardavila to Marco Mambelli

#3 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_5 to v3_4_2

#4 Updated by Marco Mambelli over 1 year ago

  • Target version changed from v3_4_2 to v3_4_3

#5 Updated by Marco Mambelli about 1 year ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF