Bug 1471507
| Summary: | Should the atomic run --detach option create a containerized ipa server in background? | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | mpanaous |
| Component: | ipa-server-container | Assignee: | Petr Vobornik <pvoborni> |
| Status: | CLOSED DEFERRED | QA Contact: | Nikhil Dehadrai <ndehadra> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | pcech, tscherf |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-01-06 11:15:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This BZ has been evaluated multiple times over the last several years and we assessed that it is a valuable request to keep in the backlog and address it at some point in future. Time showed that we did not have such capacity, nor have it now nor will have in the foreseeable future. In such a situation keeping it in the backlog is misleading and setting the wrong expectation that we will be able to address it. Unfortunately we will not. To reflect this we are closing this BZ. If you disagree with the decision please reopen or open a new support case and create a new BZ. However this does not guarantee that the request will not be closed during the triage as we are currently applying much more rigor to what we actually can accomplish in the foreseeable future. Contributions and collaboration in the upstream community and CentOS Stream is always welcome! Thank you for understanding Red Hat Enterprise Linux Identity Management Team |
Description of problem: Should the atomic run --detach option create a containerized ipa server in background? Version-Release number of selected component (if applicable): -bash-4.2# atomic host status State: idle Deployments: * rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard Version: 7.3.6 (2017-06-23 16:20:45) Commit: e073a47baa605a99632904e4e05692064302afd8769a15290d8ebe8dbfd3c81b rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard Version: 7.3.5-1 (2017-06-09 19:58:11) Commit: c04cab425084ce81d66d1717f464e292bc5a908a86802faf0da7dd22d74d3727 -bash-4.2# How reproducible: always Steps to Reproduce: -bash-4.2# atomic run --help usage: atomic run [-h] [--storage STORAGE] [-n NAME] [--spc] [-d] [--quiet | --display] image ... -d, --detach run the container in the background -bash-4.2# atomic run --name ipasrv --detach rhel7/ipa-server docker run -h ipasrv.dockerlab.local --rm --name ipasrv -v /var/lib/ipasrv:/data:Z -v /sys/fs/cgroup:/sys/fs/cgroup:ro --tmpfs /run --tmpfs /tmp -v /dev/urandom:/dev/random:ro rhel7/ipa-server Sun Jul 16 13:31:35 UTC 2017 /usr/sbin/ipa-server-configure-first upgrade FreeIPA server is already configured, starting the services. Sun Jul 16 13:32:08 UTC 2017 /usr/sbin/ipa-server-configure-first update-self-ip-address ipasrv.dockerlab.local has address 172.17.0.2 FreeIPA server started. ^C-bash-4.2# Actual results: containerized ipa continues to run in foreground unless killed by Ctrl+C Expected results: run the container in the background Additional info: