[
https://issues.jboss.org/browse/JBIDE-22596?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-22596 at 6/17/16 6:11 AM:
----------------------------------------------------------------
Validation is still working, somehow. When I am trying to create a new connection and fill
in all details (e.g. select OS 3, use server
"https://console.engint.openshift.com" and OAuth with custom string as a token)
and then I fill in registry URL to some random string, not in compliance with validator,
there is an validation error in connection wizard header.
Attached screencast from Andre to see how it is reproducible:
https://www.youtube.com/watch?v=qiKBIRDqkKw
was (Author: mlabuda):
Validation is still working, somehow. When I am trying to create a new connection and fill
in all details (e.g. select OS 3, use server
"https://console.engint.openshift.com" and OAuth with custom string as a token)
and then I fill in registry URL to some random string, not in compliance with validator,
there is an validation error in connection wizard header.
Impossible to connect to OpenShift when landrush is enabled (instead
of xip.io)
-------------------------------------------------------------------------------
Key: JBIDE-22596
URL:
https://issues.jboss.org/browse/JBIDE-22596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Final
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Blocker
Labels: respin-b
Fix For: 4.4.0.Final
When landrush is enabled on the CDK, the Docker registry url is
https://hub.openshift.openshift.cdk, it's stored in the OpenShift connection
properties when launching the CDK server adapter.
However, URL validation fails on that url, thus preventing the Connection wizard to
finish, because *.cdk urls are not valid. Indeed cdk is not a known/valid TLD, according
to Apache's commons UrlValidator
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)