Bug 1507848
Summary: | katello-change-hostname should remove last_scenario.yml only after success of installer | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Peter Ondrejka <pondrejk> |
Component: | satellite-change-hostname | Assignee: | Jonathon Turel <jturel> |
Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | bbuckingham, bkearney, ehelms, jomitsch, jturel, rdickens, swadeley |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
Satellite Installer requires absolute paths.
Always provide an absolute path for --certs-tar. For example, /root/new.name-certs.tar.
If you run the installer with a relative path, run the installer again with the absolute path and the --scenario parameter to create the last_scenario.yml.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:54:17 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
Peter Ondrejka
2017-10-31 10:00:00 UTC
Workarounds: 1. always provide an absolute path for --certs-tar (e.g. /root/new.name-certs.tar) 2. re-run the installer with --scenario parameter to re-create the last_scenario.yml If I understand correctly, there are two issues - certs tar needing an absolute path and last_scenario file being deleted, so you can't retry k-c-h. For the absolute path issue, it should be fixed by: https://bugzilla.redhat.com/show_bug.cgi?id=1466688 upstream PR - https://github.com/Katello/katello-installer/pull/542 Brad, can we pull this into 6.3? (I realize it won't make the beta) Peter For the deleting last_scenario issue, a simple solution that we can do now is - move last_scenario.yml instead of deleting it - run through k-c-h - if k-c-h fails, have a cleanup that moves last_scenario back I can work on a PR to do this, thanks for raising the issue We aligned it to 6.3 GA earlier this morning, so goal should be to include it. Sorry I meant this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1466688 Can we pull this BZ into 6.3? Created redmine issue http://projects.theforeman.org/issues/21517 from this bug The bug referenced in comment 6 has been aligned to 6.3. Hello Re the need for absolute paths what do you think of this: https://bugzilla.redhat.com/show_bug.cgi?id=1466688#c15 Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21517 has been resolved. 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-2018:0336
|