Advertisement
kmajumder

Untitled

Dec 16th, 2019
173
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.75 KB | None | 0 0
  1. 2019-12-16 18:43:50,818+05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-10) [bb1d972c-3d26-450e-b014-a4e0ae0617d2] Running command: InstallVdsInternalCommand internal: true. Entities affected : ID: 20b039e9-97ef-4a58-abbc-f93b5ce162cb Type: VDS
  2. 2019-12-16 18:43:50,831+05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-10) [bb1d972c-3d26-450e-b014-a4e0ae0617d2] Before Installation host 20b039e9-97ef-4a58-abbc-f93b5ce162cb, 10.70.35.237
  3. 2019-12-16 18:43:50,876+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [bb1d972c-3d26-450e-b014-a4e0ae0617d2] EVENT_ID: USER_UPDATE_VDS(43), Host 10.70.35.237 configuration was updated by admin@internal-authz.
  4. 2019-12-16 18:43:50,919+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-10) [bb1d972c-3d26-450e-b014-a4e0ae0617d2] START, SetVdsStatusVDSCommand(HostName = 10.70.35.237, SetVdsStatusVDSCommandParameters:{hostId='20b039e9-97ef-4a58-abbc-f93b5ce162cb', status='Installing', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 388dbb20
  5. 2019-12-16 18:43:50,937+05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-10) [bb1d972c-3d26-450e-b014-a4e0ae0617d2] FINISH, SetVdsStatusVDSCommand, return: , log id: 388dbb20
  6. 2019-12-16 18:43:51,008+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-10) [bb1d972c-3d26-450e-b014-a4e0ae0617d2] EVENT_ID: VDS_ANSIBLE_INSTALL_STARTED(560), Ansible host-deploy playbook execution has started on host 10.70.35.237.
  7. 2019-12-16 18:44:21,588+05 INFO [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] (DefaultQuartzScheduler4) [5a819dc0] No up server in cluster
  8. 2019-12-16 18:45:21,594+05 INFO [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] (DefaultQuartzScheduler9) [748bbc6e] No up server in cluster
  9. 2019-12-16 18:46:21,597+05 INFO [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] (DefaultQuartzScheduler6) [facb787] No up server in cluster
  10. 2019-12-16 18:46:21,614+05 INFO [org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob] (DefaultQuartzScheduler4) [4ee7a990] No UP server found in cluster 'Default' for snapshot monitoring
  11. 2019-12-16 18:46:21,631+05 INFO [org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob] (DefaultQuartzScheduler4) [4ee7a990] No UP server found in cluster 'Default' for snapshot configurations monitoring
  12. 2019-12-16 18:47:21,602+05 INFO [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] (DefaultQuartzScheduler1) [6319a47d] No up server in cluster
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement