ZAPI-765: Adding a fabric NIC to a VM doesn't provision a fabric NAT

Resolution

Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2017-12-29T17:08:39.213Z)

Fix Versions

2018-01-04 Icicle Inn (Release Date: 2018-01-04)

Related Links

Description

If a user has never provisioned an instance on a fabric, then their fabric will not yet have a NAT. If they then try to add a fabric NIC to existing instances, the NIC will be successfully added, but the instance will have no NAT gateway to talk to. The {{add-nics}} workflow should check the internet_nat and gateway_provisioned flags and provision a NAT if needed, as is done in the {{provision}} workflow.

Comments

Comment by Michael Zeller
Created at 2017-12-22T21:10:21.997Z
This will be fixed by ZAPI-816

Comment by Michael Zeller
Created at 2017-12-28T18:38:14.480Z
Updated at 2017-12-28T18:44:44.565Z
With the commit for ZAPI-816 in place, I created a new fabric network that wanted a nat gateway.

I then used sdc-vmapi to update a machine on that network and verified the fabric nat  instance was created for that network.

Comment by Jira Bot
Created at 2017-12-29T16:51:25.429Z
sdc-vmapi commit 6cc90e2ccb949bfafd34fb4272acb54ed1e910ff (branch master, by Mike Zeller)

ZAPI-816 vmapi should pre provision nics
ZAPI-765 Adding a fabric NIC to a VM doesn't provision a fabric NAT
Reviewed by: Cody Peter Mello <cody.mello@joyent.com>
Approved by: Cody Peter Mello <cody.mello@joyent.com>