[release-4.8] Bug 1984242: filter null yaml objects before validating to prevent undefined exception

[openshift-cherrypick-robot]

This is an automated cherry-pick of #9558

/assign jcaianirh

[openshift-ci]

@openshift-cherrypick-robot: Bugzilla bug 1983707 has been cloned as Bugzilla bug 1984242. Retitling PR to link against new bug.
/retitle [release-4.8] Bug 1984242: filter null yaml objects before validating to prevent undefined exception

In response to this:

[release-4.8] Bug 1983707: filter null yaml objects before validating to prevent undefined exception

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-cherrypick-robot: This pull request references Bugzilla bug 1984242, 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.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.8.0) matches configured target release for branch (4.8.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1983707 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Bugzilla bug 1983707 targets the "4.9.0" release, which is one of the valid target releases: 4.9.0
• bug has dependents

Requesting review from QA contact:
/cc @yapei

In response to this:

[release-4.8] Bug 1984242: filter null yaml objects before validating to prevent undefined exception

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.

[spadgett]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, spadgett

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:

• frontend/OWNERS [spadgett]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@XiyunZhao: The label(s) /label approved cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed

In response to this:

/label approved

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]

Re-validating bugzilla status after prow config updates.
/bugzilla refresh

[openshift-ci]

@sdodson: This pull request references Bugzilla bug 1984242, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.8.z) matches configured target release for branch (4.8.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1983707 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1983707 targets the "4.9.0" release, which is one of the valid target releases: 4.9.0
• bug has dependents

Requesting review from QA contact:
/cc @yapei

In response to this:

Re-validating bugzilla status after prow config updates.
/bugzilla 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 kubernetes/test-infra repository.

[ecordell]

[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window.

skipped

• Score: 0.20
• Reason: missed cutoff today, may make it tomorrow

NOTE: This message was automatically generated, if you have questions please ask on #forum-release

[ecordell]

[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window.

skipped

• Score: 0.20
• Reason: missed cutoff today, may make it tomorrow

NOTE: This message was automatically generated, if you have questions please ask on #forum-release

[ecordell]

[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window.

skipped

• Score: 0.20
• Reason: missed cutoff for today, may make tomorrow

NOTE: This message was automatically generated, if you have questions please ask on #forum-release

[ecordell]

[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window.

skipped

• Score: 0.20
• Reason: skipping for now, may still be tagged today

NOTE: This message was automatically generated, if you have questions please ask on #forum-release

[ecordell]

[patch-manager] 🚀 Approved for z-stream by score: 0.20

picked

[openshift-ci]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

• openshift/console#9565

Bugzilla bug 1984242 has been moved to the MODIFIED state.

In response to this:

[release-4.8] Bug 1984242: filter null yaml objects before validating to prevent undefined exception

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.

[XiyunZhao]

/label qe-approved

[XiyunZhao]

This issue is verified on OCP 4.8, now the console will not break down when the user import YAML with dash separator at the end