IBM Support

Collecting Data: How to use nova boot for debugging

Troubleshooting


Problem

Collecting data for problems with IBM Cloud Orchestrator. Collecting this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Cause

During the course of investigating a pattern or virtual system deployment, it might become necessary to verify the following information:

  • At a low level, the image is functional
  • Hypervisor is up and connected
  • Network parameters are correct.
In this case, you can reduce the complexity of the test by focusing specifically on the OpenStack nova boot command.

Diagnosing The Problem

To effectively help diagnose and resolve your issue, collect the following information:

Procedure:

  1. Log into the region server as root.

  2. Run the following commands (the nova boot command needs a few parameters set first):

    # source ~/keystonerc
    # nova image-list
    # nova flavor-list
    # nova network-list (or neutron net-list)

  3. Run the nova boot command using the relevant ID output from step #2.

    For example:

    Note: Run the command all on one line.

    nova boot --flavor 10 --image 420e83a2-23ff-da4b-9e79-155c424dcbad --nic net-id=178d0600-bab0-4f26-83ff-0103664522dc thisIsATest01


    To perform nova boot with an Availability Zone flag:

    # nova availability-zone-list
    +-----------------------+----------------------------------------+
    | Name                  | Status                                 |
    +-----------------------+----------------------------------------+
    | internal              | available                              |
    | |- rs01               |                                        |
    | | |- nova-conductor   | enabled :-) 2014-11-26T04:43:42.480951 |
    | | |- nova-vmware      | enabled :-) 2014-11-26T04:43:43.470038 |
    | | |- nova-consoleauth | enabled :-) 2014-11-26T04:43:42.480897 |
    | | |- nova-cert        | enabled :-) 2014-11-26T04:43:42.488266 |
    | | |- nova-scheduler   | enabled :-) 2014-11-26T04:43:42.598671 |
    | nova                  | available                              |
    | |- rs01               |                                        |
    | | |- nova-compute     | enabled :-) 2014-11-26T04:43:47.860310 |
    | nova2                 | available                              |
    | |- 2ndCluster         |                                        |
    | | |- nova-compute     | enabled :-) 2014-11-26T04:43:47.527784 |
    +-----------------------+----------------------------------------+

  4. Determine which Availability zone you require for your test and then deploy to it.

    Example:

    Note: Run the command all on one line.

    # nova boot --flavor 10 --availability-zone nova --image c1d3207e-98cb-436a-a509-c671b46f507b  --nic net-id=20199f2f-4660-4d57-a934-9c7ccec81194 thisIsATest02


    To check on the status of your nova boot, use the commands:
    # nova list
    # nova show id-number-from-list


After you have collected the preceding information, you can begin analyzing the data or simply submit the diagnostic data to IBM support. After a PMR is open, you can submit diagnostic data to IBM. If you are using Service Request (SR), update the PMR to indicate that data has been sent.

For a listing of all technotes, downloads, and educational materials search the IBM Cloud Orchestrator product support site.

Note: Do not send any confidential information from your company.

[{"Product":{"code":"SS4KMC","label":"IBM SmartCloud Orchestrator"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Deployment","Platform":[{"code":"PF016","label":"Linux"}],"Version":"2.2;2.3;2.4;2.4.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21697917

Page Feedback