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

Update bootstrap script in light of installer refactorings #3592

Merged
merged 1 commit into from Oct 7, 2017

Conversation

christophermaier
Copy link
Contributor

The recent refactoring of our installation logic (#3344) inadvertently
broke our bootstrap installation logic. Apparently, the earlier logic
pulled dependent hart files from the same directory as the hart file
being installed. In the new logic, it does not do this, but pulls
everything from Builder through the artifact cache.

The solution here is simply to place all the artifacts into the cache
before installing the desired packages, just as we do with the public
signing keys. True, we end up with some additional packages in our
artifact cache, but that's fine. Besides, once we implement #3499, we
can even clean those up.

Fixes #3591

@thesentinels
Copy link
Contributor

Thanks for the pull request! Here is what will happen next:

  1. Your PR will be reviewed by the maintainers
  2. If everything looks good, one of them will approve it, and your PR will be merged.

Thank you for contributing!

The recent refactoring of our installation logic (#3344) inadvertently
broke our bootstrap installation logic. Apparently, the earlier logic
pulled dependent hart files from the same directory as the hart file
being installed. In the new logic, it does not do this, but pulls
everything from Builder through the artifact cache.

The solution here is simply to place all the artifacts into the cache
before installing the desired packages, just as we do with the public
signing keys. True, we end up with some additional packages in our
artifact cache, but that's fine. Besides, once we implement #3499, we
can even clean those up.

Fixes #3591

Signed-off-by: Christopher Maier <cmaier@chef.io>
@mwrock
Copy link
Contributor

mwrock commented Oct 7, 2017

@thesentinels approve

@thesentinels
Copy link
Contributor

🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests.

@chefsalim
Copy link
Contributor

@thesentinels approve

tenor-85089536

@thesentinels
Copy link
Contributor

🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests.

@reset
Copy link
Collaborator

reset commented Oct 7, 2017

tenor-23803553

@thesentinels
Copy link
Contributor

:neckbeard: Travis CI has started testing this PR.

@thesentinels
Copy link
Contributor

💖 Travis CI reports this PR passed.

It always makes me feel nice when humans approve of one anothers work. I'm merging this PR now.

I just want you and the contributor to answer me one question:

gif-keyboard-3280869874741411265

@thesentinels thesentinels merged commit 9ce8276 into master Oct 7, 2017
@thesentinels thesentinels deleted the cm/3591-fix-bootstrapping branch October 7, 2017 01:52
@christophermaier christophermaier added Type: Bug Issues that describe broken functionality Type: Chore Issues for general code and infrastructure maintenance and removed C-bug labels Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issues that describe broken functionality Type: Chore Issues for general code and infrastructure maintenance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bootstrapping nodes still can require access to prod builder
5 participants