RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1277143 - No 'jetty' package - for startup script, log rotation etc
Summary: No 'jetty' package - for startup script, log rotation etc
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: jetty
Version: 7.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Mikolaj Izdebski
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-02 13:39 UTC by John Horne
Modified: 2015-11-04 09:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-04 09:01:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.