Bug 65475

Summary:	"lock" group doesn't exist during upgrade
Product:	[Retired] Red Hat Linux	Reporter:	hjl
Component:	setup	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	dwalsh, ovasik, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-23 05:39:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description hjl 2002-05-25 06:17:19 UTC

When upgrading from 7.1, I got

warning: group lock does not exist - using root

The problem is lock is new since 7.1. But /etc/group won't be
replaced by setup if it has been modified. mailcap should check
lock in /etc/group during upgrade and add it if it is missing.

Comment 1 Bill Nottingham 2002-06-12 06:36:17 UTC

Its's added in the lockdev package.

Comment 2 hjl 2002-06-19 21:46:40 UTC

The bug is in the setup spec file. It has to make sure lock is
in /etc/group for upgrade even if /etc/group was changed.

Comment 3 Bill Nottingham 2004-09-23 05:39:24 UTC

No, the lockdev packaage will add the group.