- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bug in App Volumes 2.9: references to old LUNs are not being updated in App Volume Database
We discovered a new bug in App Volumes:
When you move the appstack templates to a new datastore and afterwards rename/delete the LUN where the templatee originally were located, then it is impossible to update an appstack which was originally created on the initial LUN.
The workaround is to change the reference of the original LUN in the SQL database for each appstack which was created while the app.
The version we are using is 2.9
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Lieven,
This seems like a bug we had in the older version (not quite sure if it is still inthere) were we moved the group we used to assign appstacks.
If you move it to a different OU it cannot see it's groupmembers anymore and thus wont attach appstacks when logging in.
Same resolution though, change the DN in the database for that group.. Or detahc, remove the group in database and reassign again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a known issue and will not have a fix unfortunately until late this year. It's because we track objects based on DN and not SID.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the update Jason.
Just for the record, is it a problem if you manually change the value in the database? Or do you suggest to remove the registry entry and readd it to the manager?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Either is dangerous but both should work and neither is officially supported..