Bug 1755518 - importing an image or a template from export domain results in a non indented fields yaml files
Summary: importing an image or a template from export domain results in a non indented...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.3.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.4.0
: ---
Assignee: Liran Rotenberg
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-25 15:47 UTC by exploit
Modified: 2020-05-20 20:03 UTC (History)
5 users (show)

Fixed In Version: rhv-4.4.0-30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-20 20:03:24 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 107761 0 master MERGED core: escape new lines within OVF 2020-11-16 16:29:44 UTC

Description exploit 2019-09-25 15:47:27 UTC
Description of problem:
after importing an image from an export domain, ssh keys field or custom scripts of the cloud-init tab are no more indented, and cloud-init ignores them when booting a vm.

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


How reproducible:
import an image from export domain
look at the cloud-init tab and see that ssh key or custom scripts are not yaml indented anyore

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Sandro Bonazzola 2020-04-09 08:22:23 UTC
This bug is in modified for ovirt-4.4.3, can we re-target to ovirt-4.4.0 and move to QE?

Comment 2 Nisim Simsolo 2020-04-27 12:46:03 UTC
Verified:
ovirt-engine-4.4.0-0.33.master.el8ev
qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64
vdsm-4.40.13-1.el8ev.x86_64
libvirt-daemon-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64

Verification scenario:
1. Import sealed RHEL8 VM from templates.
2. Edit VM -> initial run and add the next yaml (don't run the VM afterward):
write_files:
- content: test_cloud_init
  path: /tmp/test.txt
  permissions: '0644'
runcmd:
 - [ systemctl, restart, network]
3. Export VM to export domain.
4. Delete source VM.
5. Import VM from export domain.
6. Edit imported VM and verify cloud-init script is still there and not in one line (with spaces and new lines)
7. Run VM and verify:
- Network service has been restarted 
- A file with permissions 0644 named test.txt was created under /tmp/ folder
  The content of the file is test_cloud_init

Comment 3 Sandro Bonazzola 2020-05-20 20:03:24 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.