When kube-burner creates custom resources (e.g. VirtualMachine), the .status field is not immediately populated by the controller. The first status check in verifyCondition (waiters.go) logs at level=error even though this is a normal transient state.

Fix: split the error handling — log.Errorf only for actual extraction errors, log.Debugf when status is simply not yet available.

Upstream PR: https://github.com/kube-burner/kube-burner/pull/1147

This eliminates noisy error lines like:

level=error msg="Error extracting or finding status in object VirtualMachine/vm-1: [nil]"