service: Avoid reading product mount points too early #1264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Changes in #1236 introduced a bug reading the product mount points.
The list of mount points was read just after selecting a new product. At that time, the storage service has not updated its config yet, so it still uses the previous product.
Note that the manager service calls to storage
#probe
when a new product is selected, and the storage service updates its config as part of the call to#probe
. For that reason, the product mount points cannot be updated until probe is done.https://bugzilla.suse.com/show_bug.cgi?id=1225348
Solution
Do not update the product mount points when the product changes. The list of product mount points is automatically refreshed once the probing is done.