[release-4.9] Bug 2038961: bump sync plugin to 1.0.52

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1361

/assign akram

[openshift-ci]

@openshift-cherrypick-robot: Bugzilla bug 2034839 has been cloned as Bugzilla bug 2038961. Retitling PR to link against new bug.
/retitle [release-4.9] Bug 2038961: bump sync plugin to 1.0.52

In response to this:

[release-4.9] Bug 2034839: bump sync plugin to 1.0.52

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 2038961, which is invalid:

• expected dependent Bugzilla bug 2034839 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

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

In response to this:

[release-4.9] Bug 2038961: bump sync plugin to 1.0.52

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

[akram]

ART team asked for a plugins RPM bump with https://issues.redhat.com/browse/ART-3681

[gabemontero]

/bugzilla refresh

[openshift-ci]

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

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

In response to this:

/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.

[gabemontero]

/approve
/lgtm

[gabemontero]

/assign @coreydaley

for backport risk assess label

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [gabemontero]

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

[gabemontero]

/assign @prietyc123

for cherry pick approval label

[coreydaley]

/bugzilla refresh

[openshift-ci]

@coreydaley: This pull request references Bugzilla bug 2038961, which is valid.

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 2034839 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2034839 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
• bug has dependents

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

In response to this:

/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.

[coreydaley]

The severity of this bug needs to be higher to warrant the backport. Can someone verify it's severity and update the bug?

[gabemontero]

The severity of this bug needs to be higher to warrant the backport. Can someone verify it's severity and update the bug?

ah I think that is my fault - I had adjusted it a while back. @prietyc123 had marked the original 4.10 bug as high, and then @akram started the backports from the 4.10 PR.

just adjusted the bz @coreydaley

/bugzilla refresh

[openshift-ci]

@gabemontero: This pull request references Bugzilla bug 2038961, which is valid.

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 2034839 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2034839 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
• bug has dependents

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

In response to this:

The severity of this bug needs to be higher to warrant the backport. Can someone verify it's severity and update the bug?

ah I think that is my fault - I had adjusted it a while back. @prietyc123 had marked the original 4.10 bug as high, and then @akram started the backports from the 4.10 PR.

just adjusted the bz @coreydaley

/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.

[coreydaley]

/label back-risk-assessed

[openshift-ci]

@coreydaley: The label(s) /label back-risk-assessed 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, backport-risk-assessed, cherry-pick-approved

In response to this:

/label back-risk-assessed

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.

[coreydaley]

/label backport-risk-assessed

[prietyc123]

/label cherry-pick-approved

[openshift-ci]

@prietyc123: The label(s) /label cherry-pick-aaproved 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, backport-risk-assessed, cherry-pick-approved

In response to this:

/label cherry-pick-aaproved

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.

[prietyc123]

/label cherry-pick-approved

[openshift-ci]

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

• openshift/jenkins#1363

Bugzilla bug 2038961 has been moved to the MODIFIED state.

In response to this:

[release-4.9] Bug 2038961: bump sync plugin to 1.0.52

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.