Hello all,
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 [1].
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
cloud-init.
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
fixed.
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
[2]
Thank you in advance.
Federico
[1] https://marcelhauri.ch/blog/swapon-swapfile-has-holes/
[2]
https://docs.fedoraproject.org/en-US/Fedora/14/html/Storage_Administration_…
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2021-04-27 from 16:00:00 to 17:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://calendar.fedoraproject.org//meeting/1999/
Hi all!
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
Global:
Link 2 (eth0):
Link 3 (eth1):
$ resolvectl status
Global
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
DNSSEC=no/unsupported
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
(https://bodhi.fedoraproject.org/updates/FEDORA-2020-3616681a70)
includes this commit:
https://src.fedoraproject.org/rpms/systemd/c/ed795fb1fc9a2c20ebcac34bdf7e7c…
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
via cloud-init:
$ cat /etc/NetworkManager/conf.d/99-cloud-init.conf
# Created by cloud-init on instance boot automatically, do not edit.
#
[main]
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.
Regards,
Tadej
Hey All,
We are running a Fedora Linux 34 Cloud Test Day from Friday, April 16
through Monday, April 19. As a part of this test day[0] we will be
testing the Fedora Cloud Images. You can test the regular base image
using testcloud or if you have an Amazon account, you can test the
AMIs listed on the wiki. The results page[1], has the test cases which
are basic and must pass.
As usual, we will be around #fedora-test-day over freenode for any questions!
[0] https://fedoraproject.org/wiki/Test_Day:2021-04-16_Fedora_34_Cloud_Testday
[1] https://testdays.fedoraproject.org/events/112
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2021-04-13 from 16:00:00 to 17:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://calendar.fedoraproject.org//meeting/1999/