NO-JIRA: Move to 4.19 on go1.23

[joepvd]

No description provided.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: joepvd
Once this PR has been reviewed and has the lgtm label, please assign emilienm for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci-robot]

@joepvd: This pull request explicitly references no jira issue.

In response to this:

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.

[joepvd]

/retest

[joepvd]

/retest

[mandre]

This looks fine to me, at least for the OpenStack images, just wondering why this isn't an automated PR... Shouldn't the bot have submitted the PR?

[gnufied]

/retest

[openshift-ci]

@joepvd: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/hypershift-e2e-openstack-csi-manila	9b41ebc	link	true	/test hypershift-e2e-openstack-csi-manila
ci/prow/okd-scos-e2e-aws-ovn	9b41ebc	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-azurestack-csi	9b41ebc	link	false	/test e2e-azurestack-csi

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-sigs/prow repository. I understand the commands that are listed here.

[jsafrane]

@joepvd all ART PRs are merged, can we close this PR?
(And how it did not conflict?)