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

Drop redhat service from default nodeset samples #1229

Merged

Conversation

karelyatin
Copy link
Contributor

@karelyatin karelyatin commented Dec 16, 2024

The service requires rhel nodes to run which we
don't have upstream and so is not being tested.
Also enabling this service requires additional
vars like activationkey,token, username etc.

Also it broke some downstream jobs which running
older version of operators and using these upstream samples.

Related-Issue: OSPCIX-596

The service requires rhel nodes to run which we
don't have upstream and so is not being tested.
Also enabling this service requires additional
vars like activationkey,token, username etc.

Also it broke some downstream jobs which running
older version of operators and using these upstream
samples.

Related-Issue: OSPCIX-596
@openshift-ci openshift-ci bot requested review from bshephar and slagle December 16, 2024 08:07
@karelyatin
Copy link
Contributor Author

/test openstack-operator-build-deploy-kuttl

@fao89
Copy link
Contributor

fao89 commented Dec 16, 2024

it shouldn't break older versions, as the redhat service isn't on older samples: https://github.com/openstack-k8s-operators/openstack-operator/blob/18.0.0-proposed/config/samples/dataplane_v1beta1_openstackdataplanenodeset.yaml#L10-L25
if it is breaking, it means older versions are wrongly using the sample from the main branch

@karelyatin
Copy link
Contributor Author

it shouldn't break older versions, as the redhat service isn't on older samples: https://github.com/openstack-k8s-operators/openstack-operator/blob/18.0.0-proposed/config/samples/dataplane_v1beta1_openstackdataplanenodeset.yaml#L10-L25 if it is breaking, it means older versions are wrongly using the sample from the main branch

Yes that is one of the reason to remove it from default samples. it can be handled downstream by using different branches. But removing it from default is due to other reasons in commit message (just adding the service is not sufficient as require other vars to be configured and it's not being tested upstream) , additionally it will also fix the downstream jobs.

@karelyatin
Copy link
Contributor Author

/test openstack-operator-build-deploy-kuttl

@karelyatin
Copy link
Contributor Author

/test openstack-operator-build-deploy-kuttl
infra-operator pr merged

@karelyatin
Copy link
Contributor Author

/test openstack-operator-build-deploy-kuttl
storage cleanup

@karelyatin
Copy link
Contributor Author

/test openstack-operator-build-deploy-kuttl
quay.rdo

Copy link
Contributor

@slagle slagle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approving to unblock CI.
However, the other issue of downstream using the upstream samples from main should still be fixed separately. I just don't see that continuing to work long term.

Copy link
Contributor

openshift-ci bot commented Dec 17, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: karelyatin, slagle

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

@openshift-merge-bot openshift-merge-bot bot merged commit 6d3e5c2 into openstack-k8s-operators:main Dec 17, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants