Question: Why is the evaluation result dropped from one stage to the next?

[johannes-b]

Use case

As a user, I have an approval task set as first task in my delivery sequence of production:

apiVersion: "spec.keptn.sh/0.2.2"
kind: "Shipyard"
metadata:
  name: "shipyard-sockshop"
spec:
  stages:

    - name: "staging"
      sequences:
        - name: "delivery"
          triggeredOn:
            - event: "dev.delivery.finished"
          tasks:
            - name: "deployment"
              properties:
                deploymentstrategy: "blue_green_service"
            - name: "test"
              properties:
                teststrategy: "performance"
            - name: "evaluation"
            - name: "release"
            - name: "approval"
              properties:
                pass: "manual"
                warning: "manual"

    - name: "production"
      sequences:
        - name: "delivery"
          triggeredOn:
            - event: "staging.delivery.finished"
          tasks:
            - name: "approval"
              properties:
                pass: "manual"
                warning: "manual"
            - name: "deployment"
              properties:
                deploymentstrategy: "blue_green_service"
            - name: "release"

I'm used to the behavior that the approval task shows the last evaluation result:

However, when using the approval task as the first task, the evaluation score is not shown.

Investigation

I figured out that during the promotion from staging to production, the score:100 dropped to 0. Why is this done?

In staging:

In production:

[ghost]

Move to discussions?

[johannes-b]

It has been sorted out by the team that here data is getting lost due to implementation in the shipyard-controller. This is marked as bug now.

[RealAnna]

I tested the same shipyard on my cluster running 0.11.3 and the score is correctly propagated. I believe the issue has been solved here #5691