Bug 1694816 - zabbix-web needs php-fpm
Summary: zabbix-web needs php-fpm
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: zabbix
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Volker Fröhlich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-01 18:45 UTC by Gwyn Ciesla
Modified: 2019-05-25 01:04 UTC (History)
4 users (show)

Fixed In Version: zabbix-4.0.7-2.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-25 01:04:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Gwyn Ciesla 2019-04-01 18:45:07 UTC 
As of at least 4.0.5, zabbix-web needs php-fpm should Require: php-fpm. Without it, I get 503s.
Comment 1 Fedora Update System 2019-04-26 16:47:12 UTC 
zabbix-4.2.1-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3090bf9e2c
Comment 2 Volker Fröhlich 2019-04-27 06:23:25 UTC 
I don't think that 4.2 is a version we want to package, as it does not align with the Fedora support cycle. 4.2 will probably receive no support whatsoever as soon as October: https://www.zabbix.com/life_cycle_and_release_policy
Comment 3 Fedora Update System 2019-04-27 22:30:38 UTC 
zabbix-4.2.1-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3090bf9e2c
Comment 4 Gwyn Ciesla 2019-04-29 13:19:42 UTC 
I thought it was on a 6-month cycle, at which time we could upgrade to the next, etc. If you'd like to revert and continue tracking LTS, that's fine; you're the maintainer and it's your call.
Comment 5 Gwyn Ciesla 2019-05-06 14:21:44 UTC 
Did you come to a decision on whether or not to go forward with 4.2.1?
Comment 6 Gwyn Ciesla 2019-05-15 18:49:11 UTC 
We should either push this to stable or revert to 4.0.x and bump Epoch.
Comment 7 Volker Fröhlich 2019-05-15 21:11:49 UTC 
(In reply to Gwyn Ciesla from comment #4)
> I thought it was on a 6-month cycle, at which time we could upgrade to the
> next, etc. If you'd like to revert and continue tracking LTS, that's fine;
> you're the maintainer and it's your call.

Since the cycles don't align and are not guaranteed and the fact that we are maintaining 2 versions of Fedora (i. e. 1 year), I don't see a way to maintain the non-LTS releases.

I'd rather drop the update that is now in testing and bump the epoch. I'm glad this is not EPEL, because Zabbix SIA is offering packages for RHEL too and that would have made a change in epoch more difficult.
Comment 8 Gwyn Ciesla 2019-05-16 15:04:33 UTC 
Will do. Sorry for the churn.
Comment 9 Fedora Update System 2019-05-16 15:35:08 UTC 
zabbix-4.0.7-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-634ccc953b
Comment 10 Volker Fröhlich 2019-05-16 15:36:43 UTC 
No worries! Thank you for taking care of it!
Comment 11 Fedora Update System 2019-05-17 15:37:54 UTC 
zabbix-4.0.7-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-634ccc953b
Comment 12 Fedora Update System 2019-05-25 01:04:57 UTC 
zabbix-4.0.7-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.