[release-4.8] Bug 2011460: Add imagestream for driver-toolkit

[openshift-cherrypick-robot]

This is an automated cherry-pick of #64

/assign kpouget

[openshift-ci]

@openshift-cherrypick-robot: Detected clone of Bugzilla bug 2008619 with correct target release. Retitling PR to link to clone:
/retitle [release-4.8] [release-4.9] Bug 2011460: Add imagestream for driver-toolkit

In response to this:

[release-4.8] [release-4.9] Bug 2008619: Add imagestream for driver-toolkit

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 2011460, 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.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 2008619 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 2008619 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 @wabouhamad

In response to this:

[release-4.8] [release-4.9] Bug 2011460: Add imagestream for driver-toolkit

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.

[kpouget]

/hold openshift/kubernetes#1005 needs to be merged first
/title [release-4.8] Bug 2011460: Add imagestream for driver-toolkit #65

[kpouget]

/retitle [release-4.8] Bug 2011460: Add imagestream for driver-toolkit

[kpouget]

Backport risk assessment

• If the Bugzilla associated with the PR has the "FastFix" keyword, the subjective assessment on the issue has already been done and a customer is impacted. These PRs should be prioritized for merge.
  • not applicable
• For branches that are in the Maintenance lifecycle phase:
  • not applicable
• The bug has significant impact either through severity, reduction in supportability, or number of users affected.
  • bugzilla/severity-high
• The severity field of the bug must be set to accurately reflect criticality.
  • bugzilla/severity-high
• The PR is merged in the next newer release branch and the bug for that newer release is VERIFIED by QE.
  • ensured by bugzilla/valid-bug tag
• The PR’s description is well formed with user-focused release notes that state the bug number, impact, cause, and resolution. Where appropriate, it should also contain information about how a user can identify whether a particular cluster is affected.
  • the original PR Add imagestream for driver-toolkit #60 has a PR description, but not this one as it was automatically created, I'm not sure how to change it ...

[kpouget]

/retest

[wabouhamad]

/lgtm

[dagrayvid]

/retest

[dagrayvid]

/unhold

[dagrayvid]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dagrayvid, 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 [dagrayvid]

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-cherrypick-robot: All pull requests linked via external trackers have merged:

• openshift/driver-toolkit#65
• openshift/kubernetes#1005

Bugzilla bug 2011460 has been moved to the MODIFIED state.

In response to this:

[release-4.8] Bug 2011460: Add imagestream for driver-toolkit

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.