kubernetes: [k8s.io] Pod Disks should schedule a pod w/ a RW PD, remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-slow/5567/

Failed: [k8s.io] Pod Disks should schedule a pod w/ a RW PD, remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/pd.go:132
Expected error:
    <*errors.errorString | 0xc8200d40b0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred

Previous issues for this test: #26970

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 57 (57 by maintainers)

Commits related to this issue

Most upvoted comments

For those who are curious how I am determining a filesystem error I am basically downloading many jenkins runs and then running the following command:

$ find . -name kern.log | xargs grep -i ext4 | grep -v -i mount | grep -v -i resiz | grep -v -i "find ext4 filesystem" 
...
$ 

Generally I am finding errors of the like:

$ find . -name kern.log | xargs grep -i ext4 | grep -v -i remounting | grep -v mounted | grep -i -v resiz | grep -v -i "find ext4 filesystem" | sed 's/.*\]//' | sort  | uniq
EXT4-fs error (device sdb): ext4_put_super:798: Couldn't clean up the journal
 EXT4-fs error (device sdb): ext4_wait_block_bitmap:494: comm kworker/u4:1: Cannot read block bitmap - block_group = 1, block_bitmap = 642
 EXT4-fs error (device sdc): ext4_put_super:798: Couldn't clean up the journal
 EXT4-fs error (device sdc): ext4_wait_block_bitmap:494: comm kworker/u4:1: Cannot read block bitmap - block_group = 1, block_bitmap = 642
 EXT4-fs error (device sdd): ext4_put_super:798: Couldn't clean up the journal
 EXT4-fs error (device sde): ext4_put_super:798: Couldn't clean up the journal
 EXT4-fs (sdb): previous I/O error to superblock detected
 EXT4-fs (sdc): previous I/O error to superblock detected
 EXT4-fs (sdd): ext4_writepages: jbd2_start: 9223372036854775806 pages, ino 14; err -30
 EXT4-fs warning (device sdb): ext4_end_bio:317: I/O error -5 writing to inode 12 (offset 0 size 4096 starting block 65537)
 EXT4-fs warning (device sdb): ext4_end_bio:317: I/O error -5 writing to inode 13 (offset 0 size 4096 starting block 33411)
 EXT4-fs warning (device sdb): ext4_end_bio:317: I/O error -5 writing to inode 13 (offset 0 size 4096 starting block 65538)
 EXT4-fs warning (device sdb): ext4_end_bio:317: I/O error -5 writing to inode 14 (offset 0 size 4096 starting block 33412)
 EXT4-fs warning (device sdb): ext4_end_bio:317: I/O error -5 writing to inode 14 (offset 0 size 4096 starting block 65539)
 EXT4-fs warning (device sdc): ext4_end_bio:317: I/O error -5 writing to inode 12 (offset 0 size 4096 starting block 65537)
 EXT4-fs warning (device sdc): ext4_end_bio:317: I/O error -5 writing to inode 13 (offset 0 size 4096 starting block 65538)
 EXT4-fs warning (device sdc): ext4_end_bio:317: I/O error -5 writing to inode 14 (offset 0 size 4096 starting block 33412)
 EXT4-fs warning (device sdc): ext4_end_bio:317: I/O error -5 writing to inode 14 (offset 0 size 4096 starting block 65539)
 EXT4-fs warning (device sdd): ext4_end_bio:317: I/O error -5 writing to inode 14 (offset 0 size 4096 starting block 33412)
 EXT4-fs warning (device sde): ext4_end_bio:317: I/O error -5 writing to inode 14 (offset 0 size 4096 starting block 33412)
$