Description of problem:
setting a linux vm, with kernel options, wrong path, give error event that do not indicate problem is in the kernel options:
"VM test2 is down with error. Exit message: unable to set security context 'system_u:object_r:virt_content_t:s0' on 'aaa/aaa': No such file or directory."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Edit a running VM with kernel options wrong path, for example, aaa/aaa
2. power down the VM
3. Try to start the VM - should fail with the above error event.
Error should indicate problem is in kernel options field.
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know
this low prio bug didn't make it for 3.6 beta cutoff, moving to 4.0
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
(In reply to Michal Skrivanek from comment #2)
> this low prio bug didn't make it for 3.6 beta cutoff, moving to 4.0
Any chance for it for 4.0?
I think "No such file or directory" does give a hint
pushed out due to capacity reasons
It's being pushed since 3.5. I would say the "'aaa/aaa': No such file or directory." is an informative message. Closing this as wont fix. If you think this should be fixed, please feel free to reopen.