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

[release-3.9] UPSTREAM: 57202: Fix format string in describers #18853

Conversation

openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Mar 6, 2018

This is an automated cherry-pick of #18810

Fixes: http://bugzilla.redhat.com/show_bug.cgi?id=1524379

/assign jsafrane

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 6, 2018
@openshift-merge-robot openshift-merge-robot added the vendor-update Touching vendor dir or related files label Mar 6, 2018
@jsafrane
Copy link
Contributor

jsafrane commented Mar 6, 2018

/retest

@jsafrane
Copy link
Contributor

jsafrane commented Mar 6, 2018

/assign @soltysh [for approval]

@jsafrane
Copy link
Contributor

jsafrane commented Mar 6, 2018

/assign @soltysh

@mfojtik
Copy link
Contributor

mfojtik commented Mar 6, 2018

/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 6, 2018
@jsafrane
Copy link
Contributor

jsafrane commented Mar 6, 2018

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 6, 2018
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, mfojtik, 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:

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

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@jsafrane
Copy link
Contributor

jsafrane commented Mar 6, 2018

/retest

1 similar comment
@jsafrane
Copy link
Contributor

jsafrane commented Mar 6, 2018

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@eparis eparis added this to the 3.9.0 milestone Mar 7, 2018
@eparis eparis added kind/bug Categorizes issue or PR as related to a bug. queue/fix labels Mar 7, 2018
@eparis eparis modified the milestones: v3.9, 3.7.0 Mar 7, 2018
@eparis eparis removed the queue/fix label Mar 7, 2018
@eparis
Copy link
Member

eparis commented Mar 7, 2018

/retest

1 similar comment
@eparis
Copy link
Member

eparis commented Mar 7, 2018

/retest

@openshift-merge-robot
Copy link
Contributor

/test all [submit-queue is verifying that this PR is safe to merge]

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 8, 2018

@openshift-cherrypick-robot: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/openshift-jenkins/extended_networking_minimal c7d54a6 link /test extended_networking_minimal

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@openshift-merge-robot
Copy link
Contributor

Automatic merge from submit-queue.

@openshift-merge-robot openshift-merge-robot merged commit c43888d into openshift:release-3.9 Mar 8, 2018
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. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants