-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asd-discovery detects asds from another env and tries to connect while it shouldn't #269
Comments
This behaviour was in the past considered as a feature ... |
Please lay your egg what should be done. |
From the FWK point of view this isn't used anymore for Alba ASD's, but what in case of Kinetic, @toolslive ? This will have to be re-introduced? |
For Kinetic, this isn't an issue as you'll always have the hardware to connect to the drive you've discovered: It's always ethernet. |
If I understand correctly no further solution is needed (for how deployments are currently done by the framework). |
Indeed. |
asd-discovery process detects asds belonging to another alba and tries to connect but it doesn't have the hardware required to do that
To be investigated
The text was updated successfully, but these errors were encountered: