scenario job uses nonexistent name of image

Bug #1555189 reported by Valeriy Ponomaryov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
High
Valeriy Ponomaryov

Bug Description

Commit [1] changed link to service image and its name. But tempest config option is not updated and refers to old nonexistent image name.

It leads to impossibility to create Nova VMs in scenario CI job.

[1] https://github.com/openstack/manila/commit/1ec8a794

description: updated
Changed in manila:
assignee: nobody → Valeriy Ponomaryov (vponomaryov)
milestone: none → mitaka-rc1
importance: Undecided → High
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

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

tags: added: ci devstack scenario tempest
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/290614
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=2358f9137e1a89b6ac50ad0fe6a13f9e3daf8fd0
Submitter: Jenkins
Branch: master

commit 2358f9137e1a89b6ac50ad0fe6a13f9e3daf8fd0
Author: Valeriy Ponomaryov <email address hidden>
Date: Wed Mar 9 17:57:17 2016 +0200

    Set proper image name for tempest

    Commit [1] changed link to service image and its name.
    But tempest config option is not updated and refers to
    old nonexistent image name.
    It leads to impossibility to create Nova VMs in scenario CI job.

    [1] I391119cf08949974efc469b8669d5e4120170c0d

    Change-Id: I912ecd61556e8a0ff3a82f7b70a47cbfcc490d22
    Closes-Bug: #1555189

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/manila 2.0.0.0rc1

This issue was fixed in the openstack/manila 2.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 2.0.0

This issue was fixed in the openstack/manila 2.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.