[Bug]: When executing `./tools/deploy/obd.sh deploy -c /data/obcluster.yaml`, it keeps in the "connect observer" state
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 342
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Describe the bug
When executing ./tools/deploy/obd.sh deploy -c /data/obcluster.yaml, it keeps in the "connect observer" state
Environment
-
OS Version and CPU Arch(
uname -a): -
OB Version(
LD_LIBRARY_PATH=../lib:$LD_LIBRARY_PATH ./observer -V): -
Hardware resource(
cpu core/memory size/disk hardware):
Fast Reproduce Steps(Required)
Steps to reproduce the behavior:
Expected behavior
Actual Behavior
Additional context
bootstrap failure
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tools/deploy/obd.sh and reproduce the deploy command using /data/obcluster.yaml, then inspect where the process remains in the "connect observer" state. Check the bootstrap failure shown in the attached output and collect the missing environment and reproduction details; done means identifying and fixing the deployment failure so observer connects successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- database, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100