Bug 1409809

Summary:

Compute Resource Network settings ignored

Product:

Red Hat Satellite

Reporter:

Ade Bradshaw <abradshaw>

Component:

Compute Resources

Assignee:

satellite6-bugs <satellite6-bugs>

Status:

CLOSED DUPLICATE

QA Contact:

Severity:

medium

Docs Contact:

Priority:

medium

Version:

6.2.6

CC:

abradshaw, bbuckingham, jcallaha, mhulan, oprazak, szadok

Target Milestone:

Unspecified

Keywords:

Triaged

Target Release:

Unused

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2017-03-06 15:06:49 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Interface settings not pulled from compute resource	none
Compute profile	none
New host - using the profile	none
Interface screenshot	none

Description Ade Bradshaw 2017-01-03 13:47:58 UTC

Description of problem:
When deploying via a compute resource, via a compute profile, settings from the profile are ignored for the network


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


How reproducible:
100%

Steps to Reproduce:
1.Create a compute resource (vmware or ovirt)
2.Create a compute profile and set the network to something other than ovirtmgmt)
3.create a New Host and select the profile created
4.Check the interface settings - name and network are ignored

Actual results:
Name and Network are ignored (not taken from the compute profile)

Expected results:
Name and network would come from the compute profile

Additional info:
See attachments

Comment 1 Ade Bradshaw 2017-01-03 13:48:34 UTC

Created attachment 1236899 [details]
Compute profile

Comment 2 Ade Bradshaw 2017-01-03 13:49:07 UTC

Created attachment 1236900 [details]
New host - using the profile

Comment 3 Ade Bradshaw 2017-01-03 13:50:03 UTC

Created attachment 1236901 [details]
Interface screenshot

Comment 6 Marek Hulan 2017-03-06 15:06:49 UTC

Thanks for the report. I'm sorry I couldn't get to this sooner. I think this is a duplicate of BZ 1322047 therefore I'm closing it. If you think I misunderstood this BZ or it's a separate issue, please let me know or reopen this. Otherwise I kindly ask you to watch BZ 1322047 for the progress, there's already a patch that should solve it.

*** This bug has been marked as a duplicate of bug 1322047 ***