Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

Keptn Bridge: Deployed services is displayed as "not deployed" #3224

Closed
1 of 12 tasks
GustavAT opened this issue Feb 10, 2021 · 2 comments
Closed
1 of 12 tasks

Keptn Bridge: Deployed services is displayed as "not deployed" #3224

GustavAT opened this issue Feb 10, 2021 · 2 comments
Assignees
Labels
bridge.2.0 Bridge Version 2 estimate: 0.5 type:bug Something is not working as intended/documented

Comments

@GustavAT
Copy link

Environment

  • 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:
bridge_service_not_deployed_environment_screen

The payload for the release.finished event is successful and shows the public URL:
bridge_service_not_deployed_release_payload

The sequence screen for that service and stage shows no errors/warnings:
bridge_service_not_deployed_sequence_screen

fyi @ermin-muratovic

@johannes-b johannes-b added bridge.2.0 Bridge Version 2 type:bug Something is not working as intended/documented labels Feb 10, 2021
@johannes-b johannes-b added this to the 0.8.0 (Bridge) milestone Feb 10, 2021
@johannes-b johannes-b added ready-for-refinement Issue is relevant for the next backlog refinment estimate: 0.5 next-sprint Items that should be discussed and implemented in the next sprint and removed ready-for-refinement Issue is relevant for the next backlog refinment labels Feb 10, 2021
@ermin-muratovic ermin-muratovic self-assigned this Feb 17, 2021
@ermin-muratovic
Copy link
Member

I think this is related to #3223 and will be fixed with that.

@johannes-b johannes-b removed the next-sprint Items that should be discussed and implemented in the next sprint label Feb 17, 2021
bacherfl added a commit that referenced this issue Feb 22, 2021
@ermin-muratovic ermin-muratovic linked a pull request Feb 22, 2021 that will close this issue
bacherfl added a commit that referenced this issue Feb 22, 2021
Signed-off-by: Florian Bacher <florian.bacher@dynatrace.com>
bacherfl added a commit that referenced this issue Feb 22, 2021
Signed-off-by: Florian Bacher <florian.bacher@dynatrace.com>

#3224 fixed service event update
bacherfl added a commit that referenced this issue Feb 22, 2021
…3338)

Signed-off-by: Florian Bacher <florian.bacher@dynatrace.com>

#3224 fixed service event update
@ermin-muratovic
Copy link
Member

Fixed with #3337

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bridge.2.0 Bridge Version 2 estimate: 0.5 type:bug Something is not working as intended/documented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants