Bug 1945683: Wait for expected number of drivers starting API #158

derekhiggins · 2021-04-01T16:16:05Z

Currently the API will start even if the conductor is still
starting up, which can lead to failures if you try to deploy
nodes as soon as the API is accessible.

Co-Author: Steven Hardy shardy@redhat.com

Currently the API will start even if the conductor is still starting up, which can lead to failures if you try to deploy nodes as soon as the API is accessible. Co-Author: Steven Hardy <shardy@redhat.com>

openshift-ci-robot · 2021-04-01T16:16:08Z

@derekhiggins: This pull request references Bugzilla bug 1945683, which is invalid:

expected Bugzilla bug 1945683 to depend on a bug targeting a release in 4.6.0, 4.6.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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:

Bug 1945683: Wait for expected number of drivers starting API

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 · 2021-04-01T16:16:18Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: derekhiggins

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~~ [derekhiggins]

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

openshift-bot · 2021-06-30T20:04:48Z

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

derekhiggins · 2021-07-01T10:08:30Z

/bugzilla refresh

derekhiggins · 2021-07-01T10:09:15Z

/remove-lifecycle stale

openshift-ci · 2021-07-01T10:24:50Z

@derekhiggins: This pull request references Bugzilla bug 1945683, which is valid.

6 validation(s) were run on this bug

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

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (augol@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.

elfosardo · 2021-07-28T07:23:40Z

/retest

elfosardo · 2021-07-28T07:24:39Z

/lgtm

openshift-ci · 2021-07-28T07:24:48Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: derekhiggins, elfosardo

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~~ [derekhiggins,elfosardo]

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

elfosardo · 2021-07-28T13:58:23Z

/test e2e-metal-ipi

openshift-bot · 2021-07-28T16:35:39Z

/retest-required