You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But if the domain is unknown, vdsm fallbacks to search the storage
domain in all connected servers:
158def_findUnfetchedDomain(self, sdUUID):
...
171self.log.info("Looking up domain %s", sdUUID)
172withutils.stopwatch(
173"Looking up domain {}".format(sdUUID),
174level=logging.INFO,
175log=self.log):
176formodin (blockSD, glusterSD, localFsSD, nfsSD):
177try:
178returnmod.findDomain(sdUUID)
179exceptse.StorageDomainDoesNotExist:
180pass181exceptException:
182self.log.error(
183"Error while looking for domain `%s`",
184sdUUID, exc_info=True)
In this case, when looking up the storage domain in blockSD, we run lvm vgs (and fail).
Actions
_findUnfetchedDomain looks for the storage domain in all storage domain types, and it could not find it.
Why is the storage domain unknown?
Domains find methods are added to knownSDs dict when connecting
to storage server. They should not be deleted when the domain is in use.
Maybe there is a bug in this mechanism?
We should investigate this, fix the issue, and verify it.
The text was updated successfully, but these errors were encountered:
Description of problem
This bug was split from downstream bug ID 2048545.
When looking up a storage domain, vdsm uses the domain find method:
But if the domain is unknown, vdsm fallbacks to search the storage
domain in all connected servers:
In this case, when looking up the storage domain in blockSD, we run lvm vgs (and fail).
Actions
_findUnfetchedDomain
looks for the storage domain in all storage domain types, and it could not find it.Why is the storage domain unknown?
Domains find methods are added to knownSDs dict when connecting
to storage server. They should not be deleted when the domain is in use.
Maybe there is a bug in this mechanism?
We should investigate this, fix the issue, and verify it.
The text was updated successfully, but these errors were encountered: