rng-tools was dropped from standard comps group recently,
so it's no longer installed by default. Lets remove it from here as well
to get arm and server images building again.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The scripts changing the image were wrongly run in --nochroot
%post section. This commit fixes it by simply moving it from
--nochroot %post to normal chroot %post.
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
The Raspberry Pi isn't properly setup for ARMv7 as the arch detect during
build was missed, hence nothing gets copied and the image won't boot.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
The langpacks-en package is pulled in by Anaconda and it seems filtering
it out using langpacks-* is not sufficient. It needs to be filtered
directly.
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
This commit removes few packages from Fedora-ELN-Guest kickstart:
- insights-client - this is RHEL only package which does not exist
in Fedora and therefore will not be installed in Fedora ELN.
- rng-tools - this is not available in Fedora-ELN compose yet. We
will enable rngd again once this is added to Fedora ELN.
- dracut-norescue - this is RHEL only package. The Fedora equivalent
of this is to remove dracut-config-rescue. This yes is also used
in other Fedora kickstarts.
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
The previous commit was supposed to merge fedora-container-common.ks
into fedora-eln-container-base.ks. I probably copy-pasted wrong
fedora-eln-guest.ks part there instead of the fedora-container-common.ks.
In this commit I'm fixing that.
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
The Fedora ELN container is special in a way that the "%{fedora}"
RPM macro is not defined there. This breaks the Fedora ELN container
build, because fedora-container-common.ks expects this macro to exist.
This commit merges fedora-container-common.ks into
fedora-eln-container-base.ks and hardcodes Fedora 34 GPG key there.
The fedora-eln-container-base.ks will be updated once we move to
newer Fedora.
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
This is a starting point for a GCP cloud image. The image boots fine
in GCP today. In the future we may want to consider adding the GCP
cloud agents if they get packaged in Fedora.
It seems we will need different set of packages Fedora-ELN base
container image and therefore we need new kickstart file for it.
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
This reworks the package list to add comments and remove some things
that didn't need to be explicitly removed.
- remove +systemd-udev -> already included by default
- remove -biosdevname -> not included by default
- remove -iprutils -> not included by default
- remove -uboot-tools -> not included by default
There are no packages added or removed from the built cloud image as
part of this change. Just updating the input package list to be more
meaningful.
We're no longer using legacy network scripts to bring up networking.
We're using NetworkManager and now in F33+ networkmanager will even
default to writing out new configuration as NM keyfiles in
/etc/NetworkManager/system-connections/. We don't need to lay down
a networking config for eth0. Either cloud-init will do that for us
or NetworkManager will default to DHCP anyway.
We also don't need to populate /etc/hosts as that will get done on
boot too with the same content we were writing there already.
As discussed here:
https://fedoraproject.org/wiki/Changes/RemoveDeviceMapperMultipathFromWorkstationLiveCD
And on the anaconda devel list, we do not want device-mapper-multipath
on the livecd / on installs done from the livecd, because rather then
properly supporting hotplug udev add/change events it brings in
the long obsolete systemd-udev-settle.service which causes significant
delays during boot.
Since multipath is very much a data-center / server only feature we
can simply exclude it from the livecd to get rid of the dependency on
systemd-udev-settle.service .
We also need to exclude fcoe-utils since that depends on
device-mapper-multipath. Since FCOE too is a data-center / server
only feature, we can simply exclude fcoe-utils too.
Upstream SSH has been claiming [1] for a few releases now that:
```
It is now possible to perform chosen-prefix attacks against the
SHA-1 algorithm for less than USD$50K. For this reason, we will be
disabling the "ssh-rsa" public key signature algorithm by default in a
near-future release.
```
In Fedora we switched recently [2] to disallow ssh-rsa. I filed a bug
upstream [3] for Vagrant to stop using an rsa key. For now let's workaround
the issue.
[1] https://www.openssh.com/txt/release-8.3
[2] b298a9e107
[3] https://github.com/hashicorp/vagrant/issues/11783
Atomic is a thing of the past and I have no idea what
fedora-cloud-bigdata.ks and fedora-cloud-experimental.ks
were ever used for. Let's get rid of them to reduce confusion.
It is obsolete; notice the reference to the old `spin-kickstarts` repo that no longer exists.
Signed-off-by: Michel Alexandre Salim <michel@michel-slm.name>
