foreman

A few days ago I started to re-surrect my Foreman(/katello) server and wanted to use it to pull content from remote repository for AlmaLinux. This involves updating Foreman with a new product and related AlmaLinux repository. I wrote a similar post on creating product & repository using hammer before for EPEL 8. However, it’s been a long while and things could change with the current version of Foreman server. # rpm -qa | egrep -i '^foreman-[0-9]|^katello-[0-9]|^pulp-server-[0-9]' katello-4....

I just updated my Foreman server and reboot, then this happened when I accessed the web console: Service unavailable ERF64-6496 [Foreman::MaintenanceException]: There are migrations pending in the system. This was the first time I’ve seen this message, and possibly because I haven’t done the update frequently enough. Fortunately, according to this blog post, it should be relatively easy to fix. [root@foreman ~]# sudo foreman-rake db:migrate API controllers newer than Apipie cache!...

Last night I published 4 or 5 of blog posts related to the Foreman/Satellite server. Well, it wasn’t a coincidence, it was me cramming the last minute for the Red Hat Satellite 6 Administration exam today. It’s also known as EX403. Needless to say, I didn’t know what was in the exam, and I can’t share what was in exam I had taken today. What I can share with you is that I passed EX403!...

In this blog post, I’m going to practice publishing and promoting content views using the hammer CLI. I already know how to do this using the Satellite/Foreman web UI. First, I’m going to create the Base content view for Operations organization and Boston location. [root@foreman ~]# hammer content-view create \ > --name Base --organization Operations \ > --description 'Base Packages' Content view created. [root@foreman ~]# hammer content-view list --organization Operations ----------------|---------------------------|--------------------------|-----------|---------------------|--------------- CONTENT VIEW ID | NAME | LABEL | COMPOSITE | LAST PUBLISHED | REPOSITORY IDS ----------------|---------------------------|--------------------------|-----------|---------------------|--------------- 6 | Base | Base | false | | ----------------|---------------------------|--------------------------|-----------|---------------------|--------------- The next step is adding the repos to the content view....

In this post, I will create a new life-cycle environment paths for the Operations organization that includes life-cycle environments named Deveopment, QA, and Production. Let’s list the current life-cycle environment for Operations organization. [root@foreman ~]# hammer lifecycle-environment list --organization Operations ---|---------|------ ID | NAME | PRIOR ---|---------|------ 6 | Library | ---|---------|------ When we create our first environment, we’ll need to use the ID of the Library, which is 6 in this case....

In this blog post, I’m going to show how to add a new product caled EPEL8 and populate it with a repository from EPEL 8. There should be 3 main steps: Create a Content-Credentials which stores the package signing key of the product or repository Create a new Product Create a new Repository Firt thing first, let’s create a new content-credentials named RPM-GPG-KEY-EPEL-8 with the contents from the EPEL 8’s GPG signing key....

Let’s learn how to create an organization and location on Foreman/Satellite server using the hammer command-line-interface. In this example, I’m going to create an organization called: Operation and assign its location to Boston. On the Foreman server, excute the following commands: [root@foreman ~]# hammer organization create --name Operations Organization created. [root@foreman ~]# hammer location create --name Boston Location created. [root@foreman ~]# hammer organization add-location --name Operations \ > --location Boston The location has been associated....

When I setup Foreman (Satellite) server, I didn’t have Ansible support enabled. Here is how it can be done later on. If we only need Ansible support, it’s sufficient to just run this command: # foreman-installer \ --enable-foreman-plugin-ansible \ --enable-foreman-proxy-plugin-ansible Just a note for myself, I also need Remote Execution enabled if I want to run Ansible playbooks as Job Templates. # foreman-installer \ --enable-foreman-plugin-remote-execution \ --enable-foreman-proxy-plugin-remote-execution-ssh Note that the remote execution feature is enabled by default on Foreman/Satellite server....