Advice on running openshift on a VM?

[Karen Schoener]

Hi, 

I was reviewing the list of tickets that are good first issues.
https://github.com/skupperproject/skupper/labels/good%20first%20issue

I wanted to ask for advice on how to reproduce this ticket:

skupper init with ingress set to empty string makes LoadBalancer as the default on Openshift #1424

https://github.com/skupperproject/skupper/issues/1424

If I ran minishift on my VM and started skupper up, would that be a reasonable way to investigate this Openshift issue?

Minishift is new to me, so I thought I'd doublecheck...

Thanks, Karen

[Ted Ross]

I don't have a minishift handy to try on, but if you do a bare "skupper init" on minishift, you can look to see if routes are created ("oc get routes").  If routes are supported, then the issue is likely to be reproducible.

-Ted

--
You received this message because you are subscribed to the Google Groups "Skupper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skupper+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/skupper/DM6PR15MB2268B5D903DA6A4844B3771585112%40DM6PR15MB2268.namprd15.prod.outlook.com.

[Danilo Hashimoto]

Karen,

Minishift, if I'm not mistaken, is OpenShift 3.11.  I'd suggest you look into CRC/OpenShift Local, instead, which is based on OpenShift 4.x:

https://developers.redhat.com/products/openshift-local/overview

Regards,

  Danilo

To view this discussion on the web visit https://groups.google.com/d/msgid/skupper/CALo7S0yaZHosLjE07FbGgdYDAnxyczanC%3D3GdLOt%3Dr6Q8pQzRw%40mail.gmail.com.

[Karen Schoener]

Hi, 

Thanks very much for the info.

I installed openshift-local on my fedora VM.

I ran the steps in this "oc hello world".

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html/networking/configuring-routes

The "oc hello world" example ended with creating an oc route.

[kschoener@fedora bin]$ oc get routes

NAME              HOST/PORT                                          PATH   SERVICES          PORT   TERMINATION   WILDCARD

hello-openshift   hello-openshift-hello-openshift.apps-crc.testing          hello-openshift   8080                 None

I installed skupper:

[kschoener@fedora ~]$ skupper init --ingress 'route'

Waiting for status...

Skupper status is not loaded yet.

Skupper is now installed in namespace 'hello-openshift'.  Use 'skupper status' to get more information.

I noticed that skupper status shows as pending:

[kschoener@fedora ~]$ skupper status -v

Status pending...

However, I believe this environment is good enough for me to investigate ticket #1424.

skupper init with ingress set to empty string makes LoadBalancer as the default on Openshift #1424

https://github.com/skupperproject/skupper/issues/1424

At some point, it would be interesting to understand why the skupper router is not fully coming up.  I noticed some 'bad certificate' logs from skupper-router.  

But, for now, I will proceed with investigating ticket #1424.

Thanks, Karen

p.s. Below, I've pasted some info about my skupper state.

oc get configmap shows:

[kschoener@fedora bin]$ oc get configmap

NAME                       DATA   AGE

kube-root-ca.crt           1      74m

openshift-service-ca.crt   1      74m

skupper-internal           1      9m1s

skupper-network-status     1      8m47s

skupper-sasl-config        1      9m4s

skupper-services           0      9m1s

skupper-site               14     9m4s

skupper-site-leader        0      8m47s

oc get pods shows:

[kschoener@fedora bin]$ oc get pods

NAME                                          READY   STATUS    RESTARTS   AGE

hello-openshift                               1/1     Running   0          73m

skupper-router-7b6c855954-gc49c               2/2     Running   0          9m6s

skupper-service-controller-8486b5d9c8-j7ctp   1/1     Running   0          9m5s

oc logs skupper-router-7b6c855954-gc49c shows some indications about bad certificate:

2024-04-25 22:49:17.049253 +0000 SERVER (info) [C12] Accepted connection to :5671 from 10.217.0.85:48406

2024-04-25 22:49:17.075831 +0000 SERVER (info) [C14] Accepted connection to :5671 from 10.217.0.85:48422

2024-04-25 22:49:17.167908 +0000 SERVER (info) [C15] Accepted connection to :5671 from 10.217.0.85:48428

2024-04-25 22:49:17.187829 +0000 SERVER (error) [C11] Connection from 10.217.0.85:48402 (to :5671) failed: amqp:connection:framing-error SSL Failure: error:0A000412:SSL routines::sslv3 alert bad certificate

---

From: Danilo Hashimoto <hort...@gmail.com>
Sent: Wednesday, April 24, 2024 8:14 AM
To: Ted Ross <therma...@gmail.com>
Cc: Karen Schoener <Karen.S...@ibm.com>; sku...@googlegroups.com <sku...@googlegroups.com>
Subject: [EXTERNAL] Re: Advice on running openshift on a VM?

 

Karen, Minishift, if I'm not mistaken, is OpenShift 3. 11. I'd suggest you look into CRC/OpenShift Local, instead, which is based on OpenShift 4. x: https: //developers. redhat. com/products/openshift-local/overview Regards, DaniloOn Tue,

ZjQcmQRYFpfptBannerStart

This Message Is From an Untrusted Sender

You have not previously corresponded with this sender.

Report Suspicious

 

ZjQcmQRYFpfptBannerEnd

[Noe Luaces]

Hi Karen, 

Just a few ideas to see if they can help us for this issue:

- "Status pending..." means that the skupper-network-status configmap is not existent or it is incomplete. In your case, it seems the latter. Could you check the config-sync logs (config-sync is a sidecar container running with the router container)?

- could you check the output of "skupper debug events" if there is any error?

- which skupper version are you using? ("skupper version")

- If you still do not find anything clear and if you are testing with skupper main version, could you set the skupper router to 2.6.0 version by running 

export QDROUTERD_IMAGE=quay.io/skupper/skupper-router:2.6.0 before skupper init and try again? 

Hope that helps,

Noe Luaces

To view this discussion on the web visit https://groups.google.com/d/msgid/skupper/DM6PR15MB2268552E0E77EFE81902D23985162%40DM6PR15MB2268.namprd15.prod.outlook.com.

[Karen Schoener]

Hi, 

Thanks for the advice!

I presumed that my openshift-local install was suspect.

I created a larger VM.  I installed openshift-local on that VM.  Skupper installed without issue.

Sorry for the false alarm...  I am all set.

I will start investigating ticket #1424.

skupper init with ingress set to empty string makes LoadBalancer as the default on Openshift #1424

https://github.com/skupperproject/skupper/issues/1424

Thanks again, Karen

[kschoener@c20928v1 ~]$ skupper init --ingress 'route'

Waiting for status...

Skupper status is not loaded yet.

Skupper is now installed in namespace 'hello-openshift'.  Use 'skupper status' to get more information.

[kschoener@c20928v1 ~]$ skupper status

Skupper is enabled for namespace "hello-openshift". It is not connected to any other sites. It has no exposed services.

[kschoener@c20928v1 ~]$

---

From: Noe Luaces <nlu...@redhat.com>
Sent: Friday, April 26, 2024 9:30 AM
To: Karen Schoener <Karen.S...@ibm.com>
Cc: Danilo Hashimoto <hort...@gmail.com>; Ted Ross <therma...@gmail.com>; sku...@googlegroups.com <sku...@googlegroups.com>

Subject: [EXTERNAL] Re: Advice on running openshift on a VM?

 

This Message Is From an External Sender

This message came from outside your organization.

Report Suspicious

 

This Message Is From an Untrusted Sender

You have not previously corresponded with this sender.

Report Suspicious