golang February 2016

golang@lists.fedoraproject.org

2 participants
213 discussions

[Bug 1246207] New: Tracker for golang-github-boltdb-bolt
by Red Hat Bugzilla 06 Apr '16

06 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1246207 Bug ID: 1246207 Summary: Tracker for golang-github-boltdb-bolt Product: Fedora Version: rawhide Component: golang-github-boltdb-bolt Severity: low Priority: low Assignee: fpokorny(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com Tracker for async updates of golang-github-boltdb-bolt 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 42

[Bug 1312886] New: Flannel service fails on reboot
by Red Hat Bugzilla 06 Apr '16

06 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1312886 Bug ID: 1312886 Summary: Flannel service fails on reboot Product: Fedora Version: 23 Component: flannel Severity: medium Assignee: jchaloup(a)redhat.com Reporter: surajd(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, linville(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Description of problem: flanneld service fails to start when restarting the Fedora 23 cloud Vagrant Box. Version-Release number of selected component (if applicable): flanneld - 0.5.4 fedora/23-cloud-base vagrant box How reproducible: Easily reproducible Steps to Reproduce: (pre-requisite = start etcd service on some other machine, here: 192.168.121.45) 1. Get a fedora/23-cloud-base vagrant box and start it. 2. Install flannel using dnf 3. Do configuration of flannel in /etc/sysconfig/flanneld as following [root@fedminion2 ~]# cat /etc/sysconfig/flanneld FLANNEL_ETCD="http://192.168.121.45:2379" FLANNEL_ETCD_KEY="/fedmaster/network" 4. enable the flannel service to autostart using systemctl 5. exit out of the box, halt it and do vagrant up again. 6. Once inside the machine check the status of flanneld service. Actual results: The service fails as: **Failed to get default interface: Unable to find default route** This is also reported at http://ask.projectatomic.io/en/question/3553/flanneld-fails-when-vm-starts/ Expected results: The service should start Additional info: I fixed this problem by changing the value in "/usr/lib/systemd/system/flanneld.service" of "After=network.target" to "After=network-online.target" -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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 1286185] New: Tracker for golang-github-opencontainers-specs
by Red Hat Bugzilla 02 Apr '16

02 Apr '16

https://bugzilla.redhat.com/show_bug.cgi?id=1286185 Bug ID: 1286185 Summary: Tracker for golang-github-opencontainers-specs Product: Fedora Version: rawhide Component: golang-github-opencontainers-specs Assignee: fpokorny(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com Tracker for async updates of golang-github-opencontainers-specs 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 33

[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 1298116] New: kubernetes: Improper admission check control
by Red Hat Bugzilla 31 Mar '16

31 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1298116 Bug ID: 1298116 Summary: kubernetes: Improper admission check control Product: Security Response Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: amaris(a)redhat.com CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jcajka(a)redhat.com, jchaloup(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com It was found that patch will check admission control with an empty object and if it passes, then will proceed to update the object with the patch. Admission control plugins don't get a chance to see/validate what is actually going to be updated. CVE request: http://seclists.org/oss-sec/2016/q1/76 Upstream patch: https://github.com/deads2k/kubernetes/commit/d1e258afcf837cf70522c2950bb0ae… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1298117] New: kubernetes: Improper admission check control [fedora-all]
by Red Hat Bugzilla 31 Mar '16

31 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1298117 Bug ID: 1298117 Summary: kubernetes: Improper admission check control [fedora-all] Product: Fedora Version: 23 Component: kubernetes Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: jchaloup(a)redhat.com Reporter: amaris(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org, jcajka(a)redhat.com, jchaloup(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Blocks: 1298116 This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs] Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1298116 [Bug 1298116] kubernetes: Improper admission check control -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1311861] New: kubectl exec is broken in kubernetes-1.2.0-0.4.alpha1
by Red Hat Bugzilla 31 Mar '16

31 Mar '16

https://bugzilla.redhat.com/show_bug.cgi?id=1311861 Bug ID: 1311861 Summary: kubectl exec is broken in kubernetes-1.2.0-0.4.alpha1 Product: Fedora Version: 23 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, jcajka(a)redhat.com, jchaloup(a)redhat.com, nhorman(a)redhat.com, vbatts(a)redhat.com Description of problem: The 'kubectl exec' command has regressed, and produces this failure: error: error executing remote command: Error executing command in container: Unrecognized input header Version-Release number of selected component (if applicable): # rpm -q kubernetes kubernetes-1.2.0-0.4.alpha1.git4c8e6f4.fc23.x86_64 How reproducible: Every time Steps to Reproduce: 1. Run some pods. 2. Run the code below. Actual results: # rpm -q kubernetes kubernetes-1.2.0-0.4.alpha1.git4c8e6f4.fc23.x86_64 # rpm -q docker docker-1.10.2-1.git86e59a5.fc23.x86_64 # docker exec k8s_mock-container.88f1f36_mock-aogwd_default_d53a657a-db98-11e5-8811-9e005dd50001_39e4050e date Thu Feb 25 08:39:58 UTC 2016 # kubectl get pods NAME READY STATUS RESTARTS AGE mock-aogwd 1/1 Running 0 2m mock-cxirx 1/1 Running 0 2m # kubectl exec mock-aogwd -- date error: error executing remote command: Error executing command in container: Unrecognized input header Expected results: # rpm -q kubernetes kubernetes-1.1.0-0.17.git388061f.fc23.x86_64 # rpm -q docker docker-1.9.1-6.git6ec29ef.fc23.x86_64 # kubectl get pods NAME READY STATUS RESTARTS AGE mock-on1bw 1/1 Running 0 46s mock-ra9ad 1/1 Running 0 36s # kubectl exec mock-on1bw -- date Thu Feb 25 08:36:13 UTC 2016 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

← Newer
1
2
3
4
5
6
7
8
9
...
22
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang February 2016