test_volume_boot_pattern scenario has a dependency on public network

Bug #1774870 reported by Manik Sidana
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Manik Sidana

Bug Description

test_volume_boot_pattern() test scenario in tempest/default/tempest/scenario/test_volume_boot_pattern.py has a dependency on public network

@testtools.skipUnless(CONF.network.public_network_id,
                          'The public_network_id option must be specified.')

This scenario should be allowed for execution without a public network as it is a volume based scenario and doesn't focusses on network.
Please suggest if this can be taken as a bug.

Manik Sidana (manik019)
description: updated
Revision history for this message
Deepak Mourya (mourya007) wrote :

Hi, yes i have tested the scenario without this and it was ran successfully but waiting for the other's opinion.

Manik Sidana (manik019)
Changed in tempest:
assignee: nobody → Manik Sidana (manik019)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/572273

Changed in tempest:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/572273
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=e1f990bdb74fb113d3ab7589f3f48edb9e31be96
Submitter: Zuul
Branch: master

commit e1f990bdb74fb113d3ab7589f3f48edb9e31be96
Author: msidana <email address hidden>
Date: Tue Jun 5 12:10:24 2018 +0530

    Adding a note for test case test_volume_boot_pattern().

    Added a comment as a NOTE for test case test_volume_boot_pattern()
    to describe its dependency on public network.

    Change-Id: I887b941b92b61f6ca9d6054f94b2ff9abbc1f5f8
    Closes-Bug: #1774870

Changed in tempest:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tempest 19.0.0

This issue was fixed in the openstack/tempest 19.0.0 release.

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.