-
Notifications
You must be signed in to change notification settings - Fork 87
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
Don't use baremetal-operator API in functional tests. #1248
Don't use baremetal-operator API in functional tests. #1248
Conversation
6ce9501
to
8f30033
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this sounds good to me.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bshephar, fao89, rabi 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 |
We can't refactor baremetal-operator API as the tests fail when building openstack-operator with a baremetal-operator change. Signed-off-by: rabi <[email protected]>
8f30033
to
0f4edc7
Compare
New changes are detected. LGTM label has been removed. |
Had to be rebased as #1245 merged before this, we did not need that. |
/test openstack-operator-build-deploy-kuttl |
1 similar comment
/test openstack-operator-build-deploy-kuttl |
Kuttl failure unrelated:
|
/test openstack-operator-build-deploy-kuttl |
800f323
into
openstack-k8s-operators:main
We can't refactor baremetal-operator API as the tests fail when building openstack-operator with a baremetal-operator change.