
| Anonymous | Login | 2025-10-27 00:19 EDT | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |||
| 0001223 | PacketFence | zen | public | 2011-06-06 17:58 | 2011-10-25 09:01 | |||
| Reporter | obilodeau | |||||||
| Assigned To | fgaudreault | |||||||
| Priority | normal | Severity | trivial | Reproducibility | always | |||
| Status | closed | Resolution | fixed | |||||
| Platform | OS | OS Version | ||||||
| Product Version | 2.2.0 | |||||||
| Target Version | 2.2.1 | Fixed in Version | 2.2.1 | |||||
| Summary | 0001223: ZEN image has both conf/named-* and conf/named/named-* files | |||||||
| Description | It's confusing. It's definitely a left over from our configuration migration in 2.2.0 / 2.1.0.[root@pf-zen pf]# ls conf/named* conf/named-isolation.ca conf/named-registration.ca conf/named_vlan.conf conf/named: named-isolation.ca named-registration.ca This ticket is to track that we should get rid of the bad one in our next zen image prior to release. | |||||||
| Tags | No tags attached. | |||||||
| fixed in git revision | ||||||||
| fixed in mtn revision | ||||||||
| Attached Files | ||||||||
Notes |
|
|
(0002094) fgaudreault (viewer) 2011-06-27 14:40 |
Removed the problematic files on the ZEN VMs |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-06-06 17:58 | obilodeau | New Issue | |
| 2011-06-27 14:40 | fgaudreault | Note Added: 0002094 | |
| 2011-06-27 14:40 | fgaudreault | Status | new => resolved |
| 2011-06-27 14:40 | fgaudreault | Fixed in Version | => 2.2.1 |
| 2011-06-27 14:40 | fgaudreault | Resolution | open => fixed |
| 2011-06-27 14:40 | fgaudreault | Assigned To | => fgaudreault |
| 2011-10-25 09:00 | obilodeau | Target Version | +1 => 2.2.1 |
| 2011-10-25 09:01 | obilodeau | Status | resolved => closed |
| Copyright © 2000 - 2012 MantisBT Group |