Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1918464 - check service status bats test failure
Summary: check service status bats test failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.9.0
Assignee: Eric Helms
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-20 19:11 UTC by Patrick Creech
Modified: 2021-04-21 13:25 UTC (History)
2 users (show)

Fixed In Version: foreman-installer-2.3.1.5-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:25:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31694 0 Normal Closed Pulpcore systemd service have incorrect 'type' key 2021-02-08 05:56:34 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:25:54 UTC

Description Patrick Creech 2021-01-20 19:11:36 UTC 
Running bats against a build resulted in a failed 'check service status' test.

not ok 2 check service status
# (in test file fb-test-katello.bats, line 33)
#   `foreman-maintain service status' failed

....

#                                                                                 / displaying pulpcore-api
# ● pulpcore-api.service - Pulp API Server
#    Loaded: loaded (/etc/systemd/system/pulpcore-api.service; disabled; vendor preset: disabled)
#    Active: inactive (dead)
# 
# Jan 20 18:02:14 {snipped hostname} systemd[1]: [/etc/systemd/system/pulpcore-api.service:7] Unknown lvalue 'type' in section 'Service'
#                                                                                 / displaying pulpcore-content
# ● pulpcore-content.service - Pulp Content App
#    Loaded: loaded (/etc/systemd/system/pulpcore-content.service; disabled; vendor preset: disabled)
#    Active: inactive (dead)
# 
# Jan 20 18:02:14 {snipped hostname} systemd[1]: [/etc/systemd/system/pulpcore-content.service:7] Unknown lvalue 'type' in section 'Service'
#                                                                                 / displaying pulpcore-resource-manager
# ● pulpcore-resource-manager.service - Pulp Resource Manager
#    Loaded: loaded (/etc/systemd/system/pulpcore-resource-manager.service; disabled; vendor preset: disabled)
#    Active: inactive (dead)

...

# Some services are not running (pulpcore-api, pulpcore-content, pulpcore-resource-manager)
# --------------------------------------------------------------------------------
# Scenario [Status Services] failed.
# 
# The following steps ended up in failing state:
# 
#   [service-status]
# 
# Resolve the failed steps and rerun
# the command. In case the failures are false positives,
# use --whitelist="service-status"
Comment 1 Justin Sherrill 2021-01-20 20:26:42 UTC 
might fix https://bugzilla.redhat.com/show_bug.cgi?id=1916485
Comment 7 Devendra Singh 2021-02-05 16:03:49 UTC 
Verified on 6.9 Snap 12.
Comment 10 errata-xmlrpc 2021-04-21 13:25:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1313
Note You need to log in before you can comment on or make changes to this bug.