Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1422468
| Summary: | atomic run does not handle malformed image/repository names | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Babinsky <mbabinsk> | ||||
| Component: | atomic | Assignee: | Daniel Walsh <dwalsh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | adimania, amurdaca, bbaude, dwalsh, fkluknav, lsm5, walters | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | atomic-1.16.4-1.fc26 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-04-01 17:10:12 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: | |||||||
| Attachments: |
|
||||||
Can you try this with the git master? I'm not able to exactly replicate the error you are seeing. Indeed on master branch I get a sensible error message in step 3:
{{{
# ./atomic install freeipa/freeipa-server hostname master.ipa.test -U -r IPA.TEST -a Secret123 -p Secret123
<SNIP>
[root@master1 atomic]# ./atomic run freeipa-server
Need to pull freeipa-server
Unable to find freeipa-server
}}}
should we set this to release pending? Fixed in atomic-1.16.2 atomic-1.16.3-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2ad6948192 atomic-1.16.3-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cf5944a771 atomic-1.16.3-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cf5944a771 atomic-1.16.3-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2ad6948192 atomic-1.16.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8cbc792c6 atomic-1.16.4-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8cbc792c6 atomic-1.16.4-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 1250559 [details] debugging output from atomic run Description of problem: When supplying atomic run subcommand with malformed image name (e.g. missing organization in the name) the error message is rather cryptic and seems to originate from problematic handling of repository names rather than from failures to locate image name. Please check the reproducer below, it explains the issue more clearly. Version-Release number of selected component (if applicable): atomic-1.15.1-1.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Pull freeipa-server image from registry: atomic pull freeipa/freeipa-server 2. Install freeipa-server container: atomic install freeipa/freeipa-server hostname master.ipa.test -U -r IPA.TEST -a Secret123 -p Secret123 3. Run the container but leave out the organization name from container name atomic run freeipa-server Actual results: The error message displayed is rather cryptic: Unable to resolve None Expected results: Error message should say something like "Unable to find image {image_name}". Additional info: I have attached a debug output from the command run in step 3.