Skip to content

Instantly share code, notes, and snippets.

---
- name: set parameters for test
hosts: localhost
tasks:
- set_fact:
emptydict: {}
- set_fact:
junkdict: {'foo':'bar'}
#!/bin/bash
set -euxo pipefail
if ! type -p hub > /dev/null 2>&1 ; then
echo ERROR: you must use the \"hub\" command line tool
echo for interacting with github
echo see https://github.com/github/hub
echo e.g. on Fedora - dnf -y install hub
exit 1
+ pushd /home/fedora/go/src/github.com/openshift/cluster-logging-operator
+ make image
/home/fedora/go/bin/imagebuilder
++ dirname hack/build-image.sh
...
+ repodir=/home/fedora/openshift-clusters/cluster.1570643004/repos
+ mountarg='-mount /home/fedora/openshift-clusters/cluster.1570643004/repos:/etc/yum.repos.d/'
+ echo building image quay.io/openshift/origin-cluster-logging-operator:latest - this may take a few minutes until you see any output . . .
building image quay.io/openshift/origin-cluster-logging-operator:latest - this may take a few minutes until you see any output . . .
+ imagebuilder -mount /home/fedora/openshift-clusters/cluster.1570643004/repos:/etc/yum.repos.d/ -t quay.io/openshift/origin-cluster-logging-operator:latest .
build/local-test-repo/
└── org
└── elasticsearch
└── distribution
└── zip
└── elasticsearch-oss
├── 6.7.1
│ ├── elasticsearch-oss-6.7.1.pom
│ ├── elasticsearch-oss-6.7.1.pom.md5
│ ├── elasticsearch-oss-6.7.1.pom.sha1
Make a working directory for holding your copies of various configmaps used by Fluentd. You will use this directory for subsequent steps below. The steps below assume the current directory is this directory:
mkdir working_dir
cd working_dir
Make sure you are in the logging project. This will be openshift-logging:
oc project openshift-logging
Make a copy of the current logging-fluentd configmap:
volumes:
hostPath:
path: /var/lib/elasticsearch
apiVersion: v1
kind: Secret
metadata:
name: marketplacesecret
namespace: openshift-marketplace
type: Opaque
stringData:
token: "basic xxxxxxxxxxxxxxxxxxxxxxxxx"
apiVersion: operators.coreos.com/v1
kind: OperatorSource
metadata:
creationTimestamp: 2019-05-16T21:51:14Z
finalizers:
- finalizer.operatorsources.operators.coreos.com
generation: 4
name: art-applications
namespace: openshift-marketplace
resourceVersion: "56863"
After moving the elasticsearch-operator to the namespace openshift-operators-redhat, the elasticsearch-operator deployment is not created in that namespace. Steps: https://github.com/richm/origin-aggregated-logging/commit/2b2a57ba7dc7c19a8466d327fc92120302018814
Create namespace openshift-operators-redhat
Create operatorgroup openshift-operators-redhat in that namespace with targetNamespace openshift-logging
Create namespace openshift-logging
Create operatorgroup openshift-logging in that namespace with targetNamespace openshift-logging
E0328 23:50:45.735510 1 queueinformer_operator.go:177] Sync "openshift-logging" failed: {cluster-logging preview {cluster-logging openshift-logging}} not found: CatalogSource {cluster-logging openshift-logging} not found
time="2019-03-28T23:50:45Z" level=info msg="building connection to registry" currentSource="{cluster-logging openshift-logging}" id=x9c9j source=cluster-loggin
time="2019-03-28T23:50:45Z" level=info msg="client hasn't yet become healthy, attempt a health check" currentSource="{cluster-logging openshift-logging}" id=x9c9j source=cluster-logging
E0328 23:50:47.403089 1 queueinformer_operator.go:177] Sync "openshift-logging" failed: {cluster-logging preview {cluster-logging openshift-logging}} not found: CatalogSource {cluster-logging openshift-logging} not found
E0328 23:51:05.127228 1 queueinformer_operator.go:177] Sync "openshift-logging" failed: {cluster-logging preview {cluster-logging openshift-logging}} not found: CatalogSource {cluster-logging openshift-logging} not