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

OCPBUGS-39149: ztp: empty file in sitegen kustomize plugin #2052

Merged

Conversation

abraham2512
Copy link
Member

@abraham2512 abraham2512 commented Sep 26, 2024

This MR includes a check to safely ignore empty file in testUserExtraManifest consumed by siteconfig-generator-kustomize-plugin, which caused addZTPAnnotationToManifest to panic.

This is an additional MR for addressing a missed scenario from
#2022

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Sep 26, 2024
@openshift-ci-robot
Copy link
Collaborator

@abraham2512: This pull request references Jira Issue OCPBUGS-39149, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This MR includes a check to safely ignore empty file in testUserExtraManifest consumed by siteconfig-generator-kustomize-plugin, which caused addZTPAnnotationToManifest to panic.

This will avoid addZTPAnnotationToManifest for empty values and will ignore file from dataMap.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 26, 2024
@sabbir-47
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Collaborator

@sabbir-47: This pull request references Jira Issue OCPBUGS-39149, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@sabbir-47
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Collaborator

@sabbir-47: This pull request references Jira Issue OCPBUGS-39149, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@sabbir-47
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 2, 2024
@sabbir-47
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 2, 2024
@openshift-ci-robot
Copy link
Collaborator

@sabbir-47: This pull request references Jira Issue OCPBUGS-39149, which is valid.

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

Requesting review from QA contact:
/cc @yliu127

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from yliu127 October 2, 2024 11:42
@sabbir-47
Copy link
Contributor

/approve

Copy link
Contributor

openshift-ci bot commented Oct 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abraham2512, sabbir-47

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 Oct 2, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit c4d48a0 into openshift-kni:master Oct 2, 2024
6 checks passed
@openshift-ci-robot
Copy link
Collaborator

@abraham2512: Jira Issue OCPBUGS-39149: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-39149 has been moved to the MODIFIED state.

In response to this:

This MR includes a check to safely ignore empty file in testUserExtraManifest consumed by siteconfig-generator-kustomize-plugin, which caused addZTPAnnotationToManifest to panic.

This is an additional MR for addressing a missed scenario from
#2022

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 openshift-eng/jira-lifecycle-plugin repository.

@sabbir-47
Copy link
Contributor

/cherry-pick release-4.17

@openshift-cherrypick-robot

@sabbir-47: new pull request created: #2101

In response to this:

/cherry-pick release-4.17

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-sigs/prow 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. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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