[Question] If new versionset is being added, I notice the first deployment fails. The second one normally succeeds.

Open
#697 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, csharp
Domain
api, devops

Research direction

Start by reproducing the deployment after creating a new API version set, using the reported Azure API Management validation error as the reference. Trace the deployment and version-set handling in the repository to determine why the first iteration uses a conflicting path. Done means a newly created version set deploys successfully on the first attempt, with the existing reproduction covered by an appropriate test if one is available.

Written by the indexing model from the issue text.

Description

Release version

5.1.4

Question Details

Throws this error: failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"path","message":"Cannot create API '-v2' with the same Path '/api' as API '***' unless it's a part of the same version set"}]}}'.

Expected behavior

For the deploy to succeed on the first iteration.

Actual behavior

Fails for the first deploy. Succeeds on the second.

Reproduction Steps

Create a new version set for an api.

Dominant language
C#
Stars
448
Forks
247
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.