Bug 1896134
Summary: | New Satellite 6.8 install fails on '/usr/sbin/foreman-rake apipie:cache:index' returned 1 instead of one of [0] | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Neal Kim <nkim> | ||||
Component: | Installation | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Devendra Singh <desingh> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6.8.0 | CC: | alsouza, ehelms, gscarbor | ||||
Target Milestone: | Unspecified | Keywords: | Triaged | ||||
Target Release: | Unused | ||||||
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: | 2020-11-18 14:46:36 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: |
|
Description
Neal Kim
2020-11-09 19:33:28 UTC
Although I'm able to reproduce this issue in my environment (along with a few other colleagues). It seems there are other people who can complete the install just fine. I'll keep digging to see what might be different. Cheers, So if I run the installer with options: satellite-installer --scenario satellite \ --foreman-initial-organization "initial_organization_name" \ --foreman-initial-location "initial_location_name" \ --foreman-initial-admin-username admin_user_name \ --foreman-initial-admin-password admin_password The installer completes cleanly without error. If I revert my VM snapshot back to before the install and execute the installer with no options (as outlined in the reproducer steps) it errors out again. I'm not discounting the fact that this all could be due to some transient IO issue. Will keep digging. Cheers, I hit this error when I ran the installer with only the username and password specified. Maybe something about the org or location prevents it? *** This bug has been marked as a duplicate of bug 1890923 *** |