Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A api-tests
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • NFV - Network Functions Virtualisation
  • api-tests
  • Issues
  • #82

Closed
Open
Created Jun 18, 2019 by Elian Kraja@krajaMaintainer

ETag should not be checked on PATCH Operations

In the PATCH operations, it should be avoided the check of the ETag, since the operation will be asynchronous. In fact, a 202 Accepted is returned and as reported in the spec (Table 5.4.3.3.4-2 of SOL003): The request was accepted for processing, but the processing has not been completed.

FILE: SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking