[jbosstools-issues] [JBoss JIRA] (JBIDE-13217) Execute permissions modified in new openshift projects causing action hoooks to not execute

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738677#comment-12738677 ] 

Max Rydahl Andersen commented on JBIDE-13217:
---------------------------------------------

Just to summarize this evil bug:

Root cause: During copy of files from the git clone we did not copy the permissions and because of changes on OpenShift there is now false errors when we deploy (server runs, but error say it could not start - i.e. confusing)

Result: on openshift *some*, not all scripts execution depends on this +x being set.

Why not seen before: before the scripts did not need +x being set, thus it went unnoticed.

Why fix it now: OpenShift recently changed their scripts and there will probably be more fixes after JBDS 6 GA that would make it worse.

Note: Bug only present on linux+mac when importing existing project into openshift since that is where we actually do a copy

Is this is perfect fix: Not really since we are only able to copy owner permissions, but for this case we don't have a better way before Java 7

                
> Execute permissions modified in new openshift projects causing action hoooks to not execute
> -------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13217
>                 URL: https://issues.jboss.org/browse/JBIDE-13217
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.0.0.CR1
>         Environment: Linux, Mac (NOT Windows)
>            Reporter: Max Rydahl Andersen
>            Assignee: Andre Dietisheim
>              Labels: respin-c
>         Attachments: hook-premissions-windows.jpg
>
>
> 1. EXEC: Create and import new app
> 2. ASSERT: execute permissions on action_hooks get resetted.
> {code}
> diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
> {code}
> 3. EXEC: publish the application to OpenShift
> Result:
> {code}
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> ...but the server is started.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira