Bug 1478420
Summary: | [Satellite 6] in foreman db hosts table, lifecycle_environment_id and content_view_id are not updated. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Stefan Nemeth <snemeth> |
Component: | Hosts - Content | Assignee: | Brad Buckingham <bbuckingham> |
Status: | CLOSED ERRATA | QA Contact: | Nikhil Kathole <nkathole> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2.10 | CC: | bbuckingham, inecas, jcallaha, nkathole |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-katello-3.4.5 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:51:07 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: |
Description
Stefan Nemeth
2017-08-04 14:11:01 UTC
Created redmine issue http://projects.theforeman.org/issues/20581 from this bug Upstream bug assigned to bbuckingham This appears to be working properly on internal Satellite 6.3 SNAP 14 : satellite-6.3.0-17.0.beta.el7sat.noarch, tfm-rubygem-katello-3.4.5-1.el7sat.noarch For a content host, changed the lifecycle environment and content view several times using the UI and in each case, it was updated correctly in the database. With satellite 6.3, the database table and attributes to monitor are: select content_view_id,lifecycle_environment_id from katello_content_facets; Moving the bugzilla forward for inclusion in next round of ON_QA. VERIFIED Version Tested: Satellite-6.3 Snap 15 # rpm -qa| grep tfm-rubygem-katello tfm-rubygem-katello_ostree-3.4.5.1-1.el7sat.noarch tfm-rubygem-katello-3.4.5.1-1.el7sat.noarch steps: # hammer lifecycle-environment list ---|---------|-------- ID | NAME | PRIOR ---|---------|-------- 2 | DEV | Library 1 | Library | 4 | PROD | QE 3 | QE | DEV ---|---------|-------- # hammer content-view list ----------------|---------------------------|---------------------------|-----------|---------------------|--------------- CONTENT VIEW ID | NAME | LABEL | COMPOSITE | LAST PUBLISHED | REPOSITORY IDS ----------------|---------------------------|---------------------------|-----------|---------------------|--------------- 4 | Capsule RHEL 7 CV | Capsule_RHEL_7_CV | | 2017/09/10 07:58:21 | 6, 3, 7 1 | Default Organization View | Default_Organization_View | | 2017/09/10 06:11:00 | 3 | RHEL 6 CV | RHEL_6_CV | | 2017/09/10 07:46:36 | 2, 4, 5 2 | RHEL 7 CV | RHEL_7_CV | | 2017/09/10 07:39:35 | 6, 1, 3 ----------------|---------------------------|---------------------------|-----------|---------------------|------------ # hammer host info --id 2 | grep "Lifecycle Environment\|Content View" Content View: RHEL 7 CV Lifecycle Environment: DEV foreman=# select content_view_id,lifecycle_environment_id from katello_content_facets; content_view_id | lifecycle_environment_id -----------------+-------------------------- 2 | 2 (1 row) # hammer host update --id=2 --content-view="RHEL 6 CV" Host updated foreman=# select content_view_id,lifecycle_environment_id from katello_content_facets; content_view_id | lifecycle_environment_id -----------------+-------------------------- 3 | 2 (1 row) # hammer host update --id=2 --lifecycle-environment="QE" Host updated foreman=# select content_view_id,lifecycle_environment_id from katello_content_facets; content_view_id | lifecycle_environment_id -----------------+-------------------------- 3 | 3 # hammer host update --id=2 --lifecycle-environment="DEV" --content-view="RHEL 7 CV" Host updated foreman=# select content_view_id,lifecycle_environment_id from katello_content_facets; content_view_id | lifecycle_environment_id -----------------+-------------------------- 2 | 2 (1 row) Successfully updates entries in database. 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/RHSA-2018:0336
|