oracle / oracle/oracle-database-operator
2.2.0: Edition is Unavailable for standby SIDB according to get singleinstancedatabase output
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 192
- Forks
- 69
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 1
Description
$ kubectl -n oracle-database get singleinstancedatabase
NAME EDITION STATUS ROLE VERSION CONNECT STR TCPS CONNECT STR OEM EXPRESS URL
sidb1 Enterprise Healthy PRIMARY 23.26.3.0.0 sidb1.oracle-database:1521/ORCL1 Not enabled Unavailable
sidb2 Unavailable Healthy PHYSICAL_STANDBY 23.26.3.0.0 sidb2.oracle-database:1521/ORCL2 Not enabled Unavailable
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 by tracing how the SingleInstanceDatabase status is assembled for a PHYSICAL_STANDBY, using the kubectl output in the issue as the reproduction. Check existing reconciliation or status tests if available, then verify that a healthy standby reports its database edition instead of Unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100