cloud-native-toolkit / cloud-native-toolkit/planning
Pipeline Error if we rerun
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 4
- Forks
- 1
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
**Describe the bug**
I tried to rerun the pipeline but am getting error whenever i rerun any pipeline run
**To Reproduce**
Click pipeline rerun and you will get this weird error
**Expected behavior**
expected pipeline to relaunch successfully
**Screenshots**

Refer (A) , (B) & (C) as it failed if i click rerun via (C)

**IBM Cloud**
Select the services and tools affected
- [ ] IBM Kubernetes Service Managed Service
- [ X] Red Hat OpenShift Managed Services
- [ ] Jenkins
- [ X] Tekton
- [ ] SonarQube
- [ ] Pact
- [ ] Artifactory
- [ ] IBM Image Registry
**Desktop (please complete the following information):**
- OS: [e.g. iOS] MAcOS
- Browser [e.g. chrome, safari] Firefox
- Version [e.g. 22] 62
**Additional context**
**Test Stage Logs
[test(5).log](https://github.com/ibm-garage-cloud/planning/files/4412170/test.5.log)
**
```
step-git-source-ocp4-aus-cp5-git-pn945
{"level":"info","ts":1585700285.7330852,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"}
{"level":"info","ts":1585700288.7598166,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"}
{"level":"info","ts":1585700290.4348805,"logger":"fallback-logger","caller":"git/git.go:102","msg":"Successfully cloned https://github.com/gsi-enablement-one/ocp4-aus-cp5.git @ master in path /workspace/source"}
{"level":"info","ts":1585700290.5253153,"logger":"fallback-logger","caller":"git/git.go:130","msg":"Successfully initialized and updated submodules in path /workspace/source"}
step-setup
{"level":"info","ts":1585700286.2064278,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"}
+ set +e
+ git fetch origin master --tags
From https://github.com/gsi-enablement-one/ocp4-aus-cp5
* branch master -> FETCH_HEAD
* [new tag] 0.0.1 -> 0.0.1
* [new tag] 0.0.2 -> 0.0.2
* [new branch] master -> origin/master
+ git checkout master
Already on 'master'
++ git describe --abbrev=0 --tags
+ echo IMAGE_VERSION=0.0.2
++ tr '[:upper:]' '[:lower:]'
++ sed s/_/-/g
+++ git config --get remote.origin.url
++ basename -s .git https://github.com/gsi-enablement-one/ocp4-aus-cp5.git
+ echo IMAGE_NAME=ocp4-aus-cp5
+ source ./env-config
++ IMAGE_VERSION=0.0.2
++ IMAGE_NAME=ocp4-aus-cp5
+ [[ -z 0.0.2 ]]
+ [[ -z ocp4-aus-cp5 ]]
step-deploy
{"level":"info","ts":1585700286.6762643,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"}
Initializing environment...
REGISTRY_URL: uk.icr.io
REGISTRY_NAMESPACE: gsi-cloudnative-squad
IMAGE_NAME: ocp4-aus-cp5
IMAGE_VERSION: 0.0.2
CHART_ROOT: ./chart
CHART: ./chart/base/Chart.yaml
CHART_NAME: base
Renaming chart from base to ocp4-aus-cp5
RELEASE_NAME: ocp4-aus-cp5
INITIALIZING helm with client-only (no Tiller)
Client: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
CHECKING CHART (lint)
==> Linting ./chart/ocp4-aus-cp5
[INFO] Chart.yaml: icon is recommended
1 chart(s) linted, no failures
global: {}
replicaCount: 1
logLevel: INFO
image:
repository: uk.icr.io/gsi-cloudnative-squad/ocp4-aus-cp5
tag: 0.0.2
pullPolicy: IfNotPresent
port: 9080
nameOverride: ocp4-aus-cp5
fullnameOverride: ocp4-aus-cp5
service:
type: ClusterIP
port: 80
route:
enabled: true
ingress:
enabled: false
appid:
enabled: false
requestType: web
namespaceInHost: true
subdomain: containers.appdomain.cloud
path: /
Generated release yaml for: dev-cp1/ocp4-aus-cp5
---
# Source: ocp4-aus-cp5/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
name: ocp4-aus-cp5
labels:
app.kubernetes.io/name: ocp4-aus-cp5
helm.sh/chart: ocp4-aus-cp5-0.0.2
app.kubernetes.io/instance: ocp4-aus-cp5
app: ocp4-aus-cp5
spec:
type: ClusterIP
ports:
- port: 80
targetPort: 9080
protocol: TCP
name: http
selector:
app.kubernetes.io/name: ocp4-aus-cp5
app.kubernetes.io/instance: ocp4-aus-cp5
---
# Source: ocp4-aus-cp5/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: ocp4-aus-cp5
labels:
app.kubernetes.io/name: ocp4-aus-cp5
helm.sh/chart: ocp4-aus-cp5-0.0.2
app.kubernetes.io/instance: ocp4-aus-cp5
app: ocp4-aus-cp5
spec:
replicas: 1
selector:
matchLabels:
app.kubernetes.io/name: ocp4-aus-cp5
app.kubernetes.io/instance: ocp4-aus-cp5
template:
metadata:
labels:
app.kubernetes.io/name: ocp4-aus-cp5
app.kubernetes.io/instance: ocp4-aus-cp5
spec:
containers:
- name: ocp4-aus-cp5
image: "uk.icr.io/gsi-cloudnative-squad/ocp4-aus-cp5:0.0.2"
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 9080
protocol: TCP
livenessProbe:
httpGet:
path: /
port: http
readinessProbe:
httpGet:
path: /
port: http
env:
- name: INGRESS_HOST
value: ""
- name: PROTOCOLS
value: ""
- name: LOG_LEVEL
value: "INFO"
resources:
null
---
# Source: ocp4-aus-cp5/templates/route.yaml
kind: Route
apiVersion: route.openshift.io/v1
metadata:
name: ocp4-aus-cp5
annotations:
argocd.argoproj.io/sync-options: Validate=false
spec:
to:
kind: Service
name: ocp4-aus-cp5
weight: 100
tls:
termination: edge
wildcardPolicy: None
---
# Source: ocp4-aus-cp5/templates/ingress.yaml
Deploying into: dev-cp1/ocp4-aus-cp5
service/ocp4-aus-cp5 created
deployment.apps/ocp4-aus-cp5 created
route.route.openshift.io/ocp4-aus-cp5 created
```
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Beginnen Sie mit der Aktion zum erneuten Ausführen der Pipeline und vergleichen Sie den fehlgeschlagenen erneuten Lauf mit der angehängten test(5).log, insbesondere die Einträge step-git-source-ocp4-aus-cp5, step-setup und step-deploy. Reproduzieren Sie den Fehler über die Pipeline-Oberfläche in Firefox und verfolgen Sie den gemeldeten Fehler durch den Ablauf zum erneuten Ausführen. Erledigt bedeutet, dass eine zuvor abgeschlossene Pipeline erfolgreich erneut ausgeführt werden kann.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git, helm, kubernetes
- Bereich
- ci-cd, devops
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100