Enabling existing volume-group replica fails without displayName value
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
Documentation for API and CLI shows volume-group replica information has optional displayName parameter. When I try with this:
oci bv volume-group update --volume-group-id ocid1.volumegroup.oc1.iad.m5lalixrxv2vvxofqanuwcljtbnkfddiaxpqrg2nduuxn2riw33b5paiom6a --volume-group-replicas '[{"availabilityDomain": "agJR:PHX-AD-2"}]'
Also fails with this:
oci bv volume-group update --volume-group-id ocid1.volumegroup.oc1.iad.m5lalixrxv2vvxofqanuwcljtbnkfddiaxpqrg2nduuxn2riw33b5paiom6a --volume-group-replicas '[{"availabilityDomain": "agJR:PHX-AD-2", "displayName": null}]'
Succeeds only if I provide a display-name
oci bv volume-group update --volume-group-id ocid1.volumegroup.oc1.iad.m5lalixrxv2vvxofqanuwcljtbnkfddiaxpqrg2nduuxn2riw33b5paiom6a --volume-group-replicas '[{"availabilityDomain": "agJR:PHX-AD-2", "displayName": "web01-vg"}]'
Version
3.20.0
Ref
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 reproducing the three oci bv volume-group update commands against the documented VolumeGroupReplicaDetails API behavior. Trace validation for the volume-group-replicas argument and determine whether the CLI or service rejects an omitted displayName; done means the documented optional form behaves consistently, with coverage for the failing command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100