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

ProxmoxVE instance fails to boot if no config drive is configured #1126

Open
tormath1 opened this issue Nov 4, 2024 · 0 comments · May be fixed by #1128
Open

ProxmoxVE instance fails to boot if no config drive is configured #1126

tormath1 opened this issue Nov 4, 2024 · 0 comments · May be fixed by #1128

Comments

@tormath1
Copy link
Contributor

tormath1 commented Nov 4, 2024

Bug

If an instance tries to boot on ProxmoxVE without configdrive afterburn will fail to execute correctly and if used for setting hostname the instance will land into emergency shell: https://github.com/coreos/afterburn/blob/main/dracut/30afterburn/afterburn-hostname.service#L31

Operating System Version

Flatcar

Afterburn Version

Latest (5.7.0)

Environment

What hardware/cloud provider/hypervisor is being used to run Afterburn? ProxmoxVE

Expected Behavior

If the config drive does not exist, just exits without error.

Actual Behavior

Emergency shell, the instance does not boot.

Reproduction Steps

  1. Boot the instance on ProxmoxVE without config drive

Other Information

if not config drive:
  exit(0)
[   62.633185] localhost coreos-metadata[704]: Error: failed to run
[   62.633185] localhost coreos-metadata[704]: Caused by:
[   62.633185] localhost coreos-metadata[704]:     0: fetching metadata from provider
[   62.633185] localhost coreos-metadata[704]:     1: maximum number of retries (3) reached
[   62.633185] localhost coreos-metadata[704]:     2: failed to mount (read-only) source '/dev/disk/by-label/cidata' to target '/tmp/afterburn-Kk3KoQ', with type 'iso9660'
[   62.633185] localhost coreos-metadata[704]:     3: ENOENT: No such file or directory
[   62.691725] localhost coreos-metadata[705]: Error: failed to run
[   62.691725] localhost coreos-metadata[705]: Caused by:
[   62.691725] localhost coreos-metadata[705]:     0: fetching metadata from provider
[   62.691725] localhost coreos-metadata[705]:     1: maximum number of retries (3) reached
[   62.691725] localhost coreos-metadata[705]:     2: failed to mount (read-only) source '/dev/disk/by-label/cidata' to target '/tmp/afterburn-2FVY0i', with type 'iso9660'
[   62.691725] localhost coreos-metadata[705]:     3: ENOENT: No such file or directory
[   62.749605] localhost systemd[1]: Dependency failed for initrd.target - Initrd Default Target.
[   62.757531] localhost systemd[1]: initrd.target: Job initrd.target/start failed with result 'dependency'.
[   62.786512] localhost systemd[1]: initrd.target: Triggering OnFailure= dependencies.
[   62.792755] localhost systemd[1]: flatcar-metadata-hostname.service: Main process exited, code=exited, status=1/FAILURE
[   62.799649] localhost systemd[1]: flatcar-metadata-hostname.service: Failed with result 'exit-code'.
@tormath1 tormath1 changed the title ProxmoxVE instance fails to boot if not config drive is configured ProxmoxVE instance fails to boot if no config drive is configured Nov 4, 2024
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 a pull request may close this issue.

1 participant