VMware Beta Community
nhutphan1987
Contributor
Contributor
Jump to solution

Cannot create an instance of Bring Your Own Encryption with UI

Dear VMware team,

I'd like to inform you about the issue when I tried to create the instance of BYOE with GUI following your Tech Preview Document. We can not create an instance of BYOE with UI, the error shows "can not research Public URL of VCD".

nhutphan1987_0-1694055084474.png

We created an instance of BYOE with CLI successfully, we used a Linux host in the same Organization VDC of Solution Landing Zone to do that. We are using VCD 10.5 GA.

nhutphan1987_1-1694056350223.png

nhutphan1987_2-1694057032613.png

 

0 Kudos
1 Solution

Accepted Solutions
tsimchev
VMware Employee
VMware Employee
Jump to solution

Dear @nhutphan1987 ,

I assume you may have encountered a bug in the Solutions Agent related to the Solutions Landing Zone (SLZ) Org VDC network configuration. Currently, if the SLZ network is set up with a Static IP Pool, and the subnet mask does not match the default mask for the subnet class (e.g., 10.x.x.x/8, 172.16-32.x.x/16), the Solutions Agent is unable to obtain a valid network configuration, resulting in a failure to orchestrate the installation. This issue is fixed in the upcoming releases of Cloud Director.

Meanwhile a workaround is to use SLZ network with DHCP or Static IP Pool where the subnet mask matches the default for the IP class.

Please take note of the following:

1. The SLZ network must have access to Cloud Director and depending on the add-on, optionally to the internet.
2. The public address configured in Cloud Director must be resolvable from the machines deployed in that network.
3. An outbound firewall rule to Cloud Director from this network must be in place.

View solution in original post

8 Replies
rtsanev
VMware Employee
VMware Employee
Jump to solution

@nhutphan1987 Sorry for the inconvenience! Can you please show us the full error message - click on the failed "Create" action in the UI and give us the text of the error message? This will help us troubleshoot and understand why this happened in your case.

0 Kudos
tsimchev
VMware Employee
VMware Employee
Jump to solution

Dear @nhutphan1987 ,

I assume you may have encountered a bug in the Solutions Agent related to the Solutions Landing Zone (SLZ) Org VDC network configuration. Currently, if the SLZ network is set up with a Static IP Pool, and the subnet mask does not match the default mask for the subnet class (e.g., 10.x.x.x/8, 172.16-32.x.x/16), the Solutions Agent is unable to obtain a valid network configuration, resulting in a failure to orchestrate the installation. This issue is fixed in the upcoming releases of Cloud Director.

Meanwhile a workaround is to use SLZ network with DHCP or Static IP Pool where the subnet mask matches the default for the IP class.

Please take note of the following:

1. The SLZ network must have access to Cloud Director and depending on the add-on, optionally to the internet.
2. The public address configured in Cloud Director must be resolvable from the machines deployed in that network.
3. An outbound firewall rule to Cloud Director from this network must be in place.

tandoiluca
Contributor
Contributor
Jump to solution

Hi all, we are having a completly similar problem but using vCD release 10.4.2.2

We have tried to deploy the vAppliance using the UI as per documentation but we have got the following error in creation phase:

operation completed with error 1 vcd-ext/cmd/instance/agent.(*waitOperationToCompleteActivity).Run vcd-ext/cmd/instance/agent/activity.go:
490 vcd-ext/cmd/instance.ActivityList.Execute.func1 vcd-ext/cmd/instance/activity.go:
78 vcd-ext/cmd/instance.ActivityList.Execute vcd-ext/cmd/instance/activity.go:
95 vcd-ext/cmd/instance/agent.(*RealizeContext).ExecuteOperation vcd-ext/cmd/instance/agent/common.go:
32 vcd-ext/cmd/instance/agent.(*RealizeContext).createInstance vcd-ext/cmd/instance/agent/create.go:
46 vcd-ext/cmd/instance/agent.(*RealizeContext).Realize vcd-ext/cmd/instance/agent/realize.go:
103 vcd-ext/cmd/instance/create.(*Options).Run vcd-ext/cmd/instance/create/cmd.go:
129 vcd-ext/cmd/instance/create.NewCreateCommand.func2 vcd-ext/cmd/instance/create/cmd.go:
36 github.com/spf13/cobra.(*Command).execute github.com/spf13/cobra@v1.5.0/command.go:
872 github.com/spf13/cobra.(*Command).ExecuteC github.com/spf13/cobra@v1.5.0/command.go:
990 github.com/spf13/cobra.(*Command).Execute github.com/spf13/cobra@v1.5.0/command.go:
918 vcd-ext/cmd/cli.Run vcd-ext/cmd/cli/cli.go:58 main.main /opt/src/vcd-ext/main.go:
13 cause: 'Running Virtual Application vmware.bring-your-own-encryption-0.9.0-appliance(c3a61058-8a8e-4f14-9613-16a61a8b6f72)':'error'

 

As you can see, strangely, it seems to attempt an access to a GitHub repository which doesn't exist (v1.5.0).

Then, we have tried to delete the faulty installation and we encoutered another issue: the delete process failed but it has deleted anything (and it seems the deleting process ha correctly completed because of we do not have any more the vAppliance in the landing zone).

The deleting operation failed with apparently the same reason (GitHub problem):

operation completed with error 1 vcd-ext/cmd/instance/agent.(*waitOperationToCompleteActivity).Run vcd-ext/cmd/instance/agent/activity.go:
490 vcd-ext/cmd/instance.ActivityList.Execute.func1 vcd-ext/cmd/instance/activity.go:
78 vcd-ext/cmd/instance.ActivityList.Execute vcd-ext/cmd/instance/activity.go:
95 vcd-ext/cmd/instance/agent.(*RealizeContext).ExecuteOperation vcd-ext/cmd/instance/agent/common.go:
32 vcd-ext/cmd/instance/agent.(*RealizeContext).deleteInstance vcd-ext/cmd/instance/agent/delete.go:
37 vcd-ext/cmd/instance/agent.(*RealizeContext).retryInstanceRequest vcd-ext/cmd/instance/agent/retry.go:
48 vcd-ext/cmd/instance/agent.(*RealizeContext).retryInstance vcd-ext/cmd/instance/agent/retry.go:
9 vcd-ext/cmd/instance/agent.(*RealizeContext).Realize vcd-ext/cmd/instance/agent/realize.go:
115 vcd-ext/cmd/instance/create.(*Options).Run vcd-ext/cmd/instance/create/cmd.go:
129 vcd-ext/cmd/instance/create.NewCreateCommand.func2 vcd-ext/cmd/instance/create/cmd.go:
36 github.com/spf13/cobra.(*Command).execute github.com/spf13/cobra@v1.5.0/command.go:
872 github.com/spf13/cobra.(*Command).ExecuteC github.com/spf13/cobra@v1.5.0/command.go:
990 github.com/spf13/cobra.(*Command).Execute github.com/spf13/cobra@v1.5.0/command.go:
918 vcd-ext/cmd/cli.Run vcd-ext/cmd/cli/cli.go:58 main.main /opt/src/vcd-ext/main.go:
13 cause: {"level":"debug","msg":"ISO is not mounted, trying to mounte it."} {"level":"debug","msg":"ISO is mounted."} {"level":"debug","msg":"Verify ISO runner is authored by VMware."} [31mERROR [0m[0005] Unknown command "retry" for "vcd-ext" [31merrorCode [0m=5012000000000000

 
 

Now, we are having problem creating a new instance starting from CLI because of the presence of the not deleting instance.

How could we forcely remove the previous failed instance?

Thanks!

0 Kudos
tsimchev
VMware Employee
VMware Employee
Jump to solution

Dear @tandoiluca ,

The actual error during instance creation is related to a failure in deploying the Bring Your Own Key Appliance. The specific low-level error should be disclosed with:

grep ExecutionFuture /opt/vmware/vcloud-director/logs/vcloud-container-debug.log*

Also, be sure to monitor for any errors associated with the virtual machine deployment of 'vmware.bring-your-own-encryption-0.9.0-appliance (c3a61058-8a8e-4f14-9613-16a61a8b6f72).'

grep "c3a61058-8a8e-4f14-9613-16a61a8b6f72" /opt/vmware/vcloud-director/logs/vcloud-container-debug.log*

The second error related to the instance deletion occurred during the first delete event (you can check the specific error by clicking on the first "Delete" task/logs). The second delete event is a retry, which is not supported in the Technical Preview.

I would suggest to have a call to clean up the installation.

Best regards,
Teodor Simchev

Tags (1)
0 Kudos
tandoiluca
Contributor
Contributor
Jump to solution

Thank you so much!

I will appreciate if we could stay in touch just in this evening to complete...we could be ready to start a meeting with you at 5:00PM (Italian time), could it work for you?

0 Kudos
tsimchev
VMware Employee
VMware Employee
Jump to solution

A member from my team can be available at 18:00 Italian time or tomorrow? Which one works for you?

—Teodor

0 Kudos
tandoiluca
Contributor
Contributor
Jump to solution

Hi all, I attached the file with command output to futher investigate and, in the mean time, we will arrange by email a time slot to continue together the instance delete process.

Thanks again for your support!

0 Kudos
tsimchev
VMware Employee
VMware Employee
Jump to solution

The issue with delete instance affects only 10.4.2.2 and its described in the release notes.

Updating a Runtime Defined Entity (RDE) that contains restricted fields might fail if you remove an item from an array in the entity contents ...

https://docs.vmware.com/en/VMware-Cloud-Director/10.4.2.2/rn/vmware-cloud-director-10422-release-not...