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

Remove some cert approval related hacks. #686

Merged
merged 1 commit into from Jul 24, 2019

Conversation

russellb
Copy link
Member

@russellb russellb commented Jul 23, 2019

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.

@russellb russellb added the CI check this PR with CI label Jul 23, 2019
Copy link
Member

@stbenjam stbenjam left a 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

@metal3ci
Copy link

Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/922/

@stbenjam
Copy link
Member

Workers are failing to come up:

Error from server (BadRequest): container "baremetal-operator" in pod "metal3-baremetal-operator-74fdb86688-wq8v9" is waiting to start: PodInitializing

Do we need some logic to check if bmo pods are up first?

@russellb
Copy link
Member Author

Workers are failing to come up:

Error from server (BadRequest): container "baremetal-operator" in pod "metal3-baremetal-operator-74fdb86688-wq8v9" is waiting to start: PodInitializing

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 run_ci.sh

@russellb russellb changed the title Remove some cert approval related hacks. WIP: Remove some cert approval related hacks. Jul 23, 2019
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.
@metal3ci
Copy link

Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/925/

@russellb russellb changed the title WIP: Remove some cert approval related hacks. Remove some cert approval related hacks. Jul 23, 2019
@russellb
Copy link
Member Author

CI passes now. :-)

@russellb russellb merged commit 6b4b6b9 into openshift-metal3:master Jul 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI check this PR with CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants