hashicorp/packer · error

the build for the component %q does not have a valid id

Error message

the build for the component %q does not have a valid id

What it means

HCP registry error from Bucket.UpdateBuildStatus: the local build entry for the named component has an empty ID, meaning it was never registered with HCP (Initialize/startBuild not completed), so its remote status cannot be updated.

Source

Thrown at internal/hcp/registry/types.bucket.go:276

	return nil
}

// UpdateBuildStatus updates the status of a build entry on the HCP Packer registry with its current local status.
// For updating a build status to DONE use CompleteBuild.
func (bucket *Bucket) UpdateBuildStatus(
	ctx context.Context, name string, status hcpPackerModels.HashicorpCloudPacker20230101BuildStatus,
) error {
	if status == hcpPackerModels.HashicorpCloudPacker20230101BuildStatusBUILDDONE {
		return fmt.Errorf("do not use UpdateBuildStatus for updating to DONE")
	}

	buildToUpdate, err := bucket.Version.Build(name)
	if err != nil {
		return err
	}

	if buildToUpdate.ID == "" {
		return fmt.Errorf("the build for the component %q does not have a valid id", name)
	}

	if buildToUpdate.Status == hcpPackerModels.HashicorpCloudPacker20230101BuildStatusBUILDDONE {
		return fmt.Errorf("cannot modify status of DONE build %s", name)
	}

	_, err = bucket.client.UpdateBuild(ctx,
		bucket.Name,
		bucket.Version.Fingerprint,
		buildToUpdate.ID,
		buildToUpdate.RunUUID,
		"",
		"",
		"",
		"",
		nil,
		status,
		nil,

View on GitHub (pinned to eb36e3c3e4)

Solutions

1. Ensure bucket.Initialize ran successfully before updating build statuses
2. Check earlier errors that may have skipped the initial build creation

When it happens

Trigger: Thrown at internal/hcp/registry/types.bucket.go:276 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of hashicorp/packer@eb36e3c3e4 (2026-09-05). Data as JSON: /api/errors/0a43772bce60f219. Report an issue: GitHub.