Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ods-infra components require OpenShift projects in Deploy stage #1047

Closed
hrcornejo opened this issue Oct 23, 2023 · 0 comments · Fixed by #1071
Closed

ods-infra components require OpenShift projects in Deploy stage #1047

hrcornejo opened this issue Oct 23, 2023 · 0 comments · Fixed by #1071
Labels
bug Something isn't working

Comments

@hrcornejo
Copy link
Contributor

hrcornejo commented Oct 23, 2023

Describe the bug
Using a component of type od-infra the Deploy stage in orchestration try to verify that the project exists in OpenShift. An infra component doesn't need a project in Openshift.

To Reproduce
Steps to reproduce the behavior:

  1. Create an ods-infra component in a new project (only -dev and -test projects has been created by default in OpenShift.
  2. Create a Release Manager component and configure properly to use the ods-infra component.
  3. Do a release to Prod environment.
  4. See error.

Expected behavior
The Release work without the creation of a project in OpenShift.

Log Output (ensure to remove any confidential information like tokens, project names, etc.

java.lang.RuntimeException: Error: target environment 'fake-prod' does not exist in [https://172.30.0.1:443](https://172.30.0.1/).
	at org.ods.orchestration.DeployStage.run(DeployStage.groovy:116)
	at org.ods.orchestration.Stage.runOnAgentPod(Stage.groovy:210)
	at ___cps.transform___(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
	at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.constructorCall(DefaultInvoker.java:25)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:100)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:85)
	at jdk.internal.reflect.GeneratedMethodAccessor332.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant