[WORKAROUND] The CK RPMS are not building in metacontent provider

To workaround this issue, the regular content provider is used and hardcoded images are used for deploying CK
ref: openstack-k8s-operators#720 (comment)

Author: elfiesmelfie

ci/cloudkitty-post_deploy.yml

@@ -50,9 +50,11 @@
               ceilometerService: CeilometerPassword
               cloudKittyService: CloudKittyPassword
             cloudKittyAPI:
-              containerImage: "{{ cloudkitty_api_image }}"
+              # containerImage: "{{ cloudkitty_api_image }}"
+              containerImage: "quay.io/efoley/cloudkitty-api"
             cloudKittyProc:
-              containerImage: "{{ cloudkitty_proc_image }}"
+              # containerImage: "{{ cloudkitty_proc_image }}"
+              containerImage: "quay.io/efoley/cloudkitty-processor"
             preserveJobs: true
             databaseAccount: cloudkitty
             databaseInstance: openstack

zuul.d/projects.yaml

@@ -162,7 +162,12 @@
     github-check:
       #debug: true
       jobs:
-        - telemetry-operator-multinode-cloudkitty
+        - telemetry-operator-multinode-cloudkitty:
+            dependencies:
+              - openstack-k8s-operators-content-provider
+          # temperorily use the regular content provider since CK rpm builds are failing
+        - openstack-k8s-operators-content-provider
+          # Keep the metacontent provider in the pipeline so we know when it is working again
         - telemetry-openstack-meta-content-provider-master
         #- telemetry-operator-multinode-default-telemetry
         #- functional-tests-osp18: &fvt_jobs_config