search

openshift / open-service-broker-sdk

A starting point for creating service brokers implementing the Open Service Broker API
Apache License 2.0
31 stars 33 forks source link

./provision.sh - the server could not find the requested resource #16

Closed debianmaster closed 4 years ago

debianmaster commented 7 years ago

After installing brokersdk i got this error when doing provision.sh

[root@ip-172-31-39-107 test-scripts]# ./provision.sh 
Internal Server Error: "/broker/sdkbroker.broker.io/v2/service_instances/d5d242c1-164e-11e7-8714-0242ac110002": the server could not find the requested resource
Internal Server Error: "/apis/sdkbroker.broker.k8s.io/v1alpha1/namespaces/brokersdk/serviceinstances": the server could not find the requested resource

Broker logs from begninng. etcd seems to be fine.

[root@ip-172-31-39-107 test-scripts]# oc logs -f brokersdk-zs3rf -c brokersdk
ERROR: logging before flag.Parse: I0513 17:28:48.788990       1 server.go:107] Preparing to run the broker API server
ERROR: logging before flag.Parse: I0513 17:28:48.790096       1 server.go:110] Setting up secure serving options
ERROR: logging before flag.Parse: I0513 17:28:49.111959       1 serving.go:270] Generated self-signed cert (/data/apiserver.crt, /data/apiserver.key)
ERROR: logging before flag.Parse: I0513 17:28:49.605999       1 apiserver.go:108] Creating the Broker API server
ERROR: logging before flag.Parse: I0513 17:28:49.607302       1 apiserver.go:125] Finished installing API groups
ERROR: logging before flag.Parse: I0513 17:28:49.607323       1 apiserver.go:127] Installing service broker api endpoints at /broker/sdkbroker.broker.io
ERROR: logging before flag.Parse: I0513 17:28:49.607771       1 apiserver.go:135] Finished installing broker api endpoints
ERROR: logging before flag.Parse: I0513 17:28:49.607969       1 server.go:172] Running the broker API server
ERROR: logging before flag.Parse: I0513 17:28:49.607989       1 serve.go:85] Serving securely on 0.0.0.0:8443
ERROR: logging before flag.Parse: I0513 17:28:49.608391       1 controller.go:82] Starting broker controller
2017-05-13T17:28:49.635320276Z AUDIT: id="cc14378a-4ac8-40d2-bba7-a97b1a0c5475" ip="::1" method="GET" user="system:apiserver" groups="\"system:masters\"" as="<self>" asgroups="<lookup>" namespace="brokersdk" uri="/apis/sdkbroker.broker.k8s.io/v1alpha1/namespaces/brokersdk/serviceinstances?resourceVersion=0"
2017-05-13T17:28:49.635608586Z AUDIT: id="cc14378a-4ac8-40d2-bba7-a97b1a0c5475" response="200"
2017-05-13T17:28:49.636472063Z AUDIT: id="78f2f2ea-6935-4bd1-b996-0e0baa989857" ip="::1" method="GET" user="system:apiserver" groups="\"system:masters\"" as="<self>" asgroups="<lookup>" namespace="brokersdk" uri="/apis/sdkbroker.broker.k8s.io/v1alpha1/namespaces/brokersdk/serviceinstances?resourceVersion=1&timeoutSeconds=582&watch=true"
2017-05-13T17:28:49.636753739Z AUDIT: id="78f2f2ea-6935-4bd1-b996-0e0baa989857" response="200"
2017-05-13T17:30:33.452500248Z AUDIT: id="112f2934-9889-4c42-9a7a-3ccb64d77e6f" ip="172.31.39.107" method="PUT" user="system:anonymous" groups="\"system:unauthenticated\"" as="<self>" asgroups="<lookup>" namespace="<none>" uri="/broker/sdkbroker.broker.io/v2/service_instances/d5d242c1-164e-11e7-8714-0242ac110002"
ERROR: logging before flag.Parse: E0513 17:30:33.467624       1 webhook.go:185] Failed to make webhook authorizer request: the server could not find the requested resource
2017-05-13T17:30:33.467647816Z AUDIT: id="112f2934-9889-4c42-9a7a-3ccb64d77e6f" response="500"
ERROR: logging before flag.Parse: E0513 17:30:33.467761       1 errors.go:80] the server could not find the requested resource
2017-05-13T17:30:33.543663348Z AUDIT: id="2f05233e-d0fd-4146-b703-fe2732294a44" ip="172.31.39.107" method="GET" user="system:anonymous" groups="\"system:unauthenticated\"" as="<self>" asgroups="<lookup>" namespace="brokersdk" uri="/apis/sdkbroker.broker.k8s.io/v1alpha1/namespaces/brokersdk/serviceinstances"
2017-05-13T17:30:33.549238518Z AUDIT: id="2f05233e-d0fd-4146-b703-fe2732294a44" response="500"
ERROR: logging before flag.Parse: E0513 17:30:33.549220       1 webhook.go:185] Failed to make webhook authorizer request: the server could not find the requested resource
ERROR: logging before flag.Parse: E0513 17:30:33.549381       1 errors.go:80] the server could not find the requested resource
bparees commented 7 years ago

what verision is your k8s/openshift cluster?

debianmaster commented 7 years ago

this is 3.6 alpha origin

pmorie commented 7 years ago

I will take a look at this when i get a chance, probably will not be until tomorrow

debianmaster commented 7 years ago

@pmorie thanks

openshift-bot commented 4 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 4 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 4 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 4 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/open-service-broker-sdk/issues/16#issuecomment-706452042): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.