Unable to start umssed without vishnuMachineID in the configuration file

[dloureiro]

I've deployed the 3.1.0 release on a ubuntu 12.10 box and when trying to launch the umssed I'm facing the following problem :

vagrant@vagrant:~$ /opt/vishnu/sbin/umssed /home/vagrant/ums.cfg 
/opt/vishnu/sbin/umssed : FAIL 12: Undefined configuration parameter [vishnuMachineId]

The vishnuMachineID is currently not defined in the umssed configuration file :

vagrant@vagrant:~$ tail -n 20 ums.cfg 
# vishnuMachineId (M<FMS,IMS,TMS>|O<UMS>): Optional for UMS and mandatory for FMS,
# IMS and TMS, this key corresponds to the identifier of the machine in VISHNU
# environment.
# When set, it MUST correspond to valid machine identifier.
#
#vishnuMachineId=machine_1

# timeout (M<Dispatcher>|O<FMS,IMS,TMS,UMS,Client>): In seconds, this defines the
# duration afer which a request is considered as expired.
#
timeout=120

# urlSupervisor (M<FMS,IMS,TMS,UMS>): Specifies the address of Supervisord
#
urlSupervisor=http://127.0.0.1:9001

# debugLevel (O): specifies the debug level. The higher the more debug information
# you'll get. Default is 0.
#
# debugLevel=0

As you can see, the vishnuMachineId value is commented. But the commentary (taken from the sample configuration file) says that this value is optional ...

Any hint ?

[keoo]

The value is not used by the code but the way we use the mandatory check. So for now just uncomment it in the config file, it will not be used. Then we can upgrade the way we check this parameter

[keoo]

Fixed in PR 388