Include dnssec-trigger package in the kickstart files for rawhide. And enable DNSSEC and unbound services: systemctl enable dnssec-triggerd.service systemctl enable unbound.service
"the kickstart files for rawhide" ? you mean install it by default in all media? This should go through the change process, and some products or spins or images may not want it... So, I would suggest file a f23 change and get discussion from stakeholders.
(In reply to Kevin Fenzi from comment #1) > "the kickstart files for rawhide" ? you mean install it by default in all > media? > > This should go through the change process, and some products or spins or > images may not want it... > > So, I would suggest file a f23 change and get discussion from stakeholders. Although this needs to be discussed with product WGs, the change was already approved for F22 and just deferred to F23. This is a part of https://bugzilla.redhat.com/show_bug.cgi?id=1182488
oh right. Somehow I read f22 here. ;) Anyhow, do we really need to make spins-kickstarts changes? Or should this be just added to comps in base or the like?
I don't think that having dnssec-trigger and unbound installed by default makes sense for all Products, especially for Cloud, maybe not even for Server. I would deffer any changes until we (change owners) discussed this with all WGs.
(In reply to Tomas Hozza from comment #4) > I don't think that having dnssec-trigger and unbound installed by default > makes sense for all Products, especially for Cloud, maybe not even for > Server. > > I would deffer any changes until we (change owners) discussed this with all > WGs. Yes but atleast add it to the Live CD spins?
(In reply to Moez Roy from comment #5) > (In reply to Tomas Hozza from comment #4) > > I don't think that having dnssec-trigger and unbound installed by default > > makes sense for all Products, especially for Cloud, maybe not even for > > Server. > > > > I would deffer any changes until we (change owners) discussed this with all > > WGs. > > Yes but atleast add it to the Live CD spins? I agree
So, it sounds like server is ok with it, but I don't know about cloud folks. If it's only cloud that doesn't want it, we would better put it in comps in a group everything installs/uses and exclude in cloud than all over the place in kickstart files. So, perhaps we should wait for the cloud folks and then add to comps and/or cloud kickstarts?
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.