Fedora 20 cloud plans?
by Matthew Miller
With F19 almost out the door, it's time to shift attention to the next
thing!
Here's what I'm thinking about right now; would love to hear your opinions
and advice here, and also about other things in the cloud arena which we
should be working on.
Cloud Image Generation
======================
- finally getting this automated weekly in koji, to a download
site and to EC2. See notes for this at
https://fedoraproject.org/wiki/Features/FirstClassCloudImages/KojiPlan
- move to Oz (or other fully anaconda-based image generation)
Improving the Cloud Image
=========================
- cloud-util improvement
- subpackaging growpart means we don't need to pull in huge deps (bz #975497)
- cloud-init improvements
- can we remove the cheetah dependency? (bz #974327)
- other dependency softening (eg bz #974329, bz #786488)
- disable direct writes to the console, which will address several
problems (bz #977952)
- others?
- disable the gettys by default?
- look at the logging configuration (rsyslog/journald double-logging issue;
look at memory and on-disk journald consumption)
- more reductionism as reasonable -- maybe we can look at tackling the docs,
translations, and kernel-modules size issues? burn sendmail with fire?
get systemd-journal-gatewayd out of the image so it stops pulling in the
libmicrohttpd web server and crypto libs which wouldn't be there otherwise
(bz #908081)
Vagrant
=======
- We're blocked from having "real" vagrant base boxes by a lack of Chef,
which is blocked by bz #823351; hope to have that resolved and Chef as
an F20 feature
- Also, Vagrant is very Virtualbox-centric, and we don't have that in Fedora
(out of tree kernel modules); work on a KVM provider for Vagrant should
make that a non-issue -- https://github.com/adrahon/vagrant-kvm
Cloud Infrastructure Software
=============================
- OpenNebula?
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
10 years, 9 months
Should Fedora revisit the idea having "one " image to be used across the cloud providers?
by Kashyap Chamarthy
(Re-directing the discussion from #fedora-cloud on Freenode..)
Heya,
(Without trying to make it a large 'theoretical' discussion..)
So, should we (Fedora) reconsider the "noble goal" (as Matthew Miller put it) of having
one cloud image serve all cloud providers? Or separate images (sure, there's more work
involved) that are specific
Because, lately we've seen several problems where cloud-init has been breaking things in
subtle ways, like output of boot messages on console.log for OpenStack/Amazon/Eucalyptus
has been broken in different
Garret Holmstrom and Matthew Miller (both who's been in the trenches of these issues can
describe much better than I can at this midnight hour). They also discussed a couple of
ideas on IRC like
- configuring journald to forward to both syslog and the console
e.g. (please read the issue described above)
https://bugzilla.redhat.com/show_bug.cgi?id=977952 -- RFE: disable all direct writes to
the console
And, comparing Fedora images with Cirros -- they output a neat array of bunch of commands
(I think I noted this previously on this list) that's helpful for debugging. Refer this
previous thread
https://lists.fedoraproject.org/pipermail/cloud/2013-April/002371.html
but haven't reached a proper conclusion.
Any further thoughts from other folks here on how to resolve this would be nice to hear.
--
/kashyap
10 years, 9 months
Fedora 19 RC2 amis
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Along with the RC2 cloud images at
http://dl.fedoraproject.org/pub/alt/stage/19-RC2/Images/
there is the ec2 amis:
ami-274d3e4e : us-east-1 image for i386
ami-3f4d3e56 : us-east-1 image for x86_64
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlHLNmcACgkQkSxm47BaWfcLXgCgkp+SrC8X+mgpxO60S9YFgiTc
W1IAnAhtmMiv/ytbp7L2dPgvjzBw/bhH
=AA2f
-----END PGP SIGNATURE-----
10 years, 9 months
Fedora 19 RC1 AMI's
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Along with the RC1 cloud images at
http://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/
there is the ec2 amis:
ami-ef1b6886 : us-east-1 image for i386
ami-79196a10 : us-east-1 image for x86_64
Ideally these will be Fedora 19 Final.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlHJnLkACgkQkSxm47BaWfecaACcCWmV2osIONwD5doBc8QyF92c
JggAniM7J43Zl1OIDQ5hdIwBh3fr4d9O
=r2gt
-----END PGP SIGNATURE-----
10 years, 9 months
TC6 cloud images available in EC2 and for download
by Matthew Miller
Fedora 19 Test Candidate 6 cloud images are now available from:
https://dl.fedoraproject.org/pub/alt/stage/19-TC6/Images/
in either qcow2 or raw.xz form. You should be able to use Glance in
OpenStack to just import the qcow2 images directly and go.
They're also in Amazon EC2 in the US East region;
ami-93c3b2fa for x86_64
ami-17c2b37e for i386
Thanks to Dennis Gilmore in Fedora Release Engineering for the extra work to
make this happen.
The images are configured with "fedora" as the default user with sudo. You
can change this behavior by passing different configuration data via the
user-data in either OpenStack or EC2. For example, to allow direct root
login and to suppress the creation of the 'fedora' user, use
#cloud-config
users:
disable_root: 0
(The first line is identifying the userdata type, not a comment.)
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
10 years, 10 months
Test Results for F19 EC2 AMIs
by Tim Flink
We have a little over a week until the first F19 final go/no-go meeting
(where we decide whether or not the release is done) and there are no
posted results for F19 final AMI tests yet.
If you have been testing the AMIs, please report your results. If you
haven't been testing them but are interested in doing so - please do.
Show stoppers for the AMIs are likely to be release blocking and the
sooner that those issues are discovered, the less likely that we'll
slip the F19 final release.
To report results or to find test cases, please visit:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
This will redirect to the most recent spin (TC5 at the time of this
email).
The relevant test cases are:
- QA:Testcase_EC2_AMI_Validation
- QA:Testcase_Boot_Methods_Xen_Para_Virt
There are links to the specific test cases from the test matrices and
result reporting is just editing the wiki page (there are example
result formats on the page as well).
Thanks,
Tim
10 years, 10 months
double logging -- should we turn one of these off?
by Matthew Miller
Sooooo. As of systemd 198-1, (March 7th), systemd enables persistent logging
of the journal by default -- that means, it's writing it to disk.
I'm not really excited about logging every event twice in the cloud image.
The journal will do handwavy magic to automatically keep from running out of
space, but until it hits its threshold, it _will_ be using up more disk.
I posted a message to the main devel list last year sometime about what
realistic requirements Fedora might have for making the systemd journal the
default logging option for the whole distro. (See
https://lists.fedoraproject.org/pipermail/devel/2012-October/172682.html)
Of the things I listed as critical, some very key ones like time-based
rotation and "journal format documented" are done. Others are still lacking,
like a mechanism for separation of authpriv data, easy Fedora-centric
disaster recovery documentation, and, simply, a lot of QA and testing.
So, the question is: do we want to be part of the testing ground for this?
There are some advantages, including of course less stuff in the image,
and anyone wanting more complicated configuration can easily install
rsyslog, and, given limited space, automatic free space management.
Or, do we want to disable the persistent store, and rely on rsyslog?
Or, do we want to just leave it?
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
10 years, 10 months
3 commits - generic/fedora-19-i386-cloud.ks generic/fedora-19-i386.ks generic/fedora-19-i386-minimal.ks generic/fedora-19-x86_64-cloud.ks generic/fedora-19-x86_64.ks generic/fedora-19-x86_64-minimal.ks
by Matthew Miller
generic/fedora-19-i386-cloud.ks | 16 ++++++++++------
generic/fedora-19-i386-minimal.ks | 13 ++++++-------
generic/fedora-19-i386.ks | 16 ++++++++++------
generic/fedora-19-x86_64-cloud.ks | 16 ++++++++++------
generic/fedora-19-x86_64-minimal.ks | 13 ++++++-------
generic/fedora-19-x86_64.ks | 16 ++++++++++------
6 files changed, 52 insertions(+), 38 deletions(-)
New commits:
commit 31947b0bbb7c0f3a280d5c51be88bde06f608d5b
Author: Matthew Miller <mattdm(a)mattdm.org>
Date: Thu Jun 20 09:50:39 2013 -0400
Revert fstrim commit because it's causing build problems. Old way slow but
effective.
In virt-install via kvm, getting "FITRIM ioctl failed: Operation not
supported". Also fails in appliance-creator via koji -- probably EL kernel mismatch.
This reverts commit 7052fa9cd6364e45dee1a5f3fe03f95e69f71fe1.
diff --git a/generic/fedora-19-i386-cloud.ks b/generic/fedora-19-i386-cloud.ks
index 13f0117..9756947 100644
--- a/generic/fedora-19-i386-cloud.ks
+++ b/generic/fedora-19-i386-cloud.ks
@@ -221,8 +221,11 @@ echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
-echo "Zeroing out empty space with fstrim."
-/usr/sbin/fstrim /
+echo "Zeroing out empty space."
+# This forces the filesystem to reclaim space from deleted files
+dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
+rm -f /var/tmp/zeros
+echo "(Don't worry -- that out-of-space error was expected.)"
%end
diff --git a/generic/fedora-19-i386-minimal.ks b/generic/fedora-19-i386-minimal.ks
index 533bb16..773cee8 100644
--- a/generic/fedora-19-i386-minimal.ks
+++ b/generic/fedora-19-i386-minimal.ks
@@ -188,8 +188,11 @@ echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
-echo "Zeroing out empty space with fstrim."
-/usr/sbin/fstrim /
+echo "Zeroing out empty space."
+# This forces the filesystem to reclaim space from deleted files
+dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
+rm -f /var/tmp/zeros
+echo "(Don't worry -- that out-of-space error was expected.)"
%end
diff --git a/generic/fedora-19-i386.ks b/generic/fedora-19-i386.ks
index 502576d..65b4c37 100644
--- a/generic/fedora-19-i386.ks
+++ b/generic/fedora-19-i386.ks
@@ -180,8 +180,11 @@ echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
-echo "Zeroing out empty space with fstrim."
-/usr/sbin/fstrim /
+echo "Zeroing out empty space."
+# This forces the filesystem to reclaim space from deleted files
+dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
+rm -f /var/tmp/zeros
+echo "(Don't worry -- that out-of-space error was expected.)"
%end
diff --git a/generic/fedora-19-x86_64-cloud.ks b/generic/fedora-19-x86_64-cloud.ks
index 469310f..cce623d 100644
--- a/generic/fedora-19-x86_64-cloud.ks
+++ b/generic/fedora-19-x86_64-cloud.ks
@@ -218,8 +218,11 @@ echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
-echo "Zeroing out empty space with fstrim."
-/usr/sbin/fstrim /
+echo "Zeroing out empty space."
+# This forces the filesystem to reclaim space from deleted files
+dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
+rm -f /var/tmp/zeros
+echo "(Don't worry -- that out-of-space error was expected.)"
%end
diff --git a/generic/fedora-19-x86_64-minimal.ks b/generic/fedora-19-x86_64-minimal.ks
index 6777c20..3ad7614 100644
--- a/generic/fedora-19-x86_64-minimal.ks
+++ b/generic/fedora-19-x86_64-minimal.ks
@@ -186,8 +186,11 @@ echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
-echo "Zeroing out empty space with fstrim."
-/usr/sbin/fstrim /
+echo "Zeroing out empty space."
+# This forces the filesystem to reclaim space from deleted files
+dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
+rm -f /var/tmp/zeros
+echo "(Don't worry -- that out-of-space error was expected.)"
%end
diff --git a/generic/fedora-19-x86_64.ks b/generic/fedora-19-x86_64.ks
index 1c1794b..d2aba45 100644
--- a/generic/fedora-19-x86_64.ks
+++ b/generic/fedora-19-x86_64.ks
@@ -178,8 +178,11 @@ echo "Cleaning old yum repodata."
yum clean all
truncate -c -s 0 /var/log/yum.log
-echo "Zeroing out empty space with fstrim."
-/usr/sbin/fstrim /
+echo "Zeroing out empty space."
+# This forces the filesystem to reclaim space from deleted files
+dd bs=1M if=/dev/zero of=/var/tmp/zeros || :
+rm -f /var/tmp/zeros
+echo "(Don't worry -- that out-of-space error was expected.)"
%end
commit de0fd360d5bce6c15cfdff827ac8af1f0acca0d9
Author: Matthew Miller <mattdm(a)mattdm.org>
Date: Tue Jun 18 11:15:10 2013 -0400
yum log from initial creation is boring and just has cleanup artifacts
from this kickstart. truncate it and start from 0 instead.
diff --git a/generic/fedora-19-i386-cloud.ks b/generic/fedora-19-i386-cloud.ks
index 8834325..13f0117 100644
--- a/generic/fedora-19-i386-cloud.ks
+++ b/generic/fedora-19-i386-cloud.ks
@@ -219,6 +219,7 @@ sed -i 's/ec2-user/fedora/;s/EC2 user/Fedora Cloud User/' /etc/cloud/cloud.cfg
echo "Cleaning old yum repodata."
yum clean all
+truncate -c -s 0 /var/log/yum.log
echo "Zeroing out empty space with fstrim."
/usr/sbin/fstrim /
diff --git a/generic/fedora-19-i386-minimal.ks b/generic/fedora-19-i386-minimal.ks
index e011053..533bb16 100644
--- a/generic/fedora-19-i386-minimal.ks
+++ b/generic/fedora-19-i386-minimal.ks
@@ -186,6 +186,7 @@ echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
echo "Cleaning old yum repodata."
yum clean all
+truncate -c -s 0 /var/log/yum.log
echo "Zeroing out empty space with fstrim."
/usr/sbin/fstrim /
diff --git a/generic/fedora-19-i386.ks b/generic/fedora-19-i386.ks
index daee9ea..502576d 100644
--- a/generic/fedora-19-i386.ks
+++ b/generic/fedora-19-i386.ks
@@ -178,6 +178,7 @@ echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
echo "Cleaning old yum repodata."
yum clean all
+truncate -c -s 0 /var/log/yum.log
echo "Zeroing out empty space with fstrim."
/usr/sbin/fstrim /
diff --git a/generic/fedora-19-x86_64-cloud.ks b/generic/fedora-19-x86_64-cloud.ks
index 15fa592..469310f 100644
--- a/generic/fedora-19-x86_64-cloud.ks
+++ b/generic/fedora-19-x86_64-cloud.ks
@@ -216,6 +216,7 @@ sed -i 's/ec2-user/fedora/;s/EC2 user/Fedora Cloud User/' /etc/cloud/cloud.cfg
echo "Cleaning old yum repodata."
yum clean all
+truncate -c -s 0 /var/log/yum.log
echo "Zeroing out empty space with fstrim."
/usr/sbin/fstrim /
diff --git a/generic/fedora-19-x86_64-minimal.ks b/generic/fedora-19-x86_64-minimal.ks
index 9cb5182..6777c20 100644
--- a/generic/fedora-19-x86_64-minimal.ks
+++ b/generic/fedora-19-x86_64-minimal.ks
@@ -184,6 +184,7 @@ echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
echo "Cleaning old yum repodata."
yum clean all
+truncate -c -s 0 /var/log/yum.log
echo "Zeroing out empty space with fstrim."
/usr/sbin/fstrim /
diff --git a/generic/fedora-19-x86_64.ks b/generic/fedora-19-x86_64.ks
index 7f636c2..1c1794b 100644
--- a/generic/fedora-19-x86_64.ks
+++ b/generic/fedora-19-x86_64.ks
@@ -176,6 +176,7 @@ echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
echo "Cleaning old yum repodata."
yum clean all
+truncate -c -s 0 /var/log/yum.log
echo "Zeroing out empty space with fstrim."
/usr/sbin/fstrim /
commit 628c3af4c96d793bb85e1868521734a67bb7503a
Author: Matthew Miller <mattdm(a)mattdm.org>
Date: Tue Jun 18 11:12:21 2013 -0400
disable persistant journal -- we're still using rsyslog, and don't
really have the luxury of using space for double-logging.
diff --git a/generic/fedora-19-i386-cloud.ks b/generic/fedora-19-i386-cloud.ks
index 2a92bc6..8834325 100644
--- a/generic/fedora-19-i386-cloud.ks
+++ b/generic/fedora-19-i386-cloud.ks
@@ -107,10 +107,10 @@ rm -f /etc/systemd/system/default.target
ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
echo .
-# If you want to remove rsyslog and just use journald, also uncomment this.
-#echo -n "Enabling persistent journal"
-#mkdir /var/log/journal/
-#echo .
+# If you want to remove rsyslog and just use journald, remove this!
+echo -n "Disabling persistent journal"
+rmdir /var/log/journal/
+echo .
# this is installed by default but we don't need it in virt
echo "Removing linux-firmware package."
diff --git a/generic/fedora-19-i386-minimal.ks b/generic/fedora-19-i386-minimal.ks
index 95df672..e011053 100644
--- a/generic/fedora-19-i386-minimal.ks
+++ b/generic/fedora-19-i386-minimal.ks
@@ -101,11 +101,6 @@ rm -f /etc/systemd/system/default.target
ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
echo .
-# because we didn't install rsyslog, enable persistent journal
-echo -n "Enabling persistent journal"
-mkdir /var/log/journal/
-echo .
-
# this is installed by default but we don't need it in virt
echo "Removing linux-firmware package."
yum -C -y remove linux-firmware
diff --git a/generic/fedora-19-i386.ks b/generic/fedora-19-i386.ks
index 24b0e0b..daee9ea 100644
--- a/generic/fedora-19-i386.ks
+++ b/generic/fedora-19-i386.ks
@@ -88,10 +88,10 @@ rm -f /etc/systemd/system/default.target
ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
echo .
-# If you want to remove rsyslog and just use journald, also uncomment this.
-#echo -n "Enabling persistent journal"
-#mkdir /var/log/journal/
-#echo .
+# If you want to remove rsyslog and just use journald, remove this!
+echo -n "Disabling persistent journal"
+rmdir /var/log/journal/
+echo .
# this is installed by default but we don't need it in virt
echo "Removing linux-firmware package."
diff --git a/generic/fedora-19-x86_64-cloud.ks b/generic/fedora-19-x86_64-cloud.ks
index b89d417..15fa592 100644
--- a/generic/fedora-19-x86_64-cloud.ks
+++ b/generic/fedora-19-x86_64-cloud.ks
@@ -103,10 +103,10 @@ rm -f /etc/systemd/system/default.target
ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
echo .
-# If you want to remove rsyslog and just use journald, also uncomment this.
-#echo -n "Enabling persistent journal"
-#mkdir /var/log/journal/
-#echo .
+# If you want to remove rsyslog and just use journald, remove this!
+echo -n "Disabling persistent journal"
+rmdir /var/log/journal/
+echo .
# this is installed by default but we don't need it in virt
echo "Removing linux-firmware package."
diff --git a/generic/fedora-19-x86_64-minimal.ks b/generic/fedora-19-x86_64-minimal.ks
index 133a882..9cb5182 100644
--- a/generic/fedora-19-x86_64-minimal.ks
+++ b/generic/fedora-19-x86_64-minimal.ks
@@ -99,11 +99,6 @@ rm -f /etc/systemd/system/default.target
ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
echo .
-# because we didn't install rsyslog, enable persistent journal
-echo -n "Enabling persistent journal"
-mkdir /var/log/journal/
-echo .
-
# this is installed by default but we don't need it in virt
echo "Removing linux-firmware package."
yum -C -y remove linux-firmware --setopt="clean_requirements_on_remove=1"
diff --git a/generic/fedora-19-x86_64.ks b/generic/fedora-19-x86_64.ks
index bb19668..7f636c2 100644
--- a/generic/fedora-19-x86_64.ks
+++ b/generic/fedora-19-x86_64.ks
@@ -86,10 +86,10 @@ rm -f /etc/systemd/system/default.target
ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
echo .
-# If you want to remove rsyslog and just use journald, also uncomment this.
-#echo -n "Enabling persistent journal"
-#mkdir /var/log/journal/
-#echo .
+# If you want to remove rsyslog and just use journald, remove this!
+echo -n "Disabling persistent journal"
+rmdir /var/log/journal/
+echo .
# this is installed by default but we don't need it in virt
echo "Removing linux-firmware package."
10 years, 10 months
Fedora 19 image on EC2
by Krishna Raman
Hi,
Wondering if there is a Fedora 19 AMI available on EC2 US-East-1?
I would like to start building and testing OpenShift Origin on there if possible.
--Krishna
10 years, 10 months
cloud-init fails to set hostname
by Sandro "red" Mathys
I just gave the F19 TC5 cloud image [1] a spin and the first impression is
very good (great job, Matthew!) except for one thing. Can anyone reproduce
the following?
[root@f19t2 ~]# journalctl -u cloud-init.service | grep hostname
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[WARNING]: Failed
to set the hostname to f19t2.novalocal (f19t2)
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Failed
to set the hostname to f19t2.novalocal (f19t2)
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[WARNING]:
Running set_hostname (<module 'cloudinit.config.cc_set_hostname' from
'/usr/lib/python2.7/site-packages/cloudinit/config/cc_set_hostname.pyc'>)
failed
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Running
set_hostname (<module 'cloudinit.config.cc_set_hostname' from
'/usr/lib/python2.7/site-packages/cloudinit/config/cc_set_hostname.pyc'>)
failed
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] helpers.py[DEBUG]:
Running config-update_hostname using lock (<cloudinit.helpers.DummyLock
object at 0x32dbb10>)
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT]
cc_update_hostname.py[DEBUG]: Updating hostname to f19t2.novalocal (f19t2)
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Running
command ['hostname'] with allowed return codes [0] (shell=False,
capture=True)
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] __init__.py[DEBUG]:
Attempting to update hostname to f19t2.novalocal in 1 files
Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Running
command ['hostnamectl', 'set-hostname', 'f19t2.novalocal'] with allowed
return codes [0] (shell=False, capture=True)
Jun 18 07:03:12 f19t2 cloud-init[447]: [CLOUDINIT] util.py[WARNING]: Failed
to write hostname f19t2.novalocal to /var/lib/cloud/data/previous-hostname
Jun 18 07:03:12 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Failed
to write hostname f19t2.novalocal to /var/lib/cloud/data/previous-hostname
[root@f19t2 ~]# hostname
f19t2
So the hostname is set to f19t2 (the name I gave the instance) somehow but
setting it to f19t2.novalocal fails...not even sure why it's set in two
different ways and to two different values.
Let me know if more information is required or if it's worth opening a bug
report for this issue.
-- Sandro
[1] https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/
10 years, 10 months
