Closed Softvision-RemusDranca closed 2 years ago
Here are some facts I've gathered about this issue:
bio config apply
command./hab/cache/keys/
./hab/cache/keys/
directory, and they have their permissions corrected properly. This is because they were deposited there during the AMI provisioning stage. (This might not be a fact, since I'm uncertain about when the AMI provisioning step occurs.)Based on that information, here are some possible solutions to choose from:
We have deployed a fix for this issue to the beta stacks. Existing beta stacks will not be fixed automatically. You will have to either terminate all your EC2 instances, or destroy and re-create the stacks for the fix to take effect.
I have verified this issue and it's no longer reproducible. Now when editing the server settings fields and saving the changes we get a "Settings saved" pop-up message.
I think we can mark this as closed. The fix involved re-deploying the janus-gateway (dialog) package with a proper key file, so there wasn't a code change involved. Feel free to reopen if needed.
Confirming this issue no longer reproduces.
[Affected Versions]:
[Affected Platforms]:
[Prerequisites]:
[Steps to reproduce]:
[Expected results]:
[Actual results]:
[Notes]: