golang June 2015

golang@lists.fedoraproject.org

2 participants
110 discussions

[Bug 1215336] New: godoc uses invalid path for documentation
by Red Hat Bugzilla 04 Jun '15

04 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1215336 Bug ID: 1215336 Summary: godoc uses invalid path for documentation Product: Fedora Version: 21 Component: golang Severity: low Assignee: vbatts(a)redhat.com Reporter: eugene.yudin(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Command "godoc" doesn't show documentation. Version-Release number of selected component (if applicable): golang-godoc.x86_64 1:0-1.0.hgd32b5854c941.fc21 How reproducible: Always. Steps to Reproduce: $ godoc fmt Println 2015/04/25 18:00:38 open /usr/lib/golang/src/pkg/fmt: no such file or directory Workaround: # cd /usr/lib/golang/src/ # ln -s . pkg -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222416] New: etcd-v2.0.11 is available
by Red Hat Bugzilla 04 Jun '15

04 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1222416 Bug ID: 1222416 Summary: etcd-v2.0.11 is available Product: Fedora Version: rawhide Component: etcd Keywords: FutureFeature, Triaged Assignee: jchaloup(a)redhat.com Reporter: jchaloup(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: avagarwa(a)redhat.com, eparis(a)redhat.com, extras-qa(a)fedoraproject.org, golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com, lacypret(a)gmail.com, lemenkov(a)gmail.com, lsm5(a)redhat.com, upstream-release-monitoring(a)fedoraproject.org, walters(a)redhat.com Latest upstream release: v2.0.11 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 11

[Bug 1160833] New: Fedora 21 Beta Atomic Image: broken links, incomplete documentation, missing "docker" executable
by Red Hat Bugzilla 03 Jun '15

03 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1160833 Bug ID: 1160833 Summary: Fedora 21 Beta Atomic Image: broken links, incomplete documentation, missing "docker" executable Product: Fedora Version: 21 Component: docker-io Severity: high Assignee: lsm5(a)fedoraproject.org Reporter: znmeb(a)znmeb.net QA Contact: extras-qa(a)fedoraproject.org CC: admiller(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, miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com, vbatts(a)redhat.com Description of problem: Multiple problems with Fedora 21 Beta Atomic Image: broken links, incomplete documentation, missing "docker" executable Version-Release number of selected component (if applicable): Atomic Images beta Steps to Reproduce: 1. Browse to http://fedoraproject.org/en/get-prerelease#cloud. 2. Attempt to download and discover broken link to qcow2 and raw disk images on the beta release page. 3. Find, download, verify checksum of images at http://mirror.pnl.gov/fedora/linux/releases/test/21-Beta/Cloud/Images/x86_6… 4. Prepare an initialization ISO file as described in http://www.projectatomic.io/docs/quickstart/ and https://www.technovelty.org//linux/running-cloud-images-locally.html. Note that said documentation a. Is *not* part of the Fedora documentation, which is something I expect for something carrying the "Fedora Cloud" brand, and b. Nowhere is it *explicitly* stated that the username is "fedora" or that once you log in as "fedora", "sudo su -" works to get you into "root" on the console. 5. Log in as "fedora", type "sudo su -" and type "docker ps". Actual results: '-bash: docker: command not found' Expected results: 1. Working links on the beta release page 2. Fedora-branded documentation with the username and how to obtain root. 3. Docker installed and ready to create images and containers. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1187649] New: Fedora:latest docker image d-bus unknown error -1
by Red Hat Bugzilla 03 Jun '15

03 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1187649 Bug ID: 1187649 Summary: Fedora:latest docker image d-bus unknown error -1 Product: Fedora Version: 21 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: cyborg101010(a)gmail.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: When trying to use anything that relies on D-Bus, on Fedora:latest, you get the error: Failed to get D-Bus connection: Unknown error -1 How reproducible: 100% Steps to Reproduce: 1. Attach to Fedora:latest 2. yum install postgresql-server -y 3. systemctl start postgresql Actual results: Failed to get D-Bus connection: Unknown error -1 Expected results: Systemd starts postgres Additional info: It's not just postgres, I've tried with others. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1216153] New: Docker daemon runs in shared mount namespace
by Red Hat Bugzilla 03 Jun '15

03 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1216153 Bug ID: 1216153 Summary: Docker daemon runs in shared mount namespace Product: Fedora EPEL Version: el6 Component: docker-io Assignee: ichavero(a)redhat.com Reporter: michaeljameswells+redhatbugzilla(a)gmail.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, 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 Description of problem: The docker daemon is run in a shared mount namespace, causing problems when restarting the docker service. This prevents starting up containers where mounts remain in place. Version-Release number of selected component (if applicable): 1.5.0-1.el6 How reproducible: Always Steps to Reproduce: 1. docker run -d --name test centos sleep infinity 2. service docker restart 3. docker start test Actual results: Error response from daemon: Cannot start container test: Error getting container 0412d5cce356ff269bd85b2096eb8bc0b2cc58a67096c6c6587a85f7e82f0b77 from driver devicemapper: Error mounting '/dev/mapper/docker-253:0-2097716-0412d5cce356ff269bd85b2096eb8bc0b2cc58a67096c6c6587a85f7e82f0b77' on '/var/lib/docker/devicemapper/mnt/0412d5cce356ff269bd85b2096eb8bc0b2cc58a67096c6c6587a85f7e82f0b77': device or resource busy FATA[0000] Error: failed to start one or more containers Expected results: Container to start. Additional info: A merged pull request containing updated sysvinit script is found here: https://github.com/docker/docker/pull/10225 It was merged prior to the 1.5.0 release and involves running "unshare -m" when starting the docker daemon to place it into its own mount namespace. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216265] New: docker exec -it bash cannot start a shell session
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1216265 Bug ID: 1216265 Summary: docker exec -it bash cannot start a shell session Product: Fedora Version: 22 Component: docker-io Severity: high Assignee: ichavero(a)redhat.com Reporter: robberphex(a)gmail.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, 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 Description of problem: `docker exec -it <name> /bin/bash` cannot work Version-Release number of selected component (if applicable): $ uname -a Linux rp.fedora 4.0.0-0.rc5.git4.1.fc22.x86_64 #1 SMP Fri Mar 27 13:51:23 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ sudo docker version Client version: 1.6.0 Client API version: 1.18 Go version (client): go1.4.2 Git commit (client): 0591dce/1.6.0 OS/Arch (client): linux/amd64 Server version: 1.6.0 Server API version: 1.18 Go version (server): go1.4.2 Git commit (server): 0591dce/1.6.0 OS/Arch (server): linux/amd64 How reproducible: Steps to Reproduce: 1. `sudo docker run --name some-nginx -d nginx:1.7` 2. `sudo docker exec -it some-nginx /bin/bash` Actual results: <no output> Expected results: start a bash session Additional info: `sudo docker exec -it some-nginx echo hello` also have no ouput. but `sudo docker exec some-nginx echo hello` get the output('hello'). -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1224417] New: add selinux label for /var/lib/kubelet
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1224417 Bug ID: 1224417 Summary: add selinux label for /var/lib/kubelet Product: Fedora Version: rawhide Component: docker-io Assignee: ichavero(a)redhat.com Reporter: eparis(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, 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 can we get system_u:object_r:svirt_sandbox_file_t:s0 added as the filecontext for /var/lib/kubelet to the docker-selinux package? can/should we maybe break docker-selinux into it's own package? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1096286] New: "docker top all" doesn't show processes when --tty=false
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1096286 Bug ID: 1096286 Summary: "docker top all" doesn't show processes when --tty=false 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: 1088259 +++ This bug was initially created as a clone of Bug #1088259 +++ After using the same magic required for the upstream docker 0.10 this behaves the same on RHEL docker-0.10.0-8.el7.x86_64 Description of problem: Hi guys, when I run docker with --tty=false, the `docker top $NAME all` doesn't show any processes (just headers). When using only `docker top $NAME` it shows them... Also the `ps` command inside container works, but `ps all` does not. Version-Release number of selected component (if applicable): docker-0.10.0-8.el7.x86_64 docker-io-0.9.0-3.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -i --tty=false fedora bash 2. docker logs $NAME Actual results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND Expected results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 24006 23954 20 0 11732 540 - R pts/14 0:00 bash --- Additional comment from Lukas Doktor on 2014-05-05 03:41:35 EDT --- Can't reproduce with the upstream Docker version 0.10.0, build dc9c28f/0.10.0 top doesn't work at all (due of https://bugzilla.redhat.com/show_bug.cgi?id=1088125 ) --- Additional comment from Lukas Doktor on 2014-05-05 03:46:07 EDT --- OK I moved it to the old cgroup location and the results are the same. So booth, fedora docker-io-0.9.0-3.fc20.x86_64 and upstream dc9c28f/0.10.0 are unable to list processes using `all` argument in non-tty mode. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1088259 [Bug 1088259] "docker top all" doesn't show processes when --tty=false -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1088259] New: "docker top all" doesn't show processes when --tty=false
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1088259 Bug ID: 1088259 Summary: "docker top all" doesn't show processes when --tty=false Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(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, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: Hi guys, when I run docker with --tty=false, the `docker top $NAME all` doesn't show any processes (just headers). When using only `docker top $NAME` it shows them... Also the `ps` command inside container works, but `ps all` does not. Version-Release number of selected component (if applicable): docker-io-0.9.0-3.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. docker run -i --tty=false fedora bash 2. docker logs $NAME Actual results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND Expected results: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 24006 23954 20 0 11732 540 - R pts/14 0:00 bash -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1226810] New: golang-vim package removed? (go syntax highlighting in vim)
by Red Hat Bugzilla 02 Jun '15

02 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1226810 Bug ID: 1226810 Summary: golang-vim package removed? (go syntax highlighting in vim) Product: Fedora Version: 22 Component: golang Severity: low Assignee: vbatts(a)redhat.com Reporter: keesdejong+bugs(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: In Fedora 21 the package 'golang-vim' was available: http://rpmfind.net/linux/rpm2html/search.php?query=golang-vim How reproducible: `dnf search golang | grep vi` returns no results. Additional info: If the package is orphaned or something like that then I would like to know. Then I will package and maintain it. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang June 2015