Blog Image

Open Grieves

Assimilate quickly!

You must comply!

CRI-O on OpenShift Container Platform 3.9 and RHEL 7.5

Out of trouble Posted on 2018-04-21 17:38:45

In order to try out CRI-O on OpenShift Container Platform 3.9 running on Red Hat Enterprise Linux 7.5, you need to label your nodes with runtime: cri-o.

Eg, in your /etc/ansible/hosts file:

mynode openshift_node_labels=”{‘region’: ‘nodes’, ‘zone’: ‘default’, ‘runtime’: ‘cri-o’}”

This is a workaround for this bug:

Ansible Tower on Azure

Out of trouble Posted on 2017-02-26 22:33:02

You can’t run the installer ( as root, run it with sudo (sudo sh ./ instead. That works, or it complains that you are not root..

Azure Load Balancer json with session persistence

Out of trouble Posted on 2017-02-13 12:33:25

It took some time for me to find out that to get session persistence, you use the variable ‘loadDistribution’ and to get Client IP session persistence, you use ‘sourceIP’ as value.

So.. yeah.. the load balancers rules would in json look something like below:

“loadBalancingRules”: [{
“name”: “myLBrules”,
“properties”: {
“frontendIPConfiguration”: {
“id”: “[variables(‘myLbFrontEndConfigId’)]”
“backendAddressPool”: {
“id”: “[variables(‘myLbBackendPoolId’)]”
“protocol”: “Tcp”,
“loadDistribution”: “sourceIP”,
“idleTimeoutInMinutes”: 30,
“frontendPort”: 8443,
“backendPort”: 8443,
“probe”: {
“id”: “[variables(‘myLb8443ProbeId’)]”

If you want something more cut and paste friendly, have a look here:

Troubleshooting Azure deployment template for OpenShift

Out of trouble Posted on 2017-02-07 13:14:13

Hi all,

If you are trying out to deploy OpenShift on Azure using instructions here:

..And you got errors doing that. Here’s how to debug the deployment process. It’s easy to type the wrong this. Try to keep to just copy-and-pasting if you are using the template in the Azure Portal. Trust me 🙂

1. Click on the resource group you’ve created.

2. Click on your deployment. It should say “1 Deploying” (or 2)

3. Click on “Microsoft Template”

4. Scroll down to “Operations details”

5. Find the resource which does not state “OK” or “Created”. Should be marked in red and state something like “Conflict” or “Error”.

6. Find out what went wrong. In this example, it’s a custom script which failed to run.

7. Logon to the server affected and follow the below debug flow:

[root@ocpmaster ~]# cd /var/lib/waagent/custom-script/download/
[root@ocpmaster download]# ls
0 1
[root@ocpmaster download]# ls */
0/: stderr stdout

1/: stderr stdout
[root@ocpmaster download]# cd 1
[root@ocpmaster 1]# tail stderr
Adding password for user mglantz
error: A server URL must be specified
[root@ocpmaster 1]#

8. Issue found.

DNS issue with OCP 3.3 deployment to Azure

Out of trouble Posted on 2017-01-04 01:38:15

* This was a DNS issue in Azure which has been resolved.

If you are deploying OpenShift to Azure using Harold Wongs deployment templates, I just stumbled into an issue where deployOpenShift would fail to trigger a successful Ansible run, due to problems with DNS resolution. I worked around this temporarily by adding the infra and node names to /etc/hosts together with their internal IPs (which you find in the Azure Portal if you goto a virtual machine and click on it’s network interface).

Will try to find out why this happens..

More info to follow here:

Red Hat Satellite 6.2.2 Pulp sync results in Error 500

Out of trouble Posted on 2016-11-02 10:43:09

If you, when you click on Content > Sync status, get an error message, and when you look at /var/log/foreman/production.log, see the below error message:

2016-11-01 19:20:52 [katello/pulp_rest] [E] “https://sat6.FQDN/pulp/api/v2/repositories/search/“, 1613 byte(s) length, “Accept”=>”*/*; q=0.5, application/xml”, “Accept-Encoding”=>”gzip, deflate”, “Content-Length”=>”1613”, “accept”=>”application/json”, “content_type”=>”application/json”
| \n# => 500 InternalServerError | text/html 531 bytes
2016-11-01 19:20:52 [app] [I] Completed 500 Internal Server Error in 1047ms
2016-11-01 19:20:52 [app] [F]
| RestClient::InternalServerError (500 Internal Server Error):
| katello ( app/models/katello/glue/pulp/repos.rb:53:in `prepopulate!’
| katello ( app/helpers/katello/sync_management_helper.rb:38:in `collect_repos’
| katello ( app/controllers/katello/sync_management_controller.rb:27:in `index’
| app/controllers/concerns/application_shared.rb:13:in `set_timezone’
| lib/middleware/catch_json_parse_errors.rb:9:in `call’

Then, perhaps, the pulp database did not upgrade properly when you upgraded pulp at some point. Try:

(Running as root)
# usermod -s /bin/bash apache
# su – apache

(Running as apache)
$ pulp-db-migrate
$ exit

(Running as root)

# usermod -s /bin/false apache
# katello-service restart


Red Hat Satellite 6.2.2 Registering client gives 500 Internal Server Errror

Out of trouble Posted on 2016-10-13 15:07:18

If you at registration of new servers encounter 500 Internal Server Error on a newly installed Red Hat Satellite 6.2.2. Like such:

[foreman-tasks/action] [E] 500 Internal Server Error (RestClient::InternalServerError)

Try running:

katello-service restart

And try again.

Satellite 6.1.7 and SCAP

Out of trouble Posted on 2016-02-20 20:11:25

If you’re trying to setup SCAP with Red Hat Satellite 6.1.7 and encounter below error message on your client when running ‘puppet agent -t’:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Unknown function pick at /etc/puppet/environments/KT_Default_Organization_Library_CONTENTVIEW_2/modules/foreman_scap_client/manifests/params.pp:2

Then the issue is that you have to add the ‘puppetlabs/stdlib’ module to your content view/host.

That was all.

KS-tree and initial sync of repos in Satellite 6

Out of trouble Posted on 2016-02-20 12:18:07

If you cancel a synchronization the first time you sync one of your RHEL repositories and leave it as ‘pending’, Satellite 6 will not properly create the default ‘Installation Media’ when you sync your kickstart tree. So, if you have a problem with installation media not getting created, even though you synced it successfully, check so that you do not have some previous reposync that is ‘pending’.

Monitoring Puppet Forge sync on Satellite 6.1.7

Out of trouble Posted on 2016-02-18 15:29:22

If you sync in Puppet Forge into Satellite 6.1, you may think that it’s not working properly. Looking at the task progress, it states 0%. Looking in Sync Status, it says something like:

‘Total module count: 3970.’

..but no progress indicated.

This is a bug, there are actually plenty of stuff happening. You can track the status by doing a grep in /var/log/messages on your satellite server.

# watch ‘echo “Puppet modules synced in so far: $(grep “pulp: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1):” /var/log/messages|wc -l)”‘

Puppet modules synced in so far: 1247

Sync time, on my VM with 8GB RAM and limited CPU was ~1-1,5 modules / second. So, approx. 1 hour to sync in all modules in Puppet Forge.

Next »