SUSE / stratos

SUSE Stratos: Web-based Console UI for Cloud Foundry and Kubernetes
Apache License 2.0
15 stars 12 forks source link

Incomplete information on "Workloads > kubecf" (no pods) #386

Open svollath opened 4 years ago

svollath commented 4 years ago

Frontend Deployment type

Backend (Jet Stream) Deployment type

SUSE CaaSP4 added as "CaaSP Endpoint" (Name: CaaSP4-tf4)

Expected behaviour

When I visit "Workloads > kubecf", status for pods is shown like for other workloads.

Actual behaviour

While information for kubecf is filled, it's incomplete - e.g. for pods it reports "0".

Steps to reproduce the behavior

Log output covering before error and any error statements

kubectl logs stratos-0 proxy -n stratos snippet

...
    stemcells:
    - alias: default
      os: ubuntu-xenial
      version: "621.59"
' 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: yaml: did not find expected comment or line break 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: yaml: line 11: could not find expected ':' 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: yaml: did not find expected comment or line break 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: Object 'Kind' is missing in '# Source: kubecf/templates/eirini.yaml
# Create the bits secret
' 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: Object 'Kind' is missing in '# Source: kubecf/templates/ingress.yaml
# If the ingress feature (ingress-controller) is not enabled, create public services to allow
# public ingress to the cluster.
' 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: Object 'Kind' is missing in '# Source: kubecf/templates/ops.yaml
# This template creates a ConfigMap for each ops file under assets/operations.
' 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: Object 'Kind' is missing in '# Source: kubecf/templates/properties.yaml
# This ConfigMap creates an ops-file containing the user provided properties.
' 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: Object 'Kind' is missing in '# Source: kubecf/templates/sync-integration-tests.yaml
# SITS only makes sense when using Diego, for this reason, we only enable it if Eirini is not
# enabled.
' 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: no kind "BOSHDeployment" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery@v0.0.0-20191001043732-d647ddbd755f/pkg/runtime/scheme.go:101" 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: no kind "QuarksJob" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery@v0.0.0-20191001043732-d647ddbd755f/pkg/runtime/scheme.go:101" 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: no kind "QuarksJob" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery@v0.0.0-20191001043732-d647ddbd755f/pkg/runtime/scheme.go:101" 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: no kind "QuarksSecret" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery@v0.0.0-20191001043732-d647ddbd755f/pkg/runtime/scheme.go:101" 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: no kind "QuarksSecret" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery@v0.0.0-20191001043732-d647ddbd755f/pkg/runtime/scheme.go:101" 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: no kind "QuarksSecret" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery@v0.0.0-20191001043732-d647ddbd755f/pkg/runtime/scheme.go:101" 
ERRO[Mon Jun  8 13:56:59 UTC 2020] Helm Manifest Parser: Error while decoding YAML object. Err was: no kind "QuarksStatefulSet" is registered for version "quarks.cloudfoundry.org/v1alpha1" in scheme "k8s.io/apimachinery@v0.0.0-20191001043732-d647ddbd755f/pkg/runtime/scheme.go:101"
WARN[Mon Jun  8 13:56:59 UTC 2020] Passthrough response: URL: https://tf4-c4-lb.cap.suse.de:6443/apis/policy/v1beta1/namespaces/kubecf/podsecuritypolicys/kubecf-default/status, Status Code: 404, Status: 404 Not Found, Content Type: application/json, Length: 174 
WARN[Mon Jun  8 13:56:59 UTC 2020] {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404} 
WARN[Mon Jun  8 13:57:00 UTC 2020] Passthrough response: URL: https://tf4-c4-lb.cap.suse.de:6443/apis/policy/v1beta1/namespaces/kubecf/podsecuritypolicys/kubecf-default/status, Status Code: 404, Status: 404 Not Found, Content Type: application/json, Length: 174 
WARN[Mon Jun  8 13:57:00 UTC 2020] {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404} 
WARN[Mon Jun  8 13:57:11 UTC 2020] Passthrough response: URL: https://tf4-c4-lb.cap.suse.de:6443/apis/policy/v1beta1/namespaces/kubecf/podsecuritypolicys/kubecf-default/status, Status Code: 404, Status: 404 Not Found, Content Type: application/json, Length: 174 
WARN[Mon Jun  8 13:57:11 UTC 2020] {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}
richard-cox commented 4 years ago

I had a quick look into this and saw similar failures in the backend. It looks like there's multiple issues when trying to pass helm's manfiest for KubeCf's.

To solve this we'd probably need to manually chop up the kubecf manifest returned by helm and parse in ever smaller chunks to narrow down on the issue.