-
Notifications
You must be signed in to change notification settings - Fork 30
coreos-metadata.service: Caused by: Couldn't find 'coreos.oem.id' flag in cmdline file (/proc/cmdline) #2303
Comments
I don't expect coreos-metadata to support any platforms without a metadata service. The intention of coreos-metadata is just to consolidate all of the You can use something like this example as your service. It fundamentally the same way as coreos-metadata, it just doesn't have any fancy code. I hope that makes sense. |
Oh interesting, I see what you mean @crawford. I just need to make sure this oneshot service starts before 'everything' else, yes? |
Exactly. |
I missed this initial bug-report, but I've left a similar comment when reviewing the resulting PR: coreos/afterburn#81 (comment). I'd guess this ticket can be closed then. |
Hi @crawford, Apologies up front if these questions are "stupid", I'm just getting up to speed and had a few questions: 1) Do I need to manually add a
|
@nickgrealy trying to answer most of your questions here, but if you keep having doubts on your journey please prefer the ML for discussion.
|
Issue Report
Bug
Container Linux Version
core@coreA11 ~ $ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1590.2.0
VERSION_ID=1590.2.0
BUILD_ID=2017-12-06-0313
PRETTY_NAME="Container Linux by CoreOS 1590.2.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
Environment
Hardware: Bare-metal Ubuntu running Libvirt/Kvm with CoreOS as the guest VM
Expected Behavior
coreos-metadata.service agent should start
Actual Behavior
jforman@desktop1:~$ ssh core@10.10.0.226
Container Linux by CoreOS beta (1590.2.0)
Failed Units: 1
coreos-metadata.service
core@coreA11 ~ $ systemctl status coreos-metadata.service
● coreos-metadata.service - CoreOS Metadata Agent
Loaded: loaded (/usr/lib/systemd/system/coreos-metadata.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-12-25 14:08:28 UTC; 36s ago
Process: 701 ExecStart=/usr/bin/coreos-metadata ${COREOS_METADATA_OPT_PROVIDER} --attributes=/run/metadata/coreos (code=exited, status=1/FAILURE)
Main PID: 701 (code=exited, status=1/FAILURE)
Dec 25 14:08:28 coreA11 systemd[1]: Starting CoreOS Metadata Agent...
Dec 25 14:08:28 coreA11 systemd[1]: coreos-metadata.service: Main process exited, code=exited, status=1/FAILURE
Dec 25 14:08:28 coreA11 systemd[1]: coreos-metadata.service: Failed with result 'exit-code'.
Dec 25 14:08:28 coreA11 systemd[1]: Failed to start CoreOS Metadata Agent.
core@coreA11 ~ $ cat /usr/lib/systemd/system/coreos-metadata.service
[Unit]
Description=CoreOS Metadata Agent
[Service]
Type=oneshot
Environment=COREOS_METADATA_OPT_PROVIDER=--cmdline
ExecStart=/usr/bin/coreos-metadata ${COREOS_METADATA_OPT_PROVIDER} --attributes=/run/metadata/coreos
[Install]
RequiredBy=metadata.target
core@coreA11 ~ $ /usr/bin/coreos-metadata --cmdline --attributes=/run/metadata/coreos
Error: initialization
Caused by: Couldn't find 'coreos.oem.id' flag in cmdline file (/proc/cmdline)
Reproduction Steps
Reboot the VM. Any login. The service just doesn't start.
Other Information
I used the vagrant-virtualbox config transpiler platform for creating my ignition config.
I plan to try to hack on the coreos-metadata repo to add support for libvirt as a provider (vagrant-virtualbox does not work as a provider since it expects eth1 as the network interface, where as libvirt provides eth0 by default).
The text was updated successfully, but these errors were encountered: