Bug 1691485

Summary:

Restraint does not provide test version in result.xml

Product:

[Retired] Restraint

Reporter:

Miroslav Vadkerti <mvadkert>

Component:

general

Assignee:

Carol Bouchard <cbouchar>

Status:

CLOSED NEXTRELEASE

QA Contact:

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

0.1.39

CC:

asavkov, bpeck, breilly, cbeer, mastyk

Target Milestone:

0.1.45

Keywords:

Triaged

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Clones:

1762731 (view as bug list)

Environment:

Last Closed:

2020-02-05 16:29:14 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

1762731

Attachments:

Description	Flags
TriageandTestingRev2	none

Description Miroslav Vadkerti 2019-03-21 17:47:37 UTC

Description of problem:
Restraint does not provide the test version in job.xml. This is an inconvenience, as without this information it is not clear which test version was run.

Beaker provides this information.

Version-Release number of selected component (if applicable):
restraint-1.39

How reproducible:
100%

Steps to Reproduce:
1. run an rpm test via restraint

Actual results:
No test version in job.xml

Expected results:
Test version in job.xml

Additional info:
Example of restraint result.xml where version is missing: https://baseos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-openstack/24462/artifact/artifact-installation-baseosci-ci-openstack-24462-1/job.xml

Example of a result xml where version is provided (from beah): https://beaker.engineering.redhat.com/recipes/6638775.xml

Comment 1 Martin Styk 2019-10-03 07:20:37 UTC

Hello Carol,

Let me clarify the issue first.

Beah doesn't support this either, so you don't have to worry about it.
NVR is provided by Beaker. Our tasks library has all the required information to supply it into the JOB.

However, in this case, we are looking for a solution where we are using only restraint-client <---> restraintd.
The requestor would like to have NVR of the installed task(s) in the output(result) file.

This change shouldn't affect restraint behavior w/ Beaker at all.

Comment 3 Carol Bouchard 2019-10-15 12:50:27 UTC

Created attachment 1625977 [details]
TriageandTestingRev2

Updated Triage and testing document

Comment 6 Martin Styk 2020-02-05 16:29:26 UTC

Restraint 0.1.45 has been released.