microsoft / microsoft/PowerPlatformConnectors

[BUG] Paconn return error when updating connector (validation is oassed, paconn create works)

Open
#3,891 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Custom Connector

Name of Connector

QA connector

Describe the bug

We have a long-running QA connector that we use for testing before production.

paconn validate is successful
paconn create with the same files is successful.

Currently, we are not able to update the existing connector with the following error:

{
"error": {
"code": "ApiHubsRequestFailed",
"message": "The request failed with client error: '{"Code":"","Message":"PUT https://power-apim-msmanaged-na.management.azure-api.net/subscriptions/{{{}}}/resourceGroups/apim-power-msmanaged-na/providers/Microsoft.ApiManagement/service/power-apim-msmanaged-na/apis/{{{}}}-5faab51c8679aa4010-5f8a0d23e493320210/policy?api-version=2019-01-01 failed with InternalServerError, content={\"error\":{\"code\":\"InternalServerError\",\"message\":\"Request processing failed due to internal error.\",\"details\":null}}","Target":null,"Details":[],"Innererror":null}'. The correlation Id is '{{{}}}'.",
"details": [
{
"code": "FullNonLocalizedError",
"message": "{"Code":"","Message":"PUT https://power-apim-msmanaged-na.management.azure-api.net/subscriptions/{{{}}}/resourceGroups/apim-power-msmanaged-na/providers/Microsoft.ApiManagement/service/power-apim-msmanaged-na/apis/{{{}}}-5faab51c8679aa4010-5f8a0d23e493320210/policy?api-version=2019-01-01 failed with InternalServerError, content={\"error\":{\"code\":\"InternalServerError\",\"message\":\"Request processing failed due to internal error.\",\"details\":null}}","Target":null,"Details":[],"Innererror":null}"
}
]
}
}
400 Client Error: Bad Request for url: https://api.powerapps.com/providers/Microsoft.PowerApps/apis/shared_{{{}}}-5faab51c8679aa4010-5f8a0d23e493320210?api-version=2016-11-01&%24filter=environment%20eq%20%27Default-637a2d98-ac73-4698-aa2d-24ec7d560f05%27

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

run paconn update

Expected behavior

paconn uopdate updates the connector

Environment summary

Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)

Additional context

no context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing paconn update with the same connector files and compare its behavior with the successful paconn validate and paconn create commands. Inspect the failing PUT request and the reported 400 response; done means the existing connector updates successfully and the failure is covered by an appropriate regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
api, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.