[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov updated JBIDE-22803:
------------------------------------
Story Points: 8
> When OS projects are created and deleted, seems Openshift explorer restores non existing values
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22803
> URL: https://issues.jboss.org/browse/JBIDE-22803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Dmitry Bocharov
> Labels: explorer, openshift, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: screenshot-1.png
>
>
> EXEC: create an Openshift project
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> ASSERT: wait for the pod to be available
> EXEC: delete the Openshit project
> EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists)
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> EXEC: expand the nodejs-example node
> ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov updated JBIDE-22803:
------------------------------------
Sprint: devex #118 July 2016
> When OS projects are created and deleted, seems Openshift explorer restores non existing values
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22803
> URL: https://issues.jboss.org/browse/JBIDE-22803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Dmitry Bocharov
> Labels: explorer, openshift, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: screenshot-1.png
>
>
> EXEC: create an Openshift project
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> ASSERT: wait for the pod to be available
> EXEC: delete the Openshit project
> EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists)
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> EXEC: expand the nodejs-example node
> ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov reassigned JBIDE-22803:
---------------------------------------
Assignee: Dmitry Bocharov
> When OS projects are created and deleted, seems Openshift explorer restores non existing values
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22803
> URL: https://issues.jboss.org/browse/JBIDE-22803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Dmitry Bocharov
> Labels: explorer, openshift, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: screenshot-1.png
>
>
> EXEC: create an Openshift project
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> ASSERT: wait for the pod to be available
> EXEC: delete the Openshit project
> EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists)
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> EXEC: expand the nodejs-example node
> ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3961:
------------------------------
Attachment: jrichter_install.log
> CDK installation failed with progress bar stuck in 99%
> ------------------------------------------------------
>
> Key: JBDS-3961
> URL: https://issues.jboss.org/browse/JBDS-3961
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Environment: h3. Operating System:
> Windows 10 Pro 64 Bit
> h3. Devstudio version
> Devstudio 1.0 GA
> Reporter: Budh Ram Gurung
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: cdk
> Attachments: dev_studio_installation.PNG, install.log, jrichter_install.log
>
>
> I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations.
> Observations:
> CDK installation stuck in 99% with "failed" mark.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3961:
------------------------------
Priority: Blocker (was: Major)
> CDK installation failed with progress bar stuck in 99%
> ------------------------------------------------------
>
> Key: JBDS-3961
> URL: https://issues.jboss.org/browse/JBDS-3961
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Environment: h3. Operating System:
> Windows 10 Pro 64 Bit
> h3. Devstudio version
> Devstudio 1.0 GA
> Reporter: Budh Ram Gurung
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: cdk
> Attachments: dev_studio_installation.PNG, install.log
>
>
> I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations.
> Observations:
> CDK installation stuck in 99% with "failed" mark.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-814) Extend the scope of projects used for testing deployment/undeployment
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-814:
---------------------------------------
Summary: Extend the scope of projects used for testing deployment/undeployment
Key: JBTIS-814
URL: https://issues.jboss.org/browse/JBTIS-814
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.3.1.Final
Reporter: Andrej Podhradsky
Assignee: Tomáš Sedmík
Priority: Critical
Fix For: 4.3.1.Final
Extend the scope of projects used for testing deployment/undeployment. It seems that projects which were imported a an existing maven project cannot be successfully deployed/undeployed. Please see FUSETOOLS-1997
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months