-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ipatests][Azure Pipelines] Populate containers with self-AAAA records #5486
Conversation
79d1f8b
to
7a4002d
Compare
No specific comments on the core changes but there is a significant number of single to double quote changes that seem to be formatting-only. |
I've especially noted that in PR message and the commit's one:
|
Yep, in that case it makes sense to do some uniformity. Thanks! |
@rcritten, if you strongly object to this I can revert extra changes, even though it was convenient for me to use |
I've never understood the significance of single vs double quotes nor why changing it en-mass is important. I don't really care about it other than polluting git history. |
I'm for enforcing code style one or another. In this case, that was easier for me to do 'hack hack black'. |
I think we can merge this. LGTM. |
IPA server's AAAA records at embedded DNS mode depend on result of `get_server_ip_address` function(`ipaserver.install.installutils`), which in turn, relies on NSS. In case of Azure Pipelines, there are neither IPv6 records in '/etc/hosts' nor external DNS, which may provide such. This leads to the missing AAAA records for master and missing AAAA records for `ipa-ca` pointing to master in embedded DNS. In particular, tests `test_ipa_healthcheck_no_errors`, `test_ipa_dns_systemrecords_check` fail with: ``` [ { "source": "ipahealthcheck.ipa.idns", "check": "IPADNSSystemRecordsCheck", "result": "WARNING", "uuid": "b979a88a-6373-4990-bc83-ce724e9730b4", "when": "20210120055054Z", "duration": "0.032740", "kw": { "msg": "Got {count} ipa-ca AAAA records, expected {expected}", "count": 1, "expected": 2 } } ] ``` where `ipa-ca` record exists only for replica. Note: since the most of the code in setup_containers was touched it has been reformatted. Fixes: https://pagure.io/freeipa/issue/8683 Signed-off-by: Stanislav Levin <slev@altlinux.org>
This test assumes that the current environment has only IPv4, but for example, Azure Pipelines provides both IPv4 and IPv6. Fixes: https://pagure.io/freeipa/issue/8683 Signed-off-by: Stanislav Levin <slev@altlinux.org>
`update-crypto-policies` tool from RPM package `crypto-policies-scripts` is required for tests. Signed-off-by: Stanislav Levin <slev@altlinux.org>
7a4002d
to
6cbaf83
Compare
@abbra, thank you!
|
Needs a manual backport to
|
@abbra, yes, sure. |
#5555, nice PR number :) |
get_server_ip_address
function(ipaserver.install.installutils
), which in turn, relies on NSS. In case of Azure Pipelines, there are neither IPv6 records in '/etc/hosts' nor external DNS, which may provide such. This leads to the missing AAAA records for master and missing AAAA records foripa-ca
pointing to master in embedded DNS. In particular, teststest_ipa_healthcheck_no_errors
,test_ipa_dns_systemrecords_check
fail with:where
ipa-ca
record exists only for replica.Note: since the most of the code in setup_containers was touched it has been reformatted.
Fixes: https://pagure.io/freeipa/issue/8683