Bug #20581
closedin foreman db hosts table, lifecycle_environment_id and content_view_id are not updated.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1478420
Description of problem:
When host gets assigned different lifecycle environment or content view, via hammer or webui, values in hosts table of foreman db are not updated.
Values gets updated properly in cp_pool and in katello_systems, but than there are different values for tested host in hosts and katello_systems and cp_pool (in candlepin db) tables
Version-Release number of selected component (if applicable):
6.2.10
How reproducible:
100%
Steps to Reproduce:
1. provision a host
2. check values in foreman database
foreman=# select content_view_id,lifecycle_environment_id from hosts where name='snemeth-hosttable-test.sysmgmt.lan';[ RECORD 1 ]-----------+--
content_view_id | 1
lifecycle_environment_id | 1
3.change lifecycle environment and content view in webui or using hammer
4. verify hosts table entry in db.
Actual results:
hosts table not updated
katello_systems and cp_pool updated as expected.
Expected results:
update hosts table as well.
Updated by Brad Buckingham over 7 years ago
- Subject changed from [Satellite 6] in foreman db hosts table, lifecycle_environment_id and content_view_id are not updated. to [Satellite 6] in foreman db hosts table, lifecycle_environment_id and content_view_id are not updated.
- Assignee set to John Mitsch
- Target version set to 208
Updated by Eric Helms over 7 years ago
- Status changed from New to Assigned
- Priority changed from Normal to High
- Translation missing: en.field_release set to 286
Updated by John Mitsch over 7 years ago
- Subject changed from [Satellite 6] in foreman db hosts table, lifecycle_environment_id and content_view_id are not updated. to in foreman db hosts table, lifecycle_environment_id and content_view_id are not updated.
Updated by Brad Buckingham over 7 years ago
- Target version changed from 208 to 213
Updated by Eric Helms over 7 years ago
- Translation missing: en.field_release changed from 286 to 295
Updated by Brad Buckingham over 7 years ago
- Status changed from New to Resolved
- Translation missing: en.field_release changed from 295 to 166
I tested this out on Katello master branch and it is no longer reproducable; therefore, going to close it out.