Red Hat Bugzilla – Bug 1320321
Updating content view of a managed host updates katello but not candlepin DB
Last modified: 2017-02-23 14:19:57 EST
Waiting on response from Pavel, have not been able to reproduce this issue in 6.1.8
(In reply to Christine Fouant from comment #1) > Waiting on response from Pavel, have not been able to reproduce this issue > in 6.1.8 See reproducer at https://bugzilla.redhat.com/show_bug.cgi?id=1314714#c8
Yes, the fields in the hosts forms were disabled. Thanks for confirming. Moving this to VERIFIED state. VERIFIED sat6.1.9 compose1 Ran the below script, before updating the cv or life-cycle env via the content-host. ./check_candle.sh xyz.redhat.com using name xyz.redhat.com uuid | name | environment_id | content_view_id --------------------------------------+-------------------------------------------------------------+----------------+----------------- baeff951-a1a6-4b51-a646-52559ba5c82e | xyz.redhat.com | 2 | 2 (1 row) uuid | name | environment_id --------------------------------------+-------------------------------------------------------------+---------------- baeff951-a1a6-4b51-a646-52559ba5c82e | xyz.redhat.com | 2-2 (1 row) ############# We are currently unable to update the hosts for content_view/life-cycle_environment, as the fields in the host forms were disabled. So updated it via the content-hosts and ran the script again, which shows the updated stuff appropriately. ############# [root@katello1 ~]# ./check_candle.sh xyz.redhat.com using name xyz.redhat.com uuid | name | environment_id | content_view_id --------------------------------------+-------------------------------------------------------------+----------------+----------------- baeff951-a1a6-4b51-a646-52559ba5c82e | xyz.redhat.com | 1 | 2 (1 row) uuid | name | environment_id --------------------------------------+-------------------------------------------------------------+---------------- baeff951-a1a6-4b51-a646-52559ba5c82e | xyz.redhat.com | 1-2 (1 row)
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:1084