Menu

#497 c3.conf issue with defined nodes not yet built

5.0 (deprecated)
open
6
2005-12-02
2004-02-09
No

I just hit something that should be a bug for the
oscar/c3 config. when there are a set of nodes defined
but one in the middle is not yet built, e.g. node33 out
of a set of 64 nodes....the c3.conf is created without
a "dead" place holder for this node. Thus, the
indexing is shift down by one. :( ewwww.

Actually this is a problem that the SIS function used
to get the list of defined nodes is doesn't included
all defined, only those that were actually built. see
also: SystemInstaller::Machine::get_machine_listing()

There's no state associated with these nodes to
determine if the defined node should be prefixed with a
"dead" flag, etc.

Have to figure out a good way to handle this. This
isn't a critical issue...been this way since about
oscar 2.x but it is still not a good thing, IMHO.

Discussion

  • Thomas Naughton

    Thomas Naughton - 2004-05-04
    • milestone: 373321 --> 355794
     
  • Thomas Naughton

    Thomas Naughton - 2004-10-27
    • milestone: 355794 --> 443353
     
  • Thomas Naughton

    Thomas Naughton - 2004-11-01

    Logged In: YES
    user_id=288102

    Need to provide a good fix for this. Discuss/fix after sc'04.

     
  • Jeff Squyres

    Jeff Squyres - 2004-11-24
    • milestone: 443353 --> 450827
     
  • John

    John - 2005-02-15
    • priority: 5 --> 6
     
  • John

    John - 2005-02-15

    Logged In: YES
    user_id=505737

    Resetting to 6. It would be nice if this one got fixed for 4.1.

     
  • John

    John - 2005-04-19
    • milestone: 450827 --> 231663
     
  • Bernard Li

    Bernard Li - 2005-12-02
    • milestone: 231663 --> 5.0 (deprecated)
     
  • Bernard Li

    Bernard Li - 2005-12-02

    Logged In: YES
    user_id=879102

    Let's take a look at this for 5.0.