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

Online Boutique demo deployed with px CLI in CrashLoopBackOff #689

Closed
bpschmitt opened this issue Jan 12, 2023 · 2 comments
Closed

Online Boutique demo deployed with px CLI in CrashLoopBackOff #689

bpschmitt opened this issue Jan 12, 2023 · 2 comments
Assignees

Comments

@bpschmitt
Copy link

Describe the bug

Two services in the Online Boutique demo deployed using px demo deploy px-online-boutique are in CrashLoopBackOff with the following errors:

emailservice

Profiler enabled.
Tracing enabled.
Debugger enabled.
{"severity":"info","time":1673536345440,"pid":1,"hostname":"currencyservice-5c7f7b6ddf-hxzh2","name":"currencyservice-server","message":"Starting gRPC server on port 7000...","v":1}
(node:1) [changeLevelName_deprecation] Warning: The changeLevelName option is deprecated and will be removed in v7. Use levelKey instead.
(Use `node --trace-warnings ...` to show where the warning was created)
{"severity":"info","time":1673536345539,"pid":1,"hostname":"currencyservice-5c7f7b6ddf-hxzh2","name":"currencyservice-server","message":"CurrencyService gRPC server started on port 7000","v":1}
/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:120
        throw new Error('Project ID must be specified in the configuration');
              ^

Error: Project ID must be specified in the configuration
    at initConfigMetadata (/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:120:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createProfiler (/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:158:26)
    at async Object.start (/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:182:22)

paymentservice

Profiler enabled.
Tracing enabled.
Debugger enabled.
(node:1) [changeLevelName_deprecation] Warning: The changeLevelName option is deprecated and will be removed in v7. Use levelKey instead.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1) [changeLevelName_deprecation] Warning: The changeLevelName option is deprecated and will be removed in v7. Use levelKey instead.
{"severity":"info","time":1673536399035,"pid":1,"hostname":"paymentservice-6d9b7cc6bf-kqjlc","name":"paymentservice-server","message":"PaymentService gRPC server started on port 50051","v":1}
/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:120
        throw new Error('Project ID must be specified in the configuration');
              ^

Error: Project ID must be specified in the configuration
    at initConfigMetadata (/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:120:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createProfiler (/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:158:26)
    at async Object.start (/usr/src/app/node_modules/@google-cloud/profiler/build/src/index.js:182:22)

To Reproduce

  1. px demo deploy px-online-boutique

Expected behavior

All pods should be in a Running state.

Screenshots
If applicable, add screenshots to help explain your problem. Please make sure the screenshot does not contain any sensitive information such as API keys or access tokens.

Logs

Attached.

App information (please complete the following information):

  • Pixie version: pem_image:0.12.10
  • K8s cluster version: v1.22.16-eks-ffeb93d
  • Node Kernel version: 5.4.226-129.415.amzn2.x86_64
  • Browser version: N/A

Additional context
Add any other context about the problem here.

@htroisi htroisi self-assigned this Jan 12, 2023
@htroisi
Copy link
Contributor

htroisi commented Jan 12, 2023

It looks like this bug was fixed in GoogleCloudPlatform/microservices-demo#665. We should update our fork and see if this fixes things on EKS.

@htroisi
Copy link
Contributor

htroisi commented Jan 12, 2023

The workaround is to uncomment all of the DISABLE_* env vars in https://github.com/pixie-io/pixie/blob/main/demos/online-boutique/online-boutique.yaml, then apply the file manually:

# Delete existing demo app
px demo delete px-online-boutique

# Manually deploy modified demo yaml
kubectl create ns px-online-boutique
kubectl apply -f online-boutique.yaml -n px-online-boutique

This was tested on EKS and it does resolve the issue.

RagalahariP pushed a commit to RagalahariP/pixie that referenced this issue Feb 15, 2023
Summary:
Fixes pixie-io#689.

The `px-online-boutique` demo app attempts to connect to GCP integrations. This causes problems when deployed on non-GCP clusters. This diff turns off GCP integrations by default for the demo app. This change has already been addressed upstream in GCP's repo, but at this time we do not want to update our fork of the repo. Upstream fix: GoogleCloudPlatform/microservices-demo#665

Test Plan: Manually deploy modified yaml file on GCP and EKS cluster.

Reviewers: michelle

Reviewed By: michelle

Signed-off-by: Hannah Troisi <htroisi@pixielabs.ai>

Differential Revision: https://phab.corp.pixielabs.ai/D12773

GitOrigin-RevId: cc6645c78a19e33af4ee9bb70b4995ee1125850d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants