Bug 2218821 - Hammer accepts non-existent LCE in host update
Summary: Hammer accepts non-existent LCE in host update
Keywords:
Status: POST
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.14.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Lucy Fu
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-30 07:26 UTC by Vladimír Sedmík
Modified: 2023-08-17 00:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36667 0 Normal New Hammer accepts non-existent LCE in host update 2023-08-09 22:05:24 UTC
Red Hat Issue Tracker SAT-18994 0 None None None 2023-07-17 13:22:18 UTC

Description Vladimír Sedmík 2023-06-30 07:26:37 UTC
Description of problem:
Hammer host update accepts non-existent LCE id and says 'Host updated.', but it's not.


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


How reproducible:
always


Steps to Reproduce:
1. Have a host registered to the Satellite
2. Run `hammer host update --id <host_id> --lifecycle-environment-id 999999`


Actual results:
[root@sat ~]# hammer host update --id 24 --lifecycle-environment-id 999999
Host updated.


Expected results:
Should fail with proper message (like "LCE does not exist", "LCE is not assigned to the content source", etc.)

Comment 3 Lucy Fu 2023-08-09 22:05:23 UTC
Created redmine issue https://projects.theforeman.org/issues/36667 from this bug

Comment 4 Bryan Kearney 2023-08-10 16:02:58 UTC
Upstream bug assigned to lufu

Comment 5 Bryan Kearney 2023-08-10 16:03:01 UTC
Upstream bug assigned to lufu

Comment 6 Bryan Kearney 2023-08-17 00:03:02 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36667 has been resolved.


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