-
Notifications
You must be signed in to change notification settings - Fork 515
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
MCO-1305: Promoting ManagedBootImagesAWS to default featureset #2079
base: master
Are you sure you want to change the base?
Conversation
@djoshy: This pull request references MCO-1305 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 story to target the "4.18.0" version, but no target version was set. 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. |
Hello @djoshy! Some important instructions when contributing to openshift/api: |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: djoshy The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
CRD generation appears to be out of date, please make sure to update the CRDs |
The field is on MachineConfig right? Is MachineConfig not exposed in HyperShift? Why is this not applicable to HyperShift? Is there an enhancement that explains why? Could you please ask QE to comment that they are happy with the feature promotion please Also, I noticed that this test and this test were failing a week ago, do we know why they were failing, and has a fix been made? |
As we understand it, Hypershift uses NodePools and not MachineSets, so this feature is not applicable for them
Will do!
This was a timeout issue(possibly due to slow cleanup from an unrelated test that ran before it) : openshift/origin#29210; https://issues.redhat.com//browse/OCPBUGS-43512. This would cascade on to the other test, but the root cause was not giving enough time for the test listed in the bug to not finish. |
Hello! We will start the pre-merge verification of this feature ASAP. We hold it until we can add the qe-approved label. Please, @ptalgulk01 , could you start the pre-merge testing? thanks! /hold |
/retest-required |
Pre-merge verification commented here: https://issues.redhat.com/browse/MCO-1335?focusedCommentId=25984304&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-25984304 Once this jobs are completed I will add QE approved label . |
@djoshy: The following test failed, say
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. |
This PR promotes the managed boot image feature for the AWS platform to GA for 4.18. It has supporting tests in openshift/origin here:
Since this feature is not applicable for the Hypershift platform, it does not have Hypershift tests and it is failing for that variant in
make verify
. This should be safe to skip.