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

Add emmc support #23

Merged
merged 1 commit into from
Feb 1, 2021
Merged

Add emmc support #23

merged 1 commit into from
Feb 1, 2021

Conversation

detiber
Copy link
Contributor

@detiber detiber commented Jan 29, 2021

Adds the support needed for us-east-detiber

@detiber
Copy link
Contributor Author

detiber commented Jan 29, 2021

Still working on testing this build

@thebsdbox
Copy link
Contributor

Adds the support needed for us-east-detiber

Arguably the most import region! Thanks for the pr (once tested)

@detiber
Copy link
Contributor Author

detiber commented Feb 1, 2021

Looks like it is still missing something, will do some more digging...

@detiber
Copy link
Contributor Author

detiber commented Feb 1, 2021

Ok, updated and tested and successfully ran a workflow with these kernel changes.

It wasn't clear to me how the kernel is picked up through the build pipeline, though.

@detiber detiber changed the title [WIP] Add emmc support Add emmc support Feb 1, 2021
@gianarb gianarb merged commit cb1336f into tinkerbell:master Feb 1, 2021
@gianarb
Copy link
Contributor

gianarb commented Feb 1, 2021

Great! Yeah it is not clear because I do it manually right now. We didn't build a good story yet @thebsdbox

mmlb pushed a commit to mmlb/tinkerbell-hook that referenced this pull request Jul 16, 2021
## Description


```
time="2021-03-04T13:18:50Z" level=info msg="Successfully written [%s] to [%s]http://192.168.1.2/focal-server-cloudimg-amd64.raw/dev/sdb"
```
Wrong function is being called here `info` -> `infof`
<!--- Please describe what this PR is going to change -->

## Why is this needed

The success meeting is mis-formatted.

<!--- Link to issue you have raised -->

Fixes: #

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->


## How are existing users impacted? What migration steps/scripts do we need?

<!--- Fixes a bug, unblocks installation, removes a component of the stack etc -->
<!--- Requires a DB migration script, etc. -->


## Checklist:

I have:

- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants