Bug #205

TM NFS scripts should set the read attribute for disks

Added by Tino Vázquez almost 11 years ago. Updated almost 10 years ago.

Status:ClosedStart date:03/15/2010
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Drivers - Auth
Target version:-
Resolution:fixed Pull request:
Affected Versions:

Description

From Tiago Batista <>, using econe
----

GOOD:
[tsbatista@parlamento images]$ ls l ../../78/images/
total 499748
-rw-r--r-
1 tsbatista users 344 Feb 25 19:34 deployment.0
rw-rw-rw 1 tsbatista users 10486808576 Feb 25 19:39 disk.0
rw-rw-rw 1 tsbatista users 536870913 Feb 25 19:34 disk.1
rw-r--r- 1 tsbatista users 376832 Feb 25 19:34 disk.2

BAD:
[tsbatista@parlamento images]$ ls l
total 1051024
-rw-r--r-
1 tsbatista users 344 Feb 25 19:20 deployment.0
rw--w--w 1 tsbatista users 1074790400 Feb 25 19:28 disk.0
rw-rw-rw 1 tsbatista users 536870913 Feb 25 19:20 disk.1
rw-r--r- 1 tsbatista users 376832 Feb 25 19:20 disk.2

Im am using tm_nfs for my deployment.

The modifications I performed have to do with the chmod commands issued on the tm* commands. They now look like this:

[tsbatista@fpa1 nfs]$ grep chmod *
tm_clone.sh:exec_and_log "chmod a+rw $DST_DIR"
tm_clone.sh:exec_and_log "chmod a+rw $DST_PATH"
tm_ln.sh:exec_and_log "chmod a+w $DST_DIR"
tm_mkimage.sh:exec_and_log "chmod a+rw $DST_PATH"
tm_mkswap.sh:exec_and_log "chmod a+w $DST_DIR"
tm_mkswap.sh:exec_and_log "chmod a+w $DST_PATH"

Associated revisions

Revision add0ca1b
Added by Juan Jose Montiel Cano almost 4 years ago

Feature 2347 (#205)

  • F #2347 Added label VM Group
  • F #2347 Added new column to show the number of vms
  • F #2347 changed notifier string error
  • F #2347 Added the new column to the .yamls
  • F #2347 Added panel vms for show the vms of a role

History

#2 Updated by Ruben S. Montero almost 11 years ago

  • Category set to Drivers - Auth
  • Assignee set to Javi Fontan
  • Target version set to Release 1.4.2

#3 Updated by Ruben S. Montero over 10 years ago

  • Status changed from New to Assigned
  • Target version changed from Release 1.4.2 to Release 2.0

#4 Updated by Javi Fontan over 10 years ago

  • Target version deleted (Release 2.0)

#5 Updated by Ruben S. Montero almost 10 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

This has been solved in 2.0 series

Also available in: Atom PDF