[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Jenkins image build step stucks on Git cloning step



Thank you for your response.

The problem was because I was using the internet of my Samsung Smartphone via Hotspot. Please, could you tell me how I can use OpenShift using the internet of my Smartphone?

2017-11-02 1:37 GMT+01:00 Ben Parees <bparees redhat com>:
can you confirm that your pods have external connectivity?  (oc rsh into the jenkins pod and see if you can reach external addresses from it).

If not (and i suspect you can't), you have a networking issue or perhaps you need to go through a proxy?


On Wed, Nov 1, 2017 at 6:17 PM, Tien Hung Nguyen <tienhng nguyen gmail com> wrote:
Hi,

However, the build is stucking at the step pulling the source from git:

Commit: 70cff8557908b592d291e6ea0b3a018069b61324 (updated README)
Author: Siamak Sadeghianfar <ssadeghi redhat com>
Date: Thu Apr 6 18:48:41 2017 +0700


It's not moving forward anymore.

This is my environment:

$ oc version
>> Output

oc v3.6.1+008f2d5

kubernetes v1.6.1+5115d708d7

features: Basic-Auth


Server https://127.0.0.1:8443

openshift v3.7.0-rc.0+de54b6e-89

kubernetes v1.7.6+a08f5eeb62

<<


$ oc describe node localhost 

Name: localhost
Role:
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/hostname=localhost
Annotations: volumes.kubernetes.io/controller-managed-attach-detach=true
Taints: <none>
CreationTimestamp: Wed, 01 Nov 2017 23:02:14 +0100
Phase:
Conditions:
  Type Status LastHeartbeatTime LastTransitionTime Reason Message
  ---- ------ ----------------- ------------------ ------ -------
  OutOfDisk False Wed, 01 Nov 2017 23:09:45 +0100 Wed, 01 Nov 2017 23:02:14 +0100 KubeletHasSufficientDisk kubelet has sufficient disk space available
  MemoryPressure False Wed, 01 Nov 2017 23:09:45 +0100 Wed, 01 Nov 2017 23:02:14 +0100 KubeletHasSufficientMemory kubelet has sufficient memory available
  DiskPressure False Wed, 01 Nov 2017 23:09:45 +0100 Wed, 01 Nov 2017 23:02:14 +0100 KubeletHasNoDiskPressure kubelet has no disk pressure
  Ready True Wed, 01 Nov 2017 23:09:45 +0100 Wed, 01 Nov 2017 23:02:14 +0100 KubeletReady kubelet is posting ready status
Addresses: 192.168.65.2,localhost
Capacity:
 cpu: 4
 memory: 8164736Ki
 pods: 40
Allocatable:
 cpu: 4
 memory: 8062336Ki
 pods: 40
System Info:
 Machine ID: def90f1040ba4fc097a8974c919abf08
 System UUID: 123EC372-2E1E-833C-8227-1CA74349D99D
 Boot ID: b70b1a58-a4ed-4984-800d-86817484b5d7
 Kernel Version: 4.9.49-moby
 OS Image: CentOS Linux 7 (Core)
 Operating System: linux
 Architecture: amd64
 Container Runtime Version: docker://Unknown
 Kubelet Version: v1.7.6+a08f5eeb62
 Kube-Proxy Version: v1.7.6+a08f5eeb62
ExternalID: localhost
Non-terminated Pods: (3 in total)
  Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
  --------- ---- ------------ ---------- --------------- -------------
  ci jenkins-blueocean-1-build 0 (0%) 0 (0%) 0 (0%) 0 (0%)
  default docker-registry-1-zxqmv 100m (2%) 0 (0%) 256Mi (3%) 0 (0%)
  default router-1-v4f2j 100m (2%) 0 (0%) 256Mi (3%) 0 (0%)
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  CPU Requests CPU Limits Memory Requests Memory Limits
  ------------ ---------- --------------- -------------
  200m (5%) 0 (0%) 512Mi (6%) 0 (0%)
Events:
  FirstSeen LastSeen Count From SubObjectPath Type Reason Message
  --------- -------- ----- ---- ------------- -------- ------ -------
  7m 7m 1 kubelet, localhost Normal Starting Starting kubelet.
  7m 7m 2 kubelet, localhost Normal NodeHasSufficientDisk Node localhost status is now: NodeHasSufficientDisk
  7m 7m 2 kubelet, localhost Normal NodeHasSufficientMemory Node localhost status is now: NodeHasSufficientMemory
  7m 7m 2 kubelet, localhost Normal NodeHasNoDiskPressure Node localhost status is now: NodeHasNoDiskPressure
  7m 7m 1 kubelet, localhost Normal NodeAllocatableEnforced Updated Node Allocatable limit across pods



I started the local OpenShift Origin installation with the command 'oc cluster up --version=latest --host-data-dir /Users/oc-data'.
The same is true when I start the local all-in-one cluster with the command 'oc cluster up --host-data-dir /Users/oc-data' (Server oc version 3.6.1).

Last time when I used oc version 3.6.0., that problem didn't occur but I got a problem described in https://github.com/openshift/origin/issues/17019





_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users




--
Ben Parees | OpenShift



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]