Bug 1697524 - retirement date of service ignored
Summary: retirement date of service ignored
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.10.1
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: 5.10.5
Assignee: Yuri Rudman
QA Contact: Niyaz Akhtar Ansari
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1704905
TreeView+ depends on / blocked
 
Reported: 2019-04-08 15:08 UTC by Felix Dewaleyne
Modified: 2023-03-24 14:42 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-17 12:01:55 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Felix Dewaleyne 2019-04-08 15:08:32 UTC
Description of problem:
With the database of this customer imported, the retirement date seems ignored and the scheduler seems to never pick up service retirements. 

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

How reproducible:
only with customer database

Steps to Reproduce:
1.import database provided from customer
2.schedule a service retirement
3.

Actual results:

The object in rails has the correct retirement date, as well as the UI.  It looks like schedueler's never picking them up for some reason.

You can see the MiqScheduleWorker constantly having at least 1 task to do, I'm assuming it's the retirement one that never gets done:
[----] I, [2019-04-05T21:37:32.727426 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.
[----] I, [2019-04-05T21:37:47.760242 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.
[----] I, [2019-04-05T21:38:02.795093 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.
[----] I, [2019-04-05T21:38:17.828415 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 4.
[----] I, [2019-04-05T21:38:32.905761 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.
[----] I, [2019-04-05T21:38:47.939209 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.
[----] I, [2019-04-05T21:39:02.971040 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.
[----] I, [2019-04-05T21:39:18.005472 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 4.
[----] I, [2019-04-05T21:39:33.085085 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.
[----] I, [2019-04-05T21:39:48.118580 #16940:716f60]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 1.


Expected results:
retirement runs as expected and usual

Additional info:
persists updated to 5.10.1

Comment 5 Yuri Rudman 2019-04-17 18:28:25 UTC
PR to fix error during retirement check when user id is present but actual user removed: https://github.com/ManageIQ/manageiq/pull/18483

Comment 22 drew uhlmann 2019-07-22 10:40:45 UTC
Hey Yuri, yeah to your question in comment 19, looks like the same issue to me.


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