MGMT-18230: Bump to go version 1.22

[paul-maidment]

In order to address a number of CVE's, a go version bump to v1.22 is recommended. This PR changes to go version v1.22

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

Checklist

• Title and description added to both, commit and PR.
• Relevant issues have been associated (see CONTRIBUTING guide)
• This change does not require a documentation update (docstring, docs, README, etc)
• Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

• Are the title and description (in both PR and commit) meaningful and clear?
• Is there a bug required (and linked) for this change?
• Should this PR be backported?

[openshift-ci-robot]

@paul-maidment: This pull request references MGMT-18230 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.

In response to this:

In order to address a number of CVE's, a go version bump to v1.22 is recommended. This PR changes to go version v1.22

List all the issues related to this PR

• New Feature
• Enhancement
• Bug fix
• Tests
• Documentation
• CI/CD

What environments does this code impact?

• Automation (CI, tools, etc)
• Cloud
• Operator Managed Deployments
• None

How was this code tested?

• assisted-test-infra environment
• dev-scripts environment
• Reviewer's test appreciated
• Waiting for CI to do a full test run
• Manual (Elaborate on how it was tested)
• No tests needed

Checklist

• Title and description added to both, commit and PR.
• Relevant issues have been associated (see CONTRIBUTING guide)
• This change does not require a documentation update (docstring, docs, README, etc)
• Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

• Are the title and description (in both PR and commit) meaningful and clear?
• Is there a bug required (and linked) for this change?
• Should this PR be backported?

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: adriengentil, paul-maidment

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 [adriengentil,paul-maidment]

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

[openshift-ci]

New changes are detected. LGTM label has been removed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.61%. Comparing base (d65b670) to head (acdf655).
Report is 51 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7011      +/-   ##
==========================================
+ Coverage   68.31%   74.61%   +6.29%     
==========================================
  Files         272      324      +52     
  Lines       38885    63167   +24282     
==========================================
+ Hits        26565    47132   +20567     
- Misses       9922    13563    +3641     
- Partials     2398     2472      +74     

see 53 files with indirect coverage changes

[paul-maidment]

/retest

[eifrach]

maybe we should update the other packages - cause you may have some issues between them
/api/go.mod /client/go.mod /models/go.mod

[eifrach]

when updating the go version you should also update the linter - you may have issues if the linter is not aligned
https://github.com/paul-maidment/assisted-service/blob/MGMT-18230/ci-images/Dockerfile.lint#L3

• https://github.com/openshift/assisted-service/blob/master/Dockerfile.assisted-service-build#L3

[paul-maidment]

Good point! I missed this one, thanks for the pointer.

[openshift-ci]

@paul-maidment: 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/edge-e2e-ai-operator-ztp	acdf655	link	true	/test edge-e2e-ai-operator-ztp
ci/prow/edge-ci-index	acdf655	link	true	/test edge-ci-index
ci/prow/edge-images	acdf655	link	true	/test edge-images
ci/prow/mce-images	acdf655	link	true	/test mce-images
ci/prow/edge-e2e-metal-assisted	acdf655	link	true	/test edge-e2e-metal-assisted
ci/prow/edge-e2e-metal-assisted-osc-sno-4-17	acdf655	link	true	/test edge-e2e-metal-assisted-osc-sno-4-17
ci/prow/edge-e2e-metal-assisted-osc-4-17	acdf655	link	true	/test edge-e2e-metal-assisted-osc-4-17

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.