Skip to content

Bug 1878040: operator/network: unify defaulting with OperatorSpec log level#754

Merged
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
sttts:sttts-loglevel-network
Sep 29, 2020
Merged

Bug 1878040: operator/network: unify defaulting with OperatorSpec log level#754
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
sttts:sttts-loglevel-network

Conversation

@sttts
Copy link
Copy Markdown
Contributor

@sttts sttts commented Sep 29, 2020

Note, that this type is already broken once it is revendored into network operator: it got the enum and the enum does not allow typos. Hence, we need support in the normalization controller in 4.6 and 4.5, cc @vareti.

The loglevel normalization controller already had operator.openshift.io/v1 networks in the list: https://github.com/openshift/cluster-config-operator/pull/150/files#diff-5f3b7bf7ad57a65830a8559927ac7c05R108

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 29, 2020
@sttts sttts changed the title operator/network: unify defaulting with OperatorSpec one operator/network: unify defaulting with OperatorSpec log level Sep 29, 2020
@sttts
Copy link
Copy Markdown
Contributor Author

sttts commented Sep 29, 2020

/assign @danwinship

@sttts sttts force-pushed the sttts-loglevel-network branch from 0df103b to bfdde78 Compare September 29, 2020 12:24
@sttts sttts changed the title operator/network: unify defaulting with OperatorSpec log level Bug 1878040: operator/network: unify defaulting with OperatorSpec log level Sep 29, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Sep 29, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@sttts: This pull request references Bugzilla bug 1878040, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
Details

In response to this:

Bug 1878040: operator/network: unify defaulting with OperatorSpec log level

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 Sep 29, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@sttts: This pull request references Bugzilla bug 1878040, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
Details

In response to this:

Bug 1878040: operator/network: unify defaulting with OperatorSpec log level

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.

1 similar comment
@openshift-ci-robot
Copy link
Copy Markdown

@sttts: This pull request references Bugzilla bug 1878040, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
Details

In response to this:

Bug 1878040: operator/network: unify defaulting with OperatorSpec log level

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.

@sttts sttts force-pushed the sttts-loglevel-network branch 3 times, most recently from 023181b to 19d0ec4 Compare September 29, 2020 12:35
Note, that this type is already broken once it is revendored into network operator: it got the enum and the enum does not allow typos. Hence, we need support in the normalization controller in 4.6 and 4.5, cc @vareti.
@sttts sttts force-pushed the sttts-loglevel-network branch from 19d0ec4 to c82088e Compare September 29, 2020 12:37
@danwinship
Copy link
Copy Markdown
Contributor

I don't really understand this, but if you say so.
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 29, 2020
@openshift-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, sttts

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-merge-robot openshift-merge-robot merged commit 9a3cfb8 into openshift:master Sep 29, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@sttts: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state.

Bugzilla bug 1878040 has not been moved to the MODIFIED state.

Details

In response to this:

Bug 1878040: operator/network: unify defaulting with OperatorSpec log level

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants