Deployment of windows vm manifest require winc-release v2.0 or higher
search cancel

Deployment of windows vm manifest require winc-release v2.0 or higher

book

Article ID: 298063

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

You have manifest that is deploying a windows vm. This manifest was working prior to PAS for Windows (PASW) v2.8.0. Here is a sample manifest:
 
name: windows-test
releases:
- name: windows2019fs
  version: latest
stemcells:
- alias: windows2019
  os: windows2019
  version: latestupdate:
  canaries: 1
  max_in_flight: 1
  canary_watch_time: 1000-30000
  update_watch_time: 1000-30000instance_groups:
- name: windows2019
  azs: [az1]
  instances: 1
  jobs:
  - name: windows2019fs
    release: windows2019fs
  vm_type: medium
  stemcell: windows2019
  networks:
  - name: infra


After upgrading to PASW 2.8.0 you noticed its errors out on pre-start script:
No signal received on event RootfsEvent after 30 minutes. This signal is generated by the pre-start script of winc-release/job=groot. You might have an older version of the winc-release. Require winc-release v2.0 or higher.

The error suggest that its needing winc-release v2.0. First thing to check if this release was uploaded:
bosh releases | grep winc
winc 2.0.0* 53487ac



And you have verified that winc-release v2.0 was indeed uploaded




Environment

Product Version: 2.8

Resolution

There was a change added from v.19.0 of the windowsfs release to ensure that it was appropriately coupled with winc release. One is not usable without the other. You need to reference winc release as well in your manifest. Here is a sample manifest:
 
name: windows-test
releases:
- name: windows2019fs
  version: latest
​
# Add the following...
- name: winc
  version: latest
stemcells:
- alias: windows2019
  os: windows2019
  version: latest
update:
  canaries: 1
  max_in_flight: 1
  canary_watch_time: 1000-30000
  update_watch_time: 1000-30000
instance_groups:
- name: windows2019
  azs: [az1]
  instances: 1
  vm_type: medium
  stemcell: windows2019
  networks:
  - name: infra
  jobs:
  - name: windows2019fs
    release: windows2019fs
​
  # Add the following...
  - name: winc
    release: winc
  - name: winc-network-hns-acls
    release: winc
    properties:
      winc_network:
        mtu: 1500
  - name: groot
    release: winc
    properties:
      groot:
        cached_image_uris:
        - oci:///C:/var/vcap/packages/windows2019fs
        driver_store: /var/vcap/data/groot
        log_level: debug
If you only need to deploy the windows stemcell and has no need for the jobs specified in the manifest, then you have the option for specifying no jobs at all with: jobs: []