You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Created) (JIRA)" <ji...@apache.org> on 2012/03/29 02:53:25 UTC

[jira] [Created] (BIGTOP-498) Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie

Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie
--------------------------------------------------------------------------------

                 Key: BIGTOP-498
                 URL: https://issues.apache.org/jira/browse/BIGTOP-498
             Project: Bigtop
          Issue Type: Bug
          Components: General
    Affects Versions: 0.4.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
             Fix For: 0.4.0


One case where this is a problem is where oozie runs an ssh action as part of its workflow. This requires creating a public/private key that must be stored in the oozie user's home dir. If the user restarts the machine, then the user will need to re-created the public/private key pair, and re-propagate the newly-created public key to all target hosts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BIGTOP-498) Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie

Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-498:
------------------------------------

    Attachment: BIGTOP-498.patch.txt
    
> Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie
> --------------------------------------------------------------------------------
>
>                 Key: BIGTOP-498
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-498
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-498.patch.txt
>
>
> One case where this is a problem is where oozie runs an ssh action as part of its workflow. This requires creating a public/private key that must be stored in the oozie user's home dir. If the user restarts the machine, then the user will need to re-created the public/private key pair, and re-propagate the newly-created public key to all target hosts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-498) Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie

Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240859#comment-13240859 ] 

Bruno Mahé commented on BIGTOP-498:
-----------------------------------

Don't we already have a ticket about that?
                
> Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie
> --------------------------------------------------------------------------------
>
>                 Key: BIGTOP-498
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-498
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>
> One case where this is a problem is where oozie runs an ssh action as part of its workflow. This requires creating a public/private key that must be stored in the oozie user's home dir. If the user restarts the machine, then the user will need to re-created the public/private key pair, and re-propagate the newly-created public key to all target hosts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (BIGTOP-498) Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie

Posted by "Peter Linnell (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240868#comment-13240868 ] 

Peter Linnell commented on BIGTOP-498:
--------------------------------------

+1 LGTM
                
> Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie
> --------------------------------------------------------------------------------
>
>                 Key: BIGTOP-498
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-498
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-498.patch.txt
>
>
> One case where this is a problem is where oozie runs an ssh action as part of its workflow. This requires creating a public/private key that must be stored in the oozie user's home dir. If the user restarts the machine, then the user will need to re-created the public/private key pair, and re-propagate the newly-created public key to all target hosts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-498) Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie

Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240870#comment-13240870 ] 

Bruno Mahé commented on BIGTOP-498:
-----------------------------------

+1
                
> Oozie's home dir is currently set to /var/run/oozie but should be /var/lib/oozie
> --------------------------------------------------------------------------------
>
>                 Key: BIGTOP-498
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-498
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-498.patch.txt
>
>
> One case where this is a problem is where oozie runs an ssh action as part of its workflow. This requires creating a public/private key that must be stored in the oozie user's home dir. If the user restarts the machine, then the user will need to re-created the public/private key pair, and re-propagate the newly-created public key to all target hosts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira