IN2P3-Forge: Issueshttps://forge.in2p3.fr/https://forge.in2p3.fr/favicon.ico?16780521162023-06-01T15:11:05ZIN2P3-Forge
Redmine PyROS - Task #57981 (In progress): **** (SF15) Agents in TEST mode (test scenarios)https://forge.in2p3.fr/issues/579812023-06-01T15:11:05ZPallier EtiennePyROS - Task #57955 (In progress): *** (SF16) MODULE - django module - organization, files, class...https://forge.in2p3.fr/issues/579552023-05-31T11:42:32ZPallier EtiennePyROS - Task #57954 (In progress): *** (SF16) MODULE (API) - django module - organization, files,...https://forge.in2p3.fr/issues/579542023-05-31T11:41:22ZPallier EtiennePyROS - Task #57943 (In progress): *** (SF05) MODULE - django module - organization, files, class...https://forge.in2p3.fr/issues/579432023-05-31T10:52:32ZPallier EtiennePyROS - Task #57940 (In progress): *** (SF03) MODULE - django module - organization, files, class...https://forge.in2p3.fr/issues/579402023-05-31T10:48:14ZPallier EtiennePyROS - Feature #57927 (In progress): *** (SF15) TESTS to validate feature & requirementshttps://forge.in2p3.fr/issues/579272023-05-31T00:18:04ZPallier EtiennePyROS - Task #57914 (In progress): **** (SF09) GET/SET device status (and save it)https://forge.in2p3.fr/issues/579142023-05-30T23:37:40ZPallier EtiennePyROS - Task #57852 (In progress): **** (SF05) OTHER actionshttps://forge.in2p3.fr/issues/578522023-05-30T13:01:43ZPallier EtiennePyROS - Task #57847 (In progress): *** (SF04) AGENT(S)https://forge.in2p3.fr/issues/578472023-05-30T12:24:43ZPallier EtiennePyROS - Feature #57841 (In progress): *** (SF16) Integration of other Features (SF & GF)https://forge.in2p3.fr/issues/578412023-05-30T10:14:53ZPallier EtiennePyROS - Task #57542 (In progress): **** (SF03) OTHER actionshttps://forge.in2p3.fr/issues/575422023-05-22T09:19:57ZPallier EtiennePyROS - Task #57532 (In progress): **** (SF03) Measure (output data)https://forge.in2p3.fr/issues/575322023-05-22T08:37:15ZPallier EtiennePyROS - Task #57529 (In progress): **** (SF03) Agent A_EnvMonitor (Environment monitoring) : synt...https://forge.in2p3.fr/issues/575292023-05-21T17:37:21ZPallier EtiennePyROS - Task #57520 (In progress): *** (SF02) GENERAL MENUhttps://forge.in2p3.fr/issues/575202023-05-19T23:34:55ZPallier EtiennePyROS - Task #57518 (In progress): **** (SF02) OTHER ENTITIES actions (ST, TP, Institute)https://forge.in2p3.fr/issues/575182023-05-19T23:23:19ZPallier EtiennePyROS - Task #57514 (In progress): **** (SF02) SP actionshttps://forge.in2p3.fr/issues/575142023-05-19T17:01:21ZPallier EtiennePyROS - Task #57513 (In progress): *** (SF02) USE CASES - ACTIONS (on entities) & VIEWS (web pages)https://forge.in2p3.fr/issues/575132023-05-19T16:57:27ZPallier EtiennePyROS - Task #57509 (In progress): **** (SF01) OTHER actionshttps://forge.in2p3.fr/issues/575092023-05-19T16:24:23ZPallier EtiennePyROS - Task #57508 (In progress): *** (SF01) USE CASES - ACTIONS (on entities) & VIEWS (web pages)https://forge.in2p3.fr/issues/575082023-05-19T16:21:46ZPallier EtiennePyROS - Task #57505 (In progress): *** (SF01) GENERAL MENU (web page)https://forge.in2p3.fr/issues/575052023-05-19T14:43:35ZPallier EtiennePyROS - Task #53356 (In progress): Compute & Save synthesis data (for Majordome decision)https://forge.in2p3.fr/issues/533562022-10-03T14:15:41ZPallier EtiennePyROS - Task #49249 (In progress): *** (SF05) GENERAL MENUhttps://forge.in2p3.fr/issues/492492022-02-03T09:39:21ZPallier EtiennePyROS - Task #49135 (In progress): SF15-SST integration (agents, start, stop, commands)https://forge.in2p3.fr/issues/491352022-01-29T00:48:20ZPallier EtiennePyROS - Task #47412 (In progress): F09 Testshttps://forge.in2p3.fr/issues/474122021-10-11T10:10:40ZPallier EtiennePyROS - Task #47408 (In progress): F05 Testshttps://forge.in2p3.fr/issues/474082021-10-11T10:10:12ZPallier EtiennePyROS - Task #47407 (In progress): F04 Testshttps://forge.in2p3.fr/issues/474072021-10-11T10:10:04ZPallier EtiennePyROS - Task #47406 (In progress): F03 Testshttps://forge.in2p3.fr/issues/474062021-10-11T10:09:56ZPallier EtiennePyROS - Task #47405 (In progress): F02 Testshttps://forge.in2p3.fr/issues/474052021-10-11T10:09:49ZPallier EtiennePyROS - Task #47387 (In progress): **** (SF14) CRUD config fileshttps://forge.in2p3.fr/issues/473872021-10-08T17:29:54ZPallier EtiennePyROS - Task #45818 (In progress): *** (SF14) TESTS to validate requirementshttps://forge.in2p3.fr/issues/458182021-07-19T15:03:54ZPallier Etienne
<p>Functional (& unit) tests to validate this feature</p> PyROS - Task #45781 (In progress): Documentation et Présentations pour les PA et PK CNEShttps://forge.in2p3.fr/issues/457812021-07-16T08:45:48ZPallier Etienne
<p>Pour les PA, contenu des rapports d’avancement :</p>
<p>1. Présentation de rappel du logiciel</p>
<p>2. Ce qu’il était prévu d’effectuer durant la période (3 mois)</p>
<p>3. Ce qui a été réalisé</p>
<p>4. Si retard expliquer pourquoi</p>
<p>5. Etat de l’avancement des différentes tâches</p>
<p>6. Ce qui va être réalisé dans la période suivante et planning</p>
<p>Vous pouvez reprendre les schémas des slides en expliquant un peu plus en détails leur description.</p>
<p>Les tableaux d’avancement que vous aviez présentés peuvent également être repris dans le rapport</p> PyROS - Task #44922 (In progress): *** (SF04) AUTHORIZATIONS (kifekoi) : doc & implhttps://forge.in2p3.fr/issues/449222021-04-30T12:51:19ZPallier EtiennePyROS - Task #44915 (In progress): Changer le mode du système : passer en mode manuel (maintenanc...https://forge.in2p3.fr/issues/449152021-04-30T12:40:51ZPallier EtiennePyROS - Task #44898 (In progress): *** (SF03) ENTITIES (MODEL) - definition & implhttps://forge.in2p3.fr/issues/448982021-04-29T17:07:19ZPallier EtiennePyROS - Task #44884 (In progress): **** (SF02) TP Entity (Time Period)https://forge.in2p3.fr/issues/448842021-04-29T13:02:52ZPallier Etienne
<p>Une période est définie grâce une date de début d'exploitation.<br />Les autres phases composant une période :</p>
<p>- Proposal (Submission, Evaluation, Validation, Notification)<br />- Exploitation (Fin exploitation)<br />- Accès aux données et archivage</p>
<p>seront déduis grâce à des durées en jours.</p> PyROS - Task #44879 (In progress): *** (SF03) AUTHORIZATIONS (kifekoi) : doc & implhttps://forge.in2p3.fr/issues/448792021-04-29T12:33:04ZPallier EtiennePyROS - Task #44878 (In progress): *** (SF02) TESTS (to validate requirements)https://forge.in2p3.fr/issues/448782021-04-29T12:28:34ZPallier Etienne
<p>Tests unitaires et fonctionnels qui valident cette feature</p>
<p>Doc specs :</p>
<p><a class="external" href="https://docs.google.com/document/d/1uDsaclR9dqXF2I4TBGhZjWiykVtpzwDiPU0Lh2g9eJQ/edit#heading=h.s228d687ay9l">https://docs.google.com/document/d/1uDsaclR9dqXF2I4TBGhZjWiykVtpzwDiPU0Lh2g9eJQ/edit#heading=h.s228d687ay9l</a></p> PyROS - Task #44843 (In progress): **** (SF01) ROLE Entity (un utilisateur peut avoir plusieurs r...https://forge.in2p3.fr/issues/448432021-04-29T09:25:11ZPallier Etienne
<p>Visitor (role par défaut, sans aucun pouvoir)<br />Admin<br />Operator (maintenance)<br />Management board<br />PI-unit<br />TAC (referee)<br />Observer<br />PI-SP (= observer créateur/propriétaire du SP)</p> PyROS - Task #44842 (In progress): **** (SF01) USER Entityhttps://forge.in2p3.fr/issues/448422021-04-29T09:24:33ZPallier Etienne
<p>Name<br />Firstname<br />Password<br />Email<br />Telephone number<br />Laboratory<br />Name<br />Address<br />Institute (affiliation, lié à l’entité institute (management board)<br />Is active (Booléen pour indiquer si un utilisateur est activé ou non)<br />Valideur (nom du valideur de ce user)<br />Role(s) (dont 1 qui est actif si l’utilisateur est connecté)<br /><abbr title="s">SP</abbr><br />Comment (observations)</p> PyROS - Task #44835 (In progress): **** (SF01) CRUD actionshttps://forge.in2p3.fr/issues/448352021-04-29T08:52:29ZPallier Etienne
<p>View & Update user own details : Un utilisateur connecté doit pouvoir consulter sa fiche et la mettre à jour (sauf son/ses role(s)) ; seul le PI-unit (et admin) peut modifier ses propres roles</p>
<p>Add new user : Le PI-unit (ou un PI-SP) doit pouvoir ajouter lui-même un nouvel utilisateur</p>
<p>Update another user (by PI) : Le PI-unit (ou un PI-SP) doit pouvoir modifier tout ou partie des attributs d’un utilisateur :<br />Nom, prénom, ...<br />Son ou ses role(s)<br />Son ou ses <abbr title="s">SP</abbr><br />son mot de passe</p>
<p>Delete user : Le PI-unit (ou un PI-SP) doit pouvoir supprimer un utilisateur</p>
<p>View users list : <br />Un utilisateur doit pouvoir consulter la liste des utilisateurs (seulement ceux du SP)<br />Un PI-SP doit pouvoir consulter la fiche détaillée de tous les utilisateurs (seulement ceux du même SP), mais pas un Observer qcq</p> PyROS - Task #44832 (In progress): Un utilisateur non connecté ne doit voir que les pages publiqueshttps://forge.in2p3.fr/issues/448322021-04-29T08:50:59ZPallier EtiennePyROS - Task #44334 (In progress): Intégration protocole INDI (Guitastro)https://forge.in2p3.fr/issues/443342021-03-24T15:29:24ZPallier EtienneTReqS - Bug #10498 (In progress): Mysql Deadlockhttps://forge.in2p3.fr/issues/104982015-07-27T14:30:32ZChambon Bernard
<p>Found in /var/log/mysql.log<br /><pre>
150721 12:19:36 [Note] Event Scheduler: [root@localhost].[treqsjobs.cleaning_jqueues] event execution failed.
150722 16:39:36 [ERROR] Event Scheduler: [root@localhost][treqsjobs.cleaning_jqueues] Deadlock found when trying to get lock; try restarting transaction
150722 16:39:36 [Note] Event Scheduler: [root@localhost].[treqsjobs.cleaning_jqueues] event execution failed.
150722 16:46:36 [ERROR] Event Scheduler: [root@localhost][treqsjobs.cleaning_jqueues] Deadlock found when trying to get lock; try restarting transaction
150722 16:46:36 [Note] Event Scheduler: [root@localhost].[treqsjobs.cleaning_jqueues] event execution failed.
</pre></p> TReqS - Task #10061 (In progress): Testing 'stability-fix' branchhttps://forge.in2p3.fr/issues/100612015-06-04T15:37:49ZChambon BernardCLASS - Bug #9916 (Feedback): CLASS compilation fails with gcc5 ( 5.1.0 )https://forge.in2p3.fr/issues/99162015-05-18T22:25:28ZLENIAU Baptistebaptiste.leniau@subatech.in2p3.fr
<p>Compiler diagnosis : <br />In file included from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSLogger.hxx:19:0,<br /> from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSObject.hxx:18,<br /> from CLASSObjectDict.h:34,<br /> from CLASSObjectDict.cxx:17:<br />/opt/local/include/gcc5/c++/sstream:300:7: error: 'struct std::__cxx11::basic_stringbuf<_CharT, <em>Traits, _Alloc>::</em>_xfer_bufptrs' redeclared with different access<br /> struct _<em>xfer_bufptrs<br /> ^<br />In file included from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSLogger.hxx:19:0,<br /> from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSObject.hxx:18,<br /> from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSFacility.hxx:15,<br /> from CLASSFacilityDict.h:34,<br /> from CLASSFacilityDict.cxx:17:<br />/opt/local/include/gcc5/c++/sstream:300:7: error: 'struct std::</em>_cxx11::basic_stringbuf<_CharT, <em>Traits, _Alloc>::</em>_xfer_bufptrs' redeclared with different access<br /> struct _<em>xfer_bufptrs<br /> ^<br />In file included from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSLogger.hxx:19:0,<br /> from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSObject.hxx:18,<br /> from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/DecayDataBank.hxx:10,<br /> from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/CLASSConstante.hxx:8,<br /> from /Users/leniau/Applications/APP_SCIENCES/CLASS_Support/source/include/FabricationPlant.hxx:15,<br /> from FabricationPlantDict.h:34,<br /> from FabricationPlantDict.cxx:17:<br />/opt/local/include/gcc5/c++/sstream:300:7: error: 'struct std::</em>_cxx11::basic_stringbuf<_CharT, <em>Traits, _Alloc>::</em>_xfer_bufptrs' redeclared with different access<br /> struct __xfer_bufptrs<br /> ^<br />make: <b>* [CLASSObjectDict.o] Error 1<br />make: <strong></b> Waiting for unfinished jobs....<br />make: <b></strong> [CLASSFacilityDict.o] Error 1<br />make: *</b> [FabricationPlantDict.o] Error 1</p> TReqS - Bug #9736 (Suspended): hpss_SetLoginCred + hpss_PurgeLoginCredhttps://forge.in2p3.fr/issues/97362015-04-21T09:40:04ZChambon Bernard
<p>Doing some tests, encountered the following behaviour</p>
<ul>
<li>Case calling hpss_PurgeLoginCred either case failure<br />With user root123 fail (=PASS), then with user root <strong>hanging on hpss_SetLoginCred</strong> (=FAILURE)</li>
</ul>
<pre>
TRACE HPSSConnection - Login for user root123 ...
TRACE HPSSConnection - Using authentication method 'unix'
ERROR HPSSConnection - Just before hpss_SetLoginCred
ERROR HPSSConnection - Just after hpss_SetLoginCred
ERROR HPSSConnection - Authentication failed for user root123, hpss_SetLoginCred return -1
TRACE HPSSConnection - Logout ...
TRACE HPSSConnection - Logout done
Calling HPSSConnection
TRACE HPSSConnection - logger already configured ...
TRACE HPSSConnection - Login for user root ...
TRACE HPSSConnection - Using authentication method 'unix'
ERROR HPSSConnection - Just before hpss_SetLoginCred
^C
Here hpss_PurgeLoginCred hang forever !
</pre>
<ul>
<li>Case calling hpss_PurgeLoginCred only if hpss_SetLoginCred succeed <br />With user root123 fail (=PASS), then with <strong>user root fail</strong> (= FAILURE)</li>
</ul>
<pre>
Calling HPSSConnection
TRACE HPSSConnection - Login for user root123 ...
TRACE HPSSConnection - Using authentication method 'unix'
ERROR HPSSConnection - Just before hpss_SetLoginCred
ERROR HPSSConnection - Just after hpss_SetLoginCred
ERROR HPSSConnection - Authentication failed for user root123, hpss_SetLoginCred return -1
Calling HPSSConnection
Exception catched : Authentication failed for user root123
TRACE HPSSConnection - logger already configured ...
TRACE HPSSConnection - Login for user root ...
TRACE HPSSConnection - Using authentication method 'unix'
ERROR HPSSConnection - Just before hpss_SetLoginCred
ERROR HPSSConnection - Just after hpss_SetLoginCred
ERROR HPSSConnection - Authentication failed for user root, hpss_SetLoginCred return -22
Exception catched : Authentication failed for user root
</pre> TReqS - Task #9545 (In progress): Provide CI with jenkinhttps://forge.in2p3.fr/issues/95452015-03-26T14:02:23ZChambon Bernard
<p>Provide CI with jenkins requires</p>
<p>1) setup a jenkins jobs</p>
<p>2) Provide a jenkins workers with HPSS stuff (HPSS libs + include) to compile</p>
<p>3) Configure the jenkins job to access private gitlab project</p>
<p>4) Configure the jenkins job to deploy rpm package on maven.in2p3.fr</p>
<p>5) Provide a jenkins workers to run tests :<br />HPSS access<br />Mysql DB<br />DB access parameters (login, password, etc.) in pre-build scripts</p> IGOSat - Task #9099 (In progress): (PRO) Phase Ahttps://forge.in2p3.fr/issues/90992015-02-10T18:41:54ZAgnan Marco
<p>On y évalue la faisabilité de la mission envisagée et de la disponibilité des technologies nécessaires</p> ROD-DASHBOARD - Feature #8645 (In progress): ROD dashboard: only verify when closing tickethttps://forge.in2p3.fr/issues/86452014-12-05T09:46:08ZFrébault Pierre
<p>Ticket link : <a class="external" href="https://ggus.eu/index.php?mode=ticket_info&ticket_id=108307">https://ggus.eu/index.php?mode=ticket_info&ticket_id=108307</a></p>
<p>ROD dashboard: only verify when closing ticket.</p>
<p>Detailed Description:<br /> Dear Dashboard Team,</p>
<p>When I try to close ticket (that has Solved status in GGUS), I get only Verify option (see attachment). I suppose there should be already "Reopen" option - I believe I already seen it earlier. Maybe it was removed accidentally?</p>
<p>Usecase: Admin solves ticket in GGUS (or dashboard), ROD wants to check it, Nagios tests are in critical state, so ROD does not only Verifies, but also should Reopen the ticket.</p>
<p>Cheers,<br />Tadeusz</p> TReqS - Feature #416 (In progress): État drainé pour TReqShttps://forge.in2p3.fr/issues/4162010-02-08T12:14:32ZSchaeffer Jonathanjonathan.schaeffer@cc.in2p3.fr
<p>Implémenter un état drainé pour TReqS.</p>
<p>Cela pourrait se faire en mettant un paramètre "global_share" dans la base de configuration.<br />Alors, le client peut se rendre compte que TReqS est drainé (via une procédure stockée dans MySQL ?) et les nouvelles requêtes sont interdites.</p>