Uploaded image for project: 'Razor'
  1. Razor
  2. RAZOR-138

Reboot of Powered-off Node Results in Continued Attempts to Reboot

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: RAZOR 0.14.1
    • Fix Version/s: RAZOR 0.15.0
    • Component/s: DOCS, QA, Server
    • Labels:
    • Environment:

      PE Version: 3.2.0-rc0-1206-gd8d46cc
      Razor Version: 0.14.1
      Master: 8GB RAM - CentOS 6.4 x64
      Razor Server: 8GB RAM - CentOS 6.4 x64
      Node: 8GB RAM - CentOS 6.4 x64

    • Template:
    • Epic Link:
    • Story Points:
      1
    • Sprint:
      April 23

      Description

      Description

      If a user attempts to issue the "reboot-node" command to a node that is already powered-off, the Razor server till continually attempt to reboot the node. (See logs)

      I would expect that if the first attempt failed then to stop trying.

      Attachments

      • Razor logs

      Repro Steps

      1. Install and configure a Razor server.
      2. Install the Razor client on the Razor server.
      3. Create a repo.
      4. Create a PE broker.
      5. Create a policy that wraps the given repo and broker.
      6. Register a node with the Razor server.
      7. Set IPMI credentials for the registered node.
      8. Power-off registered node.
      9. Execute the following command to reboot the node:

        razor reboot-node --name <NODE_NAME>

      Expect

      The Razor server should report a failure to reboot the node one time.

      Actual

      The Razor server keeps attempting to reboot the node on a periodic basis. If the node is eventually powered-on it will get rebooted which is kind of pointless.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              phong Phong Ly
              Reporter:
              ryan.gard Ryan Gard
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support