Unable to deploy to an Opeshift 3.5 cluster using FMP 3.5.34
See original GitHub issueDescription
When running the integration tests of this project (which use Arquillian Cube) on an Openshift 3.5 cluster, I am getting the following error
java.lang.RuntimeException: io.fabric8.kubernetes.clnt.v3_1.KubernetesClientException: Failure executing: POST at: https://osemaster.spring-boot.osepool.centralci.eng.rdu2.redhat.com:8443/oapi/v1/namespaces/gandrian/deploymentconfigs. Message: DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1". Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1", metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}).
Caused by: io.fabric8.kubernetes.clnt.v3_1.KubernetesClientException: Failure executing: POST at: https://osemaster.spring-boot.osepool.centralci.eng.rdu2.redhat.com:8443/oapi/v1/namespaces/gandrian/deploymentconfigs. Message: DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1". Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1", metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={})
The odd things is that when I the tests are run on an Openshift 3.7 cluster, everything works as expected.
Furthermore, when I change the version of f-m-p to 3.5.30
everything works just fine on both Openshift 3.5 and 3.7
Info
- f-m-p version : 3.5.34
- Maven version (
mvn -v
) : 3.5.2
- Kubernetes / OpenShift setup and version : Openshift 3.5
- If it’s a bug, how to reproduce : Run
mvn clean verify -Popenshift,openshift-it
on the sb-1.5.10 branch of the aforementioned project: - Sample project : https://github.com/snowdrop/spring-boot-http-booster/tree/sb-1.5.10
Notes
You can easily switch versions of fmp in the sample project by setting the fabric8-maven-plugin.version
Maven property
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
OpenShift Java Console fails to open with v3.5.34 or higher
OpenShift Java Console fails to open when you mvn fabric8:deploy the following quickstart ( master branch), which uses version 3.5.34 of ...
Read more >Deploying Red Hat OpenShift Container Platform 3.5 on ...
The user must be able to create accounts, storage accounts, roles, ... An OpenShift Container Platform cluster is deployed with-in one Azure Region...
Read more >Installing Clusters | OpenShift Container Platform 3.11
To install a OpenShift Container Platform cluster, you run a series of Ansible playbooks. Running Ansible playbooks with the --tags or --check options...
Read more >Deploy a Spring Boot Application to OpenShift - Baeldung
First, we need to install Minishift, the local single-node Openshift cluster, and the Openshift client. Before using Minishift we need to ...
Read more >fabric8io/fabric8-maven-plugin
It will create a Kubernetes Deployment and a Service as resource objects ... Alternatively, when connected to an OpenShift cluster (or using ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@geoand
I don’t think we have a documentation for this. We need to start doing this. We need to create matrix table which should inform about a particular fmp version is compatible with following OpenShift or Kubernetes version.
FYR, Our documentation is here: https://maven.fabric8.io/
Thanks
Thanks @geoand