Bug 1277143 - No 'jetty' package - for startup script, log rotation etc
No 'jetty' package - for startup script, log rotation etc
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: jetty (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Mikolaj Izdebski
BaseOS QE - Apps
Depends On:
  Show dependency treegraph
Reported: 2015-11-02 08:39 EST by John Horne
Modified: 2015-11-04 04:01 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-04 04:01:14 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Horne 2015-11-02 08:39:20 EST
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.

Actual results:
(As root) systemctl status 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 04:01:14 EST
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

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