From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Description of problem: Using the following components: ispec-0.95-1.8rc1.noarch.rpm / rhr2- rhel4-0.9-16.rc1a.noarch.rpm / 1220 RHEL 4 release. 1. Created ispec server following instructions in the pdf. 2. Ran ispec, submitted my server configuration, kickstart files were created. 3. Booted to the boot.iso cd on disc1 of the 1220 release.** 4. ran command linux ks=http://10.0.0.63/ispec/models/server/ks2.cfg 5. OS completed installation and then rebooted to a console. At this point, my assumption was that the OS would boot, automatically run the desired tests and save results. I cannot logon to the OS because the password is encrypted in the ks file and looking through the documentation I cannot find information regarding a default password. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Expected Results: At this point, my assumption was that the OS would boot, automatically run the desired tests and save results. I cannot logon to the OS because the password is encrypted in the ks file and looking through the documentation I cannot find information regarding a default password. Additional info:
The root password is "hwcert". This was pointed out by another tester and has been fixed in the documentation. Can you tail -f /var/log/redhat-ready and see if the tests are running? Due to hardware compatibility issues, for RC we had to switch the tests to not log to vt12 by default but instead log to a file. The rhrconsole option (which was not documented at the time of the RC) allows you to override this. I apologize for the inadequate documentation; all of the above issues have been documented now.
Richard Yeah, it looks like it is running. Can I ask you a couple of extra ?'s? Specifically on step 6 of the current instructions. 1.The doc mentions the key we need to use is in redhatready2_id_dsa.pub. I could not find that file, found an ispec_id file so I used that instead. 2. With RHEL3 the .ssh folder was off /root, but the only place I could find .ssh on RHEL4 was /var/crash, so I edited the authorized keys file here. I am assuming that is correct 3. Do we copy the entire contents of the .pub file into authorized_keys2, or just the actual key itself. Thanks Gregg
> Yeah, it looks like it is running. Can I ask you a couple of > extra ?'s? Specifically on step 6 of the current instructions. Thanks for the feedback. I'll work on clarifying the below in the documentation as well. > 1.The doc mentions the key we need to use is in > redhatready2_id_dsa.pub. I could not find that file, found an > ispec_id file so I used that instead. This is the same thing. > 2. With RHEL3 the .ssh folder was off /root, but the only place I > could find .ssh on RHEL4 was /var/crash, so I edited the authorized > keys file here. I am assuming that is correct You may need to create the .ssh/ directory. It should be in /root/. > 3. Do we copy the entire contents of the .pub file into > authorized_keys2, or just the actual key itself. The entire file, which really is the actual key. You can just cp the file if the authorized_keys doesn't exist, or append the contents of the entire file to the authorized_keys if it does exist.
The commands should go something like this: mkdir -p /root/.ssh chmod 700 /root/.ssh cat /etc/sysconfig/redhatready2_id_dsa.pub >> /root/.ssh/authorized_keys (the current ispec rc will use ispec_id_dsa.pub, as noted above)
I believe all these issues have been resolved.