Project

General

Profile

Actions
Copy link

Bug #50044

closed

mgr/dashboard: nodeenv can hang

Added by David Galloway about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Build, CI, Dependencies & Tools
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific,octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
40616
Crash signature (v1):
Crash signature (v2):

Description

Occasionally seeing nodeenv hang indefinitely. This locks up a Jenkins builder from being able to run anything else.

I will leave a job in this state: https://jenkins.ceph.com/job/ceph-dev-new-setup/53776/console

Job log:

Collecting nodeenv
  Using cached nodeenv-1.5.0-py2.py3-none-any.whl (21 kB)
Installing collected packages: nodeenv
Successfully installed nodeenv-1.5.0

On the server:

root@slave-ubuntu02:~# ps auxfwww | grep -A4 make 
root      6138  0.0  0.0  16796  2080 pts/0    S+   20:18   0:00                      \_ grep --color=auto -A4 make
root      3849  0.0  0.0  67384  3612 ?        Ss   Mar18   0:04 /usr/lib/postfix/sbin/master -w
postfix   3851  0.0  0.0  73860  4784 ?        S    Mar18   0:01  \_ qmgr -l -t unix -u
postfix   6028  0.0  0.0  73812  5048 ?        S    20:00   0:00  \_ pickup -l -t unix -u -c
syslog    4308  0.0  0.0 263044  3052 ?        Ssl  Mar18   0:00 /usr/sbin/rsyslogd -n
--
jenkins+  3344  0.0  0.0  15384  3260 ?        S    Mar24   0:00      \_ /bin/bash -e ./make-dist 16.1.0-1122-g8f1779fd
jenkins+  7551  0.0  0.0  59492 20388 ?        S    Mar24   0:00          \_ /tmp/tmp.xg9l0kC3A5/bin/python2 /tmp/tmp.xg9l0kC3A5/bin/nodeenv -p --node=12.18.2
uuidd    27544  0.0  0.0  28448  1240 ?        Ss   Mar18   0:00 /usr/sbin/uuidd --socket-activation
dgallow+   566  0.0  0.0  76700  7544 ?        Ss   18:23   0:00 /lib/systemd/systemd --user
dgallow+   567  0.0  0.0 259276  1964 ?        S    18:23   0:00  \_ (sd-pam)

Related issues 3 (0 open — 3 closed)

Copied to Dashboard - Backport #50170: octopus: mgr/dashboard: nodeenv can hangResolvedAvan ThakkarActions
Copied to Dashboard - Backport #50171: pacific: mgr/dashboard: nodeenv can hangResolvedAvan ThakkarActions
Copied to Dashboard - Backport #50172: nautilus: mgr/dashboard: nodeenv can hangResolvedAvan ThakkarActions
Actions
Copy link
 #1

Updated by David Galloway about 3 years ago

  • Copied from Bug #43961: mgr/dashboard: New version of angular doesn't work with Node.js v10.16.0 added
Actions
Copy link
 #2

Updated by David Galloway about 3 years ago

  • Copied from deleted (Bug #43961: mgr/dashboard: New version of angular doesn't work with Node.js v10.16.0)
Actions
Copy link
 #3

Updated by Ernesto Puerta about 3 years ago

  • Pull request ID changed from 33059 to 40616
Actions
Copy link
 #4

Updated by Ernesto Puerta about 3 years ago

  • Status changed from New to Fix Under Review
  • Backport changed from all to pacific,octopus,nautilus
Actions
Copy link
 #5

Updated by Ernesto Puerta about 3 years ago

The first trace to be displayed would be a

 * Install prebuilt node (XX.YY.ZZ) ... done

So not seeing that might mean a failure during the network connection to the node repo.

Let's start by adding more verbosity to the command.

Actions
Copy link
 #6

Updated by Ernesto Puerta about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #7

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50170: octopus: mgr/dashboard: nodeenv can hang added
Actions
Copy link
 #8

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50171: pacific: mgr/dashboard: nodeenv can hang added
Actions
Copy link
 #9

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50172: nautilus: mgr/dashboard: nodeenv can hang added
Actions
Copy link
 #10

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 160 to Build, CI, Dependencies & Tools
Actions
Copy link
 #11

Updated by Ernesto Puerta about 3 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF