Bug 43407 – s4-connector: fix `connector/s4/mapping/dns/ignorelist` handling in mapping.py

Bug 43407 - s4-connector: fix `connector/s4/mapping/dns/ignorelist` handling in mapping.py


Summary:	s4-connector: fix `connector/s4/mapping/dns/ignorelist` handling in mapping.py

Status:	RESOLVED DUPLICATE of bug 43397

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Connector maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:	32086 44374
	Show dependency tree / graph

Reported:	2017-01-24 12:50 CET by Lukas Oyen
Modified:	2018-04-14 14:15 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Flags:	oyen: Patch_Available+

Attachments
Patch: s4-connector: fix `connector/s4/mapping/dns/ignorelist` handling (3.15 KB, patch) 2017-01-24 12:50 CET, Lukas Oyen	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Lukas Oyen

2017-01-24 12:50:34 CET

Created attachment 8371 [details]
Patch: s4-connector: fix `connector/s4/mapping/dns/ignorelist` handling

The UCR variable `connector/s4/mapping/dns/ignorelist` included the attribute.
This is not the case for any other `connector/s4/mapping/*/ignorelist`
variable. The attached patch fixes the issue.
    
It also fixes a copy-paste error handling `connector/s4/mapping/dc/ignorelist`.

Comment 1 Florian Best

2017-01-24 13:02:10 CET


*** This bug has been marked as a duplicate of bug 43397 ***