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
Remove some cert approval related hacks. #686
Conversation
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.
lgtm if ci passes
Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/922/ |
Workers are failing to come up:
Do we need some logic to check if bmo pods are up first? |
The register_hosts script used to wait for a worker to come up, but I removed it since I didn't see anything that required waiting. It makes sense for CI purposes, though. I'll add something to |
This patch cleans up some hacks that are no longer needed. CSRs for masters are automatically approved by a service runningon the bootstrap node during the bootstrap process. Workers is where we are still missing some pieces. Move the fix-certs cron job to the register_hosts script, which is where worker deployment is kicked off. Also remove the add-machine-ips and link-machine-and-node scripts. cluster-api-provider-baremetal should now be automatically populating the addresses field of Machines based on introspection data it gets out of the BareMetalHost object for workers. Removing these scripts ensures we only rely on that code, and not a dev-script hack. The reigster_hosts script no longer waits for the worker to come up, since it's not required and the cluster should already be functional by this point. The run_ci script was updated to ensure the worker comes up to still make sure this case is tested.
35a8fcc
to
a991cca
Compare
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/925/ |
CI passes now. :-) |
This patch cleans up some hacks that are no longer needed. CSRs for
masters are automatically approved by a service runningon the
bootstrap node during the bootstrap process.
Workers is where we are still missing some pieces. Move the fix-certs
cron job to the register_hosts script, which is where worker
deployment is kicked off.
Also remove the add-machine-ips and link-machine-and-node scripts.
cluster-api-provider-baremetal should now be automatically populating
the addresses field of Machines based on introspection data it gets
out of the BareMetalHost object for workers. Removing these scripts
ensures we only rely on that code, and not a dev-script hack.
Related to issue #260.