Bug 2169636

Summary:	Build host reported_at status not updated correctly when you rebuild the host
Product:	Red Hat Satellite	Reporter:	Nagoor Shaik <nshaik>
Component:	Hosts	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	pnovotny
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Nagoor Shaik 2023-02-14 07:11:53 UTC

Description of problem:
When you build a host initially the build status is updated correctly, however if you rebuild the same host again then build reported_at status stays the original build time. Ideally it should be overridden with a new value.

All other host status such as Insights, Configuration, Subscription, Errata are updated correctly as per the specified run time.

Version-Release number of selected component (if applicable):
Satellite 6.13

How reproducible:
100%

Steps to Reproduce:
1. Provision a Host 
2. After sometime rebuild the host
3. Once the rebuild is complete, check the Host Status i.e. Icon next to Hostname click on it to see the latest reported data. All data except "Build" shows correctly, the "Build" reported_at value still shows the initial build time of the host.

Actual results:
Incorrect build reported_at time when you rebuild a host.

Expected results:
Build reported_at time stamp should be updated as the other status of the Host statuses are reporting correctly.

Additional info:

Comment 1 Brad Buckingham 2023-02-16 15:30:55 UTC

Is this a regression from 6.12?  Thanks!

Comment 2 Nagoor Shaik 2023-02-17 06:24:27 UTC

Hello Brad,

Just tested this on 6.12 as well, the same problem exists.