[DCOS_OSS-183] Minuteman integration test is flaky / Connection Aborted to minuteman service Created: 20/Jun/16  Updated: 09/Nov/18  Resolved: 21/Aug/16

Status: Resolved
Project: DC/OS
Component/s: networking
Affects Version/s: None
Fix Version/s: DC/OS 1.8.0

Type: Bug Priority: Medium
Reporter: Cody Maloney (Inactive) Assignee: Sargun Dhillon (Inactive)
Resolution: Done  
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

https://teamcity.mesosphere.io/viewLog.html?buildId=305528&buildTypeId=ClosedSource_Dcos_IntegrationTests_ProvisioningTestGenconfBashDownloadS3
https://teamcity.mesosphere.io/viewLog.html?buildId=304196&buildTypeId=ClosedSource_Dcos_IntegrationTests_ProvisioningTestGenconfBashDownloadS3
https://teamcity.mesosphere.io/viewLog.html?buildId=304178&buildTypeId=DcosIo_Dcos_VagrantIntegrationTests_ProvisioningTestGenconfBashMaster



 Comments   
Comment by Anonymous [ 20/Jun/16 ]

Does this happen in on the AWS deploys? This is from DCOS HEAD, right?

Comment by Cody Maloney (Inactive) [ 20/Jun/16 ]

Those were all the ones in the past 72 hours or so. I don't know if AWS ones have hit before. Definitely the vagrant hits it a lot more.

Comment by Sargun Dhillon (Inactive) [ 20/Jun/16 ]

Is there anything different about Vagrant? More / fewer nodes? Start times? Etc?

Comment by Anonymous [ 20/Jun/16 ]

It's a different way of starting VMs. it's zookeeper backed exhibitor. That whole test is just running: https://github.com/dcos/dcos/blob/master/test_util/run-all

Generated at Wed May 18 08:44:37 CDT 2022 using JIRA 7.8.4#78004-sha1:5704c55c9196a87d91490cbb295eb482fa3e65cf.