HA. corosync::commitorder calls so far

Bug #1261664 reported by Sergey Vasilenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Undecided
Unassigned

Bug Description

class {'corosync::commitorder': stage=>'main'}
call too later

2013-12-17T03:49:45.050619+00:00 debug: (/Stage[main]/Swift::Storage::Account/Swift::Storage::Generic[account]/Service[swift-account]) The container Swift::Storage::Generic[account] will propagate my refresh event
2013-12-17T03:49:49.195075+00:00 debug: (Swift::Storage::Generic[account]) The container Class[Swift::Storage::Account] will propagate my refresh event
2013-12-17T03:49:49.203593+00:00 debug: (Class[Swift::Storage::Account]) The container Stage[main] will propagate my refresh event
2013-12-17T03:49:55.370885+00:00 notice: Corosync commit order have been set!
2013-12-17T03:49:55.371295+00:00 notice: (/Stage[main]/Corosync::Commitorder/Notify[Corosync commit order have been set!]/message) defined 'message' as 'Corosync commit order have been set!'
2013-12-17T03:49:55.371997+00:00 debug: (/Stage[main]/Corosync::Commitorder/Notify[Corosync commit order have been set!]) The container Class[Corosync::Commitorder] will propagate my refresh event
2013-12-17T03:49:55.388943+00:00 notice: (/Stage[main]/Swift::Storage::All/Swift::Storage::Server[6002]/Rsync::Server::Module[account]/File[/etc/rsync.d/frag-account]/ensure) defined content as '{md5}6322ae9082574fee90fcf4a7bc356d00'
2013-12-17T03:49:55.389726+00:00 debug: (/Stage[main]/Swift::Storage::All/Swift::Storage::Server[6002]/Rsync::Server::Module[account]/File[/etc/rsync.d/frag-account]) The container Rsync::Server::Module[account] will propagate my refresh event

Changed in fuel:
milestone: none → 4.0
Changed in fuel:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.