-
-
Notifications
You must be signed in to change notification settings - Fork 784
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
Paramiko Error Reading SSH Protocol Banner #8
Comments
The SSH key should be generated automatically if it doesn't exist: Line 8 in fc2987e
However, debugging PXE boot is a bit tricky, probably the hardest part of the homelab to debug (a monitor is highly recommended), have you tried the following https://homelab.khuedoan.com/troubleshooting? |
I recalled to have this one when my servers auto-booted into the pre-installed Ubuntu that I had. What I did was plugged the monitor in and manually pick the correct boot option. After that, it's all okay. |
Thanks! I’ll give that a read.
… On Dec 30, 2021, at 11:35 PM, Khue Doan ***@***.***> wrote:
The SSH key should be generated automatically if it doesn't exists:
https://github.com/khuedoan/homelab/blob/fc2987ee42cc77354545a52a4174d5511d59ec2e/metal/Makefile#L8
However, debugging PXE boot is a bit tricky (a monitor is highly recommended), have you tried the following https://homelab.khuedoan.com/troubleshooting.html?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.
|
This actually makes perfect sense because I also have a Ubuntu pre-installed. I will hookup a monitor and look.
… On Dec 30, 2021, at 11:41 PM, Loc Mai ***@***.***> wrote:
I recalled to have this one when my servers auto-booted into the pre-installed Ubuntu that I had. What I did was plugged the monitor in and manually pick the correct boot option. After that, it's all okay.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.
|
I can close this as my nodes were not in the PXE ready state. Sorry for the false issue. |
… from renovate/renovate-32.x into master Reviewed-on: https://git.tribz.cloud/ops/homelab/pulls/8
… from renovate/paperless-9.x into master Reviewed-on: https://git.zanelab.com/ops/homelab/pulls/8
…m renovate/gitea-7.x into master Reviewed-on: https://git.zanelab.com/zhala/homelab/pulls/8
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [gopkg.in/yaml.v2](https://github.com/go-yaml/yaml) | require | major | `v2.4.0` -> `v3.0.1` | :warning: Release Notes retrieval for this PR were skipped because no github.com credentials were available. If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes). --- ### Configuration 📅 **Schedule**: At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). Co-authored-by: Renovate Bot <bot@renovateapp.com> Reviewed-on: https://git.atte.cloud/ops/homelab/pulls/8 Co-authored-by: gitea_admin <gitea@local.domain> Co-committed-by: gitea_admin <gitea@local.domain>
…n#15) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [gopkg.in/yaml.v2](https://github.com/go-yaml/yaml) | require | major | `v2.4.0` -> `v3.0.1` | :warning: Release Notes retrieval for this PR were skipped because no github.com credentials were available. If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes). --- ### Configuration 📅 **Schedule**: At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). Co-authored-by: Renovate Bot <bot@renovateapp.com> Reviewed-on: https://git.atte.cloud/ops/homelab/pulls/8 Co-authored-by: gitea_admin <gitea@local.domain> Co-committed-by: gitea_admin <gitea@local.domain> Co-authored-by: gitea_admin <gitea@local.domain> Reviewed-on: https://git.atte.cloud/ops/homelab/pulls/15
… from renovate/renovate-37.x into master Reviewed-on: https://git.qos.cc/ops/homelab/pulls/8
… from renovate/snapshot-controller-3.x into master Reviewed-on: https://git.west-beta.ts.net/ops/homelab2/pulls/8
khuedoan#8) from renovate/woodpecker-3.x into master Reviewed-on: https://git.havki.no/ops/homelab/pulls/8
Nodes don't seem to connect. I am probably doing something wrong as I am still learning Ansible.
Wondering does this mean the PXE boot to rocky has completed?
In the file ./metal/group_vars/all.yml do I need to generate the ed25519 ssh key?
Thanks for any info!
The text was updated successfully, but these errors were encountered: