EnsureJujudPassword fails if the registry keys are not present
Bug #1475779 reported by
Bogdan Teleaga
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Bogdan Teleaga |
Bug Description
EnsureJujudPassword will fail in case cloudinit is not executed on windows machines(i.3. when upgrading).
The key *could* be created if it's not found, which would be the easy fix. However it was requested that we set a number of ACL's on the key and the API's on the registry package are not suitable for this, which is the reason it was initially done in cloudinit. Since this obviously won't work, I need to do some research on finding the proper syscalls to get the permissions set.
This bug is filed so we don't release without the ability to upgrade.
Changed in juju-core: | |
assignee: | nobody → Bogdan Teleaga (bteleaga) |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.25.0 |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
In case we need to hurry, I could just exec the existing powershell code in cloudinit.
Reference: https:/ /github. com/juju/ juju/blob/ master/ cloudconfig/ windows_ userdata_ test.go# L828-L832