-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
echo 2.40.0 SIGSEGV error when enabling pubsub on Spinnaker 1.33.0 #6924
Comments
When manually modify the image to version 2.39.0 |
Slack chat here: https://spinnakerteam.slack.com/archives/C091CCWRJ/p1706171672331629 The issue is with alpine image: https://github.com/spinnaker/echo/blob/master/Dockerfile.java11.slim#L1
Thre are 2 solutions:
|
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:
|
+1 same issue with upgrade to 1.34.2, reverted back to 1.32.3
|
@spinnakerbot remove-label stale |
Issue Summary:
I tried to upgrading Spinnaker to version 1.33.0 using spinnaker-operator. However,
spin-echo
pod fail to start. I have narrowed down the issue to be with pubsub. Whenever I disable pubsub configuration on the spinnakerservice.yaml file, echo-scheduler can start successfully. But when I enable pubsub, it fails with error belowThis is my current pubsub config:
Note:
echo-scheduler 2.37.1
, the pusub config above doesn’t throw any errorecho-scheduler at 2.40.0
, it has the errorecho-scheduler
andecho-worker
both face same errorCloud Provider(s):
GCP/GKE
Environment:
I'm running Spinnaker in a GKE cluster. Deployment is using spinnaker-operator.
Storage is GCS and redis.
Feature Area:
Description:
I want to upgrade Spinnaker to version 1.33.0 but
echo-scheduler 2.40.0
fail to start.Steps to Reproduce:
Additional Details:
The text was updated successfully, but these errors were encountered: