| 38 | | SCDB `ant` target `update.vo.config` was buggy in SCDB 2.2 series and [#a2.3.02.3.1:update.vo.configbroken completely broken] in SCDB 2.3 series. This has been fixed in SCDB [milestone:SCDB-2.3.2 2.3.2]. As a consequence of the fixes and some internal changes made to ensure that the account name associated with a given FQAN will never change, this may lead to some account name changes for some VOs. The creation of the new accounts will be properly handled by QWG templates but the NCM component used to manage accounts, `ncm-accounts`, is not able to removed the obsolete acccounts. It may be necessary (it is highly recommended on a CE) to remove these accounts, easily identifed as their name contains `fqan`. A template configuring a script to do it on every node where VO accounts are created is provided as an [source:templates/trunk/site |
| | 38 | SCDB `ant` target `update.vo.config` was buggy in SCDB 2.2 series and [#a2.3.02.3.1:update.vo.configbroken completely broken] in SCDB 2.3 series. This has been fixed in SCDB [milestone:SCDB-2.3.2 2.3.2]. As a consequence of the fixes and some internal changes made to ensure that the account name associated with a given FQAN will never change, this may lead to some account name changes for some VOs. The creation of the new accounts will be properly handled by QWG templates but the NCM component used to manage accounts, `ncm-accounts`, is not able to removed the obsolete acccounts. It may be necessary (it is highly recommended on a CE) to remove these accounts, easily identifed as their name contains `fqan`. A template configuring a script to do it on every node where VO accounts are created is provided as an [source:templates/trunk/sites/example/site/misc/purge_fqan_accounts.tpl example]. To use it, define variable `GLITE_BASE_CONFIG_SITE` to the name of this template. |
