-
Story
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
-
-
-
Very Likely
-
0
Currently it's hard to debug the issue relating with openshift-maven-plugin because we can not exactly trace what kind of oc commands with resource data were executed.
For example, this is a sample ERROR log.
[INFO] oc: Using OpenShift at https://xxx.xxx.xxx.xxx in namespace sample with manifest xxx\target\classes\META-INF\jkube\openshift.yml [INFO] oc: OpenShift platform detected [INFO] oc: Updating Service from openshift.yml [ERROR] oc: Failed to update Service from openshift.yml. io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: PATCH at: https://xxx.xxx.xxx.xxx:xxx/api/v1/namespaces/demo/services/demo. Message: the server rejected our request due to an error in our request. Received status: Status -skip-
If there is an option to log executed oc commands with resources used, we can compare the OK/NG jsondata quickly and also openshift support engineer can understand what is going on easily.
Openshift-maven-plugin is still used by other full-support product(ex. CSB), so please consider about this feature request.
- clones
-
ENTESB-20477 Debug option for openshift-maven-plugin to log executed oc commands with resources used
-
- Closed
-
1.
|
Productization |
|
Closed | |
Unassigned |
2.
|
Development |
|
Closed | |
Unassigned |
3.
|
Test |
|
Closed | |
Marco Carletti |
4.
|
Documentation |
|
Closed | |
Unassigned |