https://bugzilla.redhat.com/show_bug.cgi?id=1482657
Bug ID: 1482657
Summary: The current version of kubernetes should not be
compiled with golang >= 1.8
Product: Fedora
Version: 26
Component: kubernetes
Severity: high
Assignee: jchaloup(a)redhat.com
Reporter: mbayser(a)br.ibm.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
ichavero(a)redhat.com, jbrooks(a)redhat.com,
jcajka(a)redhat.com, jchaloup(a)redhat.com,
nhorman(a)redhat.com, tstclair(a)heptio.com,
vbatts(a)redhat.com
Description of problem:
Because of a change in the go system library from version 1.8, the kubelet has
trouble removing volumes. The issue is described here:
https://github.com/kubernetes/kubernetes/issues/43534 . I've rebuilt the fedora
25 golang-1.7 packages on my fedora 26 server to rebuild the kubernetes
packages and after that this problem was gone.
Version-Release number of selected component (if applicable):
kubernetes-1.6.7-1
How reproducible:
Always
Steps to Reproduce:
Delete pods with volumes.
Actual results:
The pod will be stuck in Terminating state.
Expected results:
The pod should be removed cleanly
Additional info:
A workaround is to remove the pods from /var/lib/kubelet/pods manually and
restart the kubelet
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1367740
Bug ID: 1367740
Summary: golang-github-go-fsnotify-fsnotify FTBFS due to
failing tests on aarch64 d
Product: Fedora
Version: 25
Component: golang-github-go-fsnotify-fsnotify
Assignee: fpokorny(a)redhat.com
Reporter: pbrobinson(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
jchaloup(a)redhat.com
Blocks: 922257 (ARM64,F-ExcludeArch-aarch64)
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3677865
golang-github-go-fsnotify-fsnotify-1.2.0-0.4.git96c060f.fc25
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.1pPWD0
+ umask 022
+ cd /builddir/build/BUILD
+ cd fsnotify-96c060f6a6b7e0d6f75fddd10efeaca3e5d1bcb0
+ export
GOPATH=/builddir/build/BUILDROOT/golang-github-go-fsnotify-fsnotify-1.2.0-0.4.git96c060f.fc25.aarch64//usr/share/gocode:/usr/share/gocode
+
GOPATH=/builddir/build/BUILDROOT/golang-github-go-fsnotify-fsnotify-1.2.0-0.4.git96c060f.fc25.aarch64//usr/share/gocode:/usr/share/gocode
+ go test -compiler gc -ldflags '' github.com/go-fsnotify/fsnotify
--- FAIL: TestPollerWithBadFd (0.14s)
inotify_poller_test.go:70: Expected EBADF, got: function not implemented
--- FAIL: TestPollerWithData (0.14s)
inotify_poller_test.go:62: Failed to create poller: function not
implemented
--- FAIL: TestPollerWithWakeup (0.14s)
inotify_poller_test.go:62: Failed to create poller: function not
implemented
--- FAIL: TestPollerWithClose (0.14s)
inotify_poller_test.go:62: Failed to create poller: function not
implemented
--- FAIL: TestPollerWithWakeupAndData (0.14s)
inotify_poller_test.go:62: Failed to create poller: function not
implemented
--- FAIL: TestPollerConcurrent (0.14s)
inotify_poller_test.go:62: Failed to create poller: function not
implemented
--- FAIL: TestInotifyCloseRightAway (0.14s)
inotify_test.go:20: Failed to create watcher
--- FAIL: TestInotifyCloseSlightlyLater (0.14s)
inotify_test.go:34: Failed to create watcher
--- FAIL: TestInotifyCloseSlightlyLaterWithWatch (0.14s)
inotify_test.go:52: Failed to create watcher
--- FAIL: TestInotifyCloseAfterRead (0.14s)
inotify_test.go:71: Failed to create watcher
--- FAIL: TestInotifyCloseCreate (0.00s)
inotify_test.go:117: Failed to create watcher: function not implemented
--- FAIL: TestInotifyStress (0.00s)
inotify_test.go:162: Failed to create watcher: function not implemented
--- FAIL: TestInotifyRemoveTwice (0.00s)
inotify_test.go:269: Failed to create watcher: function not implemented
--- FAIL: TestFsnotifyMultipleOperations (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyMultipleCreates (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyDirOnly (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyDeleteWatchedDir (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifySubDir (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyRename (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyRenameToCreate (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyRenameToOverwrite (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestRemovalOfWatch (0.09s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyAttrib (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyClose (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestFsnotifyFakeSymlink (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
--- FAIL: TestClose (0.00s)
integration_test.go:50: NewWatcher() failed: function not implemented
FAIL
FAIL github.com/go-fsnotify/fsnotify 1.466s
RPM build errors:
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=922257
[Bug 922257] Tracker for ARM64 support
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1480766
Bug ID: 1480766
Summary: kubectl 1.7.3 bash completion has invalid options
Product: Fedora
Version: 26
Component: kubernetes
Assignee: jchaloup(a)redhat.com
Reporter: giovanni.tirloni(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
ichavero(a)redhat.com, jbrooks(a)redhat.com,
jcajka(a)redhat.com, jchaloup(a)redhat.com,
nhorman(a)redhat.com, tstclair(a)heptio.com,
vbatts(a)redhat.com
Description of problem:
kubectl bash completion has invalid options
Version-Release number of selected component (if applicable):
kubernetes-client-1.6.7-1.fc26.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Type: kubectl get <tab>
2. See options available
3. Try `kubectl get status` or `kubectl get thirdpartyresourcedata` or `kubectl
get cluster`
Actual results:
Error message is displayed: the server doesn't have a resource type "status"
Expected results:
These options are not available in completion options
Additional info:
Tested against minikube 1.7.3
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1426790
Bug ID: 1426790
Summary: Explain how to use the packaged files in Fedora, maybe
in a README.Fedora file
Product: Fedora
Version: rawhide
Component: golang
Assignee: vbatts(a)redhat.com
Reporter: opensource(a)till.name
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, amurdaca(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
jcajka(a)redhat.com, lemenkov(a)gmail.com,
renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
I installed golang and golang-github-kr-pty-devel from Fedora as described in
https://developer.fedoraproject.org/tech/languages/go/go-installation.htmlhttps://developer.fedoraproject.org/tech/languages/go/go-packages.html
but go does not use golang-github-kr-pty-devel without /usr/share/gocode being
added to $GOPATH. But if it is there, go complains that it cannot mkdir/write
to /usr/share/gocode/pkg.
$ export GOPATH=/usr/share/gocode:/home/till/work
$ go install till/test/pty
go install github.com/kr/pty: mkdir /usr/share/gocode/pkg: permission denied
$ export GOPATH=/home/till/work:/usr/share/gocode
$ go install till/test/pty
go install github.com/kr/pty: mkdir /usr/share/gocode/pkg: permission denied
Version-Release number of selected component (if applicable):
golang-1.6.4-3.fc24
How reproducible:
always
Steps to Reproduce:
1. dnf install golang-github-kr-pty-devel golang
2. mkdir -p $HOME/work/src/till/test/pty
export GOPATH=$HOME/work
cat > $HOME/work/src/till/test/pty <<EOF
package main
import (
"github.com/kr/pty"
"io"
"os"
"os/exec"
)
func main() {
c := exec.Command("grep", "--color=auto", "bar")
f, err := pty.Start(c)
if err != nil {
panic(err)
}
go func() {
f.Write([]byte("foo\n"))
f.Write([]byte("bar\n"))
f.Write([]byte("baz\n"))
f.Write([]byte{4}) // EOT
}()
io.Copy(os.Stdout, f)
}
EOF
3. go install till/test/pty
Actual results:
src/till/test/pty/pty.go:4:5: cannot find package "github.com/kr/pty" in any
of:
/usr/lib/golang/src/github.com/kr/pty (from $GOROOT)
/home/till/work/src/github.com/kr/pty (from $GOPATH)
Expected results:
It should install pty to $HOME/work/bin
Additional info:
It works when I do:
mkdir -p $HOME/system-golang
ln -s /usr/share/gocode/src/ $HOME/system-golang/src
export GOPATH=$GOPATH:$HOME/system-golang
If this is the recommended way of using Fedora go packages it should be
documented.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1413669
Bug ID: 1413669
Summary: README.md included in all subpackages
Product: Fedora
Version: rawhide
Component: gofed
Assignee: jchaloup(a)redhat.com
Reporter: fkluknav(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fale(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
jchaloup(a)redhat.com
Description of problem:
spec file generated by gofed contains "%doc README.md" in all subpackages.
Fedora packaging guidelines state that:
MUST: A Fedora package must not list a file more than once in the spec file's
%files listings. (Notable exception: license texts in specific situations)
If I understand it correctly, this is in conflict.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1416829
Bug ID: 1416829
Summary: golang-googlecode-google-api-client: update to a
recent version
Product: Fedora
Version: rawhide
Component: golang-googlecode-google-api-client
Assignee: fpokorny(a)redhat.com
Reporter: fkluknav(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, fpokorny(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
Upstream git repo contains code which is not present in Fedora yet. Updating
will allow to unbundle 'golang(google.golang.org/api/iterator)' and
'golang(google.golang.org/api/option)'
Version-Release number of selected component (if applicable):
0-0.16.gite6294e6
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1360748
Bug ID: 1360748
Summary: update for s390x support
Product: Fedora
Version: rawhide
Component: golang-github-golang-sys
Assignee: fpokorny(a)redhat.com
Reporter: dan(a)danny.cz
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
jchaloup(a)redhat.com
Blocks: 467765 (ZedoraTracker)
Please update to a recent snapshot to gather s390x support -
https://github.com/golang/sys/commit/33267e036fd93fcd26ea95b7bdaf2d8306cb74…
Version-Release number of selected component (if applicable):
golang-github-golang-sys-0-0.4.git9c60d1c.fc25
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=467765
[Bug 467765] Fedora for System z (s390): Bug Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1431306
Bug ID: 1431306
Summary: golang-github-digitalocean-godo-v1.0.0 is available
Product: Fedora
Version: rawhide
Component: golang-github-digitalocean-godo
Keywords: FutureFeature, Triaged
Assignee: fpokorny(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
jchaloup(a)redhat.com
Latest upstream release: v1.0.0
Current version/release in rawhide: 0-0.4.git8dc1f54.fc24
URL: https://github.com/digitalocean/godo
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.
Based on the information from anitya:
https://release-monitoring.org/project/6804/
--
You are receiving this mail because:
You are on the CC list for the bug.