OCPBUGS-27251: Requeue AgentMachine if failed to find Agent

[CrystalChun]

https://issues.redhat.com/browse/OCPBUGS-27251
It's possible that there are no valid Agents when an AgentMachine is created. The Agent will become valid later, but that doesn't cause the reconcile loop to pick it up, so the AgentMachine will never end up getting an Agent without manual intervention.

This at least allows the AgentMachine to be reconciled again in the event that an existing agent does become valid.

/cc @avishayt

[openshift-ci-robot]

@CrystalChun: This pull request references Jira Issue OCPBUGS-27251, which is invalid:

• expected the bug to target the "4.16.0" version, but no target version was set

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

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

https://issues.redhat.com/browse/OCPBUGS-27251
It's possible that there are no valid Agents when an AgentMachine is created. The Agent will become valid later, but that doesn't cause the reconcile loop to pick it up, so the AgentMachine will never end up getting an Agent without manual intervention.

This at least allows the AgentMachine to be reconciled again in the event that an existing agent does become valid.

/cc @avishayt

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CrystalChun

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 [CrystalChun]

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

[openshift-ci]

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

[avishayt]

Reconcile should be triggered when the Agent's status is updated. I'd prefer to understand why it's not happening, if possible, before going down this route.

[openshift-bot]

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

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[CrystalChun]

/close
Incorrect logic

[openshift-ci-robot]

@CrystalChun: This pull request references Jira Issue OCPBUGS-27251. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

https://issues.redhat.com/browse/OCPBUGS-27251
It's possible that there are no valid Agents when an AgentMachine is created. The Agent will become valid later, but that doesn't cause the reconcile loop to pick it up, so the AgentMachine will never end up getting an Agent without manual intervention.

This at least allows the AgentMachine to be reconciled again in the event that an existing agent does become valid.

/cc @avishayt

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 openshift-eng/jira-lifecycle-plugin repository.