lua-rover issue faced while enabling support for power(ppc64le) architecture about apicast

[tkan145]

Hi, it looks like you don't have rover installed in your image. What command did you use to build the runtime image?

For development image, you will need to run make dev-build IMAGE_NAME=quay.io/3scale/apicast-ci:openresty-X.Y.Z-{release_number}, then reference that image inside docker-compose-devel.yml

image: ${IMAGE:-quay.io/3scale/apicast-ci:openresty-1.19.3-23}

NOTE: you will need to modify Makefile to build for ppc64le. The default is linux/amd64

dev-build: ## Build development image
   $(DOCKER) build --platform linux/amd64 -t $(IMAGE_NAME) \
      --build-arg OPENRESTY_RPM_VERSION=$(OPENRESTY_RPM_VERSION) \
      --build-arg LUAROCKS_VERSION=$(LUAROCKS_VERSION) \
      $(PROJECT_PATH) -f $(DEVEL_DOCKERFILE)

[shubham-bhagwat0]

hi,
we tried to build it further and we are facing the jaegertracing issue

jaegertracing issue:

• not initially supported by power
• but it can be built and integrated as a custom build for ppc64le arch
• tried building and integrating it, ends up failing one of the test cases
• and it is also deprecated and no longer being maintained

custom jaeger build leads to the following error :

460.9 Running tests...
460.9 Test project /tmp/jaeger-client-cpp/build
460.9     Start 1: UnitTest
463.0 1/2 Test #1: UnitTest .........................***Failed    2.04 sec
463.0     Start 2: DynamicallyLoadTracerTest
463.0 2/2 Test #2: DynamicallyLoadTracerTest ........   Passed    0.01 sec
463.0
463.0 50% tests passed, 1 tests failed out of 2
463.0
463.0 Total Test time (real) =   2.05 sec
463.0
463.0 The following tests FAILED:
463.0 Errors while running CTest
463.0 Output from these tests are in: /tmp/jaeger-client-cpp/build/Testing/Temporary/LastTest.log
463.0 Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
463.0     1 - UnitTest (Failed)
463.0 make: *** [Makefile:71: test] Error 8
------
Dockerfile.devel:39
--------------------
  38 |          gcc-c++ #jaegertracing-cpp-client-${JAEGERTRACING_CPP_CLIENT_RPM_VERSION}
  39 | >>> RUN git clone https://github.com/jaegertracing/jaeger-client-cpp.git \
  40 | >>> && cd jaeger-client-cpp \
  41 | >>> && mkdir build \
  42 | >>> && cd build \
  43 | >>> && cmake .. \
  44 | >>> && make \
  45 | >>> && make test \
  46 | >>> && make install
  47 |     RUN ln -sf /dev/stdout /usr/local/openresty/nginx/logs/access.log \
--------------------
ERROR: failed to solve: process "/bin/sh -c git clone https://github.com/jaegertracing/jaeger-client-cpp.git && cd jaeger-client-cpp && mkdir build && cd build && cmake .. && make && make test && make install" did not complete successfully: exit code: 2
make: *** [Makefile:76: dev-build] Error 1

alternatively:

• the community has already suggested to use opentelemetry
• plus we've noticed the use of openresty-opentelemetry
• so should we just replace jaegertracing with opentelemetry??

[tkan145]

Hi,

This test doesn't look like APIcast test suite so I can't comment on what's wrong with it. But if I had to guess, I think your jaeger-client-cpp is not built correctly, thus leading to failed DynamicallyLoadTracerTest

Regarding jaegertracing, it will depend on your use case, but you are right, we are gradually moving to opentelemetry and keeping support jaegertracing mainly for those who have not yet migrated to opentelemetry. However, we will eventually remove jaegertracing in a future release.