[JBoss JIRA] (JBIDE-23622) Build Log: impossible to get logs once the build pod is completed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23622?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23622:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Build Log: impossible to get logs once the build pod is completed
> -----------------------------------------------------------------
>
> Key: JBIDE-23622
> URL: https://issues.jboss.org/browse/JBIDE-23622
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Marián Labuda
> Labels: build_log, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: cannot-build-log.png, log_build.png
>
>
> When I am trying to get a log of completed build, either via context menu of a pod in tabbed property Pods or via context menu of a build in tabbed property Builds, I get following error dialog
> !log_build.png!
> There is no error in log.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22375:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Improve HCR OpenShift
> ---------------------
>
> Key: JBIDE-22375
> URL: https://issues.jboss.org/browse/JBIDE-22375
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: jmx, openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.AM2
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23136:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> 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.3.AM2
>
> Attachments: 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)
7 years, 9 months
[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19506:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Connection wizard, Connection: should have unit tests
> ------------------------------------------------------
>
> Key: JBIDE-19506
> URL: https://issues.jboss.org/browse/JBIDE-19506
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, tests
> Fix For: 4.4.3.AM2
>
> Original Estimate: 2 days
> Time Spent: 3 days
> Remaining Estimate: 3 days
>
> In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-21331) Connection wizard: it looks as if the wizard is creating new connection instances several times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21331?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21331:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Connection wizard: it looks as if the wizard is creating new connection instances several times
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-21331
> URL: https://issues.jboss.org/browse/JBIDE-21331
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.4.3.AM2
>
>
> The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification)
> {code:title=ConnctionWizardPageModel}
> private void initEditConnection(IConnection connection) {
> this.selectedConnection = connection;
> this.connection = connection.clone();
> ...
> {code}
> {code:title=ConnctionWizardPageModel}
> public IStatus connect() {
> ...
> try {
> this.connection = createConnection();
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23626:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23626
> URL: https://issues.jboss.org/browse/JBIDE-23626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: oc_binary, preferences
> Fix For: 4.4.3.AM2
>
>
> oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use.
> Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months