Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing prowjob after the webhook is configured per https://github.com/GoogleCloudPlatform/oss-test-infra/pull/1195 #90

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

jcnars
Copy link
Collaborator

@jcnars jcnars commented Oct 14, 2021

GoogleCloudPlatform/oss-test-infra#1195 was merged.

Editing a README file as a test change to trigger the prowjob.

@jcnars jcnars self-assigned this Oct 14, 2021
@google-oss-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jcnars

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/meow

@google-oss-robot
Copy link
Collaborator

@jcnars: cat image

In response to this:

/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/yuks

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/joke

@google-oss-robot
Copy link
Collaborator

@jcnars: What do vegetarian zombies eat? Grrrrrainnnnnssss.

In response to this:

/joke

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/ok-to-test

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/test ?

@google-oss-robot
Copy link
Collaborator

@jcnars: The following commands are available to trigger required jobs:

  • /test testjob

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/test testjob

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/retest

Ran this manually:

jcnarasimhan@jon2:~/DriveFS/My Drive/bmaas/test_automation/oss_prow_onboarding$ kubectl apply -f - <<EOF
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    iam.gke.io/gcp-service-account: prowjob-default-sa@bmaas-testing.iam.gserviceaccount.com
  name: prowjob-default-sa
  namespace: test-pods
EOF
serviceaccount/prowjob-default-sa created

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

@jcnars: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
testjob 84dca99 link true /test testjob

The error from prow status page: https://oss-prow.knative.dev/ is:

error rendering spyglass page: error when resolving real path gs/bmaas-testing-prow-poc/pr-logs/pull/google_bms-toolkit/90/testjob/1448767330606649344: googleapi: got HTTP response code 403 with body: 
<?xml version="1.0" encoding="UTF-8"?>
<Error>
   <Code>AccessDenied</Code>
   <Message>Access denied.</Message>
   <Details>oss-prow-public-deck@oss-prow.iam.gserviceaccount.com does not have storage.objects.get access to the Google Cloud Storage object.</Details>
</Error>

Looks like a permission issue. Exploring how to give access to oss-prow-public-deck@oss-prow.iam.gserviceaccount.com.
Will first verify that prowjob-default-sa locally in the build cluster has access.

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/retest

Added as noted here: (Internal) https://screenshot.googleplex.com/3rUJ57oXXYZBpG6

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/test testjob

added this: https://screenshot.googleplex.com/C9vf3bDn9P69GY5 because got the same error:

error rendering spyglass page: error when resolving real path gs/bmaas-testing-prow-poc/pr-logs/pull/google_bms-toolkit/90/testjob/1448771039117971456: googleapi: got HTTP response code 403 with body: <?xml version='1.0' encoding='UTF-8'?><Error><Code>AccessDenied</Code><Message>Access denied.</Message><Details>oss-prow-public-deck@oss-prow.iam.gserviceaccount.com does not have storage.objects.get access to the Google Cloud Storage object.</Details></Error>

whenever we click on the "Details" link next to the test that passed and also on the prow jobs page (https://oss-prow.knative.dev/), clicking on testjob

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/test all

Editing a comment doesn't seem to trigger a test

@google-oss-robot
Copy link
Collaborator

@jcnars: No jobs can be run with /test all.
The following commands are available to trigger required jobs:

  • /test testjob

In response to this:

/test all

Editing a comment doesn't seem to trigger a test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/test testjob

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

/test testjob

Reason: Granted: https://screenshot.googleplex.com/HFdB43qEwULtx4X

Reason: (Thanks ChaodaiG for clarification) When creating, this roles/storage.objectAdmin grant was somehow missed:
https://github.com/kubernetes/test-infra/blob/75b15aa2202a3285ec737586e211025c31466908/prow/create-build-cluster.sh#L166

function createBucket() {
  gsutil mb -p "${PROJECT}" -b on "${GCS_BUCKET}"
  for i in ${CONTROL_PLANE_SA//,/ }
  do
    gsutil iam ch "serviceAccount:${i}:roles/storage.objectAdmin" "${GCS_BUCKET}"
  done
}

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 14, 2021

@jcnars-k8s-bot
Copy link

/test testjob

Reason: https://screenshot.googleplex.com/8zkPpxgdKeBNbyn

@jcnars-k8s-bot
Copy link

/test testjob

@google-oss-robot
Copy link
Collaborator

@jcnars-k8s-bot: No presubmit jobs available for google/bms-toolkit@master

In response to this:

/test testjob

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 27, 2021

/test ?

@google-oss-robot
Copy link
Collaborator

@jcnars: The following commands are available to trigger required jobs:

  • /test bms-toolkit-install

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Oct 27, 2021

/test bms-toolkit-install

@jcnars
Copy link
Collaborator Author

jcnars commented Nov 24, 2021

"cat: write error: No space left on device"] - fixed it...https://gist.github.com/jcnars/9b1ee01d6ea8bf07e67c52f66a72bfa4

Possibly the 400MB fs size is a remnant of prior troubleshooting to 'unbusy' the block device (I.O.W: in process of troubleshooting, we created the FS before extending to 60G):

[root@linuxserver44 /]# lvremove -vf /dev/mapper/sw-u01
    Removing sw-u01 (253:70)
    Archiving volume group "sw" metadata (seqno 6).
    Releasing logical volume "u01"
    Creating volume group backup "/etc/lvm/backup/sw" (seqno 7).
  Logical volume "u01" successfully removed
[root@linuxserver44 /]# #lvcreate -l 100 -n u01 sw
[root@linuxserver44 /]# lvcreate -l 100 -n u01 sw
WARNING: xfs signature detected on /dev/sw/u01 at offset 0. Wipe it? [y/n]: y
  Wiping xfs signature on /dev/sw/u01.
  Logical volume "u01" created.
[root@linuxserver44 /]# !mkfs.xfs
-bash: !mkfs.xfs: event not found
[root@linuxserver44 /]# /sbin/mkfs.xfs -f /dev/mapper/sw-u01
meta-data=/dev/mapper/sw-u01     isize=512    agcount=4, agsize=25600 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=1        finobt=0, sparse=0
data     =                       bsize=4096   blocks=102400, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal log           bsize=4096   blocks=1605, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

And now:
===================
[root@linuxserver44 /]# df -h
Filesystem                                       Size  Used Avail Use% Mounted on
devtmpfs                                         378G  200M  377G   1% /dev
tmpfs                                            378G   16K  378G   1% /dev/shm
tmpfs                                            378G  899M  377G   1% /run
tmpfs                                            378G     0  378G   0% /sys/fs/cgroup
/dev/mapper/rootvg-rootlv                        8.0G  2.9G  5.2G  36% /
/dev/mapper/3600a098038314344382b4f7539397555p2 1014M  192M  823M  19% /boot
/dev/mapper/3600a098038314344382b4f7539397555p1  204M  9.7M  195M   5% /boot/efi
/dev/mapper/rootvg-tmplv                         5.0G   34M  5.0G   1% /tmp
/dev/mapper/rootvg-homelv                         20G  6.3G   14G  32% /home
/dev/mapper/rootvg-optlv                          20G  2.4G   18G  12% /opt
/dev/mapper/rootvg-varlv                         4.0G  1.7G  2.4G  42% /var
tmpfs                                             76G     0   76G   0% /run/user/1001
tmpfs                                             76G     0   76G   0% /run/user/1532
/dev/mapper/sw-u01                               394M  394M   60K 100% /u01
/dev/mapper/sw-u02                                20G   33M   20G   1% /u02
[root@linuxserver44 /]# lvs
  LV     VG     Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  homelv rootvg -wi-ao---- 20.00g                                                    
  optlv  rootvg -wi-ao---- 20.00g                                                    
  rootlv rootvg -wi-ao----  8.00g                                                    
  swaplv rootvg -wi-ao---- 16.00g                                                    
  tmplv  rootvg -wi-ao----  5.00g                                                    
  varlv  rootvg -wi-ao----  4.00g                                                    
  u01    sw     -wi-ao---- 60.00g                                                    
  u02    sw     -wi-ao---- 20.00g 
[root@linuxserver44 /]# wipefs -a /dev/mapper/sw-u01
wipefs: error: /dev/mapper/sw-u01: probing initialization failed: Device or resource busy
[root@linuxserver44 /]# umount /u01
[root@linuxserver44 /]# wipefs -a /dev/mapper/sw-u01
/dev/mapper/sw-u01: 4 bytes were erased at offset 0x00000000 (xfs): 58 46 53 42
[root@linuxserver44 /]# mount /u01
mount: wrong fs type, bad option, bad superblock on /dev/mapper/sw-u01,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
[root@linuxserver44 /]# mkfs.xfs /dev/mapper/sw-u01
meta-data=/dev/mapper/sw-u01     isize=512    agcount=4, agsize=3932160 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=1        finobt=0, sparse=0
data     =                       bsize=4096   blocks=15728640, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal log           bsize=4096   blocks=7680, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
[root@linuxserver44 /]# mount /u01
[root@linuxserver44 /]# mount /u01
mount: /dev/mapper/sw-u01 is already mounted or /u01 busy
       /dev/mapper/sw-u01 is already mounted on /u01
[root@linuxserver44 /]# df -h /u0*
Filesystem          Size  Used Avail Use% Mounted on
/dev/mapper/sw-u01   60G   33M   60G   1% /u01
/dev/mapper/sw-u02   20G   33M   20G   1% /u02

@jcnars
Copy link
Collaborator Author

jcnars commented Nov 24, 2021

/test bms-toolkit-install

@jcnars
Copy link
Collaborator Author

jcnars commented Nov 24, 2021

/test ?

@google-oss-prow
Copy link

@jcnars: The following commands are available to trigger required jobs:

  • /test bms-toolkit-install

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Nov 24, 2021

/test bms-toolkit-install

@jcnars
Copy link
Collaborator Author

jcnars commented Nov 24, 2021

/test bms-toolkit-install

@jcnars
Copy link
Collaborator Author

jcnars commented Dec 3, 2021

/test ?

@google-oss-prow
Copy link

@jcnars: The following commands are available to trigger required jobs:

  • /test bms-toolkit-install

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Dec 3, 2021

/test bms-toolkit-install

@jcnars
Copy link
Collaborator Author

jcnars commented Dec 3, 2021

@chaodaiG
Copy link

chaodaiG commented Dec 6, 2021

/meow

@google-oss-prow
Copy link

@chaodaiG: cat image

In response to this:

/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Dec 14, 2021

/joke

@google-oss-prow
Copy link

@jcnars: I decided to sell my Hoover… well it was just collecting dust.

In response to this:

/joke

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Dec 14, 2021

/joke

@google-oss-prow
Copy link

@jcnars: People who don't eat gluten are really going against the grain.

In response to this:

/joke

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Dec 14, 2021

/test bms-toolkit-install

1 similar comment
@jcnars
Copy link
Collaborator Author

jcnars commented Jan 13, 2022

/test bms-toolkit-install

@jcnars
Copy link
Collaborator Author

jcnars commented Jan 14, 2022

/retest

2 similar comments
@jcnars
Copy link
Collaborator Author

jcnars commented Jan 14, 2022

/retest

@jcnars
Copy link
Collaborator Author

jcnars commented Mar 3, 2022

/retest

@jcnars
Copy link
Collaborator Author

jcnars commented Mar 16, 2022

/meow

@google-oss-prow
Copy link

@jcnars: cat image

In response to this:

/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Jun 5, 2022

/meow

@google-oss-prow
Copy link

@jcnars: cat image

In response to this:

/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jcnars
Copy link
Collaborator Author

jcnars commented Jun 5, 2022

/test bms-toolkit-install

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants