Project

General

Profile

Actions

Bug #35834

closed

Setting a Content Source is not persistent

Added by Lucy Fu almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Hosts
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Description of problem:

Saving a Content Source appears to work but on reopening the Edit view the setting is blank.

If you set Lifecycle Environment and Content View, and then Content Source, the Media, Partition Table, and Root Password settings are lost and have to be reselected.

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

How reproducible:
Every time

Steps to Reproduce:
1. Create a host with the follow values:
make_fake_host( {
'organization-id': module_host_template.organization.id,
'architecture-id': module_host_template.architecture.id,
'domain-id': module_host_template.domain.id,
'location-id': module_host_template.location.id,
'medium-id': module_host_template.medium.id,
'operatingsystem-id': module_host_template.operatingsystem.id,
'partition-table-id': module_host_template.ptable.id,
}
2. Open the host for editing and select a Content Source, Submit to save the changes.
3. Open the host for editing and check the Content Source to see if the change persisted.
4. Select the Lifecycle Environment and Content View, and then Content Source. Try to submit the changes.

Actual results:
A change to the Content Source does not persist.
The Media, Partition Table, and Root Password settings are lost and have to be reselected.

Expected results:
A change to the Content Source does persist.
The Media, Partition Table, and Root Password settings are not lost.

Additional info:
Test is using fake capsules

Actions

Also available in: Atom PDF