Fix fallocate issue on cloud-init 19.4 for Fedora 33 cloud images
by Federico Ressi
I am writing to this list because I found out F33 cloud image cloud init
support for creating swap files looks to be broken probably because of a
known Linux 5.7+ kernel issue .
The problem is cloud-init is trying to create a new swap file by using
fallocate command that is not working well (kernel is complaining the file
has holes when executing swapon command just later). The easy workaround
for this issue is to use dd command instead of fallocate command in
Because I don't know the whole procedure required for submitting a patch I
am writing to you in the hope you can help me in having the F33 cloud image
Please find attached to this e-mail the simple fix for cloud init 19.4 I
just wrote. The patch should apply the procedure documented in Fedora docs
Thank you in advance.
2 years, 1 month
Fedora Cloud Meeting Minutes 2021-04-27
by Dusty Mabe
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2021-04-27/fedora_clou...
Meeting started by dustymabe at 15:59:56 UTC. The full logs are
* roll call (dustymabe, 16:00:01)
* fedora cloud test day (dustymabe, 16:02:20)
* test day results are at
* ACTION: nb to hand out Fedora Badges to everyone who participated in
the test day (dustymabe, 16:05:02)
* packaging cloud agents for GCP (dustymabe, 16:05:37)
* LINK: https://pagure.io/cloud-sig/issue/313 (dustymabe, 16:05:43)
* GCP packaging reviews from ericedens has been approved. pending
import and build in rawhide (dustymabe, 16:07:32)
* cloud-init doesn't properly forward nameservers to systemd-resolved
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1950770
* triage cloud-init bugs (dustymabe, 16:17:16)
* open floor (dustymabe, 16:21:50)
Meeting ended at 16:25:58 UTC.
* nb to hand out Fedora Badges to everyone who participated in the test
Action Items, by person
* nb to hand out Fedora Badges to everyone who participated in the
People Present (lines said)
* dustymabe (47)
* otubo (15)
* zodbot (14)
* mcatanzaro (7)
* Eighth_Doctor (4)
* nb (3)
* cyberpear (1)
* michaelgugino (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
2 years, 1 month
systemd update breaks DNS resolution on Fedora 33 cloud instances
by Tadej Janež
I was recently hit by this and it took me some time to figure out what
was going on.
I provisioned a fresh Fedora 33 cloud instance on DigitalOcean.
After completing the initial upgrade via 'dnf update' and rebooting the
system, DNS resolution stopped working.
I did a little debugging and saw that no DNS servers were configured:
$ resolvectl dns
Link 2 (eth0):
Link 3 (eth1):
$ resolvectl status
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (eth0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS
Link 3 (eth1)
I was confused how could that happen since running 'dnf update' on the
first boot clearly required DNS resolution to work.
It turns out a recent systemd update, namely systemd-246.7-2.fc33
includes this commit:
which removes the fallback DNS server list (i.e. Cloudflare's and/or
Google's DNS servers) due to concerns over DNS requests being
personally identifying information (PII) in the sense of GDPR?
In combination with NetworkManager's DNS server handling being disabled
$ cat /etc/NetworkManager/conf.d/99-cloud-init.conf
# Created by cloud-init on instance boot automatically, do not edit.
dns = none
this results in no DNS servers being configured on the system.
The consequence is that Fedora 33 cloud instances are broken after
updating the systemd package to version 246.7-2.fc33.
(I haven't checked but if Fedora 34 cloud images include this version
of systemd, then DNS resolution won't work even on first boot.)
Please advise on the best steps to fix this issue.
2 years, 1 month