Carbon Black Cloud: Delay in sensor upgrade after previous upgrade job was stopped

Products

• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)
• Carbon Black Cloud Enterprise EDR (formerly Cb Threathunter)

Issue/Introduction

• Previously created upgrade job was stopped (for any reason)
• New upgrade job created for sensor included in stopped job
• Sensor does not upgrade for about 4 hours after initial job was stopped.

Environment

• Carbon Black Cloud Sensor:  All versions

Cause

• Carbon Black Cloud Backend will delay sending upgrade hints to sensors with stopped upgrade jobs to allow time for them to finish in case they were in process at the time the upgrade job was stopped.  
• Delay is 4 hours
• This delay cannot be disabled and is not configurable.

Resolution

Wait 4 hours for sensor to upgrade or wait 4 hours after stopping an existing upgrade job before creating a new one for the same sensors.