[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22626:
------------------------------------------
[~xcoulon] is this something you could look at please?
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.1.S116
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22626:
-------------------------------------
Fix Version/s: 4.4.1.S116
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.1.S116
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22626:
-------------------------------------
Priority: Critical (was: Major)
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.1.S116
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22626:
-------------------------------------
Sprint: devex #116 2016/06/15 - 07/05
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.1.S116
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22362 at 6/22/16 7:40 AM:
-------------------------------------------------------------------
If I get it right DEV_MODE is actually also used to enable debugging in the image. What else that allowing changes does this imply? Is there any harm if we simply enable DEV_MODE but wont attach a debugger in normal (aka, not attaching a debugger, just changing files and deploy them) operations?
I would simply set DEV_MODE to true as default in the tooling automatically, no need for the user to get to the env var wizard.
was (Author: adietish):
If I get it right DEV_MODE is actually also used to enable debugging in the image. What else that allowing changes does this imply? Is there any harm if we simply enable DEV_MODE but wont attach a debugger in normal (aka, not attaching a debugger, just changing files and deploy them) operations?
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.S116
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22362:
------------------------------------------
If I get it right DEV_MODE is actually also used to enable debugging in the image. What else that allowing changes does this imply? Is there any harm if we simply enable DEV_MODE but wont attach a debugger in normal (aka, not attaching a debugger, just changing files and deploy them) operations?
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.S116
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22594 at 6/22/16 7:35 AM:
-------------------------------------------------------------------
[~dbocharov] as rule of thumb we did the following in all wizards:
* launch the wizard from context menu in OpenShift explorer: dont show the connection dialog, the connection that should be used may be inferred from the selected item that we used the context menu on
* lauch the wizard with any other means (ex. main menu: File > New > OpenShift > New OpenShift Application): show the connection dialog. Preselect the connection upon the most recently used one. try to infer the connection from a selected item in explorer or use <New Connection>
Applied to the Deploy Docker Image wizard this would mean: always show the connection dialog. Try to infer the selected connection from the selected item in the explorer or default to <New Connection> with Type "OpenShift 3" (both should be done in a self sufficient manner in the connection page)
was (Author: adietish):
[~dbocharov] as rule of thumb we did the following in all wizards:
* launch the wizard from context menu in OpenShift explorer: dont show the connection dialog, the connection that should be used may be inferred from the selected item that we used the context menu on
* lauch the wizard with any other means (ex. main menu: File > New > OpenShift > New OpenShift Application): show the connection dialog
Applied to the Deploy Docker Image wizard this would mean: always show the connection dialog.
> Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22594
> URL: https://issues.jboss.org/browse/JBIDE-22594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitry Bocharov
> Labels: connection_wizard, deploy_docker_wizard, openshift_v3
> Fix For: 4.4.1.S116
>
> Attachments: out-2.ogv
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22235) NullPointerException in BarrierProgressWaitJob.canceling
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22235?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-22235.
------------------------------------
> NullPointerException in BarrierProgressWaitJob.canceling
> --------------------------------------------------------
>
> Key: JBIDE-22235
> URL: https://issues.jboss.org/browse/JBIDE-22235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.canceling(BarrierProgressWaitJob.java:143)
> at org.eclipse.core.internal.jobs.InternalJob.cancel(InternalJob.java:185)
> at org.eclipse.core.runtime.jobs.Job.cancel(Job.java:220)
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.monitorSafeJoin(BarrierProgressWaitJob.java:135)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:330)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:319)
> at org.jboss.tools.foundation.core.ecf.internal.URLTransportCache.downloadAndCache(URLTransportCache.java:177)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:186)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:88)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:244)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadProperties(VersionPropertiesProvider.java:271)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:151)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamplesUrl(ProjectExampleJsonProvider.java:141)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamples(ProjectExampleJsonProvider.java:55)
> at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.0.1.Final-v20160401-1059-B103 |
> | org.jboss.tools.foundation.core | 1.2.1.Final-v20160408-2358-B112 | 1.2.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.project.examples | 3.0.1.Final-v20160401-1059-B103 | 3.0.1.Final-v20160401-1059-B103 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a1ed7e4b0e9dd9c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22594:
------------------------------------------
[~dbocharov] as rule of thumb we did the following in all wizards:
* launch the wizard from context menu in OpenShift explorer: dont show the connection dialog, the connection that should be used may be inferred from the selected item that we used the context menu on
* lauch the wizard with any other means (ex. main menu: File > New > OpenShift > New OpenShift Application): show the connection dialog
Applied to the Deploy Docker Image wizard this would mean: always show the connection dialog.
> Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22594
> URL: https://issues.jboss.org/browse/JBIDE-22594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitry Bocharov
> Labels: connection_wizard, deploy_docker_wizard, openshift_v3
> Fix For: 4.4.1.S116
>
> Attachments: out-2.ogv
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months