Bug 1325778 - Missing signatures for 1 RPM package
Summary: Missing signatures for 1 RPM package
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhel-server-container
Version: 6.9
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Frantisek Kluknavsky
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-11 07:54 UTC by Alex Jia
Modified: 2017-03-31 14:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-19 21:30:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Alex Jia 2016-04-11 07:54:15 UTC
Description of problem:
The latest rhel-server-docker-6.8-60 is missing signatures for udev package.

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

rhel-server-docker-6.8-60.x86_64.tar.gz

# rpm -q docker kernel
docker-1.9.1-28.el7.x86_64
kernel-3.10.0-289.el7.x86_64


How reproducible:
always

Steps to Reproduce:
1. download rhel-server-docker-6.8-60.x86_64.tar.gz from brew web
2. import downloaed image into docker
3. run the container image
4. check all of RPM pacakges signature

Actual results:

# docker run -it rhel-server-docker-6.8-60.x86_64 /bin/sh

sh-4.1# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.8 Beta (Santiago)

sh-4.1# rpm -qai|grep -i -B6 none
Name        : udev                         Relocations: (not relocatable)
Version     : 147                               Vendor: Red Hat, Inc.
Release     : 2.73.el6                      Build Date: Fri Apr  8 10:10:21 2016
Install Date: Sun Apr 10 21:59:54 2016         Build Host: x86-033.build.eng.bos.redhat.com
Group       : System Environment/Base       Source RPM: udev-147-2.73.el6.src.rpm
Size        : 1280843                          License: GPLv2
Signature   : (none)


Expected results:


Additional info:

Comment 3 Daniel Walsh 2016-08-19 21:30:53 UTC
Most likely this is fixed.  Reopen if I am mistaken.


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