Bug 1745506 - mock no longer works, complaints about not finding the mock group
Summary: mock no longer works, complaints about not finding the mock group
Keywords:
Status: CLOSED DUPLICATE of bug 1740545
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-26 09:39 UTC by Wouter Verhelst
Modified: 2019-08-26 12:33 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-26 12:33:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Wouter Verhelst 2019-08-26 09:39:40 UTC
Description of problem:

Running mock in a docker container, as root, fails with an error message related to the mock group not existing

Version-Release number of selected component (if applicable):

mock-1.4.16-2.fc30.noarch
mock-core-configs-31.1-1.fc30.noarch

How reproducible:

Always

Steps to Reproduce:
1. docker run -ti fedora:latest /bin/bash
2. inside the docker container, run "dnf -y install mock git", and wait for it to complete
3. run "getent group mock"
4. run "mock", without arguments (or with arguments, it doesn't matter)

Actual results:

"getent group mock" produces no output. "mock" produces the following output:

ERROR: "getgrnam(): name not found: 'mock'"
Traceback (most recent call last):
  File "/usr/libexec/mock/mock", line 977, in <module>
    main()
  File "/usr/lib/python3.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace
    result = func(*args, **kw)
  File "/usr/libexec/mock/mock", line 644, in main
    mockgid = grp.getgrnam('mock').gr_gid
KeyError: "getgrnam(): name not found: 'mock'"


Expected results:

Either the mock group should exist after installing the package, or mock should be able to continue without it.

Additional info:

Comment 1 Miroslav Suchý 2019-08-26 12:33:29 UTC

*** This bug has been marked as a duplicate of bug 1740545 ***


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