Bug 1352314 - Release management fault in priorities
Summary: Release management fault in priorities
Keywords:
Status: CLOSED DUPLICATE of bug 1205168
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-03 16:36 UTC by DaLiV
Modified: 2016-07-04 16:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-04 16:19:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description DaLiV 2016-07-03 16:36:55 UTC
Description of problem:
- FC23 have problem with component
- was provided fix for that
- FC24 still have same problem
problem is core networking related - so can be treated as HIGH PRIORITY / URGENT


Version-Release number of selected component (if applicable):
FC23 FC24

How reproducible:
see bug
https://bugzilla.redhat.com/show_bug.cgi?id=1205168

Steps to Reproduce:
1.install openldap, dhcp-server
2.configure ldap database, and configure dhcp server to use ldap
3. dhcp fault - company NETWORK IS NOT OPERABLE - that can not be intended as primary product function
4. make fix from described bug /1205168/, and recompile
5. in FC23 as in FC24 that corrects problem

Actual results:
new version have problems in CORE components /in provided example dhcp can not read configuration from ldap - and based on that network is not function, but network is must have ... / 

Expected results:
at least all must be operable, with minor inconveniences, that not require immediate recompiling of subsystems 
/some features not optimized or not implemented is minor flaw, but not working at all - that is deny for product usage .../

Additional info:
Next idea must be in general priority structure for release management ...
claimed as "optimized", but totally not worked is more worst than worked but not optimized, we must choosing primarily "working" direction

Comment 1 Kevin Fenzi 2016-07-04 16:19:25 UTC
This is not the way to escalate issues. 

Please instead post (politely) to the devel.org list and ask if anyone has contact with the openldap maintainer or can apply the fix. There may well be reasons it hasn't been applied yet.

*** This bug has been marked as a duplicate of bug 1205168 ***


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