Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1398594
Description of problem: ipa topologysuffix-verify domain ======================================================== Replication topology of suffix "domain" contains errors. ======================================================== ------------------------------------------------------------- Recommended maximum number of agreements per replica exceeded ------------------------------------------------------------- Maximum number of agreements per replica: 4 Server "p0029ipa03.unix.local" has 5 agreements with servers: i22ldap-ipa02.unix.local p0029ipa04.unix.local p00iuipa02.unix.local p029i35ipa02.unix.local p00iuipa02.unix.local the message should turn into a warning or let's disable this check since lots of customers have more than 4 agreements per replica. Version-Release number of selected component (if applicable): python2-ipaclient-4.4.0-12.el7.noarch Additional info: source code: ======================== ======================== if max_agmts_errors: textui.print_dashed(unicode(_('Recommended maximum number of ' 'agreements per replica exceeded'))) ======================== # check if suggested maximum number of agreements per replica max_agmts_errors = [] for m in master_cns: # chosen direction doesn't matter much given that 'both' is the # only allowed direction suppliers = graph.get_tails(m) if len(suppliers) > self.api.env.recommended_max_agmts: max_agmts_errors.append((m, suppliers)) ======================= # Topology plugin ('recommended_max_agmts', 4), # Recommended maximum number of replication # agreements ========================
Metadata Update from @pvoborni: - Issue assigned to someone - Issue set to the milestone: FreeIPA 4.5 backlog
Metadata Update from @tdudlak: - Issue assigned to tdudlak (was: someone)
master:
ipa-4-5:
Metadata Update from @tkrizek: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Please ignore the commits above, I accidentally pushed the code into a mirror repo instead of upstream. Sorry about that.
Metadata Update from @tkrizek: - Issue status updated to: Open (was: Closed)
Log in to comment on this ticket.