seed-k8s.sh doesn't work properly (404 Error) #373

hsenikosk · 2024-10-25T15:29:48Z

hsenikosk
Oct 25, 2024

Hello, I was following the steps on running the Minimum Dataspace Demo using Kubernetes.
I'm following the steps exactly as they are presented on the section 5, and everything seems to be ok until the point where we
need to seed the dataspace via the shell script, which returns 404 errors indicating some issue with ingress (?).
Every curl command I issue to localhost returns 404 HTTP error, except for the root.

e.g.

$ curl http://127.0.0.1/provider-catalog-server/cp/

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Apache/2.4.58 (Ubuntu) Server at 127.0.0.1 Port 80</address>

$ curl http://127.0.0.1/

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <!--
    Modified from the Debian original for Ubuntu
    Last updated: 2022-03-22
    See: https://launchpad.net/bugs/1966004
  -->
  <head>
 . . . 
 . . . 
<div class="content_section floating_element">
        <div class="content_section_text">
          <p>
                This is the default welcome page used to test the correct 
                operation of the Apache2 server after installation on Ubuntu systems.
                It is based on the equivalent page on Debian, from which the Ubuntu Apache
                packaging is derived.
                If you can read this page, it means that the Apache HTTP server installed at
                this site is working properly. You should <b>replace this file</b> (located at
                <tt>/var/www/html/index.html</tt>) before continuing to operate your HTTP server.
          </p>

The output of the script is:

$ ./seed-k8s.sh

Seed data to 'provider-qna' and 'provider-manufacturing'
newman

MVD+IATP

❏ Seed
↳ Create Asset 1
  POST http://127.0.0.1/provider-manufacturing/cp/api/management/v3/assets [404 Not Found, 488B, 63ms]
  1. Status is OK or conflict

↳ Create Asset 2
  POST http://127.0.0.1/provider-manufacturing/cp/api/management/v3/assets [404 Not Found, 487B, 4ms]
  2. Status is OK or conflict

. . .
. . . 

↳ Create "require sensitive" definition
  POST http://127.0.0.1/provider-manufacturing/cp/api/management/v3/contractdefinitions [404 Not Found, 487B, 4ms]
  7. Status is OK or conflict

┌─────────────────────────┬──────────────────┬──────────────────┐
│                         │         executed │           failed │
├─────────────────────────┼──────────────────┼──────────────────┤
│              iterations │                1 │                0 │
├─────────────────────────┼──────────────────┼──────────────────┤
│                requests │                7 │                0 │
├─────────────────────────┼──────────────────┼──────────────────┤
│            test-scripts │               14 │                0 │
├─────────────────────────┼──────────────────┼──────────────────┤
│      prerequest-scripts │               21 │                0 │
├─────────────────────────┼──────────────────┼──────────────────┤
│              assertions │                7 │                7 │
├─────────────────────────┴──────────────────┴──────────────────┤
│ total run duration: 333ms                                     │
├───────────────────────────────────────────────────────────────┤
│ total data received: 1.9kB (approx)                           │
├───────────────────────────────────────────────────────────────┤
│ average response time: 13ms [min: 4ms, max: 63ms, s.d.: 20ms] │
└───────────────────────────────────────────────────────────────┘

  #  failure                          detail                                                                                                                        
                                                                                                                                                                    
 1.  AssertionError                   Status is OK or conflict                                                                                                      
                                      expected 404 to be one of [ 200, 204, 409 ]                                                                                   
                                      at assertion:0 in test-script                                                                                                 
                                      inside "Seed / Create Asset 1"                                                                                                
                                                                                                                                                                    
 2.  AssertionError                   Status is OK or conflict                                                                                                      
                                      expected 404 to be one of [ 200, 204, 409 ]                                                                                   
                                      at assertion:0 in test-script                                                                                                 
                                      inside "Seed / Create Asset 2"                                                                                                
. . . 
. . .                                                               
                                                                                                                                                                    
 7.  AssertionError                   Status is OK or conflict                                                                                                      
                                      expected 404 to be one of [ 200, 204, 409 ]                                                                                   
                                      at assertion:0 in test-script                                                                                                 
                                      inside "Seed / Create "require sensitive" definition"                                                                         

. . .
. . .

Create consumer participant
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Apache/2.4.58 (Ubuntu) Server at 127.0.0.1 Port 80</address>
</body></html>


Create provider participant
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Apache/2.4.58 (Ubuntu) Server at 127.0.0.1 Port 80</address>
</body></html>

All the pods are running fine:

$ kubectl get pods -A 

NAMESPACE            NAME                                                   READY   STATUS      RESTARTS   AGE
ingress-nginx        ingress-nginx-admission-create-mz7vp                   0/1     Completed   0          3m24s
ingress-nginx        ingress-nginx-admission-patch-mmbjl                    0/1     Completed   0          3m24s
ingress-nginx        ingress-nginx-controller-867bbcb78-225h4               1/1     Running     0          3m24s
mvd                  consumer-controlplane-677f95b875-xvnwm                 1/1     Running     0          66s
mvd                  consumer-dataplane-59c6859656-pxhck                    1/1     Running     0          50s
mvd                  consumer-identityhub-877f556df-787rf                   1/1     Running     0          66s
mvd                  consumer-postgres-5546fb44f4-tlkww                     1/1     Running     0          117s
mvd                  consumer-sts-67f5b9d88d-fm65x                          1/1     Running     0          92s
mvd                  consumer-vault-0                                       1/1     Running     0          116s
mvd                  provider-catalog-server-75754dc775-clrpx               1/1     Running     0          66s
mvd                  provider-identityhub-75f477c4f6-wdcm7                  1/1     Running     0          66s
mvd                  provider-manufacturing-controlplane-7f6fbd99d9-wwh4z   1/1     Running     0          66s
mvd                  provider-manufacturing-dataplane-fdc6f9f4b-nmw8m       1/1     Running     0          50s
mvd                  provider-postgres-56fd4c7cd-77vt8                      1/1     Running     0          117s
mvd                  provider-qna-controlplane-6b64d9b5b9-xzq6r             1/1     Running     0          66s
mvd                  provider-qna-dataplane-865879db7d-w2lbc                1/1     Running     0          50s
mvd                  provider-sts-b7bf7498d-n9lvz                           1/1     Running     0          92s
mvd                  provider-vault-0                                       1/1     Running     0          115s

If I try to see the logs of the ingress pod:

$ kubectl logs ingress-nginx-controller-867bbcb78-225h4 -n ingress-nginx

-------------------------------------------------------------
NGINX Ingress controller
  Release:       v1.12.0-beta.0
  Build:         80154a3694b52736c88de408811ebd1888712520
  Repository:    https://github.com/kubernetes/ingress-nginx
  nginx version: nginx/1.25.5
-------------------------------------------------------------
W1025 14:41:00.527114      10 client_config.go:659] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1025 14:41:00.527798      10 main.go:205] "Creating API client" host="https://10.96.0.1:443"
I1025 14:41:00.530835      10 main.go:248] "Running in Kubernetes cluster" major="1" minor="31" git="v1.31.0" state="clean" commit="9edcffcde5595e8a5b1a35f88c421764e575afce" platform="linux/amd64"
I1025 14:41:00.680522      10 main.go:101] "SSL fake certificate created" file="/etc/ingress-controller/ssl/default-fake-certificate.pem"
. . . 
. . .
I1025 14:44:01.813646      10 status.go:304] "updating Ingress status" namespace="mvd" ingress="provider-did-ingress" currentValue=null newValue=[{"hostname":"localhost"}]
I1025 14:44:01.813699      10 status.go:304] "updating Ingress status" namespace="mvd" ingress="provider-catalog-server-ingress" currentValue=null newValue=[{"hostname":"localhost"}]
I1025 14:44:01.813843      10 status.go:304] "updating Ingress status" namespace="mvd" ingress="consumer-identityhub-ingress" currentValue=null newValue=[{"hostname":"localhost"}]
I1025 14:44:01.813950      10 status.go:304] "updating Ingress status" namespace="mvd" ingress="consumer-did-ingress" currentValue=null newValue=[{"hostname":"localhost"}]
. . .
. . .
I1025 14:44:02.613857      10 event.go:377] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"mvd", Name:"provider-manufacturing-ingress", UID:"d60456dc-ba58-4c72-b1f5-9ae6fa85576a", APIVersion:"networking.k8s.io/v1", ResourceVersion:"1400", FieldPath:""}): type: 'Normal' reason: 'Sync' Scheduled for sync
I1025 14:44:02.813395      10 event.go:377] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"mvd", Name:"provider-identityhub-ingress", UID:"49b2a705-0b65-4991-a062-d9028b7952f1", APIVersion:"networking.k8s.io/v1", ResourceVersion:"1404", FieldPath:""}): type: 'Normal' reason: 'Sync' Scheduled for sync


W1025 14:44:05.156216      10 controller.go:1109] Error obtaining Endpoints for Service "mvd/provider-manufacturing-vault": no object matching key "mvd/provider-manufacturing-vault" in local store
W1025 14:44:05.159026      10 controller.go:1109] Error obtaining Endpoints for Service "mvd/provider-qna-vault": no object matching key "mvd/provider-qna-vault" in local store
W1025 14:44:08.487961      10 controller.go:1109] Error obtaining Endpoints for Service "mvd/provider-manufacturing-vault": no object matching key "mvd/provider-manufacturing-vault" in local store
W1025 14:44:08.488073      10 controller.go:1109] Error obtaining Endpoints for Service "mvd/provider-qna-vault": no object matching key "mvd/provider-qna-vault" in local store

I'm using the following:
-0.10.0-SNAPSHOT version (I have also tried rolling back to a previous version of the project (0.8.0, 0.8.1, 0.9.0, 0.9.1).
-Gradle 8.10
-Launcher JVM: 17.0.12 (Ubuntu 17.0.12+7-Ubuntu-1ubuntu224.04)
-kind v0.24.0 go1.22.6 linux/amd64
-Newman 6.2.1

I would appreciate any kind of help on why this is happening. Maybe I'm doing something wrong (since I'm quite new to all of this).
Thank you in advance!

paullatzelsperger · 2024-10-25T16:34:36Z

paullatzelsperger
Oct 25, 2024
Collaborator

i'm kind of curious where the Apache Webserver log comes from? One thing you could try is replace 127.0.0.1 with localhost or vice versa.
Also, please make sure that you are creating the KinD Cluster with the supplied config in deployment/kind.config.yaml.

I just verified this on a Debian installation, on macOS and our CI runs Ubuntu runners. Note that Windows is unsupported.

The problem seems to lie not with the seed script, but with your local machine or config thereof, so there is anything we can do, we certainly can't debug your setup for you :)

I would try to set this up in a fresh linux VM. In any event I'm closing this.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

seed-k8s.sh doesn't work properly (404 Error) #373

{{title}}

Replies: 1 comment

{{title}}

Select a reply

seed-k8s.sh doesn't work properly (404 Error) #373

hsenikosk Oct 25, 2024

Replies: 1 comment

paullatzelsperger Oct 25, 2024 Collaborator

hsenikosk
Oct 25, 2024

paullatzelsperger
Oct 25, 2024
Collaborator