|Product:||[Retired] 389||Reporter:||Wayne Carruthers <bugs>|
|Component:||wiki||Assignee:||Deon Ballard <dlackey>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||ecs-bugs|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-06-21 23:15:04 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
|Bug Blocks:||152373, 240316, 427409|
Description Wayne Carruthers 2006-05-18 08:54:04 UTC
Description of problem: All the mistakes I made in my first eval of the install came about answering the questions in the install script, The username pw entry screens tended to confuse rather than be self explanatory, not sure of the solution Pehaps a 1 or 2 line entry for each step Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Comment 1 Rich Megginson 2006-05-18 14:01:27 UTC
Could you be more specific about individual screens/prompts and their wording?
Comment 2 Wayne Carruthers 2006-05-25 08:16:45 UTC
I finally had time to go back & do some uninstall & re installs on the test system to define my problems better My biggest problem it turns out was poor definition of dns, if an error occurs in the installer script the admin scripts are not created & admin config files not written so cant go back & manually correct them Suggest better messages re cause of script failure & perhaps a pause on error to allow correction of problem & then continue set up script As for confusion, where the (name) is in the prompt I did not at first realise it was the last entry I made, my fault, must have been a bit slow that day Where the system user to run DS is suggested (nobody) & a non default name is entered, then a prompt to create a valid system user external to the script or auto creation of the non default user could be put into the script One other observation, a mismatch in the name of the FC5 rpm to the software actually installed made ininstall a little more complicated than normal Anyway thanks & I think problems more me on that day than anything
Comment 4 Rich Megginson 2007-09-06 18:43:13 UTC
We should make sure the docs specify that DNS and reverse DNS must be working correctly, especially if using TLS/SSL or Kerberos. The RPM should create the user - this is the usual way service RPMs work.
Comment 5 Red Hat Bugzilla 2007-10-03 01:14:47 UTC
User email@example.com's account has been closed
Comment 6 Deon Ballard 2007-10-12 00:46:18 UTC
Reassigning to me.
Comment 9 Deon Ballard 2007-10-31 04:27:23 UTC
There was alreayd a DNS/NIS section for Solaris; I used added this text to RHEL and HPUX, then I added the above note about making sure DNS and reverse DNS is working for TLS/SSL/Kerberos. E.g.: It is very important that DNS and reverse DNS be working correctly on the host machine, especially if you are using TLS/SSL or Kerberos with Directory Server. Configure the DNS resolver and the NIS domain name by the modifying the /etc/resolv.conf, /etc/nsswitch.conf, and /etc/netconfig files, and set the DNS resolver for name resolution. Edit the /etc/defaultdomain file to include the NIS domain name. This ensures that the fully-qualified host and domain names used for the Directory Server resolve to a valid IP address and that that IP address resolves back to the correct hostname. Reboot the Red Hat Enterprise Linux machine to apply these changes. http://engineering.redhat.com/docbot/en-US/RedHat_Directory_Server/8.0/html/Installation_Guide/Installation_Guide-Platform_RHEL-DNS.html
Comment 10 Deon Ballard 2011-05-19 18:43:28 UTC
Changing modifieds to ON_QA.
Comment 11 Andrew Ross 2011-05-19 21:42:23 UTC
Verified: Red_Hat_Directory_Server-Installation_Guide-8.0-web-en-US-8.0.5-5.el5 http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/8.0/html/Installation_Guide/Installation_Guide-Support-Platforms.html#Installation_Guide-Platform_RHEL-DNS
Comment 12 Deon Ballard 2012-06-21 23:15:04 UTC