Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MGMT-14631: Remove support for openshift 4.8 #5221

Conversation

danmanor
Copy link
Contributor

@danmanor danmanor commented May 17, 2023

Remove support for openshift 4.8

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 17, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 17, 2023

@danmanor: This pull request references MGMT-14631 which is a valid jira issue.

In response to this:

Remove support for openshift 4.8

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 kubernetes/test-infra repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented May 17, 2023

@danmanor: This pull request references MGMT-14631 which is a valid jira issue.

In response to this:

Remove support for openshift 4.8

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 kubernetes/test-infra repository.

@danmanor
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 17, 2023
@openshift-ci openshift-ci bot requested review from filanov and gamli75 May 17, 2023 09:46
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 17, 2023
@danmanor
Copy link
Contributor Author

/cc @osherdp

@openshift-ci openshift-ci bot requested a review from osherdp May 17, 2023 10:03
@codecov
Copy link

codecov bot commented May 17, 2023

Codecov Report

Merging #5221 (f6ec2a9) into master (db30aab) will decrease coverage by 0.01%.
The diff coverage is n/a.

❗ Current head f6ec2a9 differs from pull request most recent head dad21ee. Consider uploading reports for the commit dad21ee to get more accurate results

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5221      +/-   ##
==========================================
- Coverage   67.49%   67.49%   -0.01%     
==========================================
  Files         221      221              
  Lines       33039    33045       +6     
==========================================
+ Hits        22299    22303       +4     
- Misses       8728     8729       +1     
- Partials     2012     2013       +1     
Impacted Files Coverage Δ
internal/featuresupport/support_levels_list.go 100.00% <ø> (ø)

... and 3 files with indirect coverage changes

@danmanor danmanor force-pushed the removing-support-for-openshift-4.8 branch from 6760556 to 470c96e Compare May 17, 2023 11:24
internal/featuresupport/features.go Outdated Show resolved Hide resolved
internal/featuresupport/features.go Outdated Show resolved Hide resolved
internal/versions/api_test.go Show resolved Hide resolved
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 18, 2023
@danmanor danmanor force-pushed the removing-support-for-openshift-4.8 branch 2 times, most recently from c9c0ab8 to 7fabf24 Compare May 21, 2023 08:57
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 21, 2023
@danmanor danmanor marked this pull request as draft May 21, 2023 08:57
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 21, 2023
@danmanor
Copy link
Contributor Author

/uncc @filanov @gamli75 @osherdp

@openshift-ci openshift-ci bot removed request for filanov and gamli75 May 21, 2023 08:58
@danmanor danmanor changed the title MGMT-14631: Remove support for openshift 4.8 WIP: MGMT-14631: Remove support for openshift 4.8 May 21, 2023
@danmanor danmanor force-pushed the removing-support-for-openshift-4.8 branch from 7fabf24 to 4753132 Compare May 21, 2023 09:56
@danmanor
Copy link
Contributor Author

/retest-required

@danmanor danmanor force-pushed the removing-support-for-openshift-4.8 branch from 4753132 to b556b3a Compare May 21, 2023 12:47
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 21, 2023
@danmanor
Copy link
Contributor Author

/test

@danmanor
Copy link
Contributor Author

danmanor commented Jun 6, 2023

/test edge-e2e-metal-assisted-mce

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 7, 2023
@osherdp
Copy link
Contributor

osherdp commented Jun 7, 2023

Looks good, I guess we first need to remove the jobs that are doing installation on top of 4.8

@danmanor danmanor changed the title WIP: MGMT-14631: Remove support for openshift 4.8 MGMT-14631: Remove support for openshift 4.8 Jun 7, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 7, 2023
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 7, 2023
@danmanor danmanor force-pushed the removing-support-for-openshift-4.8 branch from 41508f9 to 058d77f Compare June 8, 2023 07:45
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2023
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 8, 2023
@danmanor danmanor requested a review from osherdp June 8, 2023 07:47
@danmanor
Copy link
Contributor Author

danmanor commented Jun 8, 2023

@osherdp sorry, needed rebase

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2023
@danmanor danmanor force-pushed the removing-support-for-openshift-4.8 branch from 058d77f to f6ec2a9 Compare June 8, 2023 08:36
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2023
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 8, 2023
@danmanor danmanor force-pushed the removing-support-for-openshift-4.8 branch from f6ec2a9 to dad21ee Compare June 11, 2023 07:44
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 11, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 11, 2023
@openshift-ci
Copy link

openshift-ci bot commented Jun 11, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danmanor, osherdp

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:

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

@danmanor
Copy link
Contributor Author

/test edge-e2e-ai-operator-ztp

@danmanor
Copy link
Contributor Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 11, 2023
@openshift-ci
Copy link

openshift-ci bot commented Jun 11, 2023

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

@openshift-merge-robot openshift-merge-robot merged commit 76bd57a into openshift:master Jun 11, 2023
20 checks passed
danielerez pushed a commit to danielerez/assisted-service that referenced this pull request Oct 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants