Open naguam opened 4 years ago
https://github.com/coreos/rpm-ostree/pull/1984 will fix this.
Edit : I'm Sorry, I followed the motd link when I ssh on my FCOS vm but after reading the repo README, I realized that I should have posted It on the forum. (Even though I'm happy to contribute).
Don't worry about this. I think it wasn't clear if this was a bug or not so this tracker is fine for what you posted.
Thanks for engaging with us and being part of the community!
Hello, I'm really interested to the fedora coreos concept and I made a clean install of fedora coreos in a vm (with libvirt on a centos 8 host) following the official documentation. So I created the ignition file with the podman container as said in the link. Here is the basic yaml fcc file next converted in an ignition file.
Then I created the vm with the virt-install example (following the documation)
virt-install --connect qemu:///system -n fcos -r 1024 --os-variant=fedora-unknown --import --graphics=none --disk size=10,backing_store=/opt/fedora-coreos-31.20200118.3.0-qemu.x86_64.qcow2 --qemu-commandline="-fw_cfg name=opt/com.coreos/config,file=/opt/example.ign"
Everything worked as expected I could ssh in the coreos host. Then I inspected
systemctl status
, and he was in a running state (good sign).And finally, here is the why I write this issue. I did
dmesg -l err
and I had many udev errors. External site because too long logs There are many errors with groups not existing and ignoring words. I don't want to flood the issue tracker but If theses are important bugs, it's important for me to report them and if theses are not important, I was intriguedContent of
rpm-ostree status
.Edit : I'm Sorry, I followed the motd link when I ssh on my FCOS vm but after reading the repo README, I realized that I should have posted It on the forum. (Even though I'm happy to contribute).