OpenShift Nexus Pod failed to Start During the CI/CD Pipeline Deployment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
Resource limit problem. | |||
=Explanation= | |||
The nexus pod would attempt to start and then would be immediately be terminated during the [[OpenShift_CI/CD_Operations#Set_Up_a_Jenkins_CI.2FCD_Pipeline|CI/CD Pipeline setup procedure]]. No useful error messages. | The nexus pod would attempt to start and then would be immediately be terminated during the [[OpenShift_CI/CD_Operations#Set_Up_a_Jenkins_CI.2FCD_Pipeline|CI/CD Pipeline setup procedure]]. No useful error messages. |
Revision as of 20:13, 1 November 2017
Internal
Overview
Resource limit problem.
Explanation
The nexus pod would attempt to start and then would be immediately be terminated during the CI/CD Pipeline setup procedure. No useful error messages.
Got it to start by editing the deployment configuration and requesting less memory.
oc edit dc/nexus
spec: template: metadata: spec: containers: - image: ... name: nexus resource: limits: cpu: memory: 1636Mi
Editing the deployment configuration triggered a successful redeployment.