[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22969:
-------------------------------
Fix Version/s: 4.4.4.AM1
(was: 4.4.3.Final)
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.4.AM1
>
> Attachments: proxy_settings.png, proxy_settings_2.png
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23005) [Watcher] Server Adapter: Stuck on creating/publishing
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23005:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.3.Final)
> [Watcher] Server Adapter: Stuck on creating/publishing
> ------------------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter, upstream
> Fix For: 4.4.4.AM2
>
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23279:
-------------------------------
Fix Version/s: 4.4.4.Final
(was: 4.4.3.Final)
> Exception generated when OS 3 connection URL is invalid
> -------------------------------------------------------
>
> Key: JBIDE-23279
> URL: https://issues.jboss.org/browse/JBIDE-23279
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3
> Fix For: 4.4.4.Final
>
>
> EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application
> EXEC: select <New Connection>
> EXEC: enter invalid URL in the host field
> ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23136:
-------------------------------
Fix Version/s: 4.4.4.AM1
(was: 4.4.3.Final)
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.4.AM1
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23567) Integration tests global refactoring
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23567?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23567:
-------------------------------
Fix Version/s: 4.4.4.Final
(was: 4.4.3.Final)
> Integration tests global refactoring
> ------------------------------------
>
> Key: JBIDE-23567
> URL: https://issues.jboss.org/browse/JBIDE-23567
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Jeff MAURY
> Labels: integration-test, integration_tests
> Fix For: 4.4.4.Final
>
>
> We should done some work on integration tests so that we can rely on them to improve our code quality and reduce the technical debt.
> A sprint will be dedicated.
> Here are the tasks we should work on:
> * run tests from Maven and document how to run them if specific steps are required
> * If failure, fix the failed tests
> * Refactor / move tests to the components repository
> * Fix/make sure tests are run in PR check
> This huge task should be done component per component. Sub-tasks JIRA will be created for each component.
> You can use this document as a starting point:[https://docs.google.com/document/d/1bl8pJ2aW65UpyGpr3qxoAUREDWL26N...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month