IZ3101: qconf -aattr overrides list attributes in queue instances

[templedf]

[Imported from gridengine issuezilla ​http://gridengine.sunsource.net/issues/show_bug.cgi?id=3101]

        Issue #:      3101             Platform:     All      Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.2u3       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     qconf -aattr overrides list attributes in queue instances
   Status whiteboard:
      Attachments:

     Issue 3101 blocks:
   Votes for issue 3101:


   Opened: Thu Aug 13 09:26:00 -0700 2009 
------------------------


If I use qconf -aattr to add a value to a list attribute in a queue instance, then that queue instance's attribute value will not include
the cluster queue's setting.  For example:

[ Add two new PEs ]
% qconf -ap test1
...
% qconf -ap test2
...

[ Add the first PE to all.q and confirm that I can submit against it ]
% qconf -aattr queue pe_list test1 all.q
dant@gridengine6 modified "all.q" in cluster queue list
% qsub -w e -pe test1 1 -l h=host1 sleeper.sh
Your job 10058 ("Sleeper") has been submitted
% qconf -aattr queue pe_list test2 all.q@host1

[ Add the second PE to all.q@host1 and confirm that I can submit against it ]
dant@gridengine6 modified "all.q" in cluster queue list
% qsub -w e -pe test2 1 -l h=host1 sleeper.sh
Your job 10059 ("Sleeper") has been submitted

[ Try to submit against the first PE ]
% qsub -w e -pe test1 1 -l h=host1 sleeper.sh
Unable to run job: error: no suitable queues.
Exiting.
% qconf -sq all.q | grep pe_list
pe_list               make,test1,[host1=test2]


While this behavior might be logical from the perspective of the way qconf is written, it's illogical from the perspective of the user.

   ------- Additional comments from reuti Thu Aug 13 09:58:20 -0700 2009 -------
What would be the option? Copy all "default" PEs for this queue to the host specific PE list while adding the new one. But in case you want only this newly added one, all others must
be removed by dattr then thereafter - also not much fun.

Also: removing one PE from one host would mean: copy all default PEs except this one. And if you want to remove a second: copy again the default except this one, or remove the
second one from the already reduced set?

And if you remove a PE from the default - shall it also be removed from all host specific definitions?


I think it's better leave it as it is with the background: all.q to -aattr on its own is not like "for all instances", but "set the default for not listed hosts with specific entries". You are
changing the default with your commands, not all queue instances of all.q.