Unable to run git clone command on KVM in Intel SDPs

Bug #1828786 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
High
Sean Feole

Bug Description

Tests like ubunut-kvm-unit-tests, ubuntu_stress_smoke_test and etc.
The git clone will failed on automation-vm1 Intel KVM nodes.

Running 'git clone git://kernel.ubuntu.com/cking/stress-ng'
 Cloning into 'stress-ng'...
 fatal: unable to connect to kernel.ubuntu.com:
 kernel.ubuntu.com[0: 91.189.94.216]: errno=Connection timed out

Talked to Sean, he will contact Intel for this.

Revision history for this message
Sean Feole (sfeole) wrote :

The Intel Security Rules opens only the ports: TCP 443, TCP 80 and UDP 53 to outside world. Git uses TCP 9418,

Unforunately the MAAS proxy sits behind the firewall too.

Rather than us going ahead making special use cases for every test that requires a clone, I have asked intel to open up access for us, they told me this is a 3 week process. We are in week #2.

Changed in ubuntu-kernel-tests:
status: New → Confirmed
assignee: nobody → Sean Feole (sfeole)
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

I think this is affecting the LXC test as well:
  ERROR: Unable to fetch GPG key from keyserver.

Revision history for this message
Sean Feole (sfeole) wrote :

Requested an update from intel today on the ETA to get the fix implemented.

Changed in ubuntu-kernel-tests:
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello,
any update on this?
Thanks!

Revision history for this message
Sean Feole (sfeole) wrote :

Intel has updated me today reporting this is fixed. Please let me know if you see otherwise.

Changed in ubuntu-kernel-tests:
status: In Progress → Won't Fix
status: Won't Fix → Fix Committed
Revision history for this message
Sean Feole (sfeole) wrote :

validated fix earlier, ok to close

Changed in ubuntu-kernel-tests:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.