Bug 1277143

Summary: No 'jetty' package - for startup script, log rotation etc
Product: Red Hat Enterprise Linux 7 Reporter: John Horne <john.horne>
Component: jettyAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED WONTFIX QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.1CC: mizdebsk
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 09:01:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Horne 2015-11-02 13:39:20 UTC
Description of problem:
Under RHEL 7.1 there is no 'jetty' package. Under Fedora 22, there is a 'jetty' package which provides the system-D startup script, provides the '/etc/jetty' directory, handles log rotation etc.
Under F22 it is possible to install 'jetty', and then just enable and start the service. This is not possible with RHEL7, it is necessary to create the files ourself in order to get the service started. Further files then need to be created for log rotation and the like.


Version-Release number of selected component (if applicable):
From F22: jetty-9.2.9-2.fc22.noarch

How reproducible:
Running 'yum search' shows that there is no 'jetty' package. There are many module packages, but nothing to start the service.

Steps to Reproduce:
1. Install the RHEL 7.1 jetty packages.
2. Run 'systemctl status jetty.service' - no service found.
3.

Actual results:
(As root) systemctl status jetty.service
jetty.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Expected results:
systemctl should show the service as being available.


Additional info:
We have just started to take a look at jetty on RHEL 7, but it is an immediate disappointment if we have to start creating our own scripts just to get the service in a usable state. It seems that a backport (or similar) of 'jetty' from Fedora is required.

Comment 2 Mikolaj Izdebski 2015-11-04 09:01:14 UTC
systemd integration is not provided because jetty package is not intended to be used as a service - it was not tested in this configuration. Also note that jetty is in Optional channel, so it is not supported by Red Hat: https://access.redhat.com/articles/1150793