Red Hat Bugzilla – Bug 1321549
selecting template while creating compute profile should automatically populate network and storage
Last modified: 2016-07-27 05:29:15 EDT
Description of problem: selecting template while creating compute profile should automatically populate network and storage info associated to it. Version-Release number of selected component (if applicable): Sat62-snap5 How reproducible: Steps to Reproduce: 1. Add RHEV compute resource 2. Update or create a compute profile, by selecting a template. 3. Actual results: selecting template while creating compute profile does not automatically populate network and storage info associated to it. the UI shows up a spinner continuously. Expected results: selecting template while creating compute profile should automatically populate network and storage info associated to it. Additional info:
This works with Satellite6.1.8, so this is a regression with Satellite6.2
If "blank" Template is selected, we still cannot add "Network Interface" as it neither automatically populates nor do we have a button "Add Interface". Also note that a image was also created and the association made, as seen from the attachment.
it looks like part of this issue is already resolved at https://github.com/theforeman/foreman/commit/26eeda8011cf1c16be9446625b201c36ebe70751.
TESTED with sat62-snap6 I still face the same issue.
small correction, TESTED With sat62-snap6.2
Created redmine issue http://projects.theforeman.org/issues/14572 from this bug
The original patch was not connected to the original issue, so no surprise it didn't work. I opened PRs to fix two independent issues that caused this behavior not not work: https://github.com/theforeman/foreman/pull/3411 https://github.com/theforeman/foreman/pull/3412
Both PRs merged: not for cherry-picker: we need both PRs to fix this BZ
VERIFIED with sat62-snap8.1 selecting template while creating compute profile now automatically populates network and storage info associated to it.
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/RHBA-2016:1501