You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Client OS (e.g., Linux, OSX, Windows): Ubuntu 20.04
Keptn Version (keptn version): 0.8.0-alpha
Kubernetes Cloud Provider (e.g., GKE, AKS):GKE
Kubernetes version (kubectl version): v1.16.15-gke.6000
Bridge image: bridge2:0.8.0-dev-PR-3169
Affected Component
Docs
CLI
Kubernetes Integration
Openshift Integration
Helm
Istio
Bridge
Gatekeeper
Datastore
REST API
eventbroker / distributor
jmeter
Describe the bug
After a service has been deployed and released successfully in a stage, the environment screen still shows "Services not deployed yet" for that service.
It can still be accessed thought by its public URL (received from the released.finished event)
To Reproduce
I was using a minimal shipyard with 1 stage, 1 sequence and 2 tasks: deploy and release.
Onboard and deploy any service.
Expected behavior
The services is shown as "deployed" and I can access it using the public URL.
Current behavior
A successfully deployed services is shown as "Service not deployed yet" in the environment screen.
Screenshots
Environment screen shows that the service is not deployed:
The payload for the release.finished event is successful and shows the public URL:
The sequence screen for that service and stage shows no errors/warnings:
Environment
Ubuntu 20.04
keptn version
):0.8.0-alpha
GKE
kubectl version
):v1.16.15-gke.6000
bridge2:0.8.0-dev-PR-3169
Affected Component
Describe the bug
After a service has been deployed and released successfully in a stage, the environment screen still shows "Services not deployed yet" for that service.
It can still be accessed thought by its public URL (received from the
released.finished
event)To Reproduce
I was using a minimal shipyard with 1 stage, 1 sequence and 2 tasks: deploy and release.
Onboard and deploy any service.
Expected behavior
The services is shown as "deployed" and I can access it using the public URL.
Current behavior
A successfully deployed services is shown as "Service not deployed yet" in the environment screen.
Screenshots
Environment screen shows that the service is not deployed:
The payload for the
release.finished
event is successful and shows the public URL:The sequence screen for that service and stage shows no errors/warnings:
fyi @ermin-muratovic
The text was updated successfully, but these errors were encountered: