Azure / Azure/azure-rest-api-specs

[BUG] giMinorVersions endpoint returns ResourceTypeRegistrationNotFound - API endpoint not implemented

Open
#40,800 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

### API Spec link

https://learn.microsoft.com/en-us/rest/api/oracle/gi-minor-versions/list-by-parent?view=rest-oracle-2025-09-01&tabs=HTTP

### API Spec version

2025-09-01

### Describe the bug

# GitHub Issue

## Title
`giMinorVersions` endpoint returns ResourceTypeRegistrationNotFound - API endpoint not implemented

---

## Issue Description

### Summary
The documented REST API endpoint for listing GI Minor Versions by parent CloudVmCluster returns a `ResourceTypeRegistrationNotFound` error, indicating the endpoint is not implemented despite being present in the official Microsoft Learn documentation.

### Documentation Reference
https://learn.microsoft.com/en-us/rest/api/oracle/gi-minor-versions/list-by-parent?view=rest-oracle-2025-09-01

### Expected Behavior
According to the documentation, the following endpoint should return a list of available GI (Grid Infrastructure) minor versions for a CloudVmCluster:

```
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Oracle.Database/cloudVmClusters/{cloudVmClusterName}/giMinorVersions?api-version=2025-09-01
```

Expected response format:
```json
{
"value": [
{
"id": "string",
"name": "string",
"type": "string",
"properties": {
"version": "string"
}
}
]
}
```

4. Attempt to call the documented endpoint:
```bash
az rest --method get --url "https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Oracle.Database/cloudVmClusters/{cloudVmClusterName}/giMinorVersions?api-version=2025-09-01"
```

5. Observe the `ResourceTypeRegistrationNotFound` error

### API Versions Tested
Tested with multiple API versions, all returned the same error:
- `2023-09-01`
- `2024-06-01`
- `2025-01-01`
- `2025-09-01`

### Workaround
The GI version information is available directly from the parent CloudVmCluster resource:

```bash
az rest --method get --url "https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Oracle.Database/cloudVmClusters/{cloudVmClusterName}?api-version=2023-09-01" --query "properties.giVersion"
```

This returns the current GI version (e.g., `19.29.0.0.0`) from the cluster's properties.

### Impact
- Developers following the official documentation cannot retrieve GI minor versions using the documented endpoint
- Documentation is misleading and causes implementation delays
- Workaround requires knowledge that the information is available elsewhere

### Requested Action
1. Either implement the `giMinorVersions` child resource endpoint as documented
2. Or update the documentation to reflect that GI version information is available via the parent CloudVmCluster resource properties
3. Clarify whether the endpoint is planned for future implementation or if it should be removed from documentation

### Additional Context
The Oracle.Database provider appears to be functioning correctly for all other operations. The parent CloudVmCluster resource is accessible and returns complete information including `giVersion` and `systemVersion` properties.

### Expected behavior

According to the documentation, the following endpoint should return a list of available GI (Grid Infrastructure) minor versions for a CloudVmCluster:

```
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Oracle.Database/cloudVmClusters/{cloudVmClusterName}/giMinorVersions?api-version=2025-09-01
```

**Expected functionality:**
- The endpoint should be accessible after the `Oracle.Database` resource provider is successfully registered
- It should return HTTP 200 OK with a JSON response body
- The response should contain a list of available Grid Infrastructure minor versions that can be used for patching or upgrading the CloudVmCluster
- Each version entry should include the version number and relevant metadata
- The endpoint should follow standard Azure REST API conventions for list operations

**Expected response format:**
```json
{
"value": [
{
"id": "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Oracle.Database/cloudVmClusters/{cloudVmClusterName}/giMinorVersions/{versionName}",
"name": "{versionName}",
"type": "Oracle.Database/cloudVmClusters/giMinorVersions",
"properties": {
"version": "19.29.0.0.0"
}
}
]
}
```

**Expected HTTP status codes:**
- `200 OK` - Successful retrieval of GI minor versions
- `404 Not Found` - CloudVmCluster does not exist
- `401 Unauthorized` - Authentication failure
- `403 Forbidden` - Insufficient permissions

### Actual behavior

The endpoint returns a `ResourceTypeRegistrationNotFound` error:

```json
{
"error": {
"code": "ResourceTypeRegistrationNotFound",
"message": "The resource type registration 'Oracle.Database/cloudVmClusters/giMinorVersions' could not be found."
}
}
```

### Reproduction Steps

1. Ensure you have an active Azure subscription with Oracle Database CloudVmCluster resources
2. Verify the `Oracle.Database` provider is registered:
```bash
az provider show --namespace Oracle.Database --query "registrationState"
```
Result: `Registered`

3. Verify the CloudVmCluster exists:
```bash
az resource show --ids "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Oracle.Database/cloudVmClusters/{cloudVmClusterName}"
```
Result: Resource exists and is in `Available` state

### Environment

- **Date Tested**: February 26, 2026
- **Azure CLI Version**: Latest
- **Resource Type**: Oracle.Database/cloudVmClusters
- **Provider Registration State**: Registered
- **Test Cluster Location**: uksouth
- **Test Cluster State**: Available

Contributor guide

Open the contributing guide

Research direction

Start by comparing the documented giMinorVersions endpoint for API version 2025-09-01 with the Oracle.Database resource specification and reproduce it using the provided az rest command. Verify whether the provider exposes the child resource despite being registered. Done means the endpoint works as documented, or the documentation clearly reflects the supported CloudVmCluster giVersion workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.