uniter_test.go, startUpgradeError{} fails for windows
Bug #1476060 reported by
Tim Penhey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned |
Bug Description
The initial part of this step is to do the following:
appendHook(c, path, "start", "chmod 555 $CHARM_DIR")
Now chmod isn't going to work on windows.
I tried the windows equivalent:
permChange := ("icacls %CHARM_DIR% /grant:r everyone:R\n" +
"icacls %CHARM_DIR% /inheritance:r\n")
appendHook(c, path, "start", permChange)
However that didn't have the desired effect of having the unit in an error state.
So, skipping the particular test in uniter_test.go for windows for now.
Changed in juju-core: | |
milestone: | none → 1.25.0 |
tags: | added: windows |
tags: | added: skipped-test |
Changed in juju-core: | |
milestone: | 1.25.0 → 1.25.1 |
Changed in juju-core: | |
assignee: | nobody → Casey Marshall (cmars) |
Changed in juju-core: | |
assignee: | Casey Marshall (cmars) → nobody |
Changed in juju-core: | |
milestone: | 1.25.1 → 1.26.0 |
Changed in juju-core: | |
milestone: | 1.26.0 → 2.0-beta5 |
Changed in juju-core: | |
milestone: | 2.0-beta5 → 2.0-beta4 |
tags: | added: tech-debt |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.1.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in juju: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
So I don't think file permissions is the way to go here. They're probably not checked on windows
There needs to be another way we can fail the upgrade.