[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25670:
------------------------------------------
[~jeffmaury] that's what you experienced, too, right?
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Description:
This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
steps:
# ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
# EXEC: launch "Delete Resources" wizard
# ASSERT: you see deployment configs, replication controllers, pods etc.
# EXEC: select all resources and hit "Finish"
# ASSERT: wait for all removal jobs to be finished
# EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
Result:
!image-2018-01-29-09-34-08-598.png!
Replication controller(s) and pods are left in place, they were not deleted.
Some pods may be in terminating state and disappear eventually.
was:
This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
steps:
# ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
# EXEC: launch "Delete Resources" wizard
# ASSERT: you see deployment configs, replication controllers, pods etc.
# EXEC: select all resources and hit "Finish"
# ASSERT: wait for all removal jobs to be finished
# EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
Result:
!image-2018-01-29-09-34-08-598.png!
Replication controller(s) and pods are left in place, they were not deleted.
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
> Some pods may be in terminating state and disappear eventually.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25670:
----------------------------------------
Summary: Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
Key: JBIDE-25670
URL: https://issues.jboss.org/browse/JBIDE-25670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.2.Final
Reporter: Andre Dietisheim
Attachments: image-2018-01-29-09-34-08-598.png
This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
steps:
# ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
# EXEC: launch "Delete Resources" wizard
# ASSERT: you see deployment configs, replication controllers, pods etc.
# EXEC: select all resources and hit "Finish"
# ASSERT: wait for all removal jobs to be finished
# EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
Result:
!image-2018-01-29-09-34-08-598.png!
Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Fix Version/s: 4.5.3.AM1
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25670:
----------------------------------------
Assignee: Andre Dietisheim
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Labels: delete_resources (was: )
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Sprint: devex #144 January 2018
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25669?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25669:
-------------------------------
Fix Version/s: 4.5.3.AM2
> Unexpected JAX-RS validation error for Feature
> ----------------------------------------------
>
> Key: JBIDE-25669
> URL: https://issues.jboss.org/browse/JBIDE-25669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.2.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Labels: jax-rs, respin-a
> Fix For: 4.5.3.AM2
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25669?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-25669:
----------------------------------
Assignee: Jeff MAURY (was: Xavier Coulon)
> Unexpected JAX-RS validation error for Feature
> ----------------------------------------------
>
> Key: JBIDE-25669
> URL: https://issues.jboss.org/browse/JBIDE-25669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.2.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Labels: jax-rs, respin-a
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBDS-4671) Errors updating from 11.1.0.GA to latest one
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4671?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4671:
-----------------------------
Sprint: devex #144 January 2018
> Errors updating from 11.1.0.GA to latest one
> --------------------------------------------
>
> Key: JBDS-4671
> URL: https://issues.jboss.org/browse/JBDS-4671
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, updatesite
> Affects Versions: 11.1.0.GA
> Environment: Red Hat JBoss Developer Studio 11.1.0.GA with early access activate.
> openjdk version "1.8.0_151" .OpenJDK Runtime Environment (build 1.8.0_151-b12)
> Operating System: Fedora 27
> Reporter: Roman Martin Gil
> Assignee: Nick Boldt
> Fix For: 11.2.0.GA
>
> Attachments: 01-rhjbds-available-updates.png, 02-rhjbds-about-installation.png, 03-rhjbds-updating-error.png
>
>
> Since some days I am getting alerts to update my RHJBDS 11.1.0.GA to latest versions however I could not complete anyway.
> Everyday I get a update alert with latest versions but it seems that they are not ready to be applied.
> After some moments updating the environment I got the following error and stack trace:
> {code:java}
> An error occurred while collecting items to be installed
> session context was:(profile=devstudio, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,com.jboss.devstudio.core,11.3.0.AM1-v20180125-1048-B1900
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.capabilities,11.3.0.v20180124-1725
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.central,11.3.0.AM1-v20180125-1048-B1900
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.project.examples,11.3.0.v20180124-1725
> No repository found containing: osgi.bundle,com.jboss.devstudio.core.usage.branding,11.3.0.v20180124-1725
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.capabilities.feature,11.3.0.v20180124-1725
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.feature,11.3.0.v20180125-1048
> No repository found containing: binary,com.jboss.devstudio.core.package.executable.gtk.linux.x86_64,11.3.0.AM1-v20180125-1048-B1900
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpm.feature,11.3.0.v20180125-1048
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpmdeps.feature,11.3.0.v20180124-1725
> No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.fuse.feature,11.3.0.v20180124-1725
> {code}
> I attached some screenshots with the process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months