Bug 715326 - chgrp: invalid group: `ssh_keys'
Summary: chgrp: invalid group: `ssh_keys'
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openssh
Version: 6.2
Hardware: All
OS: Linux
high
high
Target Milestone: beta
: 6.2
Assignee: Jan F. Chadima
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
: 715375 720888 (view as bug list)
Depends On:
Blocks: 691780
TreeView+ depends on / blocked
 
Reported: 2011-06-22 14:34 UTC by Jay Turner
Modified: 2015-01-08 00:17 UTC (History)
6 users (show)

Fixed In Version: openssh-5.3p1-61.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-27 12:45:23 UTC
Target Upstream Version:

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

Description Jay Turner 2011-06-22 14:34:26 UTC 
Description of problem:
Getting the following series of errors on boot after installing RHEL6.2-20110621.n.0_nfs-Server-x86_64 (openssh-5.3p1-60.el6.x86_64)  The invalid group prevents users from being able to ssh into the system.

Generating SSH2 RSA host key: chgrp: invalid group: `ssh_keys'
[  OK  ]

Generating SSH1 RSA host key: chgrp: invalid group: `ssh_keys'
[  OK  ]

Generating SSH2 DSA host key: chgrp: invalid group: `ssh_keys'
[  OK  ]

Version-Release number of selected component (if applicable):
openssh-5.3p1-60.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install
2. Attempt to ssh into the machine post-installation.  Client system will close the connection almost immediately.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jay Turner 2011-06-22 14:35:12 UTC 
Problem impacts Beaker and that issue is being tracked in https://engineering.redhat.com/rt3/Ticket/Display.html?id=114080
Comment 2 Jan F. Chadima 2011-06-23 05:58:12 UTC 
*** Bug 715375 has been marked as a duplicate of this bug. ***
Comment 7 Jan F. Chadima 2011-07-14 07:32:58 UTC 
*** Bug 720888 has been marked as a duplicate of this bug. ***
Comment 8 Jan F. Chadima 2011-07-27 12:45:23 UTC 
This bug is repaired by unrolling the init script change.
Note You need to log in before you can comment on or make changes to this bug.