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 2117268: api-resource-collector: Don't attempt to parse empty Ignition #81

Merged

Conversation

jhrozek
Copy link

@jhrozek jhrozek commented Aug 11, 2022

While filtering files out of MachineConfigs, we tried to also parse
ignition specification of MachineConfigs that didn't specify any,
leading to an error.

Let's just pass on MCs that don't have any Ignition spec as-is.

Resolves: rhbz#2117268

@openshift-ci
Copy link

openshift-ci bot commented Aug 11, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhrozek

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

@jhrozek jhrozek changed the title api-resource-collector: Don't attempt to parse empty Ignition rhbz#2117268: api-resource-collector: Don't attempt to parse empty Ignition Aug 11, 2022
@jhrozek jhrozek changed the title rhbz#2117268: api-resource-collector: Don't attempt to parse empty Ignition Bug 2117268: api-resource-collector: Don't attempt to parse empty Ignition Aug 11, 2022
@openshift-ci
Copy link

openshift-ci bot commented Aug 11, 2022

@jhrozek: This pull request references Bugzilla bug 2117268, 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.12.0) matches configured target release for branch (4.12.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 2117268: api-resource-collector: Don't attempt to parse empty Ignition

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.

@jhrozek
Copy link
Author

jhrozek commented Aug 11, 2022

/hold
for QE review

@jhrozek
Copy link
Author

jhrozek commented Aug 11, 2022

/test e2e-aws

1 similar comment
@jhrozek
Copy link
Author

jhrozek commented Aug 12, 2022

/test e2e-aws

@jhrozek
Copy link
Author

jhrozek commented Aug 15, 2022

@xiaojiey PTAL if this fixes the bug
@mrogers950 @rhmdnd @Vincent056 PTAL from code perspective

@mrogers950
Copy link

/lgtm

While filtering files out of MachineConfigs, we tried to also parse
ignition specification of MachineConfigs that didn't specify any,
leading to an error.

Let's just pass on MCs that don't have any Ignition spec as-is.

Resolves: rhbz#2117268
@jhrozek
Copy link
Author

jhrozek commented Aug 16, 2022

@sheriff-rh I added a CHANGELOG blob to the PR, is it sufficient for you to base a release note on? If yes, can you add the docs-approved label?

@jhrozek
Copy link
Author

jhrozek commented Aug 16, 2022

@mrogers950 sorry, I forgot to add a changelog blob earlier, so the latest push ended up removing the lgtm label. Can you re-add it please? There are no other changes.

@xiaojiey
Copy link
Collaborator

/bugzilla cc-qa

@openshift-ci
Copy link

openshift-ci bot commented Aug 16, 2022

@xiaojiey: This pull request references Bugzilla bug 2117268, which is valid.

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

Requesting review from QA contact:
/cc @xiaojiey

In response to this:

/bugzilla cc-qa

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.

@xiaojiey
Copy link
Collaborator

/label qe-approve

@sheriff-rh
Copy link
Collaborator

lgtm, thanks @jhrozek

@jhrozek
Copy link
Author

jhrozek commented Aug 16, 2022

Since this is a bug, I'm adding the px-approved label myself
/label px-approved

@jhrozek
Copy link
Author

jhrozek commented Aug 16, 2022

/hold cancel

Copy link

@Vincent056 Vincent056 left a comment

Choose a reason for hiding this comment

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

sorry for the late review,
/lgtm

@jhrozek
Copy link
Author

jhrozek commented Aug 16, 2022

@mkumku see this PR for px-approved

@mrogers950
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Aug 16, 2022
@openshift-merge-robot openshift-merge-robot merged commit 971543d into ComplianceAsCode:master Aug 16, 2022
@openshift-ci
Copy link

openshift-ci bot commented Aug 16, 2022

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

Bugzilla bug 2117268 has been moved to the MODIFIED state.

In response to this:

Bug 2117268: api-resource-collector: Don't attempt to parse empty Ignition

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants