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.

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

Bug 1873345: specify a serviceaccount in the deployment #240

Conversation

joelddiaz
Copy link
Contributor

allow downgrading from 4.6 (where we do specify a serviceaccount)

@openshift-ci-robot
Copy link
Contributor

@joelddiaz: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

specify a serviceaccount in the deployment

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 27, 2020
@joelddiaz joelddiaz changed the title specify a serviceaccount in the deployment Bug 1868376: specify a serviceaccount in the deployment Aug 27, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 27, 2020
@openshift-ci-robot
Copy link
Contributor

@joelddiaz: This pull request references Bugzilla bug 1868376, which is invalid:

  • expected the bug to target the "4.5.z" release, but it targets "---" instead
  • expected Bugzilla bug 1868376 to depend on a bug targeting a release in 4.6.0, 4.6.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1868376: specify a serviceaccount in the deployment

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.

@joelddiaz
Copy link
Contributor Author

/hold

@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 Aug 27, 2020
@joelddiaz
Copy link
Contributor Author

@sdodson here's the proposed fix

@sdodson
Copy link
Member

sdodson commented Aug 27, 2020

So this was something that defaulted in 4.5, they upgrade to 4.6 and it gets removed, downgrade to 4.5 and needs to be set explicitly on downgrade?

allow downgrading from 4.6 (where we do specify a serviceaccount)
@joelddiaz
Copy link
Contributor Author

@sdodson Yes. I built my own release image with this change, and was able to downgrade from 4.6 successfully (after fixing my typo in the original PR). The Deployment no longer references the serviceAccount that is new in 4.6, and instead references the default serviceAccount as was used pre-4.6.

  schedulerName: default-scheduler
  securityContext:
    fsGroup: 1000130000
    seLinuxOptions:
      level: s0:c11,c10
  serviceAccount: default
  serviceAccountName: default
  terminationGracePeriodSeconds: 10
  tolerations:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
    operator: Exists

It appears the CVO is not doing a full replace of the objects, but is merely patching them which is why we need to explicitly set the values so they get reverted on downgrade.

@joelddiaz
Copy link
Contributor Author

/retest

@sdodson
Copy link
Member

sdodson commented Aug 28, 2020

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelddiaz, sdodson

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

The pull request process is described here

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

@sdodson
Copy link
Member

sdodson commented Aug 28, 2020

/retitle Bug 1873345: specify a serviceaccount in the deployment

@openshift-ci-robot openshift-ci-robot changed the title Bug 1868376: specify a serviceaccount in the deployment Bug 1873345: specify a serviceaccount in the deployment Aug 28, 2020
@openshift-ci-robot
Copy link
Contributor

@joelddiaz: This pull request references Bugzilla bug 1873345, which is invalid:

  • expected dependent Bugzilla bug 1868376 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1873345: specify a serviceaccount in the deployment

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.

@sdodson sdodson added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 28, 2020
@sdodson
Copy link
Member

sdodson commented Aug 28, 2020

I've overridden bugzilla/valid-bug because this bug only happens when downgrading from 4.6 to 4.5, so while QE shall test that we've not regressed in 4.6 there's no code changes to be made on that branch and this bug was marked as a TestBlocker.

@sdodson
Copy link
Member

sdodson commented Aug 28, 2020

/refresh

@joelddiaz
Copy link
Contributor Author

/unhold

@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 Aug 28, 2020
@derekwaynecarr derekwaynecarr added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 3, 2020
@openshift-merge-robot openshift-merge-robot merged commit 7c65a11 into openshift:release-4.5 Sep 3, 2020
@openshift-ci-robot
Copy link
Contributor

@joelddiaz: All pull requests linked via external trackers have merged:

Bugzilla bug 1873345 has been moved to the MODIFIED state.

In response to this:

Bug 1873345: specify a serviceaccount in the deployment

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/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants