Opened 5 years ago

Last modified 21 months ago

#2770 new defect

LatentSlaveBuilder status does not get reset to LATENT when detached

Reported by: skelly Owned by:
Priority: major Milestone: 0.9.+
Version: 0.8.8 Keywords: virtualization
Cc:

Description (last modified by sa2ajj)

When insubstantiating a latent slave, its slavebuilders' status doesn't get reset to LATENT. On subsequent builds, the SlaveBuilder list passed to nextSlave will incorrectly note the slave as IDLE instead of LATENT.

Change History (5)

comment:1 Changed 5 years ago by dustin

  • Keywords virtualization added
  • Milestone changed from undecided to 0.8.+

comment:2 Changed 4 years ago by dustin

  • Milestone changed from 0.8.+ to 0.9.+

Ticket retargeted after milestone closed

comment:3 Changed 4 years ago by sa2ajj

  • Description modified (diff)

I am not sure I understand the desired behaviour: when the build is finished, but the buildslave is not shut down, it'd show IDLE. As soon as it's down, it'd become LATENT.

comment:4 Changed 4 years ago by skelly

Clarifying the description a bit more:

In the list of SlaveBuilder objects passed to !nextSlave, the slave's status after finishing a build is IDLE. When a slave is insubstantiated, however, the slave's status remains as IDLE. The status attribute in the SlaveBuilder object is not reset to LATENT, the state it has before first substantiation.

Last edited 4 years ago by skelly (previous) (diff)
Note: See TracTickets for help on using tickets.