Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TaskRun step status in wrong order when there are unnamed steps #2430

Closed
vincent-pli opened this issue Apr 17, 2020 · 1 comment
Closed

TaskRun step status in wrong order when there are unnamed steps #2430

vincent-pli opened this issue Apr 17, 2020 · 1 comment
Assignees
@vincent-pli
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@vincent-pli
Copy link
Member

Expected Behavior

The Taskrun.status.steps should with the exactly same order with steps defined in Task.

Actual Behavior

In Unnamed base it does not.

Steps to Reproduce the Problem

Apply the case in #2415
then check the Taskrun.status.steps

Additional Info

The root cause is we sort it based on step.name in task but they are "" in this case.

  • Kubernetes version:

    Output of kubectl version:

    Client Version: v1.16.3
Server Version: v1.15.5

  • Tekton Pipeline version:
    Master
@vincent-pli vincent-pli mentioned this issue Apr 17, 2020
Merged
3 tasks
@vdemeester
Copy link
Member

/kind bug
/assign vincent-pli

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vincent-pli vincent-pli

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vdemeester @vincent-pli @tekton-robot