Bug 759854

Summary: MySQL-zrm-2.2.0-2.el6.noarch.rpm
Product: [Fedora] Fedora EPEL Reporter: Jörg Woll <auftrag>
Component: MySQL-zrmAssignee: Orion Poplawski <orion>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: el6CC: orion
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: MySQL-zrm-2.2.0-3.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-10 21:21:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jörg Woll 2011-12-04 11:39:16 UTC
On Dec.01 MySQL-zrm was updated from 2.2.0-1 to 2.2.0-2.
The Instruction:

"/usr/bin/zrm-pre-scheduler --action backup --backup-set dailyrun --backup-level 0 --interval daily"

brings the following error message :

pre-schedule:INFO: ZRM for MySQL Community Edition - version 2.2.0
Logging to /var/log/mysql-zrm/zrm-pre-scheduler.log
Unknown Parameters 

USAGE:
/usr/bin/mysql-zrm-scheduler
		--add           To add a mysql-zrm schedule entry
		--query         To query existing mysql-zrm schedule entry
		--delete        To delete an mysql-zrm schedule entry
		  Use --start to delete entry with specific start time
		--interval <interval>   Default: weekly
		  valid value: daily, weekly or monthly
		--start-time <start-time>    e.g: 15:30 [start at 3:30pm]
		--day-of-week <day> e.g: 0 to start on Sunday, 1-3 to start on Mon, Tue and Wed.
		--day-of-month <day> e.g: 1 to start on first day of the month,
			10-13 to start on the 10th, 11th, 12th and 13th day of the month.
		--backup-level <level> Full(0) or incremental(1)
		--backup-set <backupSet name> 
		--now           To start mysql-zrm now
		--help

a rebuild from src.rpm without the Patch 
MySQL-zrm-2.2.0-quiet.patch
and the parameter --action  functioned
The Function --action in mysql-zrm-scheduler was not found, and MySQL-backups without funtion.

Comment 1 Fedora Update System 2011-12-04 17:28:17 UTC
MySQL-zrm-2.2.0-3.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/MySQL-zrm-2.2.0-3.el6

Comment 2 Fedora Update System 2011-12-04 20:00:03 UTC
Package MySQL-zrm-2.2.0-3.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing MySQL-zrm-2.2.0-3.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2011-5155/MySQL-zrm-2.2.0-3.el6
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-12-10 21:21:06 UTC
MySQL-zrm-2.2.0-3.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.