Bug 1666954 - gluster_glusto-patch-check job is failing with permission denied error on run tests
Summary: gluster_glusto-patch-check job is failing with permission denied error on run...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-17 05:16 UTC by Vijay Avuthu
Modified: 2019-01-18 11:46 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-18 11:46:37 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Vijay Avuthu 2019-01-17 05:16:10 UTC
Description of problem:

gluster_glusto-patch-check ( https://ci.centos.org/job/gluster_glusto-patch-check ) job is failing with permission denied error on run tests


https://ci.centos.org/job/gluster_glusto-patch-check/1070/console

05:10:00 TASK [Create an ssh keypair] ***************************************************
05:10:01 fatal: [localhost]: FAILED! => {"changed": true, "cmd": "ssh-keygen -b 2048 -t rsa -f $GLUSTO_WORKSPACE/glusto -q -N \"\"", "delta": "0:00:00.178959", "end": "2019-01-17 05:10:01.386921", "msg": "non-zero return code", "rc": 1, "start": "2019-01-17 05:10:01.207962", "stderr": "Saving key \"/home/gluster/workspace/gluster_glusto-patch-check/centosci/glusto\" failed: Permission denied", "stderr_lines": ["Saving key \"/home/gluster/workspace/gluster_glusto-patch-check/centosci/glusto\" failed: Permission denied"], "stdout": "", "stdout_lines": []}
05:10:01 	to retry, use: --limit @/home/gluster/workspace/gluster_glusto-patch-check/centosci/jobs/scripts/glusto/setup-glusto.retry
05:10:01

Comment 1 Nigel Babu 2019-01-17 07:21:14 UTC
Ack. This is strange, because the user absolutely has permissions. Re-running the exact same ansible script after the job works, so I'm a bit lost as to what's failing. Will dig deeper.

Comment 2 Nigel Babu 2019-01-18 11:46:37 UTC
There seems to an issue with running ssh-keygen via the Jenkins connection. I haven't figured out a solution to that. Instead, I've just generated a key manually in .ssh and we'll be using that for all our jobs. After fixing this bug, I ran into an issue with the python-docx installation failure which is fixed as well.


Note You need to log in before you can comment on or make changes to this bug.