[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478929#comment-16478929
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

wido commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-389836720
 
 
   @syed Could you take a look at this one and fix the conflicts?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> To create a better VNC client for Cloudstack using noVNC
> 
>
> Key: CLOUDSTACK-10025
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10025
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VNC Proxy
>Affects Versions: 4.11.0.0
>Reporter: Sachin
>Priority: Minor
>  Labels: features
>
> I have implemented this feature as my GSoC'17 project. noVNC is written in 
> javascript and uses websockets to connect to VNC server. We have modified the 
> ConsoleProxy server to accept websocket request from noVNC client, which then 
> forwards the request request to VNC server.
> Javascript cannot make plain tcp request, hence the websocket request have to 
> be forwarded to the VNC server via a proxy server that basically converts 
> websocket request from client to plain tcp request for VNC server.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479225#comment-16479225
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

rhtyd opened a new pull request #2651: CLOUDSTACK-10290: Introduce option to 
have config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651
 
 
   This introduces a new global setting `vm.configdrive.primarypool.enabled` to 
toggle creation/hosting of config drive iso files on primary storage, the 
default will be `false` causing them to be hosted on secondary storage. The 
support is limited from hypervisor resource side and in current implementation 
limited to KVM. The next big change is that config drive is created at a 
temporary location by management server and shipped to either KVM or SSVM agent 
via cmd-answer pattern, the data of which is not logged in logs. This saves us 
from adding `genisoimage` dependency on cloudstack-agent pkg.
   
   The APIs to reset ssh public key, password and user-data (via update VM API) 
requires that VM should be shutdown. Therefore, in the refactoring I removed 
the case of updation of existing ISO. If there are objections I'll re-put the 
strategy to detach+attach new config iso as a way of updation. In the 
refactored implementation, the folder name is changed to lower-cased 
`configdrive`. And during VM start, migration or shutdown/removal if primary 
storage is enable for use, the KVM agent will handle cleanup tasks otherwise 
SSVM agent will handle them. 
   
   ## 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)
   
   ## GitHub Issue/PRs
   
   
   
   
   
   
   ## Screenshots (if appropriate):
   
   ## How Has This Been Tested?
   
   
   
   
   
   ## Checklist:
   
   
   - [ ] I have read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md)
 document.
   - [ ] My code follows the code style of this project.
   - [ ] My change requires a change to the documentation.
   - [ ] I have updated the documentation accordingly.
   Testing
   - [ ] I have added tests to cover my changes.
   - [ ] All relevant new and existing integration tests have passed.
   - [ ] A full integration testsuite with all test that can run on my 
environment has passed.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479232#comment-16479232
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

blueorangutan commented on issue #2651: CLOUDSTACK-10290: Introduce option to 
have config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-389911606
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479228#comment-16479228
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

rhtyd commented on issue #2651: CLOUDSTACK-10290: Introduce option to have 
config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-389911334
 
 
   Work left is some testing around VM migration and unit test/marvin test 
fixing.
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479287#comment-16479287
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

blueorangutan commented on issue #2651: CLOUDSTACK-10290: Introduce option to 
have config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-389921675
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2061


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479320#comment-16479320
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

rhtyd commented on issue #2651: CLOUDSTACK-10290: Introduce option to have 
config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-389927453
 
 
   @blueorangutan test matrix 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479322#comment-16479322
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

blueorangutan commented on issue #2651: CLOUDSTACK-10290: Introduce option to 
have config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-389927817
 
 
   @rhtyd a Trillian-Jenkins matrix job (centos6 mgmt + xs71, centos7 mgmt + 
vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479861#comment-16479861
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

blueorangutan commented on issue #2651: CLOUDSTACK-10290: Introduce option to 
have config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-390041852
 
 
   Trillian test result (tid-2682)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 22215 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2651-t2682-kvm-centos7.zip
   Intermitten failure detected: 
/marvin/tests/smoke/test_deploy_virtio_scsi_vm.py
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 64 look OK, 3 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   ContextSuite context=TestDeployVirtioSCSIVM>:setup | `Error` | 0.00 | 
test_deploy_virtio_scsi_vm.py
   test_03_vpc_privategw_restart_vpc_cleanup | `Error` | 106.11 | 
test_privategw_acl.py
   test_hostha_enable_ha_when_host_in_maintenance | `Error` | 4.60 | 
test_hostha_kvm.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479923#comment-16479923
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

blueorangutan commented on issue #2651: CLOUDSTACK-10290: Introduce option to 
have config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-390051620
 
 
   Trillian test result (tid-2683)
   Environment: vmware-65 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 2 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2651-t2683-vmware-65.zip
   Intermitten failure detected: 
/marvin/tests/smoke/test_deploy_vm_root_resize.py
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_03_vpc_privategw_restart_vpc_cleanup | `Error` | 212.31 | 
test_privategw_acl.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Config drive - only supported for secondary storage
> ---
>
> Key: CLOUDSTACK-10290
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Rohit Yadav
>Assignee: Daan Hoogland
>Priority: Major
>
> Userdata disk looks like this:
>  
>    
>     file='/mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266/configdrive.iso'/>
>    
>    
>    
>    
>    
>      
> Mount is:
> root# df /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  Filesystem   1K-blocks   
>  Used Available Use% Mounted on
>  some-nfs-server.com:/nfs/secondary/ConfigDrive/i-2-24-VM  66391040 2973696  
> 63417344   5% /mnt/eba12ff3-c3a6-394a-bf0f-23291f1f6266
>  
> issue: where to find a primary storage for a VM that is not yet deployed. The 
> configdrive is created before a storage is assigned. This order of execution 
> must be reversed for this to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CLOUDSTACK-10290) Config drive - only supported for secondary storage

2018-05-17 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479924#comment-16479924
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10290:
-

blueorangutan commented on issue #2651: CLOUDSTACK-10290: Introduce option to 
have config drives on primary storage
URL: https://github.com/apache/cloudstack/pull/2651#issuecomment-390051866
 
 
   Trillian test result (tid-2681)
   Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 6
   Total time taken: 25488 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2651-t2681-xenserver-71.zip
   Intermitten failure detected: /marvin/tests/smoke/test_certauthority_root.py
   Intermitten failure detected: /marvin/tests/smoke/test_dynamicroles.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_simulator.py
   Intermitten failure detected: /marvin/tests/smoke/test_login.py
   Intermitten failure detected: 
/marvin/tests/smoke/test_outofbandmanagement_nestedplugin.py
   Intermitten failure detected: /marvin/tests/smoke/test_outofbandmanagement.py
   Intermitten failure detected: /marvin/tests/smoke/test_primary_storage.py
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Intermitten failure detected: /marvin/tests/smoke/test_usage.py
   Smoke tests completed. 56 look OK, 11 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   login_test_saml_user | `Error` | 0.63 | test_login.py
   test_revoke_certificate | `Error` | 0.01 | test_certauthority_root.py
   test_role_account_acls_multiple_mgmt_servers | `Error` | 0.72 | 
test_dynamicroles.py
   test_configure_ha_provider_invalid | `Error` | 0.01 | 
test_hostha_simulator.py
   test_configure_ha_provider_valid | `Error` | 0.01 | test_hostha_simulator.py
   test_ha_configure_enabledisable_across_clusterzones | `Error` | 0.01 | 
test_hostha_simulator.py
   test_ha_disable_feature_invalid | `Error` | 0.01 | test_hostha_simulator.py
   test_ha_enable_feature_invalid | `Error` | 0.01 | test_hostha_simulator.py
   test_ha_list_providers | `Error` | 0.01 | test_hostha_simulator.py
   test_ha_multiple_mgmt_server_ownership | `Error` | 0.01 | 
test_hostha_simulator.py
   test_ha_verify_fsm_available | `Error` | 0.01 | test_hostha_simulator.py
   test_ha_verify_fsm_degraded | `Error` | 0.01 | test_hostha_simulator.py
   test_ha_verify_fsm_fenced | `Error` | 0.01 | test_hostha_simulator.py
   test_ha_verify_fsm_recovering | `Error` | 0.01 | test_hostha_simulator.py
   test_hostha_configure_default_driver | `Error` | 0.01 | 
test_hostha_simulator.py
   test_hostha_configure_invalid_provider | `Error` | 0.01 | 
test_hostha_simulator.py
   test_hostha_disable_feature_valid | `Error` | 0.01 | test_hostha_simulator.py
   test_hostha_enable_feature_valid | `Error` | 0.01 | test_hostha_simulator.py
   test_hostha_enable_feature_without_setting_provider | `Error` | 0.01 | 
test_hostha_simulator.py
   test_list_ha_for_host | `Error` | 0.01 | test_hostha_simulator.py
   test_list_ha_for_host_invalid | `Error` | 0.01 | test_hostha_simulator.py
   test_list_ha_for_host_valid | `Error` | 0.01 | test_hostha_simulator.py
   test_02_edit_primary_storage_tags | `Error` | 0.01 | test_primary_storage.py
   test_oobm_issue_power_cycle | `Error` | 3.59 | 
test_outofbandmanagement_nestedplugin.py
   test_oobm_issue_power_off | `Error` | 3.40 | 
test_outofbandmanagement_nestedplugin.py
   test_oobm_issue_power_on | `Error` | 3.39 | 
test_outofbandmanagement_nestedplugin.py
   test_oobm_issue_power_reset | `Error` | 3.38 | 
test_outofbandmanagement_nestedplugin.py
   test_oobm_issue_power_soft | `Error` | 2.35 | 
test_outofbandmanagement_nestedplugin.py
   test_oobm_issue_power_status | `Error` | 2.27 | 
test_outofbandmanagement_nestedplugin.py
   test_oobm_background_powerstate_sync | `Failure` | 20.54 | 
test_outofbandmanagement.py
   test_oobm_background_powerstate_sync | `Error` | 20.55 | 
test_outofbandmanagement.py
   test_oobm_configure_default_driver | `Error` | 0.07 | 
test_outofbandmanagement.py
   test_oobm_configure_invalid_driver | `Error` | 0.08 | 
test_outofbandmanagement.py
   test_oobm_disable_feature_invalid | `Error` | 0.09 | 
test_outofbandmanagement.py
   test_oobm_disable_feature_valid | `Error` | 0.19 | 
test_outofbandmanagement.py
   test_oobm_enable_feature_invalid | `Error` | 0.10 | 
test_outofbandmanagement.py
   test_oobm_enable_feature_valid | `Error` | 1.16 | test_outofbandmanagement.py
   test_oobm_enabledisable_across_clusterzones | `Error` | 9.92 | 
test_outofbandmanagement.py
   test_oobm_enabledisable_across_clusterzones | `Error` | 9.93 | 
test_outofbandmanagement.py
   test_oob