Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1203950 - Include dnssec-trigger package and enable the DNSSEC and unbound services for rawhide
Summary: Include dnssec-trigger package and enable the DNSSEC and unbound services for...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: spin-kickstarts
Version: 26
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Jeroen van Meeuwen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: Default_Local_DNS_Resolver
TreeView+ depends on / blocked
 
Reported: 2015-03-20 03:04 UTC by Moez Roy
Modified: 2018-05-29 11:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:50:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Moez Roy 2015-03-20 03:04:09 UTC
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

Comment 1 Kevin Fenzi 2015-03-20 12:40:53 UTC
"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.

Comment 2 Tomáš Hozza 2015-03-20 12:59:10 UTC
(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

Comment 3 Kevin Fenzi 2015-03-20 13:24:13 UTC
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?

Comment 4 Tomáš Hozza 2015-03-20 14:18:08 UTC
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.

Comment 5 Moez Roy 2015-07-11 06:21:16 UTC
(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?

Comment 6 Tomáš Hozza 2015-07-13 07:21:07 UTC
(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

Comment 7 Kevin Fenzi 2015-07-13 14:10:07 UTC
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?

Comment 8 Jan Kurik 2015-07-15 14:23:16 UTC
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

Comment 9 Fedora End Of Life 2016-11-24 11:35:13 UTC
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.

Comment 10 Fedora End Of Life 2017-02-28 09:41:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 11 Fedora End Of Life 2018-05-03 08:08:09 UTC
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.

Comment 12 Fedora End Of Life 2018-05-29 11:50:42 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.