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 2092650: Stop treating missing network as fatal error #227

Merged
merged 1 commit into from Jun 17, 2022

Conversation

derekhiggins
Copy link

Report that NetworkData isn't available and return a
blank string id the sectret is present but doesn't contain
the expected key. This is the same as the behaviour when the
secret isn't present at all.

Report that NetworkData isn't available and return a
blank string id the sectret is present but doesn't contain
the expected key. This is the same as the behaviour when the
secret isn't present at all.
@openshift-ci openshift-ci bot added 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. labels Jun 10, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jun 10, 2022

@derekhiggins: This pull request references Bugzilla bug 2092650, 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.

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

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (adistefa@redhat.com), skipping review request.

In response to this:

Bug 2092650: Stop treating missing network as fatal error

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 openshift-ci bot requested review from honza and kirankt June 10, 2022 10:12
@honza
Copy link
Member

honza commented Jun 13, 2022

Do we want this upstream first?

@aleskandro
Copy link
Member

aleskandro commented Jun 13, 2022

Hello, PTAL my last comment in https://bugzilla.redhat.com/show_bug.cgi?id=2092650 before proceeding with the review and merge

@zaneb
Copy link
Member

zaneb commented Jun 15, 2022

/approve

@openshift-ci
Copy link

openshift-ci bot commented Jun 15, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: derekhiggins, zaneb

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 15, 2022
@derekhiggins
Copy link
Author

Do we want this upstream first?

Sorry, I should have done that first, PR is up now
metal3-io#1135

@derekhiggins
Copy link
Author

/test e2e-metal-ipi-serial-ipv4

@dtantsur
Copy link
Member

/lgtm

I don't like it, but I don't have better ideas

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2022
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 2 against base HEAD a99095a and 8 for PR HEAD 2664085 in total

@openshift-ci
Copy link

openshift-ci bot commented Jun 17, 2022

@derekhiggins: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-ci openshift-ci bot merged commit 148f2fc into openshift:master Jun 17, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jun 17, 2022

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

Bugzilla bug 2092650 has been moved to the MODIFIED state.

In response to this:

Bug 2092650: Stop treating missing network as fatal error

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.

@derekhiggins
Copy link
Author

/cherry-pick release-4.10

@openshift-cherrypick-robot

@derekhiggins: new pull request created: #230

In response to this:

/cherry-pick release-4.10

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.

None yet

7 participants