dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` This ticket will be used throughout the f26 release to track potential blocker bugs and/or important bugs for the next release. A blocker bug is a bug that we will choose not to release on if it is not fixed. An important bug is a bug that we want fixed but may choose not to block on.
**Blocker Bugs** -
**Important Bugs** - none
Over time only the description of this bug will be edited for updates. Please do not add comments to this issue.
``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261
pingou added a new comment to an issue you are following: `` ~~foo~~ ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261
strigazi added a new comment to an issue you are following: `` I tried the following: create a swarm cluster with one manger and two workers, then a secret and finally a service. Then I got:
starting container failed: RemoveSecretsPath failed: remove /var/lib/docker/containers/c51bb7d17d7916462681c0d6b862b3396f28ae965ec5ab604a03e00b2e86e754/secrets/my_secret_data: read-only file system"
To reproduce, boot a F26AH (while writing I tried with one as well) and then do: # docker swarm init # echo "This is a secret" | docker secret create my_secret_data - # docker service create --name="httpd" --secret="my_secret_data" docker.io/httpd # docker service ps httpd
Should I create a BZ?
Also, if I don't put docker.io/ in front of the image it works, but I get "unable to pin image httpd to digest: unknown: Not Found" which is a bit annoying. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261
dustymabe added a new comment to an issue you are following: ``
Are there two separate issues there, or one?
Should I create a BZ?
Yes, Please create a BZ. If two separate issues, then two BZ. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261
strigazi added a new comment to an issue you are following: `` BZ created: https://bugzilla.redhat.com/show_bug.cgi?id=1440389 ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261
dustymabe added a new comment to an issue you are following: ``
BZ created: https://bugzilla.redhat.com/show_bug.cgi?id=1440389 Dusty, I noticed that you didn't want to have comments in this issue, if you want delete them and update the description.
deleting them now :) ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261
dustymabe added a new comment to an issue you are following: `` since we are ready for F26 release we can now close this bug. Only remaining issue is the ansible bug, but there is a workaround put in place in openshift-ansible. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/261
The status of the issue: `Issue Tracker for F26 release blockers` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
-
Dusty Mabe -
Pierre-YvesChibon
-
Spyros Trigazis