MAO managed Metal3 deployment not functional #739
Comments
russellb
changed the title
russellb
added a commit
to russellb/dev-scripts
that referenced
this issue
Aug 29, 2019
This was previously disabled while we got some issues fixed up with the baremetal-operator deployment. This should now be working. Part of openshift-metal3#739
|
I propose we close this and track fixing the version of ironic in CI builds separately, since it's not strictly related to the issues we had with the MAO |
|
#788 raised to track CI image issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The machine-api-operator now manages the Deployment of the baremetal-operator and its dependencies. The Deployment is named
metal3. This support first merged in #726This Deployment does not currently come up successfully. This issue is used to track the work to get it in a functional state.
Relevant PRs or Issues:
baremetal: Adjust container order for baremetal pod openshift/machine-api-operator#382run_ci.shto wait for a successful worker again - Update CI to wait for a worker to come up. #783Fixing version of ironic included in CI releases:- [ ] openshift/release#4835- [ ] openshift/release#4836- [ ] openshift/release#4837The text was updated successfully, but these errors were encountered: