[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" even though minishift & adapter are started
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25049:
-------------------------------------
Priority: Minor (was: Major)
> Connection wizard: Cannot "Discover" "Image Registry URL" even though minishift & adapter are started
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" even though minishift & adapter are started
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25049:
-------------------------------------
Summary: Connection wizard: Cannot "Discover" "Image Registry URL" even though minishift & adapter are started (was: Connection wizard: Cannot "Discover" "Image Registry URL")
> Connection wizard: Cannot "Discover" "Image Registry URL" even though minishift & adapter are started
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25049:
-------------------------------------
Description:
# ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
{code}
[adietish@localhost minishift]$ ./minishift openshift registry
No information found for 'service/docker-registry'
{code}
# ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
# ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
# EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
# EXEC: edit the OpenShift connection
# ASSERT: connection wizard shows up
# EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
# EXEC: hit "Discover"
Result
An error dialog shows up telling you no registry provider could be found
!screenshot-1.png!
was:
# ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
# ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
# EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
# EXEC: edit the OpenShift connection
# ASSERT: connection wizard shows up
# EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
# EXEC: hit "Discover"
Result
An error dialog shows up telling you no registry provider could be found
!screenshot-1.png!
> Connection wizard: Cannot "Discover" "Image Registry URL"
> ---------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet edited comment on JBIDE-24873 at 9/18/17 10:40 AM:
---------------------------------------------------------------------
When we compare what is registered for security providers in a test to what is effectively registered in a real JBDS we see this : (quoting [~rob.stryker])
{code:java}
When tracing through SecurityProviderSaslClientFactory to locate differences between a working usecase (standalone java app)_ and failing usecase (mvn test suite), I discovered that inside createSaslClient(etc)...
Successful standalone test:
1 provider, named WildFlyElytronProvider
- 185 services of various names
Failing mvn / unit test case:
9 providers:
- SUN (30 services)
- SunRSASian (9 services)
- SunEC (10 services)
- SunJSSE (16 services)
- SunJCE (131 services)
- SunJGSS (2 services)
- SunSASL (10 services)
- XMLDSIG (13 services)
- SunPCSC (1 service)
When the initial loop is over, checking clientFactoryList reveals:
Successful case: 27 Pair objects (returns LocalUserClient)
Failing mvn case: 6 pairs (returns DigestMD5Client)
Real life JBDS: 27 Pair objects (returns LocalUserClient)
{code}
So it seems this is a configuration issue in how the testsuite runs;
Please note that the testsuite use artifacts from a maven repo instead of a real JBDS installation. So this doesn't seem to be a real user problem but more a configuration issue in this particular test case which isn't worth investigating further as the current JBDS master is running just fine in the test suite.
was (Author: ehugonnet):
When we compare what is registered for security providers in a test to what is effectively registered in a real JBDS we see this : (quoting [~rob.stryker])
{code:java}
When tracing through SecurityProviderSaslClientFactory to locate differences between a working usecase (standalone java app)_ and failing usecase (mvn test suite), I discovered that inside createSaslClient(etc)...
Successful standalone test:
1 provider, named WildFlyElytronProvider
- 185 services of various names
Failing mvn / unit test case:
9 providers:
- SUN (30 services)
- SunRSASian (9 services)
- SunEC (10 services)
- SunJSSE (16 services)
- SunJCE (131 services)
- SunJGSS (2 services)
- SunSASL (10 services)
- XMLDSIG (13 services)
- SunPCSC (1 service)
When the initial loop is over, checking clientFactoryList reveals:
Successful case: 27 Pair objects (returns LocalUserClient)
Failing mvn case: 6 pairs (returns DigestMD5Client)
Real life JBDS: 27 Pair objects (returns LocalUserClient)
{code}
So it seems this is a configuration issue in how the testsuite runs;
Please note that the testsuite use artifacts from a maven repo instead of a real JBDS installation. Maybe it is missing something in startup / config.
> Add management itests to eap jbds compatibility jenkins job
> -----------------------------------------------------------
>
> Key: JBIDE-24873
> URL: https://issues.jboss.org/browse/JBIDE-24873
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> The EAP team would like us to add this test
> org.jboss.tools.as.management.itests
> to their compatibility job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
> details here: EAP7-194
> The test to be added is run here:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cc: [~rob.stryker]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet commented on JBIDE-24873:
-------------------------------------------
When we compare what is registered for security providers in a test to what is effectively registered in a real JBDS we see this : (quoting [~rob.stryker])
{code:java}
When tracing through SecurityProviderSaslClientFactory to locate differences between a working usecase (standalone java app)_ and failing usecase (mvn test suite), I discovered that inside createSaslClient(etc)...
Successful standalone test:
1 provider, named WildFlyElytronProvider
- 185 services of various names
Failing mvn / unit test case:
9 providers:
- SUN (30 services)
- SunRSASian (9 services)
- SunEC (10 services)
- SunJSSE (16 services)
- SunJCE (131 services)
- SunJGSS (2 services)
- SunSASL (10 services)
- XMLDSIG (13 services)
- SunPCSC (1 service)
When the initial loop is over, checking clientFactoryList reveals:
Successful case: 27 Pair objects (returns LocalUserClient)
Failing mvn case: 6 pairs (returns DigestMD5Client)
Real life JBDS: 27 Pair objects (returns LocalUserClient)
{code}
So it seems this is a configuration issue in how the testsuite runs;
Please note that the testsuite use artifacts from a maven repo instead of a real JBDS installation. Maybe it is missing something in startup / config.
> Add management itests to eap jbds compatibility jenkins job
> -----------------------------------------------------------
>
> Key: JBIDE-24873
> URL: https://issues.jboss.org/browse/JBIDE-24873
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> The EAP team would like us to add this test
> org.jboss.tools.as.management.itests
> to their compatibility job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
> details here: EAP7-194
> The test to be added is run here:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cc: [~rob.stryker]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25049:
----------------------------------------
Assignee: Rob Stryker
> Connection wizard: Cannot "Discover" "Image Registry URL"
> ---------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25049:
-------------------------------------
Fix Version/s: 4.5.x
> Connection wizard: Cannot "Discover" "Image Registry URL"
> ---------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25049:
-------------------------------------
Attachment: screenshot-1.png
> Connection wizard: Cannot "Discover" "Image Registry URL"
> ---------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Attachments: screenshot-1.png
>
>
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months