Created attachment 1280324 [details] The Compute resource profile form fail to load template data when choosing a template Description of problem: The Compute resource RHEV profile form fail to load template data when choosing a template Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Goto Infrastructure > Compute resources 2. Create a RHEV compute resource 3. Select the created compute resource 4. Select Compute profiles 5. Select a profile a compute resource profile form now is opened 6. select a template Actual results: Template configuration data is not fully loaded, loading data process does not finish Expected results: Template configuration data loaded successfully, UI show the template configuration data (memory cores network interfaces storage) Additional info:
Version-Release number of selected component (if applicable): * candlepin-2.0.30-1.el7.noarch * candlepin-selinux-2.0.30-1.el7.noarch * foreman-1.15.0-0.1.RC2.el7sat.noarch * foreman-compute-1.15.0-0.1.RC2.el7sat.noarch * foreman-debug-1.15.0-0.1.RC2.el7sat.noarch * foreman-ec2-1.15.0-0.1.RC2.el7sat.noarch * foreman-gce-1.15.0-0.1.RC2.el7sat.noarch * foreman-installer-1.15.0-0.develop.201703100324gitb570b53.el7sat.noarch * foreman-installer-katello-3.5.0-1.nightly.201703312206git730de81.el7sat.noarch * foreman-libvirt-1.15.0-0.1.RC2.el7sat.noarch * foreman-openstack-1.15.0-0.1.RC2.el7sat.noarch * foreman-ovirt-1.15.0-0.1.RC2.el7sat.noarch * foreman-postgresql-1.15.0-0.1.RC2.el7sat.noarch * foreman-proxy-1.15.0-0.1.RC2.el7sat.noarch * foreman-rackspace-1.15.0-0.1.RC2.el7sat.noarch * foreman-selinux-1.15.0-0.1.RC2.el7sat.noarch * foreman-vmware-1.15.0-0.1.RC2.el7sat.noarch * katello-3.4.0-1.rc2.el7sat.noarch * katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-1.noarch * katello-certs-tools-2.4.0-1.el7sat.noarch * katello-client-bootstrap-1.3.0-1.el7sat.noarch * katello-common-3.4.0-1.rc2.el7sat.noarch * katello-debug-3.4.0-1.rc2.el7sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-base-3.5.0-1.nightly.201703312206git730de81.el7sat.noarch * katello-selinux-3.0.2-1.el7sat.noarch * katello-server-ca-1.0-1.noarch * katello-service-3.4.0-1.rc2.el7sat.noarch * openldap-2.4.40-13.el7.x86_64 * pulp-client-1.0-1.noarch * pulp-docker-plugins-2.3.0-1.git.0.02c948c.el7sat.noarch * pulp-katello-1.0.2-1.el7sat.noarch * pulp-puppet-plugins-2.12.1-1.git.0.1aeb10f.el7sat.noarch * pulp-puppet-tools-2.12.1-1.git.0.1aeb10f.el7sat.noarch * pulp-rpm-plugins-2.12.1-1.el7sat.noarch * pulp-selinux-2.12.1-1.git.0.b41b7ba.el7sat.noarch * pulp-server-2.12.1-1.git.0.b41b7ba.el7sat.noarch * python-ldap-2.4.15-2.el7.x86_64 * tfm-rubygem-ldap_fluff-0.4.6-1.el7sat.noarch * tfm-rubygem-net-ldap-0.15.0-1.el7sat.noarch
Created attachment 1280325 [details] foreman-debug output
Please note that under 6.2.9 this is working as expected
Created redmine issue http://projects.theforeman.org/issues/20134 from this bug
Upstream bug assigned to orabin
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20134 has been resolved.
*** Bug 1466648 has been marked as a duplicate of this bug. ***
VERIFIED Version Tested: Satellite-6.3 Snap 12 Steps: 1. Navigated to Infrastructure -> Compute resources 2. Created RHEV compute resource 3. Selected compute profile 4. Selected template 5. Template configuration data loaded successfully showing cores, network, storage and also spinner in UI stops.( See attachment )
Created attachment 1317412 [details] screenshot of UI
The memory is not loaded from the template look at that value from your screenshot (that template has 1 GB or 1024 MB of RAM), this cause the host provisioning to fail. To work around this we have to visit Virtual Machine tab at host creation stage and correct that value. Suggest to to revert this bug status to ASSIGNED
Thanks Djebran. Early selecting template keeps spinner active and Memory Value always resets 1 GB as per comment #10. So while verifying this, it missed. Moving this bug to assigned as this causes the problem while host provisioning.
As per discussion on IRC, the issue of memory value should track separately. We are tracking this here https://bugzilla.redhat.com/show_bug.cgi?id=1520382. So moving this to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0336