The monasca-grafana image is currently failing to build.
INFO:kolla.common.utils.monasca-grafana:go install -v ./pkg/cmd/grafana-server
INFO:kolla.common.utils.monasca-grafana:[91mgo: cannot find main module, but found vendor/vendor.json in /grafana/src/github.com/grafana/grafana
INFO:kolla.common.utils.monasca-grafana: to create a module there, run:
INFO:kolla.common.utils.monasca-grafana: go mod init
Let's unblock the gate and diagnose asynchronously.
Change-Id: Id113a53c083d105ac9200474ff20faacef6decaf
Rabbitmq requires Erlang 22.3+ while Ubuntu/aarch64 has 22.2 one.
There is no interest in using Ubuntu/aarch64 images so there is no sense
in keeping always failing CI job.
Change-Id: Ia45f01be6724ee60d5993b2ae73648a278fbf6e6
healthcheck_socket script requires lsof to check pids of processes
using that socket - that's needed for octavia-driver-agent healthchecks
in Kolla-Ansible.
Change-Id: I0f14c0f67fd81f13c58f231f800829ad759cc54c
Current rabbitmq requires erlang v22.3+ while we had v22.1 on aarch64.
On x86-64 we use upstream repo so have both v22 and v23.
On AArch64 we use Linaro backports repo so have v23.2
Change-Id: I21c3a0e423235301269d0a5b212d0ce6970ab88f
Nova looks into /usr/share/qemu/firmware/ directory. We need 2020.05
version of firmware package for it.
ERROR: nova.exception.InternalError: Failed to locate firmware descriptor files
Change-Id: I546bcf910e886eb75ece62f6be382fe1187efb32
There are several images installing 'python3-libvirt' package. Which for
Debian reside in 'libvirt' repo. So let's enable it where needed.
Change-Id: I1c91d27f2578f5ca7c83c4747725b1d9371880b0
We moved to CentOS Stream 8. Just no one noticed that binary target was
failing to build.
This change sorts out all failing images.
Change-Id: Ia7768caabfe214a629339d50973d0d9873fc65d5
Part of changes discussed during Kolla Kalls.
These make our documentation easier to digest.
Changes in conf.py are to avoid warnings from sphinx.
Change-Id: I76ab6786b271963252278fcf12f1a28cab520fdb
This is the first part in deploying octavia-api with apache (needs to
run as root).
Related-Bug: #1874228
Change-Id: I96c57032f206e47d74de07f874f8944b7a433fd0
We use official CentOS 8 Stream image as a base.
So far Stream does not have own SIG repos
RDO Wallaby packages will be built against Stream
Kolla CI jobs are renamed to centos8s. Kolla-Ansible ones will follow
in later patch.
Change-Id: Ibb23c9d0caf115fcbba7bd322ecebe8d80b6821a
Upgrade to the latest ELK OSS release. Due to the licensing change, this
effectively pins us to 7.10.x which is supported until 2022-05-11 [1].
This patch also takes advantage of the ARM artifacts which have
been kindly provided since the 7.8.0 release [2].
[1] https://www.elastic.co/support/eol
[2] https://www.elastic.co/blog/elasticsearch-on-arm
Change-Id: Icfa3db5788b25f70ee75411dbaf20d8d4a6a734b
This reverts commit 61def281d077f88051d1b1a14dfdbfabac036c8c.
Reason for revert: --location was already in curlrc and it was unified in change I46b77978926fc2b578a68d1aaa944b2198af0685
Change-Id: I066d747400ede30037ff324ad55430af7c35dc18
Deprecates support for Prometheus v1.x.
In Xena support for this image will be removed from Kolla.
Change-Id: I31a8c675323f367a2d59bfb31644ee5b4b44e3f2
-L for curl: If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place
It fixes build error for me:
INFO:kolla.common.utils.prometheus-v2-server: ---> Running in 693fd4095c77
INFO:kolla.common.utils.prometheus-v2-server:curl (https://github.com/prometheus/prometheus/releases/download/v2.23.0/prometheus-2.23.0.linux-amd64.tar.gz): response: 302, time: 0.166583, size: 640
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:gzip: stdin: not in gzip format
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:tar: Child returned status 1
INFO:kolla.common.utils.prometheus-v2-server:tar: Error is not recoverable: exiting now
Change-Id: I095ca6f34cc7c7bca485e9ec019cc52aeb8e3ff4
1. stop pinning networking-hyperv
Pike release was long time ago so maybe it is time to unpin it?
commit 6dc8e978462fd08122133e273ae956721997d3af
Author: Dan Ardelean <dardelean@cloudbasesolutions.com>
Date: Mon Aug 28 12:56:25 2017 +0300
Change networking-hyperv version for Pike
2. stop install vmware-nsxlib as a plugin
vmware-nsx is a plugin and we install it already
vmware-nsxlib can be fetched from Pypi
Solves:
INFO:kolla.common.utils.neutron-server:The conflict is caused by:
INFO:kolla.common.utils.neutron-server: The user requested vmware-nsxlib 15.0.8.dev129 (from /plugins/vmware-nsxlib-15.0.8.dev129)
INFO:kolla.common.utils.neutron-server: vmware-nsx 15.0.1.dev424 depends on vmware-nsxlib>=17.0.0
Change-Id: I6ef344d463333e5cdc3a0850c8e068218779fdbd
To better utilise caches during the working week, we decided to publish
only weekly (as opposed to daily). This is due to DockerHub-imposed
limits.
If published images are broken, or need to be refreshed, then this patch
can be temporarily reverted.
Change-Id: I3916b703e40f0b80c47501ff7faa958b903be05c
User may provide own base image but it needs to be supported one. If it
is not then we print info and error out.
So provide user with info which release is present in their image.
Change-Id: I0d8417fdeb2f02138d03cc57bd3b7b95bc43fc8f
