Opened 12 years ago
Last modified 10 years ago
#653 new defect
IZ2966: qsub -v "FOO=bar,baz" exports only FOO="bar" to the job environment
Reported by: | mcumings | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | sge | Version: | 6.2u2 |
Severity: | Keywords: | Solaris execution | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2966]
Issue #: 2966 Platform: All Reporter: mcumings (mcumings) Component: gridengine OS: Solaris Subcomponent: execution Version: 6.2u2 CC: None defined Status: NEW Priority: P2 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: pollinger (pollinger) QA Contact: pollinger URL: * Summary: qsub -v "FOO=bar,baz" exports only FOO="bar" to the job environment Status whiteboard: Attachments: Issue 2966 blocks: Votes for issue 2966: Opened: Wed Mar 25 10:33:00 -0700 2009 ------------------------ When submitting a job with an environment variable containing the "," character, only the portion of the variable value preceeding the comma is used in the environment exported to the client. ==== To replicate: - Create a job script (in this example, "grid_echo_FOO") with the following content: #!/usr/bin/env bash echo "FOO='${FOO}'" - Submit the script for execution: $ DIR_LOG=`pwd`/stdout $ qsub -o ${DIR_LOG}/stdout -v 'FOO=bar,baz' grid_echo_FOO Your job ... has been submitted $ # Wait for the job to execute $ cat ${DIR_LOG}/stdout FOO='bar' $ ==== Workaround: If the alternate form of the environment variable export is used where only the variable name is provided, the environment variable is exported properly. Example: $ FOO='bar,baz' qsub -o ${DIR_LOG}/stdout -v 'FOO' grid_echo_FOO Your job ... has been submitted $ # Wait for the job to execute $ cat ${DIR_LOG}/stdout FOO='bar,baz' $
Note: See
TracTickets for help on using
tickets.