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

Bug #1747445 reported by Andrew Price on 2018-02-05
This bug affects 2 people
Affects Status Importance Assigned to Milestone
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.


          name: "Small"
          name: "CentOS-7"
        floating_network: "floating-ip-network"
        use_floating_ip: true
        force_delete: false
            network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
          network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
          interpreter: "/bin/sh"
          script_file: "/root/bin/"
        username: "centos"
        type: "constant"
        times: 1
        concurrency: 1
        timeout: 180
        network: {}
            network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
          network_id: "32a1802a-04db-41a6-80cd-cdf102e18ef4"
          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

Changed in rally:
assignee: nobody → Manikanta Pendela (pendelamani)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers