There are places in FreeIPA when Float parameters or float values are directly compared. This can cause problems due to Float representation error (http://docs.python.org/tutorial/floatingpoint.html).
An example of an error from this limitation is a makeapi problem for Float parameter maxvalue and minvalue on RHEL 6.2:
makeapi
maxvalue
minvalue
$ ./makeapi --validate Option in dnsrecord_add doesn't match. Got Float('loc_part_lat_sec', attribute=False, cli_name='loc_lat_sec', maxvalue=59.999000000000002, minvalue=0.0, multivalue=False, option_group=u'LOC Record', required=False) Expected Float('loc_part_lat_sec', attribute=False, cli_name='loc_lat_sec', maxvalue=59.999, minvalue=0.0, multivalue=False, option_group=u'LOC Record', required=False) Option in dnsrecord_add doesn't match. Got Float('loc_part_lon_sec', attribute=False, cli_name='loc_lon_sec', maxvalue=59.999000000000002, minvalue=0.0, multivalue=False, option_group=u'LOC Record', required=False) Expected Float('loc_part_lon_sec', attribute=False, cli_name='loc_lon_sec', maxvalue=59.999, minvalue=0.0, multivalue=False, option_group=u'LOC Record', required=False) ...
master: 092dd8d[[BR]] ipa-2-2: 8c230f1
Metadata Update from @mkosek: - Issue assigned to mkosek - Issue set to the milestone: FreeIPA 2.2 Core Effort - 2012/01
Login to comment on this ticket.