Bug 1590010 - Database server hourly cron pointed at non-existent maintenance script upon migration from 4.5 to 4.6
Summary: Database server hourly cron pointed at non-existent maintenance script upon m...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.0
Assignee: Satoe Imaishi
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On:
Blocks: 1595269
TreeView+ depends on / blocked
 
Reported: 2018-06-11 20:21 UTC by David Luong
Modified: 2021-09-09 14:31 UTC (History)
10 users (show)

Fixed In Version: 5.10.0.21
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-11 18:49:13 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Luong 2018-06-11 20:21:26 UTC
Description of problem:
Database server hourly cron pointed at non-existent maintenance script upon migration from 4.5 to 4.6

Have not tested 5.8 minor update from when we change the location of database scripts, but should probably look into that as well.

Version-Release number of selected component (if applicable):
5.8.x (before db migration) to 5.9.x

How reproducible:
Always

Steps to Reproduce:
1.  Turn on DB maintenance scripts on 5.8
2.  Migrate from 5.8 to 5.9
3.  

Actual results:

The following shows up in mail after upgrade:

From root.redhat.com  Mon Jun 11 16:01:03 2018
Return-Path: <root>
X-Original-To: root
Delivered-To: root
Received: by example.com (Postfix, from userid 0)
	id 6DD5918581E0; Mon, 11 Jun 2018 16:01:03 -0400 (EDT)
From: "(Cron Daemon)" <root>
To: root.redhat.com
Subject: Cron <root@example> run-parts /etc/cron.hourly
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
Precedence: bulk
X-Cron-Env: <XDG_SESSION_ID=5>
X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/0>
X-Cron-Env: <LANG=en_US.UTF-8>
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20180611200103.6DD5918581E0>
Date: Mon, 11 Jun 2018 16:01:02 -0400 (EDT)

/etc/cron.hourly/miq-pg-maintenance-hourly.cron:

/etc/cron.hourly/miq-pg-maintenance-hourly.cron: line 2: /usr/bin/hourly_reindex_metrics_tables: No such file or directory
/etc/cron.hourly/miq-pg-maintenance-hourly.cron: line 3: /usr/bin/hourly_reindex_miq_queue_table: No such file or directory
/etc/cron.hourly/miq-pg-maintenance-hourly.cron: line 4: /usr/bin/hourly_reindex_miq_workers_table: No such file or directory

Expected results:
Crons are cleaned up/migrated/deleted

Additional info:
Was able to reproduce locally.

Comment 3 Nick Carboni 2018-06-12 15:14:20 UTC
These scripts were moved into the application in 5.9.2 as a fix for https://bugzilla.redhat.com/show_bug.cgi?id=1553795 so the messages should be harmless and the files can be removed manually.

As a fix for this bug we can check for their presence and remove them in the rpm post section.

Moving the version back to 5.9 because this is an issue with the 5.9 packages. Also, as this isn't actually causing any harm, I would say this should be medium priority at most.

Comment 4 Joe Rafaniello 2018-06-18 20:33:27 UTC
Moving back to general queue.  Workaround has been provided and this bug at this point is cleaning/preventing some harmless, although scary looking, messages.

Comment 6 Nick Carboni 2018-07-31 19:35:17 UTC
I'll look into removing those files in either a migration or as a part of the rpm cleanup step.

Comment 13 Sudhir Mallamprabhakara 2019-02-11 18:49:13 UTC
5.10 is now GA.. closing this.


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