Skip to content

Latest commit

 

History

History
30 lines (21 loc) · 1.66 KB

understanding-server-transaction.md

File metadata and controls

30 lines (21 loc) · 1.66 KB
copyright lastupdated keywords subcollection
years
2017, 2022
2022-03-09
server transaction
bare-metal

{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:new_window: target="_blank"} {:pre: .pre} {:table: .aria-labeledby="caption"}

Understanding a server transaction

{: #bm-server-transaction}

When a server at {{site.data.keyword.cloud}} is provisioned, an operating system is loaded, or software is installed, it gets put into a transaction. A transaction is an automated series of steps that are carried out by the {{site.data.keyword.cloud_notm}} management systems to configure customer servers.

If one of your servers is in a transaction, a link appears in server notes in hardware listings. You can click this link to see what transactions are pending for that specific server. You are then presented with a table listing data for the current transaction that is in progress.

  • ID is the transaction internal ID. If you open a support case about a transaction, include this number.
  • Group is a short description of the transaction type. For example, MS OS Reload means that a Microsoft® operating system is being reloaded on the server.
  • Current Status is the name of the current transaction step. For example, INSTALL_OS is a transaction step for MS OS Reload, which means that Windows® is being installed on the machine.
  • Elapsed Time and Average Time work together. Elapsed time shows how long the current transaction is running. Average time shows the amount of time this step takes on average. If elapsed time is significantly longer than the average time, you might want to open a support case for status.