Bug 1294338 - [webAdmin] VM initial run -> cloud-init section: Network & custom script are framed together
Summary: [webAdmin] VM initial run -> cloud-init section: Network & custom script are ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ovirt-4.1.0-beta
: ---
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-27 10:15 UTC by Ilanit Stein
Modified: 2019-04-28 08:36 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-14 15:36:31 UTC
oVirt Team: Virt
michal.skrivanek: ovirt-4.1?
rule-engine: planning_ack?
istein: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
cloud-init screenshot (34.69 KB, image/png)
2015-12-27 10:15 UTC, Ilanit Stein 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ilanit Stein 2015-12-27 10:15:16 UTC 
Created attachment 1109789 [details]
cloud-init screenshot

Description of problem:
In cloud-init section (via VM edit or VM run once),
network section is combined with custom script, though these 2 should be separate. It can be seen in the attached screen shot

Version-Release number of selected component (if applicable):
rhevm 3.6.1-4

How reproducible:
always

Expected results:
Frame should not wrap network & custom script together.
Comment 1 Red Hat Bugzilla Rules Engine 2016-01-10 11:54:28 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 2 Michal Skrivanek 2016-01-19 10:36:07 UTC 
it's not really impacting much. just cosmetic
Comment 3 Michal Skrivanek 2016-04-22 14:47:00 UTC 
pushed out due to capacity reasons
Comment 4 Tomas Jelinek 2016-12-14 15:36:31 UTC 
this frame is not present anymore so the issue can not happen anymore, closing.
Note You need to log in before you can comment on or make changes to this bug.