I am doing a Kickstart installation of Fedora Workstation from the Fedora Server NetInstall ISO. Everything is going as expected until I hit the installation of the package: flatpak-selinux.
It fails with the error: DNF error in POSTIN scriplet of flatpak-selinux
Well I wish Anaconda would let me continue the installation if one package failed, but no I have to exit the installer and begin downloading 2.13 GB again and again.
First question, any way for Anaconda to ignore such errors in the Kickstart file ?
Secondly, what should I do about this error ?
An open bug already exists here: https://bugzilla.redhat.com/show_bug.cgi?id=1723118 and https://bugzilla.redhat.com/show_bug.cgi?id=1723940
One has a status of CLOSED and one has a status of MODIFIED.
Now I can understand CLOSED since it was a duplicate but what does modified mean ? Also there are no solutions so what do I do now?
I actually got this bug in VirtualBox once during the testing of my Kickstart file but it got resolved automatically on a next install. This is not the case for my laptop though, it hits the error every time.
These are the packages in my Kickstart: %packages @^workstation-product-environment @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @libreoffice @mate-applications @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers
Should I delete some packages ? flatpak-selinux seems like a mandatory package, is there any way to not install it ?
Thanks.
Okay I tried with disabling SELinux but this issue still persists.
Weirdly, I could not find anything is the log files. I am uploading them here: https://drive.google.com/open?id=1X_3Je-tY6hnXrBR6cCdWidh9cANrulf5
No error, no nothing.
You would think that the errors would be logged, but nope nothing.
I will try the anaconda mailing list. Lets see what happens.
On Sat, Apr 11, 2020 at 2:25 AM Sreyan Chakravarty sreyan32@gmail.com wrote:
I am doing a Kickstart installation of Fedora Workstation from the Fedora Server NetInstall ISO. Everything is going as expected until I hit the installation of the package: flatpak-selinux.
It fails with the error: DNF error in POSTIN scriplet of flatpak-selinux
Well I wish Anaconda would let me continue the installation if one package failed, but no I have to exit the installer and begin downloading 2.13 GB again and again.
First question, any way for Anaconda to ignore such errors in the Kickstart file ?
Secondly, what should I do about this error ?
An open bug already exists here: https://bugzilla.redhat.com/show_bug.cgi?id=1723118 and https://bugzilla.redhat.com/show_bug.cgi?id=1723940
One has a status of CLOSED and one has a status of MODIFIED.
Now I can understand CLOSED since it was a duplicate but what does modified mean ? Also there are no solutions so what do I do now?
I actually got this bug in VirtualBox once during the testing of my Kickstart file but it got resolved automatically on a next install. This is not the case for my laptop though, it hits the error every time.
These are the packages in my Kickstart: %packages @^workstation-product-environment @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @libreoffice @mate-applications @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers
Should I delete some packages ? flatpak-selinux seems like a mandatory package, is there any way to not install it ?
Thanks.
-- Regards, Sreyan Chakravarty
On 4/10/20 1:55 PM, Sreyan Chakravarty wrote:
I am doing a Kickstart installation of Fedora Workstation from the Fedora Server NetInstall ISO. Everything is going as expected until I hit the installation of the package: flatpak-selinux.
Well I wish Anaconda would let me continue the installation if one package failed, but no I have to exit the installer and begin downloading 2.13 GB again and again.
First question, any way for Anaconda to ignore such errors in the Kickstart file ?
I've run into similar issues, but as annoying as it is, it would not be a good idea to continue if there's a failure.
Secondly, what should I do about this error ?
An open bug already exists here: https://bugzilla.redhat.com/show_bug.cgi?id=1723118 and https://bugzilla.redhat.com/show_bug.cgi?id=1723940
One has a status of CLOSED and one has a status of MODIFIED.
Now I can understand CLOSED since it was a duplicate but what does modified mean ? Also there are no solutions so what do I do now?
I found the documentation for the states: https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow MODIFIED means a fix is checked in, but an update hasn't been created yet.
I actually got this bug in VirtualBox once during the testing of my Kickstart file but it got resolved automatically on a next install. This is not the case for my laptop though, it hits the error every time.
These are the packages in my Kickstart: %packages @^workstation-product-environment @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @libreoffice @mate-applications @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers
Should I delete some packages ? flatpak-selinux seems like a mandatory package, is there any way to not install it ?
You can't exclude it. It's in the dependency chain of gnome-software. Try adding "selinux-policy" to the top of the packages list and see if that solves the problem.
Guys I have found the damn bug.
I have found the culprit. Not sure why is causing the problem but that's were you guys can help.
After 10 hours of installing and reinstalling in a chroot environment I have managed to isolate the DNF Group that is causing the problem:
@mate-applications
Yes Mate Applications is the one causing the problem.
This is my package list for Kickstart which does not now show the problem:
%packages @anaconda-tools @base-x @core @firefox @fonts @gnome-desktop @guest-desktop-agents @hardware-support @libreoffice @multimedia @networkmanager-submodules @printing @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers @workstation-product aajohan-comfortaa-fonts anaconda anaconda-install-env-deps anaconda-live chkconfig dracut-live glibc-all-langpacks initscripts kernel kernel-modules kernel-modules-extra memtest86+ syslinux -@input-methods -@standard -gfs2-utils -reiserfs-utils
The only difference, other than the individual packages, is @mate-applications.
It totally escapes me what is going wrong if I add this and what this has to do with flatpak-selinux.
There are however other errors that I need help with:
Running scriptlet: dbus-broker-21-6.fc31.x86_64
Failed to get unit file state for dbus-daemon.service: No such file or directory Failed to get unit file state for dbus-daemon.service: No such file or directory Failed to disable unit, unit dbus-daemon.service does not exist. Failed to disable unit, unit dbus-daemon.service does not exist.
Running scriptlet: dbus-daemon-1:1.12.16-3.fc31.x86_64
Failed to preset unit, file /etc/systemd/user/dbus.service already exists and is a symlink to /usr/lib/systemd/user/dbus-broker.service.
dracut: No '/dev/log' or 'logger' included for syslog logging dracut-install: ERROR: installing 'sr_mod' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m sr_mod sd_mod ide_cd cdrom =ata sym53c8xx aic7xxx ehci_hcd uhci_hcd ohci_hcd usb_storage usbhid uas firewire-sbp2 firewire-ohci sbp2 ohci1394 ieee1394 mmc_block sdhci sdhci-pci pata_pcmcia mptsas virtio_blk virtio_pci virtio_scsi virtio_net virtio_mmio virtio_balloon virtio-rng dracut-install: ERROR: installing 'ext4' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m vfat msdos isofs ext4 xfs btrfs squashfs
Running scriptlet: abrt-addon-ccpp-2.12.2-1.fc31.x86_64
Failed to preset unit, unit macro.service does not exist.
Any idea about the above errors ?
I more worried about the dracut errors.
On Sun, Apr 12, 2020 at 1:15 AM Samuel Sieb samuel@sieb.net wrote:
On 4/10/20 1:55 PM, Sreyan Chakravarty wrote:
I am doing a Kickstart installation of Fedora Workstation from the Fedora Server NetInstall ISO. Everything is going as expected until I hit the installation of the package: flatpak-selinux.
Well I wish Anaconda would let me continue the installation if one package failed, but no I have to exit the installer and begin downloading 2.13 GB again and again.
First question, any way for Anaconda to ignore such errors in the Kickstart file ?
I've run into similar issues, but as annoying as it is, it would not be a good idea to continue if there's a failure.
Secondly, what should I do about this error ?
An open bug already exists here: https://bugzilla.redhat.com/show_bug.cgi?id=1723118 and https://bugzilla.redhat.com/show_bug.cgi?id=1723940
One has a status of CLOSED and one has a status of MODIFIED.
Now I can understand CLOSED since it was a duplicate but what does modified mean ? Also there are no solutions so what do I do now?
I found the documentation for the states: https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow MODIFIED means a fix is checked in, but an update hasn't been created yet.
I actually got this bug in VirtualBox once during the testing of my Kickstart file but it got resolved automatically on a next install. This is not the case for my laptop though, it hits the error every time.
These are the packages in my Kickstart: %packages @^workstation-product-environment @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @libreoffice @mate-applications @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers
Should I delete some packages ? flatpak-selinux seems like a mandatory package, is there any way to not install it ?
You can't exclude it. It's in the dependency chain of gnome-software. Try adding "selinux-policy" to the top of the packages list and see if that solves the problem. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 4/12/20 6:22 AM, Sreyan Chakravarty wrote:
After 10 hours of installing and reinstalling in a chroot environment I have managed to isolate the DNF Group that is causing the problem:
@mate-applications
That was going to be my next suggestion. The bug mentioned it happened when they were trying to add the KDE DE as well.
Also is there any way I can control the order of the installation in my package list ?
For example given the package list:
%packages @^workstation-product-environment @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @libreoffice @mate-applications @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers
How do I chose which is installed first and which is installed later ? Or are they installed just in the order they are specified ?
On Sun, Apr 12, 2020 at 1:15 AM Samuel Sieb samuel@sieb.net wrote:
On 4/10/20 1:55 PM, Sreyan Chakravarty wrote:
I am doing a Kickstart installation of Fedora Workstation from the Fedora Server NetInstall ISO. Everything is going as expected until I hit the installation of the package: flatpak-selinux.
Well I wish Anaconda would let me continue the installation if one package failed, but no I have to exit the installer and begin downloading 2.13 GB again and again.
First question, any way for Anaconda to ignore such errors in the Kickstart file ?
I've run into similar issues, but as annoying as it is, it would not be a good idea to continue if there's a failure.
Secondly, what should I do about this error ?
An open bug already exists here: https://bugzilla.redhat.com/show_bug.cgi?id=1723118 and https://bugzilla.redhat.com/show_bug.cgi?id=1723940
One has a status of CLOSED and one has a status of MODIFIED.
Now I can understand CLOSED since it was a duplicate but what does modified mean ? Also there are no solutions so what do I do now?
I found the documentation for the states: https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow MODIFIED means a fix is checked in, but an update hasn't been created yet.
I actually got this bug in VirtualBox once during the testing of my Kickstart file but it got resolved automatically on a next install. This is not the case for my laptop though, it hits the error every time.
These are the packages in my Kickstart: %packages @^workstation-product-environment @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @libreoffice @mate-applications @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers
Should I delete some packages ? flatpak-selinux seems like a mandatory package, is there any way to not install it ?
You can't exclude it. It's in the dependency chain of gnome-software. Try adding "selinux-policy" to the top of the packages list and see if that solves the problem. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 4/12/20 6:31 AM, Sreyan Chakravarty wrote:
Also is there any way I can control the order of the installation in my package list ?
How do I chose which is installed first and which is installed later ? Or are they installed just in the order they are specified ?
They are installed according to their dependency chains.
Do you know anything about my other bugs ??
On Sun, Apr 12, 2020 at 8:32 PM Samuel Sieb samuel@sieb.net wrote:
On 4/12/20 6:31 AM, Sreyan Chakravarty wrote:
Also is there any way I can control the order of the installation in my package list ?
How do I chose which is installed first and which is installed later ? Or are they installed just in the order they are specified ?
They are installed according to their dependency chains. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
The dracut errors. Anyways let me try since those bugs occur even if I am building the official Fedora Workstation Live CD from Kickstart. So maybe they won't be a problem, optimistically speaking.
On Mon, Apr 13, 2020 at 2:32 AM Samuel Sieb samuel@sieb.net wrote:
On 4/12/20 8:14 AM, Sreyan Chakravarty wrote:
Do you know anything about my other bugs ??
What other bugs? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 4/12/20 10:43 PM, Sreyan Chakravarty wrote:
The dracut errors. Anyways let me try since those bugs occur even if I am building the official Fedora Workstation Live CD from Kickstart. So maybe they won't be a problem, optimistically speaking.
I don't remember seeing an email about that to this list.
I was talking about these :
dracut: No '/dev/log' or 'logger' included for syslog logging dracut-install: ERROR: installing 'sr_mod' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m sr_mod sd_mod ide_cd cdrom =ata sym53c8xx aic7xxx ehci_hcd uhci_hcd ohci_hcd usb_storage usbhid uas firewire-sbp2 firewire-ohci sbp2 ohci1394 ieee1394 mmc_block sdhci sdhci-pci pata_pcmcia mptsas virtio_blk virtio_pci virtio_scsi virtio_net virtio_mmio virtio_balloon virtio-rng dracut-install: ERROR: installing 'ext4' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m vfat msdos isofs ext4 xfs btrfs squashfs
On Mon, Apr 13, 2020 at 12:10 PM Samuel Sieb samuel@sieb.net wrote:
On 4/12/20 10:43 PM, Sreyan Chakravarty wrote:
The dracut errors. Anyways let me try since those bugs occur even if I am building the official Fedora Workstation Live CD from Kickstart. So maybe they won't be a problem, optimistically speaking.
I don't remember seeing an email about that to this list. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 4/12/20 11:59 PM, Sreyan Chakravarty wrote:
I was talking about these :
dracut: No '/dev/log' or 'logger' included for syslog logging dracut-install: ERROR: installing 'sr_mod' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m sr_mod sd_mod ide_cd cdrom =ata sym53c8xx aic7xxx ehci_hcd uhci_hcd ohci_hcd usb_storage usbhid uas firewire-sbp2 firewire-ohci sbp2 ohci1394 ieee1394 mmc_block sdhci sdhci-pci pata_pcmcia mptsas virtio_blk virtio_pci virtio_scsi virtio_net virtio_mmio virtio_balloon virtio-rng dracut-install: ERROR: installing 'ext4' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m vfat msdos isofs ext4 xfs btrfs squashfs
We need a lot more context. What are you doing when that happens? What is the command? Does the resulting initrd boot?
Thank fully that did not cause any problems. I could fully install my system.
On Mon, Apr 13, 2020 at 1:58 PM Samuel Sieb samuel@sieb.net wrote:
On 4/12/20 11:59 PM, Sreyan Chakravarty wrote:
I was talking about these :
dracut: No '/dev/log' or 'logger' included for syslog logging dracut-install: ERROR: installing 'sr_mod' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m sr_mod sd_mod ide_cd cdrom =ata sym53c8xx aic7xxx ehci_hcd uhci_hcd ohci_hcd usb_storage usbhid uas firewire-sbp2 firewire-ohci sbp2 ohci1394 ieee1394 mmc_block sdhci sdhci-pci pata_pcmcia mptsas virtio_blk virtio_pci virtio_scsi virtio_net virtio_mmio virtio_balloon virtio-rng dracut-install: ERROR: installing 'ext4' dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YxAPo1/initramfs --kerneldir /lib/modules/5.3.7-301.fc31.x86_64/ -m vfat msdos isofs ext4 xfs btrfs squashfs
We need a lot more context. What are you doing when that happens? What is the command? Does the resulting initrd boot? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org