cloudfoundry / cloudfoundry/windows2019fs-release
CF deployment is failing with latest windows2019 stemcell update
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Cloud Foundry Bosh deployment is failing with the latest stemcells windows2019 stemcell updated to 2019.86 (see https://github.com/cloudfoundry/cf-deployment/commit/50f87016740582da0f50ada94f2b5f41f15d962f)
windows-deploy job is failing on bosh-deploy-cf-develop task with the following error message:
Task 23261 | 13:22:09 | Updating instance windows2019-cell: windows2019-cell/30054b5e-2b5b-4972-8afe-68a2f4246aad (0) (canary) (00:05:44)
L Error: Action Failed get_task: Task 0f917631-f500-404b-68d9-2716f5c2d081 result: 1 of 11 pre-start scripts failed. Failed Jobs: windows2019fs. Successful Jobs: loggregator_agent_windows, loggr-syslog-agent-windows, bosh-dns-windows, loggr-forwarder-agent-windows, prom_scraper_windows, enable_ssh, loggr-system-metrics-agent-windows, rep_windows, winc-network-hns-acls, groot.
Task 23261 | 13:22:09 | Error: Action Failed get_task: Task 0f917631-f500-404b-68d9-2716f5c2d081 result: 1 of 11 pre-start scripts failed. Failed Jobs: windows2019fs. Successful Jobs: loggregator_agent_windows, loggr-syslog-agent-windows, bosh-dns-windows, loggr-forwarder-agent-windows, prom_scraper_windows, enable_ssh, loggr-system-metrics-agent-windows, rep_windows, winc-network-hns-acls, groot.
Concourse job: https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/cf-deployment/jobs/windows-deploy/builds/2220
The deployment was successful with the previous stemcell version:
value:
alias: windows2019
os: windows2019
version: "2019.85
CF deployment should work with the latest windows2019 stemcell.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Concourse windows-deploy build and compare its Windows 2019 stemcell 2019.86 deployment with the previously successful 2019.85 deployment. Investigate the windows2019fs pre-start failure and confirm done when CF deployment succeeds with the latest stemcell.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100