Launch new volume as instance via horizon failed

Bug #1887591 reported by Yvonne Ding
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Incomplete
Medium
Lin Shuicheng

Bug Description

Brief Description
-----------------
Launch a new volume as instance via horizon is failed.

Severity
--------
Major

Steps to Reproduce
------------------
1. Login as Tenant
2. Go to Project > Compute > Instance
3. Create a new volume
4. Edit new volume as bootable
5. Launch volume as instance
6. Check the instance is 'active' and attached by the volume

TC-name:

Expected Behavior
-----------------
The instance is 'active' and attached by the volume

Actual Behavior
----------------
The instance is not 'active'

Reproducibility
---------------
reproducible

System Configuration
--------------------
Regular standard 2+2

Lab-name:
wcp-7-10

Branch/Pull Time/Commit
-----------------------
BUILD_ID="20200709T013419Z"

Timestamp/Logs
--------------
[2020-07-10 16:19:16,752] 61 DEBUG MainThread conftest.update_results:: ***Failure at test call: /home/svc-cgcsauto/wassp-repos.new/testcases/cgcs/CGCSAuto/testcases/functional/horizon/test_volumes.py:333: AssertionError: assert False
***Details: volumes_pg_action = <utils.horizon.pages.project.volumes.volumespage.VolumesPage object at 0x7f7de8cbf390>

......
        volumes_pg_action.launch_as_instance(volume_name,
                                             instance_name,
                                             delete_volume_on_instance_delete=False,
                                             flavor_name=flavor_name,
                                             network_names=[mgmt_net_name])
        LOG.tc_step('Check that instance is Active and attached by the volume')
        time.sleep(5)
        instances_pg = instancespage.InstancesPage(volumes_pg_action.driver, volumes_pg_action.port)
        instances_pg.go_to_target_page()
> assert instances_pg.is_instance_active(instance_name)
E AssertionError: assert False
E + where False = <bound method InstancesPage.is_instance_active of <utils.horizon.pages.project.compute.instancespage.InstancesPage object at 0x7f7de8a00550>>('test_volume_instance_10-07-12-12-17')
E + where <bound method InstancesPage.is_instance_active of <utils.horizon.pages.project.compute.instancespage.InstancesPage object at 0x7f7de8a00550>> = <utils.horizon.pages.project.compute.instancespage.InstancesPage object at 0x7f7de8a00550>.is_instance_active

logs of .tar and video
https://files.starlingx.kube.cengn.ca/launchpad/1887589

Test Activity
-------------
stx.4.0 regression

Yvonne Ding (yding)
description: updated
Revision history for this message
Ghada Khalil (gkhalil) wrote :

stx.4.0 / medium - looks to be an openstack regression. Marking as stx.4.0 gating until the openstack team has a read-out

Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → yong hu (yhu6)
tags: added: stx.4.0 stx.distro.openstack
description: updated
Changed in starlingx:
importance: Medium → High
importance: High → Medium
yong hu (yhu6)
Changed in starlingx:
assignee: yong hu (yhu6) → Lin Shuicheng (shuicheng)
Revision history for this message
Lin Shuicheng (shuicheng) wrote :

Hi Yvonne,
The log url is the same as LP1887589 "Create new instance failed via horizon".
I try to reproduce it in my 2+2 system. And VM with new volume could be launched successfully.
Here is the volume "test" I created:
 test - 5GiB In-use - ceph-store /dev/vda on test nova Yes No

    Overview
Name
    test
ID
    9e547337-d83f-4db3-a1a7-f76a54c51627
Project ID
    b451ad80787b4d2faf4d276cbcd8ed44
Status
    In-use
Group
    -

Specs

Size
    5 GiB
Type
    ceph-store
Bootable
    Yes
Encrypted
    No
Created
    July 17, 2020, 12:05 a.m.

Attachments

Attached To
    test on /dev/vda

Could you help confirm whether the issue exist with latest build?
The log you pasted seems like auto script which I don't have. Could you help use manual step to reproduce the issue, and share the detail step with me?
Also is there any regression info for this issue? Thanks.

Changed in starlingx:
status: Triaged → Incomplete
Revision history for this message
Lin Shuicheng (shuicheng) wrote :

Mark as duplicate since both issue share the same log in the same machine.

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.