[CREAM-142] SLURM provider should publish undefined values Created: 10/Apr/14  Updated: 10/Jun/14  Resolved: 10/Jun/14

Status: Resolved
Project: CREAM
Component/s: None
Affects Version/s: CREAM SLURM module 1.0.1
Fix Version/s: CREAM SLURM module 1.0.2
Security Level: Public (Visbile by non-authn users.)

Type: Bug Priority: Major
Reporter: Paolo Andreetto Assignee: Paolo Andreetto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Source: https://ggus.eu/index.php?mode=ticket_info&ticket_id=97721

SLURM infoproviders must publish the values for all the attributes managed; if a value is not defined the one published is the max or min value available according to GLUE1/GLUE2



 Comments   
Comment by Paolo Andreetto [ 10/Jun/14 ]

Fix with tag info-dynamic-scheduler-slurm_R_1_0_2_1

Comment by Paolo Andreetto [ 06/Jun/14 ]

Regressiont tests:

Run the following commands:

ldapsearch -h cehost.pd.infn.it -x -p 2170 -b "o=grid" objectclass=GLUECEPolicy | grep 999999999
ldapsearch -h cehost.pd.infn.it -x -p 2170 -b "o=grid" objectclass=GLUECEPolicy | grep 444444

ldapsearch -h cehost-42.pd.infn.it -x -p 2170 -b "o=glue" objectclass=GLUE2ComputingShare | grep 999999999
ldapsearch -h cehost-42.pd.infn.it -x -p 2170 -b "o=glue" objectclass=GLUE2ComputingShare | grep 444444

and verify that no attribute is reported.
If this is not, verify that an error is report in the BDII log and the error is related to the SLURM infoprovider.

Generated at Wed Jan 22 09:08:23 CET 2025 using Jira 10.3.1#10030001-sha1:7c16d34d98ce5cdd7a13118a6e1535e014ad7025.