[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-13319.
---------------------------------------
Resolution: Won't Fix
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: embed-by-name.patch, mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13319:
---------------------------------------------
users of openshift should use JBDS 6/JBT 4 instead where there are other important fixes.
If they do bump into this issue use rhc tail-files as a workaround or upgrade to JBDS 6/JBT 4 where there are more fixes.
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: embed-by-name.patch, mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13318) Cannot tail files at all
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13318?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13318:
---------------------------------------------
users of openshift should use JBDS 6/JBT 4 instead where there are other important fixes.
If they do bump into this issue use rhc tail-files as a workaround or upgrade to JBDS 6/JBT 4 where there are more fixes.
> Cannot tail files at all
> ------------------------
>
> Key: JBIDE-13318
> URL: https://issues.jboss.org/browse/JBIDE-13318
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: tail-files-options.patch
>
>
> Still getting {code}Could not find any files matching glob{code} using JBoss AS/EAP application type, either via server adapter or OpenShift Explorer. Maybe an OpenShift API change?
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-13320.
---------------------------------------
Resolution: Rejected
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: copy-file-permissions.patch, 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
13 years, 6 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13320:
---------------------------------------------
users of openshift should use JBDS 6/JBT 4 instead where there are other important fixes.
If they do bump into this issue on previous release the workaround is to set the execute permissions on the .openshift/action_hooks/* files manually after import.
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: copy-file-permissions.patch, 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
13 years, 6 months