[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23358:
---------------------------------------
Yeah, it's a one way to reproduce, but not the only one. Such an issue can be caused in more cases, this is just one way to get to it. Basically if something goes wrong with image pulling etc. Added steps to reproduce.
> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
> Key: JBIDE-23358
> URL: https://issues.jboss.org/browse/JBIDE-23358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: pod_status.png
>
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help.
> !pod_status.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23358:
----------------------------------
Steps to Reproduce:
ASSERT: Have an OpenShift connection with a project and a docker connection with a local image.
EXEC: Select the docker image and select its context menu item Deploy to OpenShift.
EXEC: Proceed through Deploy Image to OpenShift wizard but do not push image to OpenShift registry.
RESULT: Deployment fails and status of pods is Crash loop back off, but status of pod in OpenShift Explorer is still Running.
EXPECTED RESULT: Status of failed pod in OpenShift explorer reflects reality.
> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
> Key: JBIDE-23358
> URL: https://issues.jboss.org/browse/JBIDE-23358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: pod_status.png
>
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help.
> !pod_status.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23300) After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23300?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23300:
----------------------------------
Steps to Reproduce:
EXEC: Create a CDK server adapter.
ASSERT: Don't have an OpenShift connection with same username and server as the one being created by the CDK server adapter. If there is such connection, remove it. If it is present in secure storage, remove it as well.
EXEC: Start the CDK server adapter.
ASSERT: OpenShift 3 connection is created.
EXEC: Select the connection and open its context menu item Edit connection...
ASSERT: Checkbox to store credentials in secure storage is checked.
EXEC: Open secure storage and check storage of OpenShift credentials.
RESULT: There is no password stored for the connection.
EXPECTED RESULT: Password for the OpenShift connection is stored in secure storage.
was:
EXEC: Create a CDK server adapter.
ASSERT: Don't have an OpenShift connection with same username and server as the one being created by the CDK server adapter. If there is such connection, remove it.
ASSERT: There is not an entry
> After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23300
> URL: https://issues.jboss.org/browse/JBIDE-23300
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.4.2.AM3
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23382) Cannot start CDK adapter after deletion of secure storage
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23382?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23382:
----------------------------------
Description:
If I have a CDK server adapter in Servers view and I clear secure storage, after next start of DevStudio I cannot start the CDK server adapter, because password is removed and there is no choice to edit an existing credentials (username, password pair) or removing an existing one. I get an error dialog with message:
{code}
The server Container Development Environment has no password associated with it. Please open the server editor and configure the credentials.
{code}
It would be nice, if I would be allowed to edit existing credentials or at least remove it/replace by another one.
was:
If I have a CDK server adapter in Servers view and I clear secure storage, after next start of DevStudio I cannot start the CDK server adapter, because password is removed and there is no choice to edit an existing credentials (username, password pair) or removing an existing one. I get an error dialog with message:
{code}
The server Container Development Environment has no password associated with it. Please open the server editor and configure the credentials.
{code}
Workaround Description: In the CDK Server editor uncheck checkbox "Pass credentials to environment"
Workaround: Workaround Exists
> Cannot start CDK adapter after deletion of secure storage
> ---------------------------------------------------------
>
> Key: JBIDE-23382
> URL: https://issues.jboss.org/browse/JBIDE-23382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
>
> If I have a CDK server adapter in Servers view and I clear secure storage, after next start of DevStudio I cannot start the CDK server adapter, because password is removed and there is no choice to edit an existing credentials (username, password pair) or removing an existing one. I get an error dialog with message:
> {code}
> The server Container Development Environment has no password associated with it. Please open the server editor and configure the credentials.
> {code}
> It would be nice, if I would be allowed to edit existing credentials or at least remove it/replace by another one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months