Can't specify Router External Network ID for scenario VMTasks.boot_runcommand_delete

Bug #1747445 reported by Andrew Price
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Rally
New
Undecided
Manikanta Pendela

Bug Description

For the scenario VMTasks.boot_runcommand_delete I have the job configured as below which creates the network, subnet, router however I have two different external networks for which the router can choose for an external gateway. Rally always chooses the same external network, however it is one I cannot use for Floating IP tests.

---

  VMTasks.boot_runcommand_delete:
    -
      args:
        flavor:
          name: "Small"
        image:
          name: "CentOS-7"
        floating_network: "floating-ip-network"
        use_floating_ip: true
        force_delete: false
        router_create_args:
          external_gateway_info:
            network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
          network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
        command:
          interpreter: "/bin/sh"
          script_file: "/root/bin/instance_test.sh"
        username: "centos"
      runner:
        type: "constant"
        times: 1
        concurrency: 1
        timeout: 180
      context:
        network: {}
        router:
          external_gateway_info:
            network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
          network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
      sla:
        failure_rate:
          max: 0

As you can see, I tried a few ways to specify the Router external network, but I am having no luck.

Any thoughts would be much appreciated.

$ rally --version
0.10.1

Changed in rally:
assignee: nobody → Manikanta Pendela (pendelamani)
Revision history for this message
Ievgeniia Zadorozhna (izadorozhna) wrote :

Hi, seems the router information in context should be inside the "network" key:
"context": {
        "network": {
          "router": {
            "external_gateway_info": {
              "network_id": 6e077c4c-f081-470a-8d9c-3260bd597350
            }
          }
        }
      }

The following works for me.

Revision history for this message
frigo (rigault-francois) wrote :

Works for me too! Thanks

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.