Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Aggregate profile in OpenShift mode does not use openshift.yml

See original GitHub issue

Description

I use aggregate profile to pull in configurations of different modules for integration testing. Tests run on openshift and openshift profile is picked up correctly. However, after upgrade to FMP 4.0.0 aggregate profile started using kubernetes.yml instead of openshift.yml from the dependency jars. My FMP setup: https://github.com/snowdrop/spring-boot-messaging-work-queue-booster/blob/sb-2.1.x-upgrade-fmp-to-4.0.0/tests/pom.xml#L75

Info

f-m-p version : 4.0.0
Maven version (mvn -v) : 3.3.9
Kubernetes / OpenShift setup and version :

OpenShift Master: v3.11.0+06cfa24-67
Kubernetes Master: v1.11.0+d4cacc0
OpenShift Web Console: v3.11.0+ea42280
oc: v3.11.0+0cbc58b

If it’s a bug, how to reproduce :

git clone https://github.com/snowdrop/spring-boot-messaging-work-queue-booster -b sb-2.1.x-upgrade-fmp-to-4.0.0
cd spring-boot-messaging-work-queue-booster
./mvnw clean verify -Popenshift,openshift-it

Issue Analytics

State:
Created 4 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

rohanKanojiacommented, Apr 12, 2019

@Ladicek @gytis : yeah, sorry. It has got delayed a bit. I would try to do it as soon as I can.

1reaction

Ladicekcommented, Apr 12, 2019

It was “within a week” 9 days ago 😉 https://github.com/fabric8io/fabric8-maven-plugin/issues/1607#issuecomment-479440910

For now, we stayed on 4.0.0-M2 in those 2 or 3 boosters that used aggregation.

Top Results From Across the Web

Aggregating Container Logs | Configuring Clusters

Fluentd splits logs between the main cluster and a cluster reserved for operations logs, which consists of the logs from the projects default,...

Post-installation configuration OpenShift Container Platform 4.8

Configure storage: By default, containers operate using ephemeral storage or transient local storage. The ephemeral storage has a lifetime limitation.

OpenShift Container Platform 4.11 Post-installation configuration

fips: Enable FIPS mode. FIPS should be set at installation-time setting and not a post- installation procedure. IMPORTANT. The use of FIPS ...

Post-installation configuration OpenShift Container Platform 4.6

If a node is being cordoned, that node is not included in the ... myconfig.yaml to apply a machine config, you could remove...

Networking OpenShift Container Platform 4.7

If not set, the default value is based on the apiservers.config.openshift.io/cluster resource. When using the Old , Intermediate , and Modern profile types, ......