Bug 1624020 - Content View is not updated on Content Host when change is made via Hosts / All Hosts <Edit option>
Summary: Content View is not updated on Content Host when change is made via Hosts / A...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.3.0
Hardware: All
OS: All
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
: 1638216 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-30 16:54 UTC by Mike McCune
Modified: 2021-12-10 17:14 UTC (History)
17 users (show)

Fixed In Version: tfm-rubygem-foreman-tasks-0.9.6.8-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1566825
Environment:
Last Closed: 2018-10-11 15:18:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 23837 0 High Closed Content View is not updated on Content Host when change is made via Hosts / All Hosts <Edit option> 2020-10-14 09:04:52 UTC
Red Hat Product Errata RHBA-2018:2915 0 None None None 2018-10-11 15:18:44 UTC

Comment 4 Patrick Creech 2018-09-05 14:11:50 UTC
Andrew,

This failed cherrypick, can you take a look?

Comment 7 Andrew Kofink 2018-09-10 14:02:39 UTC
I've tried to reproduce this bug on Satellite 6.3.3, and the content host is properly updated when the content view or lifecycle environment is changed, and the Host::Update task is properly run. This BZ appears to be fixed in 6.3.3.

Comment 8 Patrick Creech 2018-09-10 18:03:56 UTC
Moving to ON_QA as per https://bugzilla.redhat.com/show_bug.cgi?id=1624020#c7 this appears to be resolved in 6.3.3 or earlier

Comment 11 Peter Ondrejka 2018-09-13 14:53:02 UTC
Verified on 6.3.4 content hosts got correctly updated after changing the CV for host in the ui

Comment 13 errata-xmlrpc 2018-10-11 15:18:07 UTC
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-2018:2915

Comment 14 Nagoor Shaik 2018-10-15 09:32:08 UTC
*** Bug 1638216 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.