Description of problem: When adding glance image as a template on the PPC platform. On X86 works fine. Versions: 4.0.0 3.6.7 and probably older. How reproducible: Add glance image repository and import image as a template. Steps to Reproduce: 1. Add glance external provider 2. Storage tab -> select added glance 3. Select image -> Click on Import 4. Check Import as Template and click on OK Actual results: Disk is created but no template appear Expected results: created template, and disk which should be attached to this template.
Please attach logs, this issue can be either storage or virt and we need more data to figure out in which team field of expertise the issue lies
Closing, until logs are supplied. Note that severity was missing as well - added 'Low' (this is not supported, but for the benefit of QE I'm OK with understanding why it did not work).
Created attachment 1164081 [details] Engine, vdsm, supervdsm logs These logs are from our rhev environment 3.6.7-1. Logs are from the time when I started adding glance external provider. Is it enough or do you need logs from 4.0? Thanks, Petr
Michal, seems like it's your turf: 2016-06-02 15:44:34,987 WARN [org.ovirt.engine.core.bll.AddVmTemplateCommand] (org.ovirt.thread.pool-6-thread-26) [7399c012] CanDoAction of action 'AddVmTemplate' failed for user admin@internal. Reasons: VAR__ACTION__ADD,VAR__TYPE__VM_TEMPLATE,ACTION_TYPE_FAILED_ILLEGAL_VM_DISPLAY_TYPE_IS_NOT_SUPPORTED_BY_OS
(In reply to Tal Nisan from comment #4) Nope, that's import from glance, nothing wrong with templates;-) AFAICT you're using Blank template for filling up the defaults, but e.g. display settings in Blank(qxl/spice) are not valid for ppc64le, so it fails and I would say it never worked.
flags were wrong and it got acked by bot by mistake. This is a 4.0 bug which is fixed in latest 4.0.
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA