Bug 2043807: add deprecated parser build flag

[sosiouxme]

What type of PR is this?

/kind bug

What this PR does / why we need it:

ref https://issues.redhat.com/browse/ART-3664

Does this PR introduce a user-facing change?

NONE

[openshift-ci]

@sosiouxme: This pull request references Bugzilla bug 2043807, which is valid. 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.9.z) matches configured target release for branch (4.9.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 2042493 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2042493 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
• bug has dependents

Requesting review from QA contact:
/cc @wangke19

In response to this:

Bug 2043807: add deprecated parser build flag

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]

@sosiouxme: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 308c38b|hyperkube Dockerfile: add deprecated parser build flag: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[aojea]

/lgtm
/retest
/assign @sttts

[soltysh]

The commit needs to be titled:
UPSTREAM: <carry>: ...

[openshift-ci-robot]

@sosiouxme: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 3fa2820|UPSTREAM: : hyperkube Dockerfile: add deprecated parser build flag: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[sosiouxme]

@soltysh commit title revised

[sosiouxme]

/retest-required

[openshift-ci]

@sosiouxme: 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.

[soltysh]

/lgtm
/approve
/label backport-risk-assessed
/remove-label backports/unvalidated-commits
/label backports/validated-commits

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, soltysh, sosiouxme

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:

• DOWNSTREAM_OWNERS [soltysh]

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

[wangke19]

/label cherry-pick-approved

[openshift-ci]

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

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

• openshift/kubernetes#1134 is open

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

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

In response to this:

Bug 2043807: add deprecated parser build flag

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.