Hi! Did you read the discussion ``Q: crm shell's "migrate lifetime"''?
I wrote (28.09.2012 10:31:49): --- It seems it was my fault (due to the remarkable ISO syntax using 'M' for both, months and minutes): I never thought that somebody could specify months as a duration for migration, but "P5M" are 5 months, while "PT5M" are 5 minutes. --- I'm not saying I'm happy with the situation... Regards, Ulrich >>> Tomas Nunez <[email protected]> schrieb am 09.11.2012 um 10:06 in Nachricht <CAPFraJtUG0k_n7ucoXv=Pv=as6opFRe7xf=9wr5NB5=jx51...@mail.gmail.com>: > Hi! > > I've been using pacemaker for a while and I'm very happy with it. But now I > upgraded to 1.1.8 version, and installed crmsh, and migrating services is > now different. > > Until now I used the following syntax: > crm resource migrate <service> P30S > > The last part (P30S) was to disable this constraint 30 seconds later, so it > would be a temporary migration. I has worked fine since our first > installation until the upgrade. But now I can make no sense of the duration > of the constraints. Look: > > [root@server1 ]# date > dv nov 9 09:52:20 CET 2012 > [root@server1 ]# crm resource migrate service P30S > Migration will take effect until: *2012-11-09 08:00:3179Z* > WARNING: Creating rsc_location constraint 'cli-standby-service' with a > score of -INFINITY for resource service on server2. > This will prevent service from running on server2 until the > constraint is removed using the 'crm_resource -U' command or manually with > cibadmin > This will be the case even if server2 is the last node in the > cluster > This message can be disabled with -Q > [root@server1 ]# date > dv nov 9 *09:52:31* CET 2012 > [root@server1 ]# crm configure show|grep service > (...) > location cli-standby-service service \ > rule $id="cli-standby-rule-service" -inf: #uname eq server2 and > date lt "2012-11-09 08:00:3179Z" > > Well... It didn't went well. I wanted the constraint to be enabled for 30 > seconds, but it was valid almost two hours ago. The difference could be on > the time zone (I'm on UTC+1), but even the minutes don't match. How about > 30 minutes? > > [root@server1 ]# crm resource migrate service P30M > Migration will take effect until: *2015-05-09 08:00:3452Z* > WARNING: Creating rsc_location constraint 'cli-standby-service' with a > score of -INFINITY for resource service on server2. > This will prevent haproxy from running on server2 until the > constraint is removed using the 'crm_resource -U' command or manually with > cibadmin > This will be the case even if server2 is the last node in the > cluster > This message can be disabled with -Q > [root@server1 ]# date > dv nov 9 *09:57:58* CET 2012 > > And 1h30? > > [root@server1 ]# crm resource migrate service P1H30M > Migration will take effect until: *2015-05-09 09:00:3510Z* > WARNING: Creating rsc_location constraint 'cli-standby-service' with a > score of -INFINITY for resource service on server2. > This will prevent haproxy from running on server2 until the > constraint is removed using the 'crm_resource -U' command or manually with > cibadmin > This will be the case even if server2 is the last node in the > cluster > This message can be disabled with -Q > [root@server1 ]# date > dv nov 9 *09:58:42 *CET 2012 > > It's obvious that I'm missing something, because I can't make sense of all > this, and I'm following http://en.wikipedia.org/wiki/ISO_8601#Durations ... > Can anyone help me? > > PD: BTW, a minor glitch: When using a wrong duration, crm points you to a > URL lacking a "s" at the end: > > # crm resource migrate service dsadsadsa > Invalid duration specified: dsadsada > Please refer to *http://en.wikipedia.org/wiki/ISO_8601#Duration* for > examples of valid durations > Error performing operation: Invalid argument > > It should be "Duration*s*" with a final "s" _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
