Project

Profile

Help

Issue #3563

Travis tests are failing for pulp

Added by daviddavis over 1 year ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
High
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
3. High
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 35

Description

There's a new pulp-smash test ArtifactsDeleteFileSystemTestCase and it's failing in Travis. Here's an example of the failure:

https://travis-ci.org/pulp/pulp/jobs/364883594

Relevant output:

pulpcore/api_v3/test_crd_artifacts.py::ArtifactsDeleteFileSystemTestCase::test_all <- ../../../virtualenv/python3.5.5/lib/python3.5/site-packages/pulp_smash/tests/pulp3/pulpcore/api_v3/test_crd_artifacts.py The authenticity of host 'localhost (127.0.0.1)' can't be established.
ECDSA key fingerprint is 11:ea:b3:83:4b:31:e1:b7:65:17:48:b8:8d:dd:5a:3c.
Are you sure you want to continue connecting (yes/no)? 
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Looks like it's waiting on stdin.

Associated revisions

Revision 84897a78 View on GitHub
Added by dalley over 1 year ago

Merge pull request #3430 from dkliban/fix-smash-failure

closes #3563

Revision 84897a78 View on GitHub
Added by dalley over 1 year ago

Merge pull request #3430 from dkliban/fix-smash-failure

closes #3563

Revision 84897a78 View on GitHub
Added by dalley over 1 year ago

Merge pull request #3430 from dkliban/fix-smash-failure

closes #3563

History

#1 Updated by daviddavis over 1 year ago

  • Tags Pulp 3 added

#2 Updated by dalley over 1 year ago

  • Priority changed from Normal to High
  • Severity changed from 2. Medium to 3. High
  • Triaged changed from No to Yes
  • Sprint set to Sprint 35

#3 Updated by Ichimonji10 over 1 year ago

<ichimonji10> The CLI client is trying to SSH into the local host.
<ichimonji10> I assume Smash is running on the same host that's being tested?
<dkliban> yes
<ichimonji10> Either SSH can be configured, OR things can be tweaked so that a local shell is spawned.
<ichimonji10> The latter option is probably preferred.
<dkliban> ichimonji10: https://github.com/pulp/pulp/blob/3.0-dev/.travis/pulp-smash-config.json
<dkliban> that's the config we are using
<dkliban> ichimonji10: can we modify it to fix this problem?
<ichimonji10> Easily.
<ichimonji10> There's one of two solutions.
<ichimonji10> One solution is to make the hostname be equal to the output of socket.getfqdn().
<ichimonji10> https://github.com/pulp/pulp/blob/3.0-dev/.travis/pulp-smash-config.json#L8
<dkliban> what's the other solution? though i think we can work with this one
<ichimonji10> The other solution is to insert 'transport': 'local' here: https://github.com/pulp/pulp/blob/3.0-dev/.travis/pulp-smash-config.json#L17

#4 Updated by dkliban@redhat.com over 1 year ago

  • Status changed from NEW to MODIFIED

#6 Updated by dalley over 1 year ago

  • Assignee set to dkliban@redhat.com

#7 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#8 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF