-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins LTS 2.60.3-cb-1
Jobs are not getting assigned to labeled nodes. While digging into this, we discovered some cases where the node labels are not appearing on the node status page. When looking at the node config page, the labels do exist.
- Agent is configured as (slave-it0400-config.jpg)
- After saving the agent configration, assigned labels are not being showed on the slave status page (slave-it0400-status.jpg)
But labels are actually serialized in the agent `config.xml` (slave-it0400-configfile.xml)
Browse details as follows:
Browser
=======
* Screen size: 2560x1440
* User Agent
- Type: Browser
- Name: Chrome
- Family: CHROME
- Producer: Google Inc.
- Version: 62.0.3202.94
- Raw: `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36`
* Operating System
- Name: Windows
- Family: WINDOWS
- Producer: Microsoft Corporation.
- Version: 10.0
HAR file seems normal in terms of HTTP response codes (buildmaster-alpha.devsnc.com-slave-it0400.har)
- duplicates
-
-
- Resolved
-
- links to
[JENKINS-48563] Agent Labels missing in GUI
| Description |
Original:
Jobs are not getting assigned to labeled nodes. While digging into this, we discovered some cases where the node labels are not appearing on the node status page. When looking at the node config page, the labels do exist. * Agent is configured as (slave-it0400-config.jpg) * After saving the agent configration, assigned labels are not being showed on the slave status page (slave-it0400-status.jpg) Labels are actually serialized in the agent `config.xml` (slave-it0400-configfile.xml) Browse details as follows: {code:java} Browser ======= * Screen size: 2560x1440 * User Agent - Type: Browser - Name: Chrome - Family: CHROME - Producer: Google Inc. - Version: 62.0.3202.94 - Raw: `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36` * Operating System - Name: Windows - Family: WINDOWS - Producer: Microsoft Corporation. - Version: 10.0 {code} HAR file seems normal in terms of HTTP response codes (buildmaster-alpha.devsnc.com-slave-it0400.har). Not reproducible in running it on MacOSX as Server and Web Client Windows Server 12 with Chrome 62.0. |
New:
Jobs are not getting assigned to labeled nodes. While digging into this, we discovered some cases where the node labels are not appearing on the node status page. When looking at the node config page, the labels do exist. * Agent is configured as (slave-it0400-config.jpg) * After saving the agent configration, assigned labels are not being showed on the slave status page (slave-it0400-status.jpg) But labels are actually serialized in the agent `config.xml` (slave-it0400-configfile.xml) Browse details as follows: {code:java} Browser ======= * Screen size: 2560x1440 * User Agent - Type: Browser - Name: Chrome - Family: CHROME - Producer: Google Inc. - Version: 62.0.3202.94 - Raw: `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36` * Operating System - Name: Windows - Family: WINDOWS - Producer: Microsoft Corporation. - Version: 10.0 {code} HAR file seems normal in terms of HTTP response codes (buildmaster-alpha.devsnc.com-slave-it0400.har) |
| Summary | Original: Agent Label missing in GUI | New: Agent Labels missing in GUI |
| Component/s | New: core [ 15593 ] | |
| Component/s | Original: remoting [ 15489 ] |
Remoting does not manage labels, it's the Jenkins Core functionality
IIRC agent labels are updated in background threads. Check the thread dump to see whether there's something delayed there.
danielbeck I opened this issue on behalf of jnewblanc.
jnewblanc - Can you please provide the requested input when the issue is exposed? The output from Required Data: CJP/CJT Hang Issue On Linux might be really useful in this context.
IIRC agent labels are updated in background threads. Check the thread dump to see whether there's something delayed there.