RC9 : Snapin dissociate from hosts
- Version: 1.3-RC9
- OS: Debian 8.5
- Version: 0.11.5
- OS: Win 10
ok it will be a little bit hard to explain, but to deploy snapin since RC9, I have to upload snapin file again. If not, snapin is no more associate to hosts (no membership).
After upload, it generates File hash and at this point, i can associate again snapin to host.
I have to do this for each snapin, so it’s annoying…
Should be fixed in latest working branch. Nearly had to recode the whole method, but it is much cleaner, and is creating the hash for us. From what I can see, it’s also downloading the files where appropriate as well.
I’m sure there’s still a couple of kinks (though I can’t see what or where).
@Tom-Elliott My building is stand-alone. I was just testing out the latest, and it upgraded fine. I’m reverting back to the snapshot I took beforehand after I do a few tests.
@Wayne-Workman I don’t where the issue resides but it sounds a lot like the issue from yesterday where you update but the update doesn’t reflect as expected. For example updating a node but all main is going to a non updated system first.
@Tom-Elliott This is not solved yet.
I’m on 1.3.0 working-RC-10 version 27, pre-existing snapins will still not deploy.
@Tom-Elliott ok great, so I’m waiting ! With RC10, all snapin will work gain directly ? Or do we have to re-upload snapin file once for each ?
@Matthieu-Jacquart this has been addressed already for RC 10 which I hope to push out tonight due to multicast unusable. After I fix upload issue of course.