Bug 1242950 – Installer is creating a gutterball user account/group, but are not required.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1242950 - Installer is creating a gutterball user account/group, but are not required.

Summary:	Installer is creating a gutterball user account/group, but are not required.

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	6.1.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium (vote)
Target Milestone:	Beta
Target Release:	Unused
Assigned To:	Tom McKay
QA Contact:	Corey Welton
Docs Contact:

URL:	http://projects.theforeman.org/issues...
Whiteboard:	Verified in Upstream
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-07-14 09:13 EDT by Michael Stead
Modified:	2018-03-02 05:54 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-07-27 04:53:53 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:1500	normal	SHIPPED_LIVE	Red Hat Satellite 6.2 Base Libraries	2016-07-27 08:24:38 EDT

Groups: None (edit)

Description Michael Stead 2015-07-14 09:13:33 EDT

Description of problem:

When setting up gutterball, the installer is creating a gutterball user account and group, and they are not required. Gutterball only requires that a DB user be created.


Steps to Reproduce:
1. Install/Upgrade Sat6
2. Verify that a gutterball user account and group were created.

Actual results:
gutterball user account/group were created.

Expected results:
The gutterball user account/group should not be created after install/upgrade.

Comment 4 Tom McKay 2015-09-24 13:01:23 EDT

Created redmine issue http://projects.theforeman.org/issues/11957 from this bug

Comment 5 Bryan Kearney 2015-10-06 10:01:36 EDT

Moving to POST since upstream bug http://projects.theforeman.org/issues/11957 has been closed

Comment 6 Tazim Kolhar 2015-11-17 07:17:26 EST

VERIFIED:
# rpm -qa | grep foreman
dell-pem600-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-release-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
foreman-ovirt-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
foreman-libvirt-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
foreman-postgresql-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch
tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch
tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch
dell-pem600-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
dell-pem600-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch
foreman-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch
foreman-debug-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
foreman-proxy-1.11.0-0.develop.201511111339git7cbe47a.el7.noarch
foreman-compute-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch
tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.4.0-1.201511111650gitdda13df.el7.noarch
foreman-gce-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
foreman-release-scl-1-1.el7.x86_64
foreman-vmware-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch
tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch

steps:
1. Install/Upgrade Sat6
2. Verify that a gutterball user account and group were created.

Comment 10 errata-xmlrpc 2016-07-27 04:53:53 EDT

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, 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/RHBA-2016:1500

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