Quantcast
Channel: VMware Communities: Message List - VMware vCloud Director
Viewing all 7719 articles
Browse latest View live

Re: vCD 9.7 / The requested operation on VM "CentOS-7.6.1810" is not supported since the VM is in an inconsistent state.

$
0
0

2019-04-12 14:14:26,652 | DEBUG    | pool-jetty-66             | NetworkFabricExtensionUtils    | Extension not found for phase CREATE_TRANSPORT_ZONE | requestId=2de09646-f0cd-4bf7-a70d-42d32c337feb,request=POST https://vCD-DOMAIN/api/vdc/cc8ee2e4-6e26-4f39-b9ca-cc1f62c82e1f/action/instantiateVmFromTemplate,requestTime=1555071266197,remoteAddress=X.X.X.167:53975,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+xml;version 32.0

It seems there is something wrong with the NSX integration.

 

But go inside the log and look at the messages between this error message and "Transaction rolled back". Not all related events are marked with the request ID, so with the use of "grep" you will miss important error messages, details and java stack traces.


Importing/Creating VM in vCloud Director sets the MAC address allocation to Static (instead of Automatic)

$
0
0

Hi,

We have in premises vCloud Director 9.5.0 environment.

 

Whenever we import VM in vSphere with MAC address allocation Automatic to vCloud Director, after successful import the VM's MAC address allocation gets changed to Static.

 

Before Import to vCloud Director

Created VM with Automatic MAC allocation in vSphere.png

 

Importing VM from vSphere to vCloud Director


After Importing to vCloud Director

 

Also, when we create new VM in vCloud Director, the MAC address allocation is set to Static(by default).

 

Is there any configuration in vCloud Director to enforce *Automatic* MAC address allocation?

Re: vCD 9.7 / The requested operation on VM "CentOS-7.6.1810" is not supported since the VM is in an inconsistent state.

$
0
0

OK i will try check logs.

Strange because this is related only to some specific VM template.

 

Sebastian

Re: Importing/Creating VM in vCloud Director sets the MAC address allocation to Static (instead of Automatic)

$
0
0

@VMware vCloud Director engineering/support team,

Is this expected behavior or bug? Is there any workaround to retain MAC address allocation Automatic of VM in vCenter even after importing to vCloud Director?

 

Note: We are running into duplicate MAC address problems due to Static MAC allocation in vCloud Director. Resetting MAC from vCloud Director GUI, solves duplicate MAC problem, however we expect MAC address allocation to remain Automatic even after importing to vCloud Director so that we don't have to manually reset MAC of imported VM.

Importing/Creating VM in vCloud Director sets the MAC address allocation to Static (instead of Automatic)

$
0
0

Hi,

We have in premises vCloud Director 9.5.0 environment.

 

Whenever we import VM from vCenter with MAC address allocation Automatic to vCloud Director, after successful import the VM's MAC address allocation gets changed to Static.

 

Before Import to vCloud Director

Created VM with Automatic MAC allocation in vSphere.png

 

Importing VM from vCenter to vCloud Director


After Importing to vCloud Director

 

Also, when we create new VM in vCloud Director, the MAC address allocation is set to Static(by default).

 

Is there any configuration/setting in vCloud Director/vCenter to retain MAC address allocation Automatic of VM in vCenter even after importing to vCloud Director?

 

Note: We are running into duplicate MAC address problems due to Static MAC allocation in vCloud Director. Resetting MAC from vCloud Director GUI, solves duplicate MAC problem, however we expect MAC address allocation to remain Automatic even after importing to vCloud Director so that we don't have to manually reset MAC of imported VM.

How to disable SAML from console?

$
0
0

Due to wrong SAML configuration, I cannot login into vCloud Director.

 

It redirects me to PSC page and show 400 Bad request error.

 

How to disable SAML from console or config files?

 

vCloud Director 9.0.0

Re: NFS configuration / Proper configuration on vCD CELL (CentOS) /etc/fstab

$
0
0

Hi!

 

Found some useful info here:

https://help.ubuntu.com/community/Fstab

 

The first "2" has to do with the dump command, and the second "2" has to do with fsck during boot (if needed). I'd say that you probably should change the fields to "0" at your earliest convenience.

MS SQL to PostgreSQL for vCloud Director 9.7 and future release

$
0
0

Hi Guys

 

 

I see vmware just release vcloud director 9.7 and they also stated that 9.7 will be final release that will support MS SQL as the vcloud database.

 

in my environment we are currently vcloud director 9.5 and MS sql database

 

does anyone know if and how we can migrate from MS SQL to PostgreSQL

 

 

Thanks in advanced


Re: MS SQL to PostgreSQL for vCloud Director 9.7 and future release

$
0
0

You will need to utilize the migrate database functionality built into the vCD upgrade process. The database migration tool is fully compatible with SQL to Postgres (and previously we supported Oracle to Postgres). This works well.

vCD 9.7 Appliance ==> How should working HA ?

$
0
0

Yesterday i deployed 3 x appliance with embedded DB.

 

For configuration used bellow commands:

 

CELL1(primary)

/opt/vmware/vcloud-director/bin/configure --unattended-installation --database-type postgres --database-user vcloud --database-password PASSWORD --database-host ETH1-IP-OF-PRIMARY-APPLIANCE --database-port 5432 --database-name vcloud --database-ssl false --uuid --keystore /opt/vmware/vcloud-director/certificates.ks --keystore-password PASSWORD --primary-ip ETH0-IP-CURRENT-APPLIANCE --console-proxy-ip ETH0-IP-CURRENT-APPLIANCE --console-proxy-port-https 8443

 

 

CELL2(standby)

/opt/vmware/vcloud-director/bin/configure --unattended-installation --database-type postgres --database-user vcloud --database-password PASSWORD --database-host ETH1-IP-OF-PRIMARY-APPLIANCE --database-port 5432 --database-name vcloud --database-ssl false --uuid --keystore /opt/vmware/vcloud-director/certificates.ks --keystore-password PASSWORD --primary-ip ETH0-IP-CURRENT-APPLIANCE --console-proxy-ip ETH0-IP-CURRENT-CELL3-APPLIANCE --console-proxy-port-https 8443

 

 

CELL3(standby)

/opt/vmware/vcloud-director/bin/configure --unattended-installation --database-type postgres --database-user vcloud --database-password PASSWORD --database-host ETH1-IP-OF-PRIMARY-APPLIANCE --database-port 5432 --database-name vcloud --database-ssl false --uuid --keystore /opt/vmware/vcloud-director/certificates.ks --keystore-password PASSWORD --primary-ip ETH0-IP-CURRENT-APPLIANCE --console-proxy-ip ETH0-IP-CURRENT-CELL3-APPLIANCE --console-proxy-port-https 8443

 

From GUI perspective everything is workling... but im not sure if every standby Appliance should use connection to PRIMARY DB but when i tried use yesterday standby DB i received errors about "READONY TRANSACTIONS" Thats swhy im used command how above.

 

Lets back to my main question: How should working HA ? in Appliance configuration ?

 

Previous i used 2x CentOS cells and when 1 node was down 2nd deliver service for clients...

 

Now i have 3x node with embedded DB and when i shutdown primary node portal for vCD stops working too... According to documentation Recover from a Primary Database Failure in a High Availability Cluster  we can recover PRIMARY node only manually...

 

How then should we configure cluster in proper way ? Maybe should be deploy additional Appliance for Application (what is role fo this Appliance) ?

 

 

Orchestrate another Openstack vendors with VMware Cloud Drector

$
0
0

I have a doubt. We have Openstack, not VMware, I mean another Openstack from another versions/vendors.

 

Can I orchestrate these Openstack pools with VMware Cloud Director?

 

Thanks in advance.

Kubernetes || CSE installation issue

$
0
0

Hi All,

 

Im new to CSE K8s.While installating CSE on photon OS,im getting the below error.Please suggest.

 

 

root@photon-machine [ ~ ]# cse install --config config.yaml

Traceback (most recent call last):

  File "/usr/bin/cse", line 10, in <module>

    sys.exit(cli())

  File "/usr/lib/python3.6/site-packages/click/core.py", line 764, in __call__

    return self.main(*args, **kwargs)

  File "/usr/lib/python3.6/site-packages/click/core.py", line 717, in main

    rv = self.invoke(ctx)

  File "/usr/lib/python3.6/site-packages/click/core.py", line 1137, in invoke

    return _process_result(sub_ctx.command.invoke(sub_ctx))

  File "/usr/lib/python3.6/site-packages/click/core.py", line 956, in invoke

    return ctx.invoke(self.callback, **ctx.params)

  File "/usr/lib/python3.6/site-packages/click/core.py", line 555, in invoke

    return callback(*args, **kwargs)

  File "/usr/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func

    return f(get_current_context(), *args, **kwargs)

  File "/usr/lib/python3.6/site-packages/container_service_extension/cse.py", line 239, in install

    ext_install=ext_install)

  File "/usr/lib/python3.6/site-packages/container_service_extension/configure_cse.py", line 644, in install_cse

    config = get_validated_config(config_file_name)

  File "/usr/lib/python3.6/site-packages/container_service_extension/configure_cse.py", line 328, in get_validated_config

    config = yaml.safe_load(config_file)

  File "/usr/lib/python3.6/site-packages/yaml/__init__.py", line 162, in safe_load

    return load(stream, SafeLoader)

  File "/usr/lib/python3.6/site-packages/yaml/__init__.py", line 114, in load

    return loader.get_single_data()

  File "/usr/lib/python3.6/site-packages/yaml/constructor.py", line 41, in get_single_data

    node = self.get_single_node()

  File "/usr/lib/python3.6/site-packages/yaml/composer.py", line 36, in get_single_node

    document = self.compose_document()

  File "/usr/lib/python3.6/site-packages/yaml/composer.py", line 55, in compose_document

    node = self.compose_node(None, None)

  File "/usr/lib/python3.6/site-packages/yaml/composer.py", line 84, in compose_node

    node = self.compose_mapping_node(anchor)

  File "/usr/lib/python3.6/site-packages/yaml/composer.py", line 127, in compose_mapping_node

    while not self.check_event(MappingEndEvent):

  File "/usr/lib/python3.6/site-packages/yaml/parser.py", line 98, in check_event

    self.current_event = self.state()

  File "/usr/lib/python3.6/site-packages/yaml/parser.py", line 439, in parse_block_mapping_key

    "expected <block end>, but found %r" % token.id, token.start_mark)

yaml.parser.ParserError: while parsing a block mapping

  in "config.yaml", line 1, column 1

expected <block end>, but found '-'

  in "config.yaml", line 87, column 1

root@photon-machine [ ~ ]#

Re: Kubernetes || CSE installation issue

$
0
0

  File "/usr/lib/python3.6/site-packages/yaml/parser.py", line 439, in parse_block_mapping_key

    "expected <block end>, but found %r" % token.id, token.start_mark)

yaml.parser.ParserError: while parsing a block mapping

  in "config.yaml", line 1, column 1

expected <block end>, but found '-'

  in "config.yaml", line 87, column 1

It looks like you have a syntax error in your config.yaml file.

 

You can try YAMLlint - The YAML Validator for validating your yaml file.

Re: Kubernetes || CSE installation issue

$
0
0

Hi Sebestian,

 

I checked this.It says as valid.

 

However,while running this command from CSE machine,i getting below error.

 

root@photon-machine [ ~ ]# cse check

Validating config file 'config.yaml'

Config file 'config.yaml' is invalid

root@photon-machine [ ~ ]#

Re: Orchestrate another Openstack vendors with VMware Cloud Drector

$
0
0

I have not done it before, but I presume there's vRealize Orchestrator integration into specific components of OpenStack. We can then present any vRealize Orchestrator workflow to vCloud Director. I'm not sure specifically what you're trying to accomplish, but that's my initial thoughts.


Re: Kubernetes || CSE installation issue

$
0
0

In this case you are probably using a config option that is not supported (maybe a typo) or an option has a value that is not allowed.

Re: Kubernetes || CSE installation issue

$
0
0

Thank you.but i could not find out where is the issue?

 

You can see the yaml config file.Attached.

 

Thanks,

Manivel R

Re: Orchestrate another Openstack vendors with VMware Cloud Drector

$
0
0

I can clarify some details:

 

I work in a company that developes his own openstack platform. Our customer has VMware Cloud Director for the VMware Openstack resources.

 

The customer is askig us if Vmware Cloud Director can manage whatever Openstack platform, not only VMware.

 

Thanks for the answers.

Re: Kubernetes || CSE installation issue

$
0
0

In the attached file the end seems to be missing. Because the comment is incomplete and the last line only consists of several tab stops.

 

So, a few things:

- Did you start by creating the config.yaml file with the command "cse sample --output config.yaml" or "cse sample > config.yaml" ?

- In the broker section you have line breaks in your descriptions. I'm not sure that's a problem. But I would remove it for a test.

- In the broker section you have an Org named CSE and an orgVDC with the name "Cse". Is that correct?

- Where did the last lines with "pks_config: null" come from? If you don't use pks I would recommend that you remove these lines completely.

 

And usually it's recommend to start and end a yaml file with "---" and "...".
Maybe it's worth a try to insert "---" into the first line and remove all tabstops in the last line and replace them with "...".

 

---

amqp:

  exchange: cse-ext

  host: 10.128.7.36

 

MORE CONTENT

 

    temp_vapp: ubuntu1604-temp

  type: default

  vdc: Cse

...

Re: Orchestrate another Openstack vendors with VMware Cloud Drector

$
0
0

There is not a way to manage an OpenStack platform in vCD today. We can execute workflows to a OpenStack platform, but that's the limit of capability.

Viewing all 7719 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>