[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
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}
You can achieve that by :
* have server adapter stopped, minishift started
* logging into your cdk with oc as "admin" and then:
{code}
oc project default
oc delete svc docker-registry
{code}
Once the service is deleted you need to start the cdk.
# 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!
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
was:
# 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}
You can achieve that by logging into your cdk with oc as "admin" and then:
{code}
oc project default
oc delete svc docker-registry
{code}
Once the service is deleted you need to restart the cdk.
# 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!
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both 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
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> 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}
> You can achieve that by :
> * have server adapter stopped, minishift started
> * logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to start the cdk.
> # 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!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
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" as if there was no minishift nor adapter (even though both are started)
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}
You can achieve that by logging into your cdk with oc as "admin" and then:
{code}
oc project default
oc delete svc docker-registry
{code}
Once the service is deleted you need to restart the cdk.
# 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!
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
was:
# 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}
You can achieve that by logging into your cdk with oc as "admin" and then:
{code}
oc project default
oc delete svc 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!
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both 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
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> 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}
> You can achieve that by logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to restart the cdk.
> # 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!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
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" as if there was no minishift nor adapter (even though both are started)
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}
You can achieve that by logging into your cdk with oc as "admin" and then:
{code}
oc project default
oc delete svc 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!
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
was:
# 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!
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both 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
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> 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}
> You can achieve that by logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc 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!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24764:
------------------------------------
Current status:
!fuse-master-job-on-dev-platform-jenkins.png|thumbnail! vs. !fuse-master-job-on-fusesource-jenkins.png|thumbnail!
So now that the job configs are nearly identical on both servers, we should compare the slave configs to see how they differ. Insufficient ram? disk? other deltas?
> migrate fusetools job from fusesource jenkins to dev-platform jenkins
> ---------------------------------------------------------------------
>
> Key: JBIDE-24764
> URL: https://issues.jboss.org/browse/JBIDE-24764
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM3
>
> Attachments: fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png
>
>
> {quote}
> Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job"
> for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI
> don't know exactly pros and cons, Lars reported the advantages:
> * more slaves
> * faster
> * easier to manage with the other JBoss Tools job
> the issue is that it is not working:
> * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded
> * one test is failing
> * and a third issue now seems that it goes into timeout{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24764:
-------------------------------
Attachment: fuse-master-job-on-dev-platform-jenkins.png
> migrate fusetools job from fusesource jenkins to dev-platform jenkins
> ---------------------------------------------------------------------
>
> Key: JBIDE-24764
> URL: https://issues.jboss.org/browse/JBIDE-24764
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM3
>
> Attachments: fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png
>
>
> {quote}
> Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job"
> for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI
> don't know exactly pros and cons, Lars reported the advantages:
> * more slaves
> * faster
> * easier to manage with the other JBoss Tools job
> the issue is that it is not working:
> * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded
> * one test is failing
> * and a third issue now seems that it goes into timeout{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24764:
-------------------------------
Attachment: fuse-master-job-on-fusesource-jenkins.png
> migrate fusetools job from fusesource jenkins to dev-platform jenkins
> ---------------------------------------------------------------------
>
> Key: JBIDE-24764
> URL: https://issues.jboss.org/browse/JBIDE-24764
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM3
>
> Attachments: fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png
>
>
> {quote}
> Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job"
> for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI
> don't know exactly pros and cons, Lars reported the advantages:
> * more slaves
> * faster
> * easier to manage with the other JBoss Tools job
> the issue is that it is not working:
> * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded
> * one test is failing
> * and a third issue now seems that it goes into timeout{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months