This job does not have a trace errors when viewing jobs in GitLab 18.X
 

Description

Users may encounter "This job does not have a trace" errors when viewing completed CI/CD jobs after upgrading to GitLab 18.0 or above. This is caused by a migration bug that affects the display of job traces.

 

Impacted offerings:

  • GitLab Self-Managed
     

Impacted versions:

GitLab 18.0 and above

 

Cause

This issue is caused by a migration bug in GitLab 18.0 that affects customers who have both:

  • Object storage enabled
  • Incremental logging previously enabled via the removed feature flag ci_enable_live_trace . This feature flag was normally enabled automatically in GET or Helm Chart deployments, but could also be enabled manually.
     

Solution

To resolve this issue, incremental logging needs to be re-enabled via the GitLab settings.

This will restore the ability to view job traces for affected jobs.
 

Related Links

BackfillCiJobLiveTraceApplicationSetting doesn't enable incremental logging as expected

 

 

On this page...