Opened 15 years ago

Last modified 11 years ago

#953 new enhancement

IZ12: installation on a filesystem where root has no write access

Reported by: joga Owned by:
Priority: normal Milestone:
Component: testsuite Version: current
Severity: Keywords: framework


[Imported from gridengine issuezilla]

        Issue #:      12              Platform:     All           Reporter: joga (joga)
       Component:     testsuite          OS:        All
     Subcomponent:    framework       Version:      current          CC:    None defined
        Status:       NEW             Priority:     P3
      Resolution:                    Issue type:    ENHANCEMENT
                                  Target milestone: milestone 1
      Assigned to:    issues@testsuite
      QA Contact:     joga
       * Summary:     installation on a filesystem where root has no write access
   Status whiteboard:

     Issue 12 blocks:   50             50
   Votes for issue 12:                    Vote for this issue

   Opened: Fri Nov 10 01:41:00 -0700 2006 

This was IZ 135 in project gridengine.

Currently the testsuite cannot install and use a cluster on a filesystem where
root has no write access - while Grid Engine can handle this case in an admin
user installation.

Steps to to (maybe not complete):
- when install script detects situation (message "Please hit <RETURN> to
continue once you set your file permissions")  try to set the file permissions
by executing the setfileperm shell script as root on the file server.

It might make sense to introduce filesystem settings in testsuite, similar to
host configuration, where we could configure the filesystems available, together
with some attributes, like hostname of the fileserver, permissions etc. This
would deprecate the current "host" settings "NFS shared directory ...".

   ------- Additional comments from joga Wed Nov 22 03:30:06 -0700 2006 -------
first implement testsuite filesystem configuration

   ------- Additional comments from joga Thu Mar 1 01:42:51 -0700 2007 -------
*** Issue 122 has been marked as a duplicate of this issue. ***

Change History (0)

Note: See TracTickets for help on using tickets.