Bug 1677948 - Old bug 128967 symptom seems to be back (or patch has failed to apply)
Summary: Old bug 128967 symptom seems to be back (or patch has failed to apply)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: docker
Version: 29
Hardware: armv7hl
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-17 06:14 UTC by PhillB
Modified: 2019-11-27 22:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 22:22:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description PhillB 2019-02-17 06:14:23 UTC
Description of problem:
Starting any container from systemd service file fails.

Version-Release number of selected component (if applicable):
root@localhost run]# rpm -qa | grep docker
docker-rhel-push-plugin-1.13.1-62.git9cb56fd.fc29.armv7hl
docker-1.13.1-62.git9cb56fd.fc29.armv7hl
docker-common-1.13.1-62.git9cb56fd.fc29.armv7hl

How reproducible:
Always

Steps to Reproduce:
1. Take any docker service file for a container
2. systemctl start mydockercontainer
3. fails for all containers.

Actual results:
Feb 17 12:57:26 rpi2host2 dockerd-current[665]: time="2019-02-17T12:57:26.694878781+11:00" level=error msg="Failed to convert loginuid to int: strconv.ParseInt: parsing \"4294967295\": value out of range"


Expected results:
Determines that the logged in UID is not set (which is the meaning of a UID -1). This might be expected since systemd is starting the container, not the logged in user.

Additional info:
It almost looks as if the patch in bug 128967 has not been applied. Worked OK in Fedora 27. Might be a regression.

Comment 1 Ben Cotton 2019-10-31 19:27:14 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-11-27 22:22:11 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.