Univention Bugzilla – Full Text Bug Listing |
Summary: | NoAnswer exception in adconnector/admember/check_dcmaster_srv_rec | ||
---|---|---|---|
Product: | UCS | Reporter: | Florian Best <best> |
Component: | AD Connector | Assignee: | Arvid Requate <requate> |
Status: | CLOSED FIXED | QA Contact: | Stefan Gohmann <gohmann> |
Severity: | normal | ||
Priority: | P5 | CC: | gohmann, requate |
Version: | UCS 4.0 | ||
Target Milestone: | UCS 4.2-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=44849 | ||
What kind of report is it?: | Bug Report | What type of bug is this?: | 6: Setup Problem: Issue for the setup process |
Who will be affected by this bug?: | 2: Will only affect a few installed domains | How will those affected feel about the bug?: | 5: Blocking further progress on the daily work |
User Pain: | 0.343 | Enterprise Customer affected?: | |
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | 2017040821000087, 2017022121000485, 2017020821000563, 2017092721000096 | Bug group (optional): | Error handling, External feedback |
Max CVSS v3 score: | |||
Bug Depends on: | |||
Bug Blocks: | 45578 |
Description
Florian Best
2015-06-29 17:20:43 CEST
Reported again: Traceback (c56c59df25a822d731b9ec4dad990915): Execution of command 'adconnector/admember/check_dcmaster_srv_rec' has failed: Traceback (most recent call last): File "%PY2.7%/univention/management/console/base.py", line 282, in execute function(self, request) File "%PY2.7%/univention/management/console/modules/decorators.py", line 316, in _response result = _multi_response(self, request) File "%PY2.7%/univention/management/console/modules/decorators.py", line 460, in _response return list(function(self, iterator, *nones)) File "%PY2.7%/univention/management/console/modules/decorators.py", line 282, in _fake_func yield function(self, *args) File "%PY2.7%/univention/management/console/modules/adconnector/__init__.py", line 574, in check_dcmaster_srv_rec result = self._check_dcmaster_srv_rec() File "%PY2.7%/univention/management/console/modules/adconnector/__init__.py", line 567, in _check_dcmaster_srv_rec if admember.get_domaincontroller_srv_record(ucr.get('domainname')): File "%PY2.7%/univention/lib/admember.py", line 1108, in get_domaincontroller_srv_record response = resolver.query('_domaincontroller_master._tcp.%s.' % domain, 'SRV') File "/usr/lib/python2.7/dist-packages/dns/resolver.py", line 858, in query raise_on_no_answer) File "/usr/lib/python2.7/dist-packages/dns/resolver.py", line 133, in __init__ raise NoAnswer NoAnswer Remark: after first insall Version: 4.0-2 errata264 (Walle) Reported again, 4.0-3 errata292 (Walle) Reported again by the same UUID, 4.0-3 errata292 (Walle) Why is it NoAnswer and not NXDomain? Reported again, 4.0-2 errata193 (Walle) Reported again, 4.0-4 errata377 (Walle) Reported again, 4.1-1 errata121 (Vahr) Reported again, 4.1-1 errata128 (Vahr) Move setup issues to 4.2-0-errata. Version: 4.1-3 errata278 (Vahr) Version: 4.1-4 errata360 (Vahr) Version: 4.1-4 errata389 (Vahr) Remark: Error pops up after logging into UMC dns.resolver.query throws NoAnswer by default (raise_on_no_answer=True) if no definite answer is received. univention.lib.admember.get_domaincontroller_srv_record now catches that too. Advisory: univention-lib.yaml Code review: OK Tests: OK YAML: OK Version: 4.1-4 errata324 (Vahr) Remark: how do I solve this? Re: Comment 15: this requests a backport or what's the intention of the comment here? If so, then please clone the bug, this one is dead and closed. (In reply to Arvid Requate from comment #16) > Re: Comment 15: this requests a backport or what's the intention of the > comment here? If so, then please clone the bug, this one is dead and closed. I am just showing that it has been reported again. If there are very much reports for old versions then the maintainers of the specific component have the chance to decide to make a backport. > I am just showing that it has been reported again.
Yes, but please open a bug for 4.1-4 then, because this one is for 4.2.
Just clone it, as usual.
|