Bug 1361619 - v3 API | The link to activate a vm's disk is broken
Summary: v3 API | The link to activate a vm's disk is broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.0.2
: 4.0.2.2
Assignee: Juan Hernández
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-29 14:22 UTC by Raz Tamir
Modified: 2016-08-12 14:24 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-12 14:24:33 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.0.z+
rule-engine: blocker+
rule-engine: planning_ack+
juan.hernandez: devel_ack+
ratamir: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 61695 0 ovirt-engine-4.0 MERGED restapi: Fix typo in disk activate link 2016-07-29 14:55:43 UTC
oVirt gerrit 61700 0 ovirt-engine-4.0 MERGED restapi: Fix typo in disk activate link 2016-07-31 08:22:21 UTC
oVirt gerrit 61701 0 ovirt-engine-4.0.2 MERGED restapi: Fix typo in disk activate link 2016-07-31 04:51:58 UTC

Description Raz Tamir 2016-07-29 14:22:13 UTC 
Description of problem:
The action name to activate a vm's disk is wrongly spelled:
api/v3/vms/{vm:id}/disks/{disk:id}/acivate

It 'acivate' instead of 'activate'

* No logs needed

Version-Release number of selected component (if applicable):
ovirt-engine-4.0.2-0.1.rc.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Red Hat Bugzilla Rules Engine 2016-07-29 14:26:48 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 2 Lukas Svaty 2016-08-01 09:37:02 UTC 
verified in ovirt-engine-restapi-4.0.2.3-0.1.el7ev.noarch
Note You need to log in before you can comment on or make changes to this bug.