[JBoss JIRA] (JBIDE-22592) Application wizard: Failed even though provided required value to parameters
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22592?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22592:
-------------------------------
Story Points: 6
> Application wizard: Failed even though provided required value to parameters
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22592
> URL: https://issues.jboss.org/browse/JBIDE-22592
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBoss OpenShift 3 Tools 3.3.0.Final-v20160610-1836-B1369
> JBoss OpenShift 3 Tools Developer Resources 3.3.0.Final-v20160610-1836-B1369
> Eclipse: Neon Milestone 7 (4.6.0M7)
> Reporter: Xia Zhao
> Assignee: Jeff MAURY
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.1.AM2
>
> Attachments: application-template-stibuild.json, fails-even-though-required-value-provided.png, Screenshot from 2016-06-12 01-59-02.png
>
>
> Create app from the local template in attachment,give required value to parameter "xiazhao_checkfail" inside new-app wizard, get error message after clicking on the "Next>" button:
> Template "ruby-helloworld-sample" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified
> Could not create resource ruby-helloworld-sample in namespace 'xiazhao-1': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Template \"ruby-helloworld-sample\" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","reason":"Invalid","details":{"name":"ruby-helloworld-sample","kind":"Template","causes":[{"reason":"FieldValueRequired","message":"Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","field":"template.parameters[5]"}]},"code":422}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22592) Application wizard: Failed even though provided required value to parameters
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22592?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22592:
-------------------------------
Sprint: devex #117 July 2016
> Application wizard: Failed even though provided required value to parameters
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22592
> URL: https://issues.jboss.org/browse/JBIDE-22592
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBoss OpenShift 3 Tools 3.3.0.Final-v20160610-1836-B1369
> JBoss OpenShift 3 Tools Developer Resources 3.3.0.Final-v20160610-1836-B1369
> Eclipse: Neon Milestone 7 (4.6.0M7)
> Reporter: Xia Zhao
> Assignee: Jeff MAURY
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.1.AM2
>
> Attachments: application-template-stibuild.json, fails-even-though-required-value-provided.png, Screenshot from 2016-06-12 01-59-02.png
>
>
> Create app from the local template in attachment,give required value to parameter "xiazhao_checkfail" inside new-app wizard, get error message after clicking on the "Next>" button:
> Template "ruby-helloworld-sample" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified
> Could not create resource ruby-helloworld-sample in namespace 'xiazhao-1': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Template \"ruby-helloworld-sample\" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","reason":"Invalid","details":{"name":"ruby-helloworld-sample","kind":"Template","causes":[{"reason":"FieldValueRequired","message":"Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","field":"template.parameters[5]"}]},"code":422}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22603:
-------------------------------
Story Points: 10
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22653:
-------------------------------
Sprint: devex #117 July 2016
> Can't scale pods down to 0
> --------------------------
>
> Key: JBIDE-22653
> URL: https://issues.jboss.org/browse/JBIDE-22653
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Labels: explorer, openshift_v3
> Fix For: 4.4.1.AM2
>
>
> The scale to... menu lets you scale to any number of replicas, but you can't go down to 0.
> The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment."
> My take is we should have the same behavior in eclipse
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-22603 at 6/30/16 4:46 AM:
-------------------------------------------------------------
OK seems I am able to reproduce the problem with a single watched connection. Seems the web socket is closed or timeout expired after a certain period.
Anyway, reading the code, I found several pbs:
* watchers are registered using Openshift project as key so if two different connections have the same project name, ....
* there is one job per project and resource type where the REST client allows to have a single watcher for multiple resource type
* in some rare case, the initial watcher cannot be started for a resource type but this is hard to reproduce and may disappear when a single watcher per project will be set
Given the amount of work, I propose to delay this issue to the next sprint
was (Author: jeffmaury):
OK seems I am able to reproduce the problem with a single watched connection. Seems the web socket is closed or timeout expired after a certain period.
Anyway, reading the code, I found several pbs:
* watchers are registered using Openshift project as key so if two different connections have the same project name, ....
* there is one job per project and resource type where the REST client allows to have a single watcher for multiple resource type
* in some rare case, the initial watcher cannot be started for a resource type but this is hard to reproduce and may disappear when a single watcher per project will be set
Given the amount of work, I propose to delay this issue to the next one
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21745:
---------------------------------------
I'm not sure I understand. Are you saying it wouldn't work even if I had the correct password? I'm sorry, but Rob didn't give me the passwords, so I guess I can't really know if it fails for me because of wrong password or wrong login. But in any case, I don't get the error Rob mentioned.
> Unable to download EAP 7 Beta runtime using username without "@redhat.com"
> --------------------------------------------------------------------------
>
> Key: JBIDE-21745
> URL: https://issues.jboss.org/browse/JBIDE-21745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Final, 4.3.1.CR1
> Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.x
>
> Attachments: rh-developer-credentials.png
>
>
> Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page.
> Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown:
> {noformat}
> You Entered All Necessary Information
> Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
> {noformat}
> But even after that I'm unable to download that runtime with the same credentials.
> Using login with "@redhat.com" I'm able to download the runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ]
David Hladky commented on JBIDE-21745:
--------------------------------------
The problem is not the password. The password is the one you used during registration of your account. The problem is the user name, because it does not match the one you expect. I hope it to be fixed today, but until this happen, you can go here https://www.redhat.com/wapps/sso/lostPassword.html and use "Forgot your login". You will receive your login name by e-mail and with it you will be able to finish the download.
> Unable to download EAP 7 Beta runtime using username without "@redhat.com"
> --------------------------------------------------------------------------
>
> Key: JBIDE-21745
> URL: https://issues.jboss.org/browse/JBIDE-21745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Final, 4.3.1.CR1
> Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.x
>
> Attachments: rh-developer-credentials.png
>
>
> Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page.
> Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown:
> {noformat}
> You Entered All Necessary Information
> Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
> {noformat}
> But even after that I'm unable to download that runtime with the same credentials.
> Using login with "@redhat.com" I'm able to download the runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22603:
------------------------------------
OK seems I am able to reproduce the problem with a single watched connection. Seems the web socket is closed or timeout expired after a certain period.
Anyway, reading the code, I found several pbs:
* watchers are registered using Openshift project as key so if two different connections have the same project name, ....
* there is one job per project and resource type where the REST client allows to have a single watcher for multiple resource type
* in some rare case, the initial watcher cannot be started for a resource type but this is hard to reproduce and may disappear when a single watcher per project will be set
Given the amount of work, I propose to delay this issue to the next one
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22639) Opening an Openshift3 server adapter when connection does not exists anymore causes NPE
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22639?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22639 at 6/30/16 4:03 AM:
-------------------------------------------------------------------
[~scabanovich] IMHO the problem is not within VariablesHelper in this particular case. The root cause is that there's no connection for the editor. We should therefore display an appropriate error. That's what I did in https://github.com/jbosstools/jbosstools-openshift/pull/1243
was (Author: adietish):
[~scabanovich] IMHO the problem is not within VariablesHelper in this particular case. The root cause is that there's no connection for the editor. We should therefore display an appropriate error and keep the editor section disabled. That's what I did in https://github.com/jbosstools/jbosstools-openshift/pull/1243
> Opening an Openshift3 server adapter when connection does not exists anymore causes NPE
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22639
> URL: https://issues.jboss.org/browse/JBIDE-22639
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Fix For: 4.4.1.AM2
>
> Attachments: non-existent-workspace-reference.png, screenshot-1.png
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: NPE is thrown and dialog is displayed (see [^screenshot-1.png])
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months