Skip to content

Conversation

@andrewballantyne
Copy link
Contributor

  • Pipeline Operator 0.8.0 deprecates serviceAccount in favour of serviceAccountName
  • Pipeline Operator 0.9.0 will make serviceAccount an invalid field

https://jira.coreos.com/browse/ODC-2439

Tekton Pipeline 0.8.0 Release Notes

@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Dec 2, 2019
@openshift-ci-robot openshift-ci-robot added component/dev-console Related to dev-console approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 2, 2019
@andrewballantyne
Copy link
Contributor Author

/hold

Let's not get this in just yet. More investigation can be done to see the longevity of a Pipeline Operator and see if we can better transition rather than hard cut. 0.7.0 does NOT support the serviceAccountName field.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 2, 2019
@andrewballantyne andrewballantyne changed the title Remove serviceAccount in favour of serviceAccountName Bug 1778958: Remove serviceAccount in favour of serviceAccountName Dec 2, 2019
@openshift-ci-robot
Copy link
Contributor

@andrewballantyne: This pull request references Bugzilla bug 1778958, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Bug 1778958: Remove serviceAccount in favour of serviceAccountName

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Dec 2, 2019
@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 3, 2019
@andrewballantyne
Copy link
Contributor Author

Resized this to allow for ports back to 4.3 & 4.2. The YAMLs are not used in todays scripts, so deleting them serves as nothing but potential conflict as I cherry pick to previous releases.

@andrewballantyne
Copy link
Contributor Author

Waiting for Canary 0.9.0 before trying to push this through - shouldn't be too much longer. Once it's tested with 0.9.0, we should be good to go with this change & the backports.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Going with a specific spread to allow wider version support.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prep for changing apiVersions (unrelated to this fix though - future assistance)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorted

@abhinandan13jan
Copy link
Contributor

/assign

@abhinandan13jan
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 6, 2019
@abhinandan13jan
Copy link
Contributor

/retest

- Pipeline Operator 0.8.0 deprecates serviceAccount in favour of
serviceAccountName
- Pipeline Operator 0.9.0 will make serviceAccount an invalid field
@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Dec 31, 2019
@andrewballantyne
Copy link
Contributor Author

The Operator got the canary channel for 0.9.x. Tested it against the migration (from 0.8.x to 0.9.x) and saw there is a chance that the user created their own PipelineRun that has a serviceAccount and then the Operator got upgraded; this would cause a UI error preventing re-runs.

Changes since last review:

  • Added a migration that changes serviceAccount to serviceAccountName if it exists
  • Added tests for the migration code

@andrewballantyne
Copy link
Contributor Author

/kind cleanup

@openshift-ci-robot openshift-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jan 2, 2020
@andrewballantyne
Copy link
Contributor Author

/hold cancel
/retest
#3847 has fixed the e2e tests

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 2, 2020
@andrewballantyne
Copy link
Contributor Author

/retest

@abhinandan13jan
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 6, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinandan13jan, andrewballantyne

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit c12d0fc into openshift:master Jan 6, 2020
@openshift-ci-robot
Copy link
Contributor

@andrewballantyne: All pull requests linked via external trackers have merged. Bugzilla bug 1778958 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1778958: Remove serviceAccount in favour of serviceAccountName

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@andrewballantyne
Copy link
Contributor Author

/cherry-pick release-4.3

@openshift-cherrypick-robot

@andrewballantyne: new pull request created: #3869

Details

In response to this:

/cherry-pick release-4.3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@andrewballantyne
Copy link
Contributor Author

/cherry-pick release-4.2

@openshift-cherrypick-robot

@andrewballantyne: #3632 failed to apply on top of branch "release-4.2":

Using index info to reconstruct a base tree...
A	frontend/packages/dev-console/src/components/pipelines/detail-page-tabs/pipeline-details/__tests__/pipelinerun-mock.ts
M	frontend/packages/dev-console/src/utils/__tests__/pipeline-actions.spec.ts
M	frontend/packages/dev-console/src/utils/pipeline-actions.tsx
M	frontend/packages/dev-console/src/utils/pipeline-augment.ts
Falling back to patching base and 3-way merge...
Auto-merging frontend/packages/dev-console/src/utils/pipeline-augment.ts
CONFLICT (content): Merge conflict in frontend/packages/dev-console/src/utils/pipeline-augment.ts
Auto-merging frontend/packages/dev-console/src/utils/pipeline-actions.tsx
CONFLICT (content): Merge conflict in frontend/packages/dev-console/src/utils/pipeline-actions.tsx
Auto-merging frontend/packages/dev-console/src/utils/__tests__/pipeline-actions.spec.ts
CONFLICT (content): Merge conflict in frontend/packages/dev-console/src/utils/__tests__/pipeline-actions.spec.ts
Auto-merging frontend/packages/dev-console/src/components/pipelines/__tests__/pipelinerun-mock.ts
error: Failed to merge in the changes.
Patch failed at 0001 Handle serviceAccount migration to serviceAccountName

Details

In response to this:

/cherry-pick release-4.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. component/dev-console Related to dev-console kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants