Opened 51 years ago

Last modified 10 years ago

#901 new defect

IZ597: set_bootstrap_config_property fails with implicit preferences type feature

Reported by: afisch Owned by:
Priority: normal Milestone:
Component: hedeby Version: 1.0u1
Severity: Keywords: Sun cli


[Imported from gridengine issuezilla]

        Issue #:      597          Platform:     Sun         Reporter: afisch (afisch)
       Component:     hedeby          OS:        All
     Subcomponent:    cli          Version:      1.0u1          CC:    None defined
        Status:       NEW          Priority:     P3
      Resolution:                 Issue type:    DEFECT
                               Target milestone: 1.0u5next
      Assigned to:    adoerr (adoerr)
      QA Contact:     adoerr
       * Summary:     set_bootstrap_config_property fails with implicit preferences type feature
   Status whiteboard:

     Issue 597 blocks:
   Votes for issue 597:     Vote for this issue

   Opened: Wed Nov 5 09:39:00 -0700 2008 

   The set_bootstrap_config_property command is not aware of the implicit pref type
   if the real preftype is user mode and the command is executed in user mode.

     % ./sdmadm -s dummy set_bootstrap_config_property -p no_ssl -v true
     Error: Cannot set "no_ssl" to "true" for system "dummy" using preference type
     The system returned the following error:
     Can not access lock file /etc/sdm/bootstrap/.lock

   The system dummy has user preferences and as it is unambigous (no other dummy
   system), there should be no need to specify the pref type. However SDM assumes
   that it has pref type system, also it states: ..using preference type
   "SYSTEM_PROPERTIES" what means that the type is not defined by the user and
   should be auto discovered by the command (options: USER,SYSTEM,SYSTEM_PROPERTIES).

   The issue is rated as p3 defect. A workaround exists. However it might be not to
   obvious from the error message provided.

   Suggested fix:
   The command should be able to auto detect the correct preferences type.
   Work Around:
   The command can be successfully executed by explicity providing the pref type.

   There is not explicit validity test in
   for the -p option. Such a test is present in
   However the issue should be fixed with the resolveSyste routine for 589 once it
   is developed.

   How to test:
   A Test suit test has to be written, that creates a dummy bootstrap config with
   user prefs. Then set_bootstrap_config_property should be executed as user with
   the above options.

   +1.5 PD (considering that 589 is fixed and the resolveSystem routine can be used
               ------- Additional comments from rhierlmeier Wed Nov 25 07:21:11 -0700 2009 -------
   Milestone changed

Change History (0)

Note: See TracTickets for help on using tickets.