Skip to content

Use IDE as the bus type for root disks and VIRTIO for data disks on platforms without support for para virtualization when using managed storage - #3319

Merged
yadvr merged 6 commits into
apache:masterfrom
skattoju4:incorrect_bus_type_for_windows_vms
Jul 12, 2019
Merged

Use IDE as the bus type for root disks and VIRTIO for data disks on platforms without support for para virtualization when using managed storage#3319
yadvr merged 6 commits into
apache:masterfrom
skattoju4:incorrect_bus_type_for_windows_vms

Conversation

@skattoju4

@skattoju4 skattoju4 commented May 8, 2019

Copy link
Copy Markdown
Contributor

Description

This change addresses #3089. There was an issue when disks were being added with bus type IDE when creating windows VMs from ISOs. It is not possible to select bus type when creating a VM with an ISO. The bus type is inferred based on the platform emulator string provided to the KVM agent. Currently when creating a VM with managed storage (ex: Solidfire) and OS type string Windows*, all disks are added as IDE. Qemu currently does not support multiple IDE controllers and this configuration results in VMs that cannot be started. This issue does not occur when using NFS as the storage provider due to logic in that KVM agent that makes all data volumes (non root) use a virtio controller for file based disk. Similar logic was added for raw physical disks so that managed storage has the same behavior as NFS. In addition specific versions were removed from the code that guesses the disk controller to be used based on the platform emulator string since most modern operating systems support virtio.

steps to reproduce are described in #3089

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)

How Has This Been Tested?

In a Cloudstack system with Solidfire managed primary storage and a KVM host the following steps were performed:

  1. Register to an ISO template with OS set to Windows 2016
  2. Create a VM using this template with Solidfire Storage
  3. Verify that the VM starts successfully
  4. Verify that disks are attached on the virtio bus and only the cdrom device is ide by executing virsh dumpxml <id> on the KVM host

@svenvogel

Copy link
Copy Markdown
Contributor

@skattoju3 thanks we will test it and come back tomorrow.

@ustcweizhou

Copy link
Copy Markdown
Contributor

@skattoju4
for windows vm, we need to install virtio drivers.
for now, we can register template without virtio drivers as Windows XX, and template with virtio drivers as "Windows PV".
This PR will break actions above.

so -1 for me.

@svenvogel

Copy link
Copy Markdown
Contributor

@ustcweizhou

Maybe we talk past each other. It should only set the first disk to ide device and all other to virtio like in the bug Report #3089 described.

We don’t want to break things and we don’t want only virtio disks.

Simple it should be
Cdrom ide
First disk ide
Second virtio
Third virtio
And so one ...

The bug with solidfire / iscsi we got is

Cdrom ide
First ide
Second ide
...that’s but really supported in kvm. With nfs there is no problem.

@skattoju4 is that what I understand it Correctly?

@syed what do you think?

@ustcweizhou

Copy link
Copy Markdown
Contributor

@svenvogel
the main problem for this PR is, all Windows vm will be running with virtio (no ide any more !!)
If vm does not have virtio drivers, they will not boot up

@svenvogel

Copy link
Copy Markdown
Contributor

@ustcweizhou

You are right. That should not be the solution. I understand. Let’s investigate and fix that. What I wrote above the goal was another.

@syed

syed commented May 9, 2019

Copy link
Copy Markdown
Contributor

I agree with @svenvogel. The first disk should always be IDE. The subsequent disks can be virtio.

@ustcweizhou

Copy link
Copy Markdown
Contributor

@skattoju4 @svenvogel @syed
I have no idea why the first disk should be always IDE.
If I have installed virtio driver in windows vm, and OS type (vm or template) is set to 'Windows PV', I hope all disk are virtio, not IDE.

@skattoju4

Copy link
Copy Markdown
Contributor Author

@ustcweizhou the thinking behind always setting the root disk to ide was to be able to boot a windows vm regardless of whether or not virtio drivers were installed. That said setting all disks to virtio when selecting "Windows PV" when registering the template is one way to move forward. @svenvogel what do you think ?

@svenvogel

svenvogel commented May 10, 2019

Copy link
Copy Markdown
Contributor

@skattoju4 @ustcweizhou @syed i will try to explain it.

@ustcweizhou the thinking behind always setting the root disk to ide was to be able to boot a windows vm regardless of whether or not virtio drivers were installed. That said setting all disks to virtio when selecting "Windows PV" when registering the template is one way to move forward.

first i have to say is yes! let me explain. as written in #3089 we have "NOT" only the problem with template!
@DennisKonrad wrote:

When we select "Windows Server 2016 (64-bit)" as OS Type for an W2K16 cd image the resulting
VMs will not start with multiple disks attached. This is due to the usage of multiple IDE interfaces in the VM description XML.

  1. we create a machine with "Windows Server 2016 (64-bit)" we have one disk with type root "ide".

Bildschirmfoto 2019-05-10 um 21 50 40

2. after that we add **two more data disks** and those should "NOT" be IDE because QEMU dont like this! When we use NFS the second and third disk will be a "virtio" disk automatically.

this pr should "NOT" remove/break or add functionality.

it should enable the normal functionality for managed storage according to NFS works and it is needed by QEMU if we choose "Windows Server 201X..." as OS Type. it is a bug that will affect only managed storage (as far as i i know). If any user wants "ONLY" virtio driver he can choose "other pv ..." OS Type.
Bildschirmfoto 2019-05-10 um 21 58 11

there is no discussion about performance of IDE or move all Microsoft Windows OS Types to virtio. it should be clear for everybody here that virtio is faster than ide and yes we dont need a driver for the root disk. but this content is not part of this discussion here.

i hope it is more clear now?

@ustcweizhou

Copy link
Copy Markdown
Contributor

@svenvogel thanks for you explanation.
Currently we use 'Windows PV' for windows vm. All disk are virtio.
We hope this will not be broken.
Change OS type from 'Windows PV' to 'Other PV' will lead to changes not only in cloudstack itself, but also in some maintenance scripts.

so please change the code to following if possible.

                if (volume.getType() == Volume.Type.ROOT &&
                    vmSpec.getPlatformEmulator().startsWith("Windows") &&
                    ! vmSpec.getPlatformEmulator().equals("Windows PV")){

@svenvogel

Copy link
Copy Markdown
Contributor

@ustcweizhou no we will check this before and have a look on the PR that we dont break the virtio.

@syed @skattoju4 what do think, can we add this?

@syed

syed commented May 13, 2019

Copy link
Copy Markdown
Contributor

Sounds good to me. @skattoju4 can you take care of it?

@kiwiflyer

kiwiflyer commented May 13, 2019 via email

Copy link
Copy Markdown
Contributor

@DennisKonrad

Copy link
Copy Markdown
Contributor

@kiwiflyer Such a feature would a way in the direction of further untangling this os-type problem. I am looking forward to your pr.

@svenvogel

Copy link
Copy Markdown
Contributor

@svenvogel thanks for you explanation.
Currently we use 'Windows PV' for windows vm. All disk are virtio.
We hope this will not be broken.
Change OS type from 'Windows PV' to 'Other PV' will lead to changes not only in cloudstack itself, but also in some maintenance scripts.

so please change the code to following if possible.

                if (volume.getType() == Volume.Type.ROOT &&
                    vmSpec.getPlatformEmulator().startsWith("Windows") &&
                    ! vmSpec.getPlatformEmulator().equals("Windows PV")){

@skattoju4 @syed do you think the fix from @ustcweizhou will fix this?

@kiwiflyer better configuration options for the os type sounds good.

@skattoju4

Copy link
Copy Markdown
Contributor Author

@sven , @ustcweizhou 's suggestion sounds reasonable. I think this is ok for now but ideally this should be handle in a better way. @kiwiflyer could you link your PR please ?

@skattoju4 skattoju4 changed the title Use virtio for platform emulator strings starting with Windows* Use IDE as the bus type for root disks when platform emulator strings start with Windows* except Windows PV May 13, 2019
@skattoju4 skattoju4 changed the title Use IDE as the bus type for root disks when platform emulator strings start with Windows* except Windows PV Use IDE as the bus type for root disks and VIRTIO for data disks when platform emulator strings start with Windows* except Windows PV May 13, 2019
@svenvogel

Copy link
Copy Markdown
Contributor

@skattoju4 do you mean we should test it? i think @kiwiflyer 's PR is out of scope of this one. right?

@skattoju4

Copy link
Copy Markdown
Contributor Author

@svenvogel now we should have the same behavior as nfs when selecting os type Windows* (except Windows PV) I think it might be better to select Windows PV and have all disk be virtio when para-virtualization is supported. With the current code vm created from iso templates with os type Windows* (Except Windows PV) will have an ide root disk but there is no way to attach a data disk as IDE. (one additional ide disk is possible before the error is triggered if i am not mistaken)

I'm guessing @kiwiflyer 's PR will enable setting the disk controller when registering an iso similar to how this can be specified when registering a template. I think this would be a cleaner solution than trying to guess the controller / bus type based on the os type string.

@svenvogel

Copy link
Copy Markdown
Contributor

@skattoju4 we will test it

(one additional ide disk is possible before the error is triggered if i am not mistaken)
unfortunately no. only one ide disk so what i know.

okay there should not be a second ide disk right?

@skattoju4

skattoju4 commented May 14, 2019 via email

Copy link
Copy Markdown
Contributor Author

@DennisKonrad

Copy link
Copy Markdown
Contributor

@skattoju4 @svenvogel I will build this today and testing can happen the following days.

@kiwiflyer

Copy link
Copy Markdown
Contributor

To be clear, the feature that allows selection of root disk controller for a template using vmdetails has been in cloudstack for a couple of major versions now -

image

@skattoju4

skattoju4 commented Jul 8, 2019

Copy link
Copy Markdown
Contributor Author

@svenvogel yeah @ustcweizhou suggestion is cleaner / more generic the windows specific logic can be removed. As pointed out the issue is guest OSs without pv support using managed storage. (sorry missed previous messages)

@svenvogel

Copy link
Copy Markdown
Contributor

@skattoju4 should we change it like the suggestion of @ustcweizhou? i mean the ide managed storage...

@skattoju4

Copy link
Copy Markdown
Contributor Author

@svenvogel it sounds logical will test and update the pr

@svenvogel

Copy link
Copy Markdown
Contributor

@skattoju4 sound good. thx!

@ustcweizhou

Copy link
Copy Markdown
Contributor

@skattoju4 good, looking forward to your update.
@svenvogel @skattoju4 thanks for nice discussion tonight. have a good evening.

@skattoju4

Copy link
Copy Markdown
Contributor Author

@svenvogel Agree with you.
Furthermore, I think it is better to use

platformEmulator.contains("Ubuntu")

because some users use "Other Ubuntu" for the Ubuntu versions which are not in the list, for example Ubuntu 17.04, Ubuntu 18.04.

Regardless of this fix ... the code below should included in any case because it looks ugly at the moment. (code below)

        } else if (platformEmulator.startsWith("Ubuntu") ||
                platformEmulator.startsWith("Fedora") ||
                platformEmulator.startsWith("CentOS") ||
                platformEmulator.startsWith("Red Hat Enterprise Linux") ||
                platformEmulator.startsWith("Debian GNU/Linux") ||
                platformEmulator.startsWith("FreeBSD") ||
                platformEmulator.startsWith("Oracle") ||
                platformEmulator.startsWith("Windows PV") ||
                platformEmulator.startsWith("Other PV")) {

Are there any Ubuntu versions which don't support PV ?

…isks so that data disks are always virtio (or iscsi) like with nfs (or file based disks)
@ustcweizhou

Copy link
Copy Markdown
Contributor

@svenvogel Agree with you.
Furthermore, I think it is better to use

platformEmulator.contains("Ubuntu")

because some users use "Other Ubuntu" for the Ubuntu versions which are not in the list, for example Ubuntu 17.04, Ubuntu 18.04.

Regardless of this fix ... the code below should included in any case because it looks ugly at the moment. (code below)

        } else if (platformEmulator.startsWith("Ubuntu") ||
                platformEmulator.startsWith("Fedora") ||
                platformEmulator.startsWith("CentOS") ||
                platformEmulator.startsWith("Red Hat Enterprise Linux") ||
                platformEmulator.startsWith("Debian GNU/Linux") ||
                platformEmulator.startsWith("FreeBSD") ||
                platformEmulator.startsWith("Oracle") ||
                platformEmulator.startsWith("Windows PV") ||
                platformEmulator.startsWith("Other PV")) {

Are there any Ubuntu versions which don't support PV ?

as far as I know, pv is supported by all ubuntu versions in past 10 years.

@yadvr yadvr removed this from the 4.13.0.0 milestone Jul 9, 2019
@yadvr

yadvr commented Jul 9, 2019

Copy link
Copy Markdown
Member

Looks like there are still on-going discussions with no clear consensus. Because of this I've removed the milestone on this PR, kindly ping me when a consensus is reached. If this could make into 4.13.0.0 before the freeze I'll be happy to help run tests, otherwise we can revisit this after 4.13.0.0, either in 4.13.1.0 or 4.14.0.0.

platformEmulator.startsWith("Debian GNU/Linux") ||
platformEmulator.startsWith("FreeBSD") ||
platformEmulator.startsWith("Oracle") ||
platformEmulator.startsWith("Windows PV") ||

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually the platformEmulator is "Other PV" if guest os type is "Windows PV".
so line 3212 is not needed

mysql> select * from guest_os where display_name='Windows PV';
+-----+-------------+------+--------------------------------------+--------------+---------------------+---------+-----------------+---------+
| id  | category_id | name | uuid                                 | display_name | created             | removed | is_user_defined | display |
+-----+-------------+------+--------------------------------------+--------------+---------------------+---------+-----------------+---------+
| 160 |           6 | NULL | e1990eb3-4b9d-11e3-8346-2c44fd7a3378 | Windows PV   | 2016-07-27 10:48:33 | NULL    |               0 |       0 |
+-----+-------------+------+--------------------------------------+--------------+---------------------+---------+-----------------+---------+
1 row in set (0.00 sec)

mysql> select * from guest_os_hypervisor where guest_os_id=160;
+------+-----------------+---------------+-------------+--------------------+--------------------------------------+---------------------+---------+-----------------+
| id   | hypervisor_type | guest_os_name | guest_os_id | hypervisor_version | uuid                                 | created             | removed | is_user_defined |
+------+-----------------+---------------+-------------+--------------------+--------------------------------------+---------------------+---------+-----------------+
| 1264 | KVM             | Other PV      |         160 | default            | e768e05d-53d6-11e6-8d7a-2c44fd7a3454 | 2016-07-27 10:48:35 | NULL    |               0 |
| 2114 | LXC             | Other PV      |         160 | default            | e965179c-53d6-11e6-8d7a-2c44fd7a3454 | 2016-07-27 10:48:38 | NULL    |               0 |
+------+-----------------+---------------+-------------+--------------------+--------------------------------------+---------------------+---------+-----------------+
2 rows in set (0.00 sec)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ustcweizhou does it select "display_name" or "guest_os_name"? you mean we dont need "Windows PV" in the list right?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@svenvogel yes, we do not need "Windows PV" in the line.
the platformEmulator is "Other PV" when guest os is "Windows PV".

@ustcweizhou

ustcweizhou commented Jul 9, 2019

Copy link
Copy Markdown
Contributor

Looks like there are still on-going discussions with no clear consensus. Because of this I've removed the milestone on this PR, kindly ping me when a consensus is reached. If this could make into 4.13.0.0 before the freeze I'll be happy to help run tests, otherwise we can revisit this after 4.13.0.0, either in 4.13.1.0 or 4.14.0.0.

@rhtyd
the last commit looks good to me, except some small changes (startsWith -> contains, remove "Windows PV" line)

@skattoju4 skattoju4 changed the title Use IDE as the bus type for root disks and VIRTIO for data disks when platform emulator strings start with Windows* except Windows PV Use IDE as the bus type for root disks and VIRTIO for data disks on platforms without support for para virtualization when using managed storage Jul 9, 2019

@ustcweizhou ustcweizhou left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved
please squash the commits into one commit.

@svenvogel

Copy link
Copy Markdown
Contributor

@skattoju4 is it ready for merge?

@yadvr

yadvr commented Jul 11, 2019

Copy link
Copy Markdown
Member

Let me also help review and test it @svenvogel
@blueorangutan package

@blueorangutan

Copy link
Copy Markdown

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan

Copy link
Copy Markdown

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-114

@yadvr yadvr added this to the 4.13.0.0 milestone Jul 11, 2019
@yadvr

yadvr commented Jul 11, 2019

Copy link
Copy Markdown
Member

@blueorangutan test

@yadvr

yadvr commented Jul 11, 2019

Copy link
Copy Markdown
Member

@blueorangutan test

@blueorangutan

Copy link
Copy Markdown

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@blueorangutan

Copy link
Copy Markdown

Trillian test result (tid-146)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 17707 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3319-t146-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_public_ip_range.py
Intermittent failure detected: /marvin/tests/smoke/test_reset_vm_on_reboot.py
Intermittent failure detected: /marvin/tests/smoke/test_resource_accounting.py
Intermittent failure detected: /marvin/tests/smoke/test_router_dhcphosts.py
Intermittent failure detected: /marvin/tests/smoke/test_router_dns.py
Intermittent failure detected: /marvin/tests/smoke/test_router_dnsservice.py
Intermittent failure detected: /marvin/tests/smoke/test_routers_iptables_default_policy.py
Intermittent failure detected: /marvin/tests/smoke/test_routers_network_ops.py
Intermittent failure detected: /marvin/tests/smoke/test_routers.py
Intermittent failure detected: /marvin/tests/smoke/test_secondary_storage.py
Intermittent failure detected: /marvin/tests/smoke/test_service_offerings.py
Intermittent failure detected: /marvin/tests/smoke/test_snapshots.py
Intermittent failure detected: /marvin/tests/smoke/test_ssvm.py
Intermittent failure detected: /marvin/tests/smoke/test_templates.py
Intermittent failure detected: /marvin/tests/smoke/test_usage.py
Intermittent failure detected: /marvin/tests/smoke/test_vm_life_cycle.py
Intermittent failure detected: /marvin/tests/smoke/test_vm_snapshots.py
Intermittent failure detected: /marvin/tests/smoke/test_volumes.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_router_nics.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_vpn.py
Intermittent failure detected: /marvin/tests/smoke/test_host_maintenance.py
Smoke tests completed. 51 look OK, 21 have error(s)
Only failed tests results shown below:

Test Result Time (s) Test File
ContextSuite context=TestResetVmOnReboot>:setup Error 0.00 test_reset_vm_on_reboot.py
ContextSuite context=TestRAMCPUResourceAccounting>:setup Error 0.00 test_resource_accounting.py
ContextSuite context=TestRouterDHCPHosts>:setup Error 0.00 test_router_dhcphosts.py
ContextSuite context=TestRouterDHCPOpts>:setup Error 0.00 test_router_dhcphosts.py
ContextSuite context=TestRouterDns>:setup Error 0.00 test_router_dns.py
ContextSuite context=TestRouterDnsService>:setup Error 0.00 test_router_dnsservice.py
ContextSuite context=TestRouterIpTablesPolicies>:setup Error 0.00 test_routers_iptables_default_policy.py
ContextSuite context=TestVPCIpTablesPolicies>:setup Error 0.00 test_routers_iptables_default_policy.py
test_01_isolate_network_FW_PF_default_routes_egress_true Error 0.19 test_routers_network_ops.py
test_02_isolate_network_FW_PF_default_routes_egress_false Error 0.18 test_routers_network_ops.py
ContextSuite context=TestRedundantIsolateNetworks>:setup Error 1.39 test_routers_network_ops.py
test_02_create_template_with_checksum_sha1 Error 65.51 test_templates.py
test_03_create_template_with_checksum_sha256 Error 65.51 test_templates.py
test_04_create_template_with_checksum_md5 Error 65.54 test_templates.py
test_05_create_template_with_no_checksum Error 65.51 test_templates.py
test_02_deploy_vm_from_direct_download_template Error 1.32 test_templates.py
test_03_deploy_vm_wrong_checksum Error 1.37 test_templates.py
ContextSuite context=TestTemplates>:setup Error 15.08 test_templates.py
ContextSuite context=TestRouterServices>:setup Error 0.00 test_routers.py
test_01_sys_vm_start Failure 0.12 test_secondary_storage.py
test_02_sys_template_ready Failure 0.11 test_secondary_storage.py
ContextSuite context=TestCpuCapServiceOfferings>:setup Error 0.00 test_service_offerings.py
ContextSuite context=TestServiceOfferings>:setup Error 0.23 test_service_offerings.py
ContextSuite context=TestSnapshotRootDisk>:setup Error 0.00 test_snapshots.py
test_01_list_sec_storage_vm Failure 0.04 test_ssvm.py
test_02_list_cpvm_vm Failure 0.04 test_ssvm.py
test_03_ssvm_internals Failure 0.04 test_ssvm.py
test_04_cpvm_internals Failure 0.04 test_ssvm.py
test_05_stop_ssvm Failure 0.04 test_ssvm.py
test_06_stop_cpvm Failure 0.04 test_ssvm.py
test_07_reboot_ssvm Failure 0.04 test_ssvm.py
test_08_reboot_cpvm Failure 0.04 test_ssvm.py
test_09_destroy_ssvm Failure 0.04 test_ssvm.py
test_10_destroy_cpvm Failure 0.04 test_ssvm.py
ContextSuite context=TestISOUsage>:setup Error 0.00 test_usage.py
ContextSuite context=TestLBRuleUsage>:setup Error 0.00 test_usage.py
ContextSuite context=TestNatRuleUsage>:setup Error 0.00 test_usage.py
ContextSuite context=TestPublicIPUsage>:setup Error 0.00 test_usage.py
ContextSuite context=TestSnapshotUsage>:setup Error 0.00 test_usage.py
ContextSuite context=TestVmUsage>:setup Error 0.00 test_usage.py
ContextSuite context=TestVolumeUsage>:setup Error 0.00 test_usage.py
ContextSuite context=TestVpnUsage>:setup Error 0.00 test_usage.py
ContextSuite context=Test01DeployVM>:setup Error 0.00 test_vm_life_cycle.py
ContextSuite context=Test02VMLifeCycle>:setup Error 0.00 test_vm_life_cycle.py
ContextSuite context=Test03SecuredVmMigration>:setup Error 0.00 test_vm_life_cycle.py
ContextSuite context=TestVmSnapshot>:setup Error 0.07 test_vm_snapshots.py
ContextSuite context=TestCreateVolume>:setup Error 0.00 test_volumes.py
ContextSuite context=TestVolumes>:setup Error 0.00 test_volumes.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL Error 4.03 test_vpc_redundant.py
test_02_redundant_VPC_default_routes Error 4.02 test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers Error 3.00 test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics Error 1.98 test_vpc_redundant.py
test_05_rvpc_multi_tiers Error 3.02 test_vpc_redundant.py
test_01_VPC_nics_after_destroy Error 4.00 test_vpc_router_nics.py
test_02_VPC_default_routes Error 2.97 test_vpc_router_nics.py
test_01_redundant_vpc_site2site_vpn Failure 2.40 test_vpc_vpn.py
test_01_vpc_site2site_vpn_multiple_options Failure 2.36 test_vpc_vpn.py
test_01_vpc_remote_access_vpn Failure 2.23 test_vpc_vpn.py
test_01_vpc_site2site_vpn Failure 2.36 test_vpc_vpn.py
test_02_cancel_host_maintenace_with_migration_jobs Failure 0.14 test_host_maintenance.py
ContextSuite context=TestHostMaintenanceAgents>:setup Error 0.22 test_host_maintenance.py

@yadvr

yadvr commented Jul 11, 2019

Copy link
Copy Markdown
Member

@blueorangutan test

@blueorangutan

Copy link
Copy Markdown

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@blueorangutan

Copy link
Copy Markdown

Trillian test result (tid-150)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 28753 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3319-t150-kvm-centos7.zip
Smoke tests completed. 72 look OK, 0 have error(s)
Only failed tests results shown below:

Test Result Time (s) Test File

@yadvr
yadvr merged commit 1bf4dd3 into apache:master Jul 12, 2019
winterhazel pushed a commit that referenced this pull request Jan 28, 2026
Correção no _script_ de _upgrade_ para a versão `4.20.0.8-scclouds`

Closes #3319

See merge request scclouds/scclouds!1371
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants