Testing voms-admin 2.0.3-2

Test 1: Clean db

This test has been succesfully executed and the result was OK. No configuration scripts were available. I did some parts of the configuration manually.

This is the procedure I followed:

• • Install voms-admin 1.2.19 without any VOs
  • Upgrade to voms-admin 2.0.3-2 using the RPM available in the etics repository
  • Apply the changes described in bug #19654
  • make the necessary modifications in the python scripts to reconfigure the new version (due to changes in voms-admin)
  • Start the service

Test 2: Upgraded db

This test has been succesfully executed. No configuration scripts were available. I did some parts of the configuration manually. Some errors were found:

• voms-core didn't start properly
• vomses webui was not working

This is the procedure I followed:

• Install voms-admin 1.2.19 with one VO
• Insert some data in it
• Upgrade to voms-admin 2.0.3-2 using the RPM available in the etics repository
• Apply the changes described in bug #19654 (important! do not forget to restart tomcat)
• run voms-admin-configure upgrade
• Start the service

Testing voms-admin 2.0.3-3

Test 1: Clean db

Not done

Test 2: Upgraded db

This test has been succesfully executed. No configuration scripts were available. I did some parts of the configuration manually. Some errors were found:

• even if I was a member of the VO registered in 1.2.19, VOMS doesn't recognise me and asks me to register when I open the webui
• cli commands to access data inserted in 1.2.19 doesn't return any values
• if I insert new data (like user, role or group) it's ok and it doesn't give any error but I can't list it either

The errors found in the previous version were fixed.

I followed the same procedure as in the latest version.