April 2015 - golang - Fedora mailing-lists

[Bug 1210364] New: Embedded kubelet cadvisor fails to enumerate docker containers
by Red Hat Bugzilla 29 Jun '16

29 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1210364 Bug ID: 1210364 Summary: Embedded kubelet cadvisor fails to enumerate docker containers Product: Fedora Version: 22 Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: stefw(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Description of problem: The cAdvisor embedded in kubelet fails to enumerate docker containers. It fails with the message: failed to get all Docker containers with error: unable to find data for container /system.slice/docker-....scope Version-Release number of selected component (if applicable): kubernetes-0.13.2-0.5.git8d94c43.fc22.x86_64 How reproducible: Every time. Tried restarting Docker. Steps to Reproduce: 1. http://localhost:4194/api/v1.2/docker 1. Or just go to http://localhost:4194 and click on 'Docker Containers' to see the same thing. Actual results: failed to get all Docker containers with error: unable to find data for container /system.slice/docker-9dade0a01bf0368b6c0dad722f7e85af98593dde00873e6abb2cfd86d2d2b7a9.scope Expected results: Output like this: {"/system.slice/docker-1a0bda816225dc1fcae4e9f0583f982664675f66d523095513ff01694c3311e1.scope":{"name":"/system.slice/docker-1a0bda816225dc1fcae4e9f0583f982664675f66d523095513ff01694c3311e1.scope","aliases":["k8s_ruby-helloworld.8ec853e6_frontend-58wav_default_19192267-d9c8-11e4-b2d6-10c37bdb8410_025ed744","1a0bda816225dc1fcae4e9f0583f982664675f66d523095513ff01694c3311e1"],"namespace":"docker","spec":{"creation_time":"0001-01-01T00:00:00Z","has_c... Additional info: When running standalone cadvisor I get the above expected output. cadvisor-0.10.1-0.1.gitef7dddf.fc22.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1038683] New: golang appears to contain an ECC implementation
by Red Hat Bugzilla 17 Jun '16

17 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1038683 Bug ID: 1038683 Summary: golang appears to contain an ECC implementation Product: Fedora Version: 20 Component: golang Assignee: adam(a)spicenitz.org Reporter: notting(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, skottler(a)redhat.com, vbatts(a)redhat.com Blocks: 182235 (FE-Legal), 1019390 (ecc) Description of problem: At least, I would assume that's what is in go/src/pkg/crypto/elliptic/. In Fedora, we only ship certain reviewed curves. Version-Release number of selected component (if applicable): 1.2-1 How reproducible: 100% Steps to Reproduce: 1. look at golang's crypto code Actual results: Hey, that looks like ECC, and it appears to have been always included. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=182235 [Bug 182235] Fedora Legal Tracker https://bugzilla.redhat.com/show_bug.cgi?id=1019390 [Bug 1019390] [tracking bug] re-enable ECC/ECDHE/EC/ECDSA/elliptic curves in Fedora -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1046469] New: docker privileged mode with cmd /sbin/init - agetty & high cpu
by Red Hat Bugzilla 08 Jun '16

08 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1046469 Bug ID: 1046469 Summary: docker privileged mode with cmd /sbin/init - agetty & high cpu Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: fortuik(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: docker containers in privileged mode mess with the host agetty and produce very hicht cpu load Version-Release number of selected component (if applicable): Fedora 20 Docker 0.7.1, 0.7.2 How reproducible: docker run -privileged -d mattdm/fedora:latest /sbin/init Actual results: docker container runs cpu load is very high - agetty stopping the container & the docker daemon do not free the cpu resources one have to kill the agetty process Expected results: docker container runs Additional info: In my real case i run rhel containers with puppet & ssh daemons for a small puppet lab. The reason i met this bug is that running docker container with /sbin/init cmd under RHEL 6.5 require priviliged mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1192081] New: Modify base image Dockerfile to enable systemd to run smoothly
by Red Hat Bugzilla 08 Jun '16

08 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1192081 Bug ID: 1192081 Summary: Modify base image Dockerfile to enable systemd to run smoothly Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: vpavlin(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: systemd requires container=docker set in env and /run, /tmp to be mountpoints start successfully. In my opinion, we should add ENV container=docker VOLUME ['/run', '/tmp'] to the base image Dockerfile. Command docker run --it --rm -v /sys/fs/cgroup:/sys/fs/cgroup:ro fedora:rawhide /usr/sbin/init would then be all an user would need to "boot" systemd in a container. I've already made some changes in KS file - remove fstab and machine-id, mask mount units... which make the boot sequence smooth. More changes to boot sequence will probably come later (f.e. switch from graphical.target to multi-user target) I'd also like to suggest new Rawhide build to be pushed to registry. This one works for me quite well: http://koji.fedoraproject.org/koji/taskinfo?taskID=8883309 -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1192848] New: docker no longer supports socket-activation
by Red Hat Bugzilla 03 Jun '16

03 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1192848 Bug ID: 1192848 Summary: docker no longer supports socket-activation Product: Fedora Version: 21 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: tim(a)gfxmonk.net QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Version-Release number of selected component (if applicable): docker-io-1.4.1-8.fc21.x86_64 How reproducible: Always Steps to Reproduce: $ docker ps Actual results: FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this host? Expected results: /var/run/docker.sock should automatically start `docker.service` via socket activation. This was the case on fedora 20. Additional info: I looked in the package history, and it looks like it was disabled by: commit aecb9bfe55824e2c9c7be4afce3ac8dd7e3395f5 Author: Lokesh Mandvekar <lsm5(a)fedoraproject.org> Date: Fri Jan 16 17:06:40 2015 +0000 docker group and socket activation not used NVR: docker-io-1.4.1-7 - sysconfig file updates Signed-off-by: Lokesh Mandvekar <lsm5(a)fedoraproject.org> I assume there's a reason for this, but there's no bugzilla or other issue reference, and no description of why the functionality should be removed. The removal of socket activation is pretty annoying, so it would be great if it could be re-enabled. If it can't be enabled, it would be good to document why. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1214778] New: Tracker for golang-github-prometheus-procfs
by Red Hat Bugzilla 31 May '16

31 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214778 Bug ID: 1214778 Summary: Tracker for golang-github-prometheus-procfs Product: Fedora Version: rawhide Component: golang-github-prometheus-procfs Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-prometheus-procfs for rawhide and other fedora distribution. As golang devel packages are used only as a build-time dependency at the moment, this tracker keeps updates and other information about this package, e.g. broken dependencies, exceptions, important pieces of information and other issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 39

[Bug 1091538] New: golang crashing on ARMv7
by Red Hat Bugzilla 09 May '16

09 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1091538 Bug ID: 1091538 Summary: golang crashing on ARMv7 Product: Fedora Version: rawhide Component: golang Assignee: adam(a)spicenitz.org Reporter: pbrobinson(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Blocks: 245418 (ARMTracker) We're getting an crash with go when I try and enable go support for ARM in the swig package. http://koji.fedoraproject.org/koji/taskinfo?taskID=6780663 It's currently just a scratch build as I obviously can't push it if it fails. checking Examples/go/callback checking Examples/go/class unexpected fault address 0x40440000 fatal error: fault [signal 0xb code=0x1 addr=0x40440000 pc=0x40440000] goroutine 1 [running]: runtime.throw(0x15691f) /usr/lib/golang/src/pkg/runtime/panic.c:464 +0x5c fp=0xb6ba5f7c runtime: unexpected return pc for runtime.sigpanic called from 0x40440000 runtime.sigpanic() /usr/lib/golang/src/pkg/runtime/os_linux.c:237 +0xa8 fp=0xb6ba5f88 goroutine 3 [syscall]: runtime.goexit() /usr/lib/golang/src/pkg/runtime/proc.c:1394 checking Examples/go/constants make[3]: *** [go_run] Error 2 make[2]: *** [check] Error 2 make[1]: *** [class.actionexample] Error 2 checking Examples/go/enum checking Examples/go/extend checking Examples/go/funcptr checking Examples/go/multimap checking Examples/go/pointer checking Examples/go/reference checking Examples/go/simple checking Examples/go/template checking Examples/go/variables Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=245418 [Bug 245418] Tracker for ARM support -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1211266] New: Tracking bugzilla for kubernetes updates
by Red Hat Bugzilla 07 May '16

07 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1211266 Bug ID: 1211266 Summary: Tracking bugzilla for kubernetes updates Product: Fedora Version: rawhide Component: kubernetes Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Tracker used for kubernetes updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 86

[Bug 1200612] New: Package rocksdb binary for Fedora
by Red Hat Bugzilla 03 May '16

03 May '16

https://bugzilla.redhat.com/show_bug.cgi?id=1200612 Bug ID: 1200612 Summary: Package rocksdb binary for Fedora Product: Fedora Version: rawhide Component: golang-github-influxdb-rocksdb Assignee: jchaloup(a)redhat.com Reporter: ggillies(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com Hi, With influxdb version 0.9 moving to completely utilise rocksdb, we probably want to look at expanding this package to fully provide a rocksdb compiled binary. That is, a rocksdb package that has /usr/bin/rocksdb, as well as the devel package with the raw go code for deps (which this package currently provides) Regards, Graeme -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1100000] New: can't run iscsid in a docker container
by Red Hat Bugzilla 11 Apr '16

11 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1100000 Bug ID: 1100000 Summary: can't run iscsid in a docker container Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: jslagle(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Created attachment 898086 --> https://bugzilla.redhat.com/attachment.cgi?id=898086&action=edit iscsid strace showing failure Description of problem: Can't start iscsid in a docker container Version-Release number of selected component (if applicable): # rpm -q docker-io docker-io-0.11.1-3.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. use the published fedora image, docker pull fedora 2. start the container, docker run -t -i fedora /bin/bash 3. install iscsi-initiator-utils 4. try to start iscsid: bash-4.2# iscsid -f iscsid: can not bind NETLINK_ISCSI socket strace also attached -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1096273] New: repetition of signal 21 with --sig-proxy and SIGSTOP of docker
by Red Hat Bugzilla 05 Apr '16

05 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1096273 Bug ID: 1096273 Summary: repetition of signal 21 with --sig-proxy and SIGSTOP of docker Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Severity: low Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Depends On: 1087704 +++ This bug was initially created as a clone of Bug #1087704 +++ Description of problem: I noticed weird reaction to SIGSTOP signal. When you start container with --sig-proxy, ignore all signals in container and from OS use kill -SIGSTOP to the `docker run` process, it's put into background. (so far correct behavior) Than when you use kill -SIGCONT, it's resumed (still in background) and it's continuing to send signal 21 to the container (100% CPU utilization). This disappears once you attach the process with fg. Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. kill -SIGSTOP $PID 4. kill -SIGCONT $PID Actual results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... Received 21, ignoring... ... (100% CPU utilization, when you use fg it stops and you can use the container again...) Expected results: [1]+ Pozastavena /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' [root@t530 ~]# Received 21, ignoring... Additional info: I'm not definitely sure if this is really required as it's not a common usage. But as there is no way to detach the process apart from kill -SIGSTOP people might use it and get to this problem... --- Additional comment from Lukas Doktor on 2014-05-05 03:59:30 EDT --- I retested this with the upstream dc9c28f/0.10.0 with the same results. The daemon output is: ... [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) [/home/medic/Work/Projekty/Docker/root|fa3816b6] -job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) = OK (0) 2014/05/05 09:58:13 POST /v1.10/containers/b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5/kill?signal=TTIN [/home/medic/Work/Projekty/Docker/root|fa3816b6] +job kill(b01a849cb45ebe94c3a61fa021a5464186345d5b159faee4ea9d5da39fb36de5, TTIN) ... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087704 [Bug 1087704] repetition of signal 21 with --sig-proxy and SIGSTOP of docker -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1202517] New: docker fd leak
by Red Hat Bugzilla 02 Apr '16

02 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1202517 Bug ID: 1202517 Summary: docker fd leak Product: Red Hat Enterprise Linux 7 Version: 7.2 Component: docker Assignee: dwalsh(a)redhat.com Reporter: dwalsh(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: adimania(a)gmail.com, admiller(a)redhat.com, arozansk(a)redhat.com, b(a)wtnb.mydns.jp, dwalsh(a)redhat.com, extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jeder(a)redhat.com, jmario(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, srao(a)redhat.com, thrcka(a)redhat.com, tstclair(a)redhat.com, vbatts(a)redhat.com, vgoyal(a)redhat.com Depends On: 1189028 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1189028 [Bug 1189028] docker fd leak -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1189028] New: docker 1.4.1-3.el6 fd leak
by Red Hat Bugzilla 02 Apr '16

02 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1189028 Bug ID: 1189028 Summary: docker 1.4.1-3.el6 fd leak Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: b(a)wtnb.mydns.jp QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: docker daemon doesn't close file descriptor. Version-Release number of selected component (if applicable): docker-io-1.4.1-3.el6.x86_64 How reproducible: Steps to Reproduce: 1. while true; do docker run -t -i --rm busybox /bin/true ; done 2. (in other terminal) DEBUG=1 docker info 3. check values at Fds: and Goroutines: lines Actual results: Fds and Goroutines values are increased forever Expected results: Additional info: - It doesn't happen on RHEL7 + docker 1.4.1 - It doesn't happen on RHEL6 + docker-io-1.3.2-2.el6.x86_64 # lsof -p $(pidof docker) <snip> docker 7771 root 14u REG 0,9 0 3791 [eventfd] docker 7771 root 15u REG 0,9 0 3791 [eventfd] docker 7771 root 16r REG 0,21 0 20709 /cgroup/memory/docker/98b529e398bec4568c58ea96088aef1535eca504bed6453bab8f6f7803d31cfb/memory.oom_control (deleted) docker 7771 root 17u REG 0,9 0 3791 [eventfd] docker 7771 root 18r REG 0,21 0 21176 /cgroup/memory/docker/bc213d3e80815021780064874665fe80801c5a1010d1c0bc4bd5b118ca45d11f/memory.oom_control (deleted) docker 7771 root 19u REG 0,9 0 3791 [eventfd] docker 7771 root 20r REG 0,21 0 21626 /cgroup/memory/docker/7b8d59ec4f23c14e2732726594460ccf89fe31c06e60fabbdc4e358f794af102/memory.oom_control (deleted) docker 7771 root 21w REG 0,9 0 3791 [eventfd] docker 7771 root 22r REG 0,21 0 22112 /cgroup/memory/docker/99ac44fcb18a3e1aea00a5e7cfb040942f2c4f2c673c291105c367788e49d0f2/memory.oom_control (deleted) docker 7771 root 24r REG 0,21 0 22672 /cgroup/memory/docker/b1804ae48289df81d3a5c54167baf729612e12c552ef98917df90d8645d235ad/memory.oom_control (deleted) <snip> # ps $(pidof docker) m PID TTY STAT TIME COMMAND 7771 pts/0 - 0:09 /usr/bin/docker -d - - Sl 0:02 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:00 - - - Sl 0:01 - - - Sl 0:00 - <snip> -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1214958] New: etcd-v2.1.0-alpha.0 is available
by Red Hat Bugzilla 01 Apr '16

01 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214958 Bug ID: 1214958 Summary: etcd-v2.1.0-alpha.0 is available Product: Fedora Version: rawhide Component: etcd Keywords: FutureFeature, Triaged Assignee: lacypret(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: avagarwa(a)redhat.com, eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lacypret(a)gmail.com, lemenkov(a)gmail.com, lsm5(a)redhat.com, walters(a)redhat.com Latest upstream release: v2.1.0-alpha.0 Current version/release in rawhide: 2.0.10-1.fc23 URL: https://github.com/coreos/etcd Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1214769] New: Tracker for golang-github-spf13-cobra
by Red Hat Bugzilla 17 Mar '16

17 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214769 Bug ID: 1214769 Summary: Tracker for golang-github-spf13-cobra Product: Fedora Version: rawhide Component: golang-github-spf13-cobra Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-spf13-cobra for rawhide and other fedora distribution. As golang devel packages are used only as a build-time dependency at the moment, this tracker keeps updates and other information about this package, e.g. broken dependencies, exceptions, important pieces of information and other issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 36

[Bug 1214797] New: Tracker for golang-github-matttproud-golang_protobuf_extensions
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214797 Bug ID: 1214797 Summary: Tracker for golang-github-matttproud-golang_protobuf_extensions Product: Fedora Version: rawhide Component: golang-github-matttproud-golang_protobuf_extensions Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-matttproud-golang_protobuf_extensions for rawhide and other fedora distribution. As golang devel packages are used only as a build-time dependency at the moment, this tracker keeps updates and other information about this package, e.g. broken dependencies, exceptions, important pieces of information and other issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1214731] New: Tracker for golang-github-spf13-pflag
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214731 Bug ID: 1214731 Summary: Tracker for golang-github-spf13-pflag Product: Fedora Version: rawhide Component: golang-github-spf13-pflag Assignee: lsm5(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-spf13-pflag for rawhide and other fedora distribution. As golang devel packages are used only as a build-time dependency at the moment, this tracker keeps updates and other information about this package, e.g. broken dependencies, exceptions, important pieces of information and other issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1214784] New: Tracker for golang-github-prometheus-client_golang
by Red Hat Bugzilla 15 Mar '16

15 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1214784 Bug ID: 1214784 Summary: Tracker for golang-github-prometheus-client_golang Product: Fedora Version: rawhide Component: golang-github-prometheus-client_golang Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-prometheus-client_golang for rawhide and other fedora distribution. As golang devel packages are used only as a build-time dependency at the moment, this tracker keeps updates and other information about this package, e.g. broken dependencies, exceptions, important pieces of information and other issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 36

[Bug 1215656] New: Tracker for golang-github-fsouza-go-dockerclient
by Red Hat Bugzilla 21 Feb '16

21 Feb '16

https://bugzilla.redhat.com/show_bug.cgi?id=1215656 Bug ID: 1215656 Summary: Tracker for golang-github-fsouza-go-dockerclient Product: Fedora Version: rawhide Component: golang-github-fsouza-go-dockerclient Assignee: lsm5(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, eparis(a)redhat.com, extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Tracker for async updates of golang-github-fsouza-go-dockerclient for rawhide and other fedora distribution. As golang devel packages are used only as a build-time dependency at the moment, this tracker keeps updates and other information about this package, e.g. broken dependencies, exceptions, important pieces of information and other issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 48

[Bug 1204620] New: container stays around wihtout any processes in it
by Red Hat Bugzilla 17 Feb '16

17 Feb '16

https://bugzilla.redhat.com/show_bug.cgi?id=1204620 Bug ID: 1204620 Summary: container stays around wihtout any processes in it Product: Fedora Version: 22 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mvollmer(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Created attachment 1005245 --> https://bugzilla.redhat.com/attachment.cgi?id=1005245&action=edit Setup script for reproducing Description of problem: When running a specific custom image (see attachement), docker fails to notice when the single process exits. The container stays around, and attempts to stop or remove it result in errors. Doing the same with a slightly older version of docker shows expected behavior. Version-Release number of selected component (if applicable): docker-io-1.5.0-19.git5d7adce.fc22.x86_64 How reproducible: Always. Steps to Reproduce: 1. Run the attached SETUP script in an empty directory 2. Run the resulting image # docker run --name=probe cp /bin/container-probe 3. After wrestling control back from the hanging "docker run", try to stop or remove the container. # docker stop probe # docker rm -f probe Actual results: The expected output of container-probe is shown, but "docker run ..." does not return to the command line prompt. In fact, job control doesn't work anymore either (C-c, C-z, C-\). Stopping and removing leads to these errors: # docker stop probe Error response from daemon: Cannot stop container probe: active container for c492b7203b3d465c778935f97a12b3bf8a4c442731c7fd25cee6f50798ac4f65 does not exist FATA[0000] Error: failed to stop one or more containers # docker rm -f probe Error response from daemon: Could not kill running container, cannot remove - active container for c492b7203b3d465c778935f97a12b3bf8a4c442731c7fd25cee6f50798ac4f65 does not exist FATA[0000] Error: failed to remove one or more containers Expected results: The output is shown and "docker run" terminates successfully, the container is show as "exited" and can be removed. Additional info: docker-io-1.5.0-1.fc21.x86_64 shows the expected behavior. "docker run -i" return control to the shell, but the resulting container can't be stopped or removed either. "systemctl restart docker" puts the "probe" container into a state where it can be removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1145659] New: [PATCH] Support /etc/sysconfig/docker-storage
by Red Hat Bugzilla 07 Jan '16

07 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1145659 Bug ID: 1145659 Summary: [PATCH] Support /etc/sysconfig/docker-storage Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)fedoraproject.org Reporter: walters(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, dwalsh(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, jperrin(a)centos.org, lsm5(a)fedoraproject.org, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com, virt-bugs(a)redhat.com Depends On: 1144206 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1144206 [Bug 1144206] [PATCH] Support /etc/sysconfig/docker-storage -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1096296] New: man page inaccuracy about --sig-proxy and --tty
by Red Hat Bugzilla 07 Jan '16

07 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1096296 Bug ID: 1096296 Summary: man page inaccuracy about --sig-proxy and --tty Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com, whenry(a)redhat.com Depends On: 1087697 +++ This bug was initially created as a clone of Bug #1087697 +++ Description of problem: Hi guys, the man page states: --sig-proxy=true: Proxify all received signal to the process (even in non-tty mode) But the real behavior is, that sig-proxy doesn't work when --tty=true. It should be mentioned in there, taht --sig-proxy is incompatible with --tty. Version-Release number of selected component (if applicable): docker-io-0.9.1-1.fc21.x86_64 How reproducible: always Steps to Reproduce: 1. man docker Actual results: man page says it works even in non-tty Expected results: man page warns that --tty can't be used with --sig-proxy How to verify: 1. docker run --tty=true -i --rm fedora bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps -ax | grep docker 3. kill -SIGUSR1 $PID 4. (with --tty=true no signals are received, when you try the same with --tty=false, signals are proxified and messages are displayed) --- Additional comment from Lokesh Mandvekar on 2014-04-15 02:11:48 EDT --- Copying William (he recently got per subcommand manpages merged upstream). this seems to be the case even in the latest manpage (I'm guessing this was inherited from the original manpage). William, was there any discussion about this in your PR? --- Additional comment from Lokesh Mandvekar on 2014-04-15 02:15:31 EDT --- btw, the 0.10 rpm includes the latest manpages (should be in yum soon) --- Additional comment from Lukas Doktor on 2014-04-15 04:45:55 EDT --- Thanks for a quick reply. I tried the docker-io-0.10.0-2.fc20.x86_64 which says: --sig-proxy=true|false: When set to true, proxify all received signals to the process (even in non-tty mode). The default is true. I'd really like to change it to "only in non-tty" with possible warning that --tty=true is incompatible with --sig-proxy. --- Additional comment from William Henry on 2014-04-30 15:54:25 EDT --- I go this text from upstream. I'll check. --- Additional comment from William Henry on 2014-04-30 16:02:22 EDT --- Lukas,according to the folks upstream, this is a bug in docker run and attach. It should be as the text suggests. Can you file a bug upstream with docker? Here: https://github.com/dotcloud/docker/issues Please just take the information you posted above and post it there. Thanks. Well spotted. Best, William --- Additional comment from Lukas Doktor on 2014-05-02 04:02:01 EDT --- Upstream tracer: https://github.com/dotcloud/docker/issues/5547 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087697 [Bug 1087697] man page inaccuracy about --sig-proxy and --tty -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1096276] New: signal 27 (SIGPROF) not passed to container using --sig-proxy
by Red Hat Bugzilla 07 Jan '16

07 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1096276 Bug ID: 1096276 Summary: signal 27 (SIGPROF) not passed to container using --sig-proxy Product: Red Hat Enterprise Linux 7 Version: 7.1 Component: docker Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: virt-bugs(a)redhat.com CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Depends On: 1087720 +++ This bug was initially created as a clone of Bug #1087720 +++ Description of problem: When I send signal 27 to the docker process, which is running with --sig-proxy=true, it's not forwarded. Other signals are... Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.9.1-1.fc21.x86_64 upstream Docker version 0.10.0, build dc9c28f/0.10.0 How reproducible: always Steps to Reproduce: 1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done' 2. ps ax |grep docker 3. kill -27 $PID Actual results: nothing Expected results: Received 27, ignoring... Additional info: When you send any other signal (apart from 19 or 9) it works fine. --- Additional comment from Lukas Doktor on 2014-04-15 04:59:24 EDT --- The signal 17 is also ignored. --- Additional comment from Lukas Doktor on 2014-05-05 03:48:25 EDT --- The same bug is in upstream Docker version 0.10.0, build dc9c28f/0.10.0 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1087720 [Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1217613] New: Cannot start container [8] System error: mountpoint for cpuset not found
by Red Hat Bugzilla 02 Dec '15

02 Dec '15

https://bugzilla.redhat.com/show_bug.cgi?id=1217613 Bug ID: 1217613 Summary: Cannot start container [8] System error: mountpoint for cpuset not found Product: Fedora Version: 21 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: jiri.folta(a)centrum.cz QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Created attachment 1020711 --> https://bugzilla.redhat.com/attachment.cgi?id=1020711&action=edit screenshot of the error Description of problem: when trying to run a container using Cockpit I get "System error: mountpoint for cpuset not found" error Version-Release number of selected component (if applicable): cockpit: Version 0.27. Built on Wed Mar 25 12:53:20 UTC 2015. How reproducible: allways Steps to Reproduce: 1.Install minimal Fedora 21 for arm platform from http://www.digitaldreamtime.co.uk/images/Fidora/21/ 2.update the system 3.install cockpit and docker 4.login to the server using web interface https://ip:9090 5.download Image: docker.io/wordpress:latest 6. try running the image Actual results: you get an error message(attached) Expected results: actually running the image Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1212190] New: Unable to 'docker login' with 1.6.0-0.1.rc6.fc21
by Red Hat Bugzilla 02 Dec '15

02 Dec '15

https://bugzilla.redhat.com/show_bug.cgi?id=1212190 Bug ID: 1212190 Summary: Unable to 'docker login' with 1.6.0-0.1.rc6.fc21 Product: Fedora Version: 21 Component: docker-io Keywords: Extras Assignee: ichavero(a)redhat.com Reporter: agoldste(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adimania(a)gmail.com, admiller(a)redhat.com, dwalsh(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, ichavero(a)redhat.com, jchaloup(a)redhat.com, jperrin(a)centos.org, lsm5(a)redhat.com, lsu(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Depends On: 1212188 The same issue reported below exists in 1.6.0-0.1.rc6.fc21 +++ This bug was initially created as a clone of Bug #1212188 +++ Description of problem: I'm unable to 'docker login' using 1.6.0-2.el7 Version-Release number of selected component (if applicable): docker-1.6.0-2.el7 How reproducible: 100% Steps to Reproduce: 1. docker login -u <user> -p <pass> -e <email> Actual results: FATA[0001] Post http:///var/run/docker.sock/v1.18/auth: EOF. Are you trying to connect to a TLS-enabled daemon without TLS? Expected results: WARNING: login credentials saved in /home/vagrant/.dockercfg. Login Succeeded Additional info: >From journalctl: time="2015-04-15T13:18:12-04:00" level=info msg="POST /v1.18/auth" time="2015-04-15T13:18:12-04:00" level=info msg="+job auth()" time="2015-04-15T13:18:12-04:00" level=info msg="-job auth()" 2015/04/15 13:18:12 http: panic serving @: runtime error: invalid memory address or nil pointer dereference goroutine 2838 [running]: net/http.funcÂ·011() /usr/lib/golang/src/net/http/server.go:1130 +0xbb fp=0xc20810d4c8 sp=0xc20810d3e8 runtime.call16(0xc20810def0, 0xc209c32510, 0x0) /usr/lib/golang/src/runtime/asm_amd64.s:401 +0x45 fp=0xc20810d4e0 sp=0xc20810d4c8 runtime.gopanic(0xb15060, 0xc20802a050) /usr/lib/golang/src/runtime/panic.go:387 +0x3a8 fp=0xc20810d548 sp=0xc20810d4e0 runtime.panicmem() /usr/lib/golang/src/runtime/panic.go:42 +0x4e fp=0xc20810d570 sp=0xc20810d548 runtime.sigpanic() /usr/lib/golang/src/runtime/sigpanic_unix.go:26 +0x274 fp=0xc20810d5c0 sp=0xc20810d570 github.com/docker/docker/registry.NewEndpoint(0x0, 0xc1e1d0, 0x0, 0x0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/registry/endpoint.go:47 +0x31 fp=0xc20810d620 sp=0xc20810d5c0 github.com/docker/docker/registry.(*Service).Auth(0xc20802e340, 0xc208d91900, 0x2) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/registry/service.go:64 +0x168 fp=0xc20810d730 sp=0xc20810d620 github.com/docker/docker/registry.*Service.AuthÂ·fm(0xc208d91900, 0x7fac53e860a0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/registry/service.go:33 +0x31 fp=0xc20810d750 sp=0xc20810d730 github.com/docker/docker/engine.(*Job).Run(0xc208d91900, 0x0, 0x0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/engine/job.go:90 +0x936 fp=0xc20810d8a0 sp=0xc20810d750 github.com/docker/docker/api/server.postAuth(0xc2080e20d0, 0xc208984c27, 0x4, 0x7fac53ead348, 0xc208d917c0, 0xc20893e000, 0xc20933a6c0, 0x0, 0x0) /builddir/build/BUILD/docker-b27feb4ff804f335c80861b17a4e2bfc29fbbf45/_build/src/github.com/docker/docker/api/server/server.go:189 +0x292 fp=0xc20810d9e0 sp=0xc20810d8a0 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1212188 [Bug 1212188] Unable to 'docker login' with 1.6.0-2.el7 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang April 2015