Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1003992 - Implement kafo katello installer checks
Summary: Implement kafo katello installer checks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-03 16:38 UTC by Lukas Zapletal
Modified: 2019-09-26 13:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:28:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6278 0 Normal Closed [RFE] katello-installer pre-installation requirements check 2021-01-28 16:35:13 UTC

Description Lukas Zapletal 2013-09-03 16:38:54 UTC
More info here:

https://github.com/theforeman/kafo#system-checks

Checks:

a) openjdk java is installed
b) proper version of java (1.7?) is installed
c) there is enough space (4 GB) for katello installation (mongodb needs 3,5 GB)
d) check free space on /var/lib/pulp and issue WARNING (not error) when there is less than 20 GB (no free space no syncing fun)

Also look into the original katello-configure script, there are many other checks which can be implemented here (ping hostname, ping fqdn, hostname is set properly etc).

All of this should go into these system checks.

Comment 1 Mike McCune 2013-09-03 16:50:58 UTC
related:

https://bugzilla.redhat.com/show_bug.cgi?id=1003961

Comment 2 RHEL Program Management 2013-09-17 04:16:11 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 5 Mike McCune 2013-09-18 22:11:14 UTC
Since MDP3 will be adopting kafo entirely lets move this bug there

Comment 8 Lukas Zapletal 2014-03-12 10:12:13 UTC
This is still relevant, go ahead and add checkers for those (or similar) if needed. Foreman installer / kafo have support for these checkers.

Comment 11 Bryan Kearney 2014-06-18 19:49:14 UTC
This bug will fix all lzaps suggestions excpet for pulp disk space which will be tracked under https://bugzilla.redhat.com/show_bug.cgi?id=1110521.

Comment 12 Bryan Kearney 2014-06-18 20:27:16 UTC
Connecting redmine issue http://projects.theforeman.org/issues/6278 from this bug

Comment 13 Bryan Kearney 2014-07-16 14:44:11 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/6278 has been closed
-------------
Anonymous
Applied in changeset commit:katello-installer|98d602575dba25c50b6a901d2f2b3d72109f004e.

Comment 15 Bryan Kearney 2014-09-11 12:28:45 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


Note You need to log in before you can comment on or make changes to this bug.