Commit Graph

79 Commits

Author SHA1 Message Date
Joe Doss
c3841ff35a Revert "Remove -NetworkManager to fix BZ#1596062"
This reverts commit d95b59ac3b.
2018-07-12 15:33:14 -05:00
Joe Doss
d95b59ac3b Remove -NetworkManager to fix BZ#1596062 2018-07-12 14:43:44 -05:00
Kevin Fenzi
9a25016bac When building cloud images oz uses dracut to setup networking and it
in turn makes a ifcfg-en<something> file with this config. We don't
want to use this, we want to always use ifcfg-eth0 so it's the same
on all images. So, we remove ifcfg-en* (They are different on each
arch we make cloud images for, but en* gets them all).
Additionally we were using some old udev tricks to get eth0, but this
is error prone and already incorrect as systemd-udev has moved files
around, so instead we just switch to net.ifnames=0 on the boot line,
which should continue working.
2018-03-19 17:43:39 -07:00
Ralph Bean
d702d27389 Fix links to this example TDL file.
Signed-off-by: Ralph Bean <rbean@redhat.com>
2017-07-07 15:58:34 -04:00
Dusty Mabe
68804358d8
atomic, cloud: remove rhgb by removing plymouth
a59dfe5 caused us a few problems:
  - sed was breaking the symlink on atomic systems
  - /boot/grub2/grub.cfg is not the right file on a UEFI system
  - etc..

We'll solve this problem a different way by just not installing
plymouth in our systems, which is another way [1] to make sure
rhgb/quiet don't appear on your kernel command line.

[1] ee91db6fa3/pyanaconda/payload/__init__.py (L722-L726)
2017-05-24 01:41:20 -04:00
Dusty Mabe
ba950669f1
cloud: fix errors that happen on UEFI systems
We are seeing an error on aarch64 cloud image creation because
of the vfat filesystem and the fixfiles command failing:

+ /usr/sbin/fixfiles -R -a restore
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/fonts/unicode.pf2:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/gcdaa64.efi:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/grub.cfg:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/grubaa64.efi:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/grubenv:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/BOOT/BOOTAA64.EFI:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/BOOT/fallback.efi:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/BOOT.CSV:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/MokManager.efi:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/shim-fedora.efi:  Operation not supported
/sbin/restorecon: Could not set context for /boot/efi/EFI/fedora/shim.efi:  Operation not supported
2017-05-24 01:39:49 -04:00
Peter Robinson
00e6c35287 cloud/docker: move to autopart with the new no home/swap/boot options to enable generic architecture images
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2017-05-15 17:30:43 +01:00
Dusty Mabe
a59dfe5f40
atomic, cloud: disable rhgb/quiet on boot
We want more verbose output on boot.

See https://bugzilla.redhat.com/show_bug.cgi?id=510523
2017-05-08 11:35:19 -04:00
Dusty Mabe
4948e8c002
atomic, cloud: don't create none user
Anaconda doesn't seem to require it anymore so no need to create it
and then delete it.
2017-05-08 11:35:16 -04:00
Dusty Mabe
fc0a635bc4
zero out resolv.conf during install
Anaconda is writing an /etc/resolv.conf from the install environment.
The system should start out with an empty file, otherwise cloud-init
will try to use this information and may error:
https://bugs.launchpad.net/cloud-init/+bug/1670052
2017-03-28 16:20:25 -04:00
Peter Robinson
c9fceb1c03 Fix the vagrant and bigdata cloud images
With moving to grub2 we now need to remove the extlinux bits from the
other cloud images. They were missed in the move

Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2017-03-28 16:04:52 +01:00
Peter Robinson
15a6627e09 Add bits required for aarch64 images
We drop the explicit grub2 as aarch64 only has grub2-efi but anaconda will
sort that out and ensure all the right bits are installed during the install
so we should get the right grub2 bootloader options for each arch OOTB.

Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2017-03-03 17:48:29 +00:00
Peter Robinson
2077c2935d Minor inline docs updates
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2017-03-03 15:24:05 +00:00
Peter Robinson
bea832564f switch cloud images permanently to grub2
The main reason for cloud to use extlinux is the size of deps being
pulled in by grub2-tools. This will be fixed in F-26 with the ability
to use grub2/grub2-efi without the tools package and it's deps fixing
this issue for good. There will no doubt need to be be some tweaking
required here.

We need grub2 in cloud images for non x86 as well as for the increasing
x86 cloud platforms that require the support of uEFI which extlinux
doesn't support.

Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
2017-03-03 15:24:01 +00:00
Colin Walters
9912269d88 all: Correct path to /var/lib/systemd/random-seed
At least for Atomic Host, AFAICS it isn't actually in the final
image; not entirely sure why.  But we should be using the right
path here anyways.

https://bugzilla.redhat.com/show_bug.cgi?id=1424404
2017-02-17 15:05:13 -05:00
Dusty Mabe
f6ecdc348a
docker, cloud: don't use cmdline for install mode
cmdline makes it so that %post --erroronfail won't actually stop the
installation in a way that imagefactory will detect the problem and
fail the build. See [1] for more details.

[1] https://github.com/rhinstaller/anaconda/issues/931
2017-01-19 20:57:24 -05:00
Pavel Raiskup
fa73086cf1 Don't hack 'override_install_langs' yum option
This shouldn't be needed, re-defining %_install_langs should be
enough.
2016-11-24 11:23:06 +01:00
Peter Robinson
30c3f7e721 Touch the machine-id file
So is seems that if you remove the machine-id file it won't regenerate the file
but if you touch the file and leave it empty on boot it'll put a new machine-id
in the empty file. So work around this bug ("feature"?) by touching the file
so we don't have other issues in the process.

We're track the outcome of this in RHBZ 1379800
2016-09-27 20:17:46 +01:00
Peter Robinson
890829fdbb Remove machine-id on pre generated images so it's unique on each deployed device
As referenced on the arm list [1] and as already being done on the docker image we
should remove the unique /etc/machine-id file on compose artifacts to ensure it's
regenerated and unique on each deployed host/device. This unifies the process across
all base ks so it's inherited for each artifact.

[1] https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/message/Q3YZVF5P2OLLPUJQ2LYZSTKWGGDIU6QO/

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2016-09-13 09:11:57 +01:00
Kevin Fenzi
99727567b0 Switch cloud base back to extlinux from grub2.
We need to unset the 64bit option on ext4 to make extlinux work.
See https://bugzilla.redhat.com/show_bug.cgi?id=1369934
and http://www.syslinux.org/wiki/index.php/Filesystem#ext
2016-08-30 10:44:02 -06:00
Kevin Fenzi
7a37fb6304 Merge #54 Switch the cloud base image back to grub2 for now. 2016-08-24 21:40:25 +00:00
Kevin Fenzi
a28a951979 Switch the cloud base image back to grub2 for now.
For some reason extlinux isn't working right to boot the image.
See bug https://bugzilla.redhat.com/show_bug.cgi?id=1369934
2016-08-24 14:43:30 -06:00
Adam Williamson
aca01e6eea drop rsyslog service from all cloud kickstarts
it's no longer pulled in by cloud-init (since 2014...). None
of these kickstarts has it in %packages, and it's not in any
of the cloud environment or package groups in comps either. So
it seems like no-one particularly wants rsyslog in the cloud
images.

From compose logs, it looks like trying to enable a non-existent
service in anaconda in Fedora 24 and earlier wasn't a fatal
error (anaconda more or less logged a warning and continued),
but in Fedora 25 and later it does seem to be fatal. It at least
causes one anaconda thread to crash, though the image compose
completes. I think possibly at least the way anaconda's run
in the Cloud compose process, the main thread manages to exit,
but it seems pretty likely the thread crash will result in
problems in the produced image.

Needed on master and f25.
2016-08-24 11:11:01 -07:00
Adam Williamson
4af7364074 manipulate network service in %post (#1369794)
Due to #1369794 , anaconda cannot currently manipulate sysv
services in F25+. So to work around this, take 'network' out of
the services lines in all kickstarts and instead manipulate
it in the %post section, with chkconfig.

Also remove rsyslog from the Atomic image services line because
it doesn't appear to be included in the OStree tree at present
and so attempting to enable the service breaks Atomic image
compose, see e.g.:

https://kojipkgs.fedoraproject.org//work/tasks/9022/15349022/oz-x86_64.log

also correct the name of the ssh service in fedora-arm-base.ks;
it's sshd not ssh.
2016-08-24 11:27:40 -06:00
Dusty Mabe
b529dcba60
fedora-cloud-base: Add which package back.
After removing grub2 the which package gets removed. Let's add it back
because it is generally useful and because it is needed for many vagrant
utilities to work.
2016-05-20 11:02:44 -04:00
Kushal Das
a5ad80cbc1 Pulls in the systemd-udev subpackage 2016-04-13 15:24:01 +05:30
Peter Robinson
42de211146 Cloud: Base: add arm config, use includes for ppc config 2016-04-12 14:22:03 +01:00
Matthew Miller
9d0ef8b63c adds kbd,plymouth rpms back.
We have had -kbd in the kickstart for a long time, but because of BZ#1199868
it wasn't actually getting excluded. Not having it causes
systemd-vconsole-setup.service to fail so we are adding it back for now.

Additionally we need to add back plymouth to cover up the subsequent failure
of systemd-vconsole-setup.service. See BZ#1272684.
2015-10-17 13:01:18 -04:00
Kushal Das
c5098636e8 Fixes trac #128 Removes extra ifcfg file. 2015-10-15 13:46:12 +05:30
Peter Robinson
78114bb82f adjust linux-firmware for cloud images 2015-09-23 07:16:18 +01:00
Dusty Mabe
29181aa376 cloud-base: workaround issue where langs are not getting installed.
Workaround BZ1262040 by removing the --instLangs arg from the
%packages line and rely on our previous hack to manually remove
langs after install. This fixes BZ1261249.

Signed-off-by: Kushal Das <kushaldas@gmail.com>
2015-09-15 02:45:50 +05:30
Kushal Das
030ae28c34 Commenting out removal of linux-firmware package for #1234504
For some reason the kernel-core is not protected by dnf, so when
we are trying to remove linux-firmware, it was actually removing
kernel-core package. Commenting out the lines for now.
2015-07-15 19:42:16 +05:30
Kevin Fenzi
9f254062c3 Switch md5 to sha512. Fixes bug #1234068
This is pretty cosmetic as live and cloud images don't use passwords
and they install with sha512 fine, but some people may use these
kickstarts as a base for their spins, so we should use best practices.
2015-06-21 10:38:20 -06:00
Ian McLeod
1e1a531b9b grow base partition for cloud and vagrant images
We control the actual size of the virtual disks with options on the
koji command line.  This change will allow the Vagrant root
partition to grow to the 40 GB we allocate in the koji image build
while the base cloud image will remain essentially unchanged, as it
is set to 3 GB in the rel-eng koji call.
2015-05-04 14:35:23 -05:00
Amit Saha
1dd0bbf214 Small fix for local cloud image creation instruction
ksflatten expects a "-c" option to point to the kickstart.
2015-04-27 14:10:55 +10:00
Colin Walters
e371dd6c3c cloud-base: Document how to use ImageFactory locally 2015-04-22 17:41:21 -04:00
Kushal Das
042f73d0f7 Adds DEVTIMEOUT option to /etc/sysconfig/network. #1204612
https://bugzilla.redhat.com/show_bug.cgi?id=1204612
2015-03-26 15:12:56 +05:30
Dennis Gilmore
b947d49831 use link as the device for netwrok in the cloud images 2014-12-12 16:07:54 -08:00
Matthew Miller
5710f9ff65 make the cloud base lang hacks line up with the same filenames as in the docker image 2014-11-14 10:20:05 -05:00
Matthew Miller
39c412833e more hacks for en_US in cloud base image 2014-11-13 14:10:52 -05:00
Matthew Miller
0d68707f4b hack around instLangs not working (due to https://bugzilla.redhat.com/show_bug.cgi?id=1051816) 2014-11-08 13:29:50 -05:00
Matthew Miller
f59d761db7 cloud images -- leave persistant journal, since upcoming cloud-init no longer pulls in rsyslog 2014-11-07 22:04:33 -05:00
Matthew Miller
0679b37d65 Revert "Use fstrim to zero out empty space rather than forcing it with dd"
Nope -- still does not work

This reverts commit 99c9224ef5.
2014-11-03 15:27:08 -05:00
Matthew Miller
0ab674dc2a cmdline output for hopefully better debugging in automation 2014-11-03 12:30:39 -05:00
Matthew Miller
aa63eae541 switch to use dnf for f22 2014-11-03 12:30:23 -05:00
Matthew Miller
99c9224ef5 Use fstrim to zero out empty space rather than forcing it with dd
This didn't work with appliance-creator but _should_ for imagefactory. It's
a whole lot faster too.
2014-10-23 15:30:24 -04:00
Matthew Miller
7f202a0e53 dd extlinux mbr during post as temporary workaround for bug #1147998 2014-10-14 16:00:42 -04:00
Matthew Miller
5f0fcd1d5e put the remove-firewalld code back -- apparently still needed and having it
there is breaking openstack
2014-10-02 13:23:32 -04:00
Matthew Miller
8ba8270ff8 only english to keep the locale archive down until there's a better solution 2014-09-27 09:06:06 -04:00
Dennis Gilmore
91e15f750c CLOUD: install the environment correctly 2014-09-11 18:42:37 -05:00