Bug 754662

Summary: cp error "cannot stat '/root/.ssh/config' " occurrs during configure kdump with ssh
Product: Red Hat Enterprise Linux 6 Reporter: Guohua Ouyang <gouyang>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED WORKSFORME QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.2CC: acathrow, bsarathy, cshao, jboggs, leiwang, mburns, moli, ovirt-maint, vincent, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-28 01:53:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
the error on screen none

Description Guohua Ouyang 2011-11-17 09:28:52 UTC
Description of problem:
There is a cp error "cannot stat '/root/.ssh/config' " occurrs during configure kdump with ssh.

Version-Release number of selected component (if applicable):
6.2-20111116.1

How reproducible:
100%.

Steps to Reproduce:
1. configure kdump with ssh

Actual results:
cp error "cannot stat '/root/.ssh/config' " occurrs .

Expected results:
no such error occurs

Comment 1 Guohua Ouyang 2011-11-17 09:29:29 UTC
Created attachment 534164 [details]
the error on screen

Comment 3 Mike Burns 2011-11-17 12:39:25 UTC
Probably a target for z-stream

Comment 4 Mike Burns 2011-11-17 12:40:01 UTC
Does this break kdump configuration, or is it just cosmetic?

Comment 5 Alan Pevec 2011-11-17 13:36:12 UTC
afaict, this is during service kdump restart, so not a bug in rhevh kdump configuration.

Comment 6 Guohua Ouyang 2011-11-18 03:31:02 UTC
(In reply to comment #4)
> Does this break kdump configuration, or is it just cosmetic?

It does not break kdump configuration, just cosmetic.

Comment 7 Vincent S. Cojot 2012-01-24 20:00:12 UTC
Maybe it's just me but kdump through ssh insists on using RSA keys instead the properly configured DSA key:
[root@ntamack ~]# /etc/init.d/kdump restart
Stopping kdump:                                            [  OK  ]
Detected change(s) the following file(s):
  
  /etc/kdump.conf
Rebuilding /boot/initrd-2.6.32-220.2.1.el6.x86_64kdump.img
Warning: Identity file /root/.ssh/kdump_id_rsa not accessible: No such file or directory.
Warning: Identity file /root/.ssh/kdump_id_rsa not accessible: No such file or directory.
Warning: Identity file /root/.ssh/kdump_id_rsa not accessible: No such file or directory.
Warning: Identity file /root/.ssh/kdump_id_rsa not accessible: No such file or directory.
cp: cannot stat `/root/.ssh/kdump_id_rsa': No such file or directory
Starting kdump:                                            [  OK  ]

Workaround:
[root@ntamack .ssh]# cp -p  kdump_id_dsa  kdump_id_rsa
[root@ntamack .ssh]# cp -p  kdump_id_dsa.pub  kdump_id_rsa.pub
[root@ntamack .ssh]# /etc/init.d/kdump restart
Stopping kdump:                                            [  OK  ]
No kdump initial ramdisk found.                            [WARNING]
Rebuilding /boot/initrd-2.6.32-220.2.1.el6.x86_64kdump.img
Starting kdump:                                            [  OK  ]

What the heck?

Vincent (This is on a DL360G4 system where we cannot use local kdumping because of the older SmartArrat 6i HBA).

Comment 8 Vincent S. Cojot 2012-01-24 20:00:55 UTC
[root@ntamack ~]# uname -a
Linux ntamack 2.6.32-220.2.1.el6.x86_64 #1 SMP Tue Dec 13 16:21:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@ntamack ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.2 (Santiago)

Comment 10 RHEL Program Management 2012-07-10 05:56:09 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 11 RHEL Program Management 2012-07-11 01:47:25 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.