Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The state of a deployed app differs between cli and ui.

See original GitHub issue

Stratos Version

4.2.1

Frontend Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, single container deploying all components
npm run start
Other (please specify below)

Backend (Jet Stream) Deployment type

Cloud Foundry Application (cf push)
Kubernetes, using a helm chart
Docker, single container deploying all components
Other (please specify below)

Expected behaviour

Stratos Frontend shows the correct state of the deployed app.

Actual behaviour

The state of the app differs between cli and ui.

Steps to reproduce the behavior

Installing the app https://github.com/cloudfoundry-samples/spring-music
Added a postgres db https://github.com/bitnami/charts/tree/master/bitnami/postgresql
after some time the state of the cli and the ui differs.

Log output covering before error and any error statements

grafik

cf7 app spring-music
Showing health and status for app spring-music in org cloudness / space java as johannes...

name:                spring-music
requested state:     started
isolation segment:   placeholder
last uploaded:       Mon 02 Nov 21:42:00 CET 2020
stack:
buildpacks:
isolation segment:   placeholder

type:           web
sidecars:
instances:      1/1
memory usage:   1024M
     state     since                  cpu    memory         disk      details
#0   running   2020-11-02T20:47:17Z   0.2%   243.1M of 1G   0 of 1G

type:           executable-jar
sidecars:
instances:      0/0
memory usage:   1024M
There are no running instances of this process.

type:           task
sidecars:
instances:      0/0
memory usage:   1024M
There are no running instances of this process.

Issue Analytics

State:
Created 3 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

1reaction

richard-coxcommented, Nov 4, 2020

Yes, though the v2 api implementation part is my assumption. We do know that it’s a cf-for-k8s specific issue and other cf types work fine. Feel free to link this issue, I’ll monitor it and add comments as required.

0reactions

richard-coxcommented, Nov 6, 2020

I’m going to close this. It seems to be an issue with cf-for-k8s not supporting v2. I’ll continue chasing them to discover more.