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.

Sign up for GitHub

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

Jump to bottom

Tink_worker on sandbox deployment fails with CERT issue #145

Closed
umashankar1988 opened this issue Jul 21, 2022 · 3 comments · Fixed by #154
Closed

Tink_worker on sandbox deployment fails with CERT issue #145

umashankar1988 opened this issue Jul 21, 2022 · 3 comments · Fixed by #154

Comments

@umashankar1988
Copy link

As soon as the tink_worker is started it fails with an error x509 : certificate signed by unknown authority at linuxkit

Expected Behaviour

The tink_worker should work as the certificate is signed by Tinkerbell CA

Current Behaviour

The linuxkit boot screen is stuck waiting for the deployment. Upon checking the logs of the container we see that it fails to start with Unknown certificate issue.

Possible Solution

Need to sign the certificate properly

Steps to Reproduce (for bugs)

  1. Run the docker container sandbox
  2. Complete the template, hardware and workflow
  3. Wait for the physical machine to acquire PXE boot and start of linuxkit
  4. Linuxkit is stuck waiting for the container (tink_worker) to start. Upon evaluating the container logs we see the x509: certificate signed by Unknown authority.

Context

We are using tinkerbell in production to provision multiple linux physical machines and this issue has stopped us from moving forward.

Your Environment

  • Operating System and version (e.g. Linux, Windows, MacOS):

Ubuntu 18.04

  • How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:

Using docker-compose from sandbox ( https://github.com/tinkerbell/sandbox/tree/main/deploy/compose)

  • Link to your project or a code example to reproduce issue:

image
@parauliya
Copy link

@gianarb , Did you get a chance to have a look at this issue? because I am also facing some cert related issues in tink-worker from last couple of days while setting it up on local machine using vagrant and virtualbox on Ubuntu 20.04.
I have not created a new ticket/issue because I think it is somewhat similar to this one.

@jacobweinstock
Copy link
Member

jacobweinstock commented Aug 15, 2022 •
edited
Loading

Hey @umashankar1988, sorry for the delayed response. I've experienced this before and was able to resolve it by deleting the ca.pem file (this is in the deploy/compose/state/webroot/workflow/ dir) and then docker-compose down and docker-compose up -d. Mind trying that?

@umashankar1988
Copy link
Author

umashankar1988 commented Aug 17, 2022 •
edited
Loading

Hi @jacobweinstock I tried using the steps suggested above but the issue still remains the same. Below is a screenshot of docker container logs from the worker

MicrosoftTeams-image

@jacobweinstock jacobweinstock mentioned this issue Oct 5, 2022
Merged
3 tasks
@jacobweinstock jacobweinstock linked a pull request Oct 5, 2022 that will close this issue
k8s docker-compose #154
Merged
3 tasks
mergify bot added a commit that referenced this issue Oct 25, 2022
@mergify
k8s docker-compose (#154)
f180972 
## Description


This PR brings up the sandbox via Docker compose using the Kubernetes backend for all service. This does not completely remove the postgres backend setup but moves all the compose with postgres into an isolated directory (deploy/compose/postgres) that can be removed when we're ready. 

> I did not touch the terraform setup. I need some help validating that one. please and thank you. CC @mmlb @displague

## Why is this needed



Fixes: #142 #45 #118 #131 #133 #145 #148 
- This "fixes" a quite a few issues related to TLS cert generation. This is the case because we are not using TLS in this deployment. Also see, tinkerbell/tink#555.
- This also "fixes" any issues related to the internal registry as that is removed as the default.

## How Has This Been Tested?



Manually tested vagrant with virtualbox (on a Mac), vagrant with libvirt (on Ubuntu 22.04), and docker-compose (on on Ubuntu 22.04). 


## How are existing users impacted? What migration steps/scripts do we need?
There is no migration support. Users will need to follow a quick start guide to get started.





## Checklist:

I have:

- [x] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
@mergify mergify bot closed this as completed in #154 Oct 25, 2022
ttwd80 pushed a commit to ttwd80/tinkerbell-playground that referenced this issue Sep 7, 2024
@mergify
k8s docker-compose (tinkerbell#154)
1c9b833 
## Description


This PR brings up the sandbox via Docker compose using the Kubernetes backend for all service. This does not completely remove the postgres backend setup but moves all the compose with postgres into an isolated directory (deploy/compose/postgres) that can be removed when we're ready. 

> I did not touch the terraform setup. I need some help validating that one. please and thank you. CC @mmlb @displague

## Why is this needed



Fixes: tinkerbell#142 tinkerbell#45 tinkerbell#118 tinkerbell#131 tinkerbell#133 tinkerbell#145 tinkerbell#148 
- This "fixes" a quite a few issues related to TLS cert generation. This is the case because we are not using TLS in this deployment. Also see, tinkerbell/tink#555.
- This also "fixes" any issues related to the internal registry as that is removed as the default.

## How Has This Been Tested?



Manually tested vagrant with virtualbox (on a Mac), vagrant with libvirt (on Ubuntu 22.04), and docker-compose (on on Ubuntu 22.04). 


## How are existing users impacted? What migration steps/scripts do we need?
There is no migration support. Users will need to follow a quick start guide to get started.





## Checklist:

I have:

- [x] 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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

k8s docker-compose jacobweinstock/playground
3 participants
@umashankar1988 @jacobweinstock @parauliya