Environment info

CLI version: 5.13.0
noobaa-image: noobaa/noobaa-core:master-20220913
operator-image: noobaa/noobaa-operator:5.13.0

Actual behavior

1. Default Backing Store is in phase ready, but test pool cannot be used.

Expected behavior

1. Default Backing Store is in phase read and we can use test pool.

Steps to reproduce

See in this PR, take the changes from this commit, or use the instructions here. This issue is related to timing, so if every step will take a couple of minutes, it will not be reproduced (all steps must be done immediately or automatically).

1. Based on the instructions here - the steps of ‘Build images’ and ‘Deploy noobaa’.
2. I’ve noticed that after installing noobaa we need to wait before running the job, otherwise all the tests will be failed.
   kubectl wait --for=condition=available backingstore/noobaa-default-backing-store --timeout=3m
   Do not wait a couple of minutes after this condition is met, immediately move to the next step.
3. Deploy the tests job (run it from the noobaa-core repo):
   
kubectl apply -f src/test/system_tests/ceph_s3_tests/test_ceph_s3_job.yml
4. View the logs:
   kubectl logs job/noobaa-tests-s3 -f

More information - Screenshots / Logs / Other output

The test pool when it will be reproduce (and all the tests will be failed):

{ name: 'noobaa-default-backing-store', resource_type: 'HOSTS', pool_node_type: 'BLOCK_STORE_FS', storage: { total: 84223205376, free: 0, used: 0, reserved: 104857600, unavailable_free: 16048295936, unavailable_used: 0, used_other: 68070051840 }, create_time: 1672658604000, io_stats: { read_count: 0, write_count: 0, read_bytes: 0, write_bytes: 0 }, data_activities: { activities: [], host_count: 0 }, nodes: { count: 1, online: 1, by_mode: { INITIALIZING: 1 } }, storage_nodes: { count: 1, online: 1, by_mode: { INITIALIZING: 1 } }, s3_nodes: { count: 0, online: 0, by_mode: {} }, hosts: { count: 1, by_mode: { INITIALIZING: 1 }, by_service: { STORAGE: 1 }, configured_count: 1 }, host_info: { volume_size: 53687091200 }, is_managed: true, undeletable: 'IN_USE', mode: 'INITIALIZING', associated_accounts: [] }

Describe the solution you'd like
I would like to have an option in nb that would give the actual moment when I can use the default backing store since the solution kubectl wait --for=condition=available backingstore/noobaa-default-backing-store --timeout=3m is not always working.