Bug 1777806
Summary: | When Service weight is set as 0 for server in IPA location "IPA Error 903: InternalError" is displayed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Sudhir Menon <sumenon> |
Component: | ipa | Assignee: | François Cami <fcami> |
Status: | CLOSED ERRATA | QA Contact: | ipa-qe <ipa-qe> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.2 | CC: | fcami, ksiddiqu, pasik, pcech, rcritten, tscherf, twoerner |
Target Milestone: | rc | Keywords: | TestCaseProvided |
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ipa-4.8.7-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 02:50:15 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sudhir Menon
2019-11-28 11:08:25 UTC
Taking for investigation. Quoting https://tools.ietf.org/html/rfc2782 Weight A server selection mechanism. The weight field specifies a relative weight for entries with the same priority. Larger weights SHOULD be given a proportionately higher probability of being selected. The range of this number is 0-65535. This is a 16 bit unsigned integer in network byte order. Domain administrators SHOULD use Weight 0 when there isn't any server selection to do, to make the RR easier to read for humans (less noisy). In the presence of records containing weights greater than 0, records with weight 0 should have a very small chance of being selected. The RFC states that weight=0 is a valid use-case. If all servers in a location have weight=0, the sum of their weights is still 0: for server in servers: weight = int(server.get('ipaserviceweight', [100])[0]) weight_sum += weight leading to a division by zero later on: for server in servers_additional_info.values(): server['service_relative_weight'] = [ u'{:.1f}%'.format( int(server['ipaserviceweight'][0])*100.0/weight_sum) ] Upstream ticket: https://pagure.io/freeipa/issue/8135 Fixed upstream master: https://pagure.io/freeipa/c/f589a8952c33a25794e577077bb3c0bda740667c ipa-4-8: https://pagure.io/freeipa/c/12d6864b6dc30155414e2483f7634684ccc9ee3e Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: idm:DL1 and idm:client security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4670 |