Bug 1584162
Summary: | Error: No such repository with name <MISSING> | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Lukáš Hellebrandt <lhellebr> |
Component: | Hammer | Assignee: | Rahul Bajaj <rabajaj> |
Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | Unspecified | CC: | akarsale, apatel, bkearney, dhlavacd, ehelms, kgaikwad, mbacovsk, mhulan, rabajaj |
Target Milestone: | 6.5.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-14 12:37:23 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: |
Description
Lukáš Hellebrandt
2018-05-30 12:20:04 UTC
upstream fix is merged: https://github.com/Katello/hammer-cli-katello/pull/561 Connecting redmine issue https://projects.theforeman.org/issues/23872 from this bug rabajaj can you please check the upstream issue as to why it is not moved to fixed? Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/23872 has been resolved. The fix for this is merged upstream and is in the latest 6.5 SNAP. Verified with Sat 6.5 snap 7 # hammer host create --compute-resource-id 1 --architecture x86_64 --domain example.com --operatingsystem-id 1 --partition-table-id 1 --location-id 2 --organization-id 1 --name fishy --root-password toortoor --kickstart-repository 'NONEXISTENT_REPO' --lifecycle-environment-id 1 --content-view-id 1 Could not create the host: Error: No such repository with name NONEXISTENT_REPO, in lifecycle environment 1 and content view 1 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222 Clearing out the needinfo since the issue was resolved :) |