{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":68121501,"defaultBranch":"main","name":"om","ownerLogin":"pivotal-cf","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2016-09-13T15:30:05.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5497370?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1714954159.0","currentOid":""},"activityList":{"items":[{"before":"7dc8442a9ac4a1a289cdf32ee7747f528b097f1c","after":null,"ref":"refs/heads/tmp/upgrade-golang-206d60e","pushedAt":"2024-05-06T00:09:22.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"tas-operability-bot","name":null,"path":"/tas-operability-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/149723437?s=80&v=4"}},{"before":"206d60e42462dfcddd10f643d4be29782f903a91","after":"3c4a3caa3079da876ae2a869060bba38470d823b","ref":"refs/heads/main","pushedAt":"2024-05-06T00:09:22.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"tas-operability-bot","name":null,"path":"/tas-operability-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/149723437?s=80&v=4"},"commit":{"message":"Upgrade Golang","shortMessageHtmlLink":"Upgrade Golang"}},{"before":null,"after":"7dc8442a9ac4a1a289cdf32ee7747f528b097f1c","ref":"refs/heads/tmp/upgrade-golang-206d60e","pushedAt":"2024-05-06T00:09:19.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Upgrade Golang","shortMessageHtmlLink":"Upgrade Golang"}},{"before":"99183ceb0d26a826bb9c0464c6c55f245044b297","after":null,"ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-05-01T20:59:52.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"wayneadams","name":"Wayne Adams","path":"/wayneadams","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15034841?s=80&v=4"}},{"before":"2af88e833ef0333dcaa99649fa198e2111bc9fb8","after":"206d60e42462dfcddd10f643d4be29782f903a91","ref":"refs/heads/main","pushedAt":"2024-05-01T20:59:51.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"wayneadams","name":"Wayne Adams","path":"/wayneadams","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15034841?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"6a9b90c22e65828f959a49109286a1c39a291c73","after":"99183ceb0d26a826bb9c0464c6c55f245044b297","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-05-01T18:28:39.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"5ca9251446131cb82e7e3f1a238af28690fee9f2","after":"6a9b90c22e65828f959a49109286a1c39a291c73","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-30T23:32:40.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wayneadams","name":"Wayne Adams","path":"/wayneadams","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15034841?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"4fe477e0eb6ee92b2c6313ce02e0567d0b0c3681","after":"2af88e833ef0333dcaa99649fa198e2111bc9fb8","ref":"refs/heads/main","pushedAt":"2024-04-30T23:22:35.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"wayneadams","name":"Wayne Adams","path":"/wayneadams","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15034841?s=80&v=4"},"commit":{"message":"Update depnames fixtures\n\nAuthored-by: Wayne Adams <wayne.adams@broadcom.com>","shortMessageHtmlLink":"Update depnames fixtures"}},{"before":"7acec010e80ce8099fbeae6949846fa903e0118b","after":"5ca9251446131cb82e7e3f1a238af28690fee9f2","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-29T16:34:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"5d3bbcd9f64dd389f8d4fb6f32e17dbe4ff22e9e","after":"7acec010e80ce8099fbeae6949846fa903e0118b","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-29T03:33:35.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"926b0d9a3cd6b3e04ea16129bd88844c7f746296","after":"5d3bbcd9f64dd389f8d4fb6f32e17dbe4ff22e9e","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-29T01:39:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"e06e7be1bac41847877ce09516f7b1ad9851caa5","after":null,"ref":"refs/heads/tmp/upgrade-golang-3da97eb","pushedAt":"2024-04-29T00:09:03.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"tas-operability-bot","name":null,"path":"/tas-operability-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/149723437?s=80&v=4"}},{"before":"3da97ebf52c67655c60f18ded08274914b8538e8","after":"4fe477e0eb6ee92b2c6313ce02e0567d0b0c3681","ref":"refs/heads/main","pushedAt":"2024-04-29T00:09:02.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"tas-operability-bot","name":null,"path":"/tas-operability-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/149723437?s=80&v=4"},"commit":{"message":"Upgrade Golang","shortMessageHtmlLink":"Upgrade Golang"}},{"before":null,"after":"e06e7be1bac41847877ce09516f7b1ad9851caa5","ref":"refs/heads/tmp/upgrade-golang-3da97eb","pushedAt":"2024-04-29T00:09:00.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Upgrade Golang","shortMessageHtmlLink":"Upgrade Golang"}},{"before":"8161d54a88008cb2b6dcc499046eb179b060086f","after":"926b0d9a3cd6b3e04ea16129bd88844c7f746296","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-25T20:20:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"bfd3ca1daa6885c75a054e17ad51ec983c35ddde","after":"8161d54a88008cb2b6dcc499046eb179b060086f","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-25T19:58:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman.\n\nTypical output when resetting a failed initial boot:\n\n```\nExecuting: \"govc vm.info -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -waitip\"\nThis could take a few moments...\nVM hasn't acquired IP, is probably stuck, resetting VM to free it\n\nExecuting: \"govc vm.power -vm.ipath=/dc/vm/pcf_vms/om.tas.nono.io -reset\"\nThis could take a few moments...\ngovc[stdout]: Reset VirtualMachine:vm-42616... OK\n```","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"a42f530dcaf875a45a70e7a6ad403fe073dd6546","after":"bfd3ca1daa6885c75a054e17ad51ec983c35ddde","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-25T19:47:05.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address to vCenter, and if it hasn't reported its IP\naddress by then, it sends a hardware reset to the VM. An opsman VM\ntypically reports its IP address to vCenter 43 seconds after being\npowered-on.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.\n\nMore about the boot failure:\n\n- The boot failure only occurs the very first time an opsman is booted;\n  subsequent boots will always succeed. We tested 100 shutdown/boots to\n  confirm.\n- The failure was seen both on vSphere 7 and vSphere 8.\n- Sending a reset or a ctl-alt-del to the machine within the first few\n  seconds of being powered-on reduced but did not eliminate the failure.\n\nThis fix should have negligible impact on the length of time to deploy\nopsman","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"8bc3b9037062b72d085606311f4f73743952d2eb","after":"a42f530dcaf875a45a70e7a6ad403fe073dd6546","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-25T19:39:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"🐞 Fix: deploying opsman to vSphere 15% boot fail\n\nWhen deploying opsman to vSphere, it fails to boot 15% of the time. It\nhappens very early in the boot process, apparently even before loading\nthe kernel. When viewing the opsman's VM's console, the symptom is a\nflashing cursor in the upper left hand side of the screen.\n\nThis commit fixes that failure by waiting 80 seconds for the opsman VM\nto report its IP address, and if it hasn't reported its IP address by\nthem, it sends a hardware reset to the VM.\n\nWe verified this fix by successfully deploying & booting opsman 146\ntimes in a row.","shortMessageHtmlLink":"🐞 Fix: deploying opsman to vSphere 15% boot fail"}},{"before":"cf456fc7ef5d7bda043e7280ee58bcef12de959e","after":"8bc3b9037062b72d085606311f4f73743952d2eb","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-25T18:37:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"Wait 80 seconds for vSphere OM to get IP before resetting\n\nDrive-by:\n\n- bumped the number of vCPUs 1 → 2 to match other IaaSes such as AWS.","shortMessageHtmlLink":"Wait 80 seconds for vSphere OM to get IP before resetting"}},{"before":"a147ef88ae4285b08e41b924142be3b81a0ac640","after":"cf456fc7ef5d7bda043e7280ee58bcef12de959e","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-24T12:53:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"Wait 80 seconds for vSphere OM to get IP before resetting\n\nDrive-by:\n\n- bumped the number of vCPUs 1 → 2 to match other IaaSes such as AWS.","shortMessageHtmlLink":"Wait 80 seconds for vSphere OM to get IP before resetting"}},{"before":"0e0b5492f3bdf97b1479d017aac9835b9c051f12","after":"a147ef88ae4285b08e41b924142be3b81a0ac640","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-24T02:03:53.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"Use context to detect whether vSphere OM is stuck","shortMessageHtmlLink":"Use context to detect whether vSphere OM is stuck"}},{"before":"a44a3f60574e01020f6ddf1fccf141b0095fb5ed","after":"0e0b5492f3bdf97b1479d017aac9835b9c051f12","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-23T22:51:03.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"Attempt delayed power-on, reset, then CTL-ALT-DEL\n\n...and it still doesn't work.","shortMessageHtmlLink":"Attempt delayed power-on, reset, then CTL-ALT-DEL"}},{"before":"a126477f36f777aa5f425845f72dc3b8608fc5b0","after":"3da97ebf52c67655c60f18ded08274914b8538e8","ref":"refs/heads/main","pushedAt":"2024-04-23T17:02:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"jtarchie","name":"JT A.","path":"/jtarchie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/75184?s=80&v=4"},"commit":{"message":"bump to 7.11.0","shortMessageHtmlLink":"bump to 7.11.0"}},{"before":"2d84ab5aa0afa317818cff8a27ec8e1854295873","after":"a126477f36f777aa5f425845f72dc3b8608fc5b0","ref":"refs/heads/main","pushedAt":"2024-04-23T17:02:48.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pcf-platform-automation","name":"pcf-platform-automation","path":"/pcf-platform-automation","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/35970477?s=80&v=4"},"commit":{"message":"Brew formula update for om version 7.11.0","shortMessageHtmlLink":"Brew formula update for om version 7.11.0"}},{"before":"efdc352be8e95ada216a07bc91620db1aaf8774d","after":null,"ref":"refs/tags/7.11.0","pushedAt":"2024-04-23T16:56:20.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"staylor14","name":"Steve Taylor","path":"/staylor14","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/504044?s=80&v=4"}},{"before":"d82fd1f727fb1f350460eeaf3f66334040dcd73d","after":null,"ref":"refs/heads/tmp/upgrade-golang-efdc352","pushedAt":"2024-04-23T16:55:10.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"tas-operability-bot","name":null,"path":"/tas-operability-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/149723437?s=80&v=4"}},{"before":"efdc352be8e95ada216a07bc91620db1aaf8774d","after":"2d84ab5aa0afa317818cff8a27ec8e1854295873","ref":"refs/heads/main","pushedAt":"2024-04-23T16:55:09.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"tas-operability-bot","name":null,"path":"/tas-operability-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/149723437?s=80&v=4"},"commit":{"message":"Upgrade Golang","shortMessageHtmlLink":"Upgrade Golang"}},{"before":null,"after":"a44a3f60574e01020f6ddf1fccf141b0095fb5ed","ref":"refs/heads/vsphere-stuck-boot","pushedAt":"2024-04-22T22:22:10.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cunnie","name":"Brian Cunnie","path":"/cunnie","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1020675?s=80&v=4"},"commit":{"message":"Fix intermittent boot problem on vSphere\n\nOM won't boot 5-15% of the time; vCenter says VM is powered on, but the\nconsole only shows a flashing cursor up in the upper left hand corner.","shortMessageHtmlLink":"Fix intermittent boot problem on vSphere"}},{"before":"42b4b77c0266dda544928cbcea7980cd9df99c98","after":null,"ref":"refs/tags/7.11.0","pushedAt":"2024-04-22T20:07:19.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"staylor14","name":"Steve Taylor","path":"/staylor14","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/504044?s=80&v=4"}},{"before":null,"after":"d82fd1f727fb1f350460eeaf3f66334040dcd73d","ref":"refs/heads/tmp/upgrade-golang-efdc352","pushedAt":"2024-04-22T00:09:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Upgrade Golang","shortMessageHtmlLink":"Upgrade Golang"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEQhGylgA","startCursor":null,"endCursor":null}},"title":"Activity · pivotal-cf/om"}