I was trying to help on a new test for test_integration/test_ipa_ipa_migration.py::TestIPAMigrationProdMode and consistently got a failure in cls.replicas[0] trying to read cls.master with "Failed to bind to remote server: cannot connect to 'ldap://ipa.example.test': Connection refused"
I manually added master to the replica hosts file and that resolved the issue.
I created three new VMs: one for the controller, one for the master and one for the other master (replica[0]).
I setup a pretty standard config file declaring the two servers.
I disabled client in the MigrationTest class because I didn't need it.
I run the tests with: PYTHONPATH=. IPATEST_YAML_CONFIG=/root/freeipa/ipatests/test-config.yaml ipatests/ipa-run-tests test_integration/test_ipa_ipa_migration.py::TestIPAMigrationProdMode
PYTHONPATH=. IPATEST_YAML_CONFIG=/root/freeipa/ipatests/test-config.yaml ipatests/ipa-run-tests test_integration/test_ipa_ipa_migration.py::TestIPAMigrationProdMode
I don't understand how this works in PR-CI with the replica not knowing how to connect to the master without some pointer in DNS or /etc/hosts, but it obviously works somehow.
This issue can also be replicated with the ipa-migrate example in https://github.com/freeipa/freeipa-local-tests: - start the environment - stop systemd-resolved on m2.target.test and point /etc/resolv.conf to 127.0.0.1 - try to do migration
ipa-migrate
m2.target.test
master:
ipa-4-13:
ipa-4-12:
Metadata Update from @sumenon: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)