I wasn't able to link the Salesforce ticket to the BZ. I have updated the ticket with a comment piinting to the BZ URL. The case no. if you are interested is 02593519
This bug hasn't had any engineering activity in the last ~30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it and remove the "LifecycleStale" keyword, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
I can't say why there hasn't been traction yet, priorities maybe? I am not aware of any fix being applied for this issue and understand that it remains an issue. Sally, can you clarify the position from your viewpoint please?
This bug hasn't had any activity 7 days after it was marked as LifecycleStale, so we are closing this bug as WONTFIX. If you consider this bug still valuable, please reopen it or create new bug.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
Again, I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
Again, I’m adding UpcomingSprint, will set up Windows + 3.11 and address this bug this sprint.
ahah, I see this when comparing golang "path" vs "path/filepath" packages: from "path" overview: Package path implements utility routines for manipulating slash-separated paths. The path package should only be used for paths separated by forward slashes, such as the paths in URLs. This package does not deal with Windows paths with drive letters or backslashes; to manipulate operating system paths, use the path/filepath package. and "path/filepath" overview: Package filepath implements utility routines for manipulating filename paths in a way compatible with the target operating system-defined file paths. The filepath package uses either forward slashes or backslashes, depending on the operating system. To process paths such as URLs that always use forward slashes regardless of the operating system, see the path package. I see volume.go is indeed using "path" not "path/filepath" I'll update that and that should resolve this issue.
I tested with oc where path->"path/filepath" in set/volume.go and while the mountPath does not have the undesired prefix, it does have a backwards slash, like so: volumeMounts: - mountPath: \app name: test-vol It looks like we'll have to do some string manipulation to get this correct. Working on it.
I've confirmed that this is not an issue in oc 4.4.16, 4.5.4, or latest oc built from master. volumeMounts: - mountPath: /app name: test-vol "path" rather than "path/filepath" package was chosen deliberately in set/volume.go to result in forward rather than backward slash in container mountPath paths. Still working on the proper fix for this in 3.11.
I should have done this first, but I tested on an ocp 3.11 cluster and I cannot reproduce this. Looking at the dc yaml after the set volume cmd from above, I see this: volumeMounts: - mountPath: /app name: test-vol # oc version oc v3.11.265 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-172-18-15-1.ec2.internal:8443 openshift v3.11.265 kubernetes v1.11.0+d4cacc0 Please try this again to let me know if this is still an issue, otherwise I will be closing this.
SFDC case has been closed. As you point out the behaviour is different now. I think it is OK to leave for now and see if there are any further reports.