Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Replica deployment fails when "dns" is used. #2

Open
rjeffman opened this issue Dec 12, 2024 · 3 comments
Open

Replica deployment fails when "dns" is used. #2

rjeffman opened this issue Dec 12, 2024 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@rjeffman
Copy link
Owner

When creating a deployment with a custom container file and using the dns option, the ipareplica role fails with:

TASK [ipaclient : Install - IPA client test] ********************************************************************************
fatal: [replica]: FAILED! => {"changed": false, "msg": "Failed to verify that m1.ipa.test is an IPA Server."}

Servers and clients are correctly deployed, even if multiple deployments are used on the same configuration.
rjeffman added a commit that referenced this issue Dec 12, 2024
@rjeffman
Bump version for releane 0.3.0
ffc1b58 
Highligths for this release

* New support for custom container files
* New support for podman '--dns' option
* Split __main__ in separate files for better code organization
* Documentation enhancements

Bugs Fixed since 0.2.0

* Only copy data files if configuration is generated
* Don't add '*_remove_from_domain' to ipaclient and ipareplica, due to
  'delege_to' issue
* Fixed nameserver for hosts not on the first deployment

Known Issues

* When using 'dns' replica installation fails, only server and client
  deployments work in this case. (Issue #2)
@rjeffman
Copy link
Owner Author

As of the current version, this issue is still valid, although the effect is that the replica is partially deployed, and fails during first replication.

@rjeffman rjeffman added the help wanted Extra attention is needed label Dec 13, 2024
@rjeffman
Copy link
Owner Author

To circunvent this issue, use container_fqdn: true (See #3).

@rjeffman
Copy link
Owner Author

The docker compose spec does not define dns or disable-dns for networks, instead in forces the use of external networks.

This behavior is implemented in ipalab-config, but as the goal is to have the whole configuration in a single file, this issue will be kept open until there's a better solution or containers/podman-compose#1104 gets merged and released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rjeffman