Description of problem: when adding a host and not supplying --os, a default value of "redhat 5.3 Tikanga" is being added. I don't think we should assume this. If it is a required field then it should error, otherwise leave it with no value. [root@jennyv2 schema]# ipa host-add jennyv3.bos.redhat.com Host added [root@jennyv2 schema]# ldapsearch -x -D "cn=Directory Manager" -w Secret123 -b "cn=jennyv3.bos.redhat.com,cn=computers,cn=accounts,dc=bos,dc=redhat,dc=com" # extended LDIF # # LDAPv3 # base <cn=jennyv3.bos.redhat.com,cn=computers,cn=accounts,dc=bos,dc=redhat,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # jennyv3.bos.redhat.com, computers, accounts, bos.redhat.com dn: cn=jennyv3.bos.redhat.com,cn=computers,cn=accounts,dc=bos,dc=redhat,dc=com cn: jennyv3.bos.redhat.com nsHardwarePlatform: i686 objectClass: nshost objectClass: ipahost objectClass: pkiuser objectClass: krbprincipalaux objectClass: krbprincipal objectClass: top nsOsVersion: redhat 5.3 Tikanga enrolledBy: uid=admin,cn=users,cn=accounts,dc=bos,dc=redhat,dc=com krbPrincipalName: host/jennyv3.bos.redhat.com.COM serverHostName: jennyv3 Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. install ipa server 2. ipa host-add <fqdn_hostname> 3. Actual results: Expected results: Additional info:
It currently defaults to the settings of the machine that the command is run on.
Ummm ... what if you were doing a bulk add - that would be a lot of incorrect data
If you were doing a bulk add w/o providing it yes, there would be a lot of bad data. I guess it is a bit of a policy question. I have no problem removing the default if desired.
The defaults have been removed, it was a poor assumption.