Modify Ansible Tower inventory moment

This post was originally published on this site

Hi all,

 

We’ve added a Ansible Tower integration to vRA8 and so far so good. But a action to add the vm to the inventory is triggered before the vm is finished.. Should this succeed before the vm is ready, or does this have to wait??

 

If it has to wait, how can I change this?

 

I’m getting this error:

Ansible create workflow failed with error. Unable to add host to the inventory with Id: 5.

 

I have a Windows 2016 image with a Customization Specification containing this:

  • 1 auto logons as Administrator
  • 1 RunOnce command to enable remote Powershell and WinRM:

C:WindowsSystem32WindowsPowerShellv1.0powershell.exe -Command "&{Enable-PSRemoting -Force; winrm quickconfig -force;}"

Bad vCenter Server logon

This post was originally published on this site

Hi, we’re using Horizon 7.6.0 and everything looks fine except that we get a lot of failed logon attempts to the vCenter server from one of the connection servers.

 

In the log file from the connection server we get a lot of these:

2020-07-08T09:55:33.573+02:00 DEBUG (0F68-1FF8) <VC thread> [VimClientConnection] Invalid VC login: ‘Cannot complete login due to an incorrect user name or password.’. Check username and password for VirtualCenter at https://[vCenter]:443/sdk com.vmware.vdi.logger.Logger.debug(Logger.java:44)

com.vmware.vim25hic.InvalidLoginFaultMsg: Cannot complete login due to an incorrect user name or password.

    at sun.reflect.GeneratedConstructorAccessor19482.newInstance(Unknown Source)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)

    at org.apache.cxf.interceptor.ClientFaultConverter.processFaultDetail(ClientFaultConverter.java:183)

    at org.apache.cxf.interceptor.ClientFaultConverter.handleMessage(ClientFaultConverter.java:83)

    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)

    at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112)

    at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)

    at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)

    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)

    at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:835)

    at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1684)

    at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1560)

    at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1361)

    at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)

    at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:658)

    at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63)

    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)

    at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:535)

    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:444)

    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:345)

    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:298)

    at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)

    at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)

    at com.sun.proxy.$Proxy158.login(Unknown Source)

    at com.vmware.daas.cloneprep.vcsubsystem.VimClientConnection.login(VimClientConnection.java:349)

    at com.vmware.daas.cloneprep.vcsubsystem.VimClientConnection.<init>(VimClientConnection.java:328)

    at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.reconnect(VcSubsystem25.java:532)

    at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.checkVcConnection(VcSubsystem25.java:959)

    at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.getPropCol(VcSubsystem25.java:599)

    at com.vmware.daas.cloneprep.vcsubsystem.PropertyCollectorUpdateTracker.createFilterSpec(PropertyCollectorUpdateTracker.java:419)

    at com.vmware.daas.cloneprep.vcsubsystem.PropertyCollectorUpdateTracker.checkTasks(PropertyCollectorUpdateTracker.java:942)

    at com.vmware.daas.cloneprep.vcsubsystem.PropertyCollectorUpdateTracker.run(PropertyCollectorUpdateTracker.java:338)

    at java.lang.Thread.run(Thread.java:748)

2020-07-08T09:55:33.577+02:00 ERROR (0F68-1FF8) <VC thread> [VimClientConnection] Unable either to logout from url:https://[vCenter5]:443/sdk with username: [username] or to dispose the connection.

 

In the Horizon Administrator system health is green, and I’ve checked the configuration, but does anybody have a suggestion where the username/password comes from?

 

Any help is welcome.

 

Regards

Peter

Cloning a vm via dcli – is it possible?

This post was originally published on this site

One of the blogs Considerations for vSphere Component Backup and Restore: Part 1 – VMware vSphere Blog  suggests the Datacentre CLI ( dcli) can be used for backup purposes.

Having looked through all the available commands with this api like interface I am not so sure. I can see that you can create a vm but backing up or cloning a vm seems to be missing.

Is the blog correct and there is some undocumented command that allows for vm cloning?

 

Thanks
Paul

Unable to delete the assignment because inventory updates are in progress

This post was originally published on this site

Hello Team, we are getting an error message as “Unable to delete the assignment because inventory updates are in progress. Please wait a few minutes and try again.” when deleting an assignment. The assignment is offline and there is no desktop in it. Moreover, the error message remain same last 20 hours. The POD version is “1976.3“. Is there any possibility for us find out the issue ?

Outlook SSO window disappearing

This post was originally published on this site

Hi All

 

We have an issue that occurs from time to time where Outlook will start looking for credentials, and when we click on the provide password the workspace one windows pops up and flashes away instantly not allowing the user to sign in. It open happens in Outlook and it’s on random machines / user profiles. If another user logs in they can open Outlook just fine.

 

Sometimes clearing the SSO key from credential manager and signing into workspace one via teams or OWA etc will fix it but I have one laptop at the moment thats not working for, blowing away his profile will fix it but is there any easier way to fix this? Would this be a Windows / Office issue or is it related to his workspace one profile?

 

Thanks

Migrating VMware VMs to VMware on AWS

This post was originally published on this site

Dear experts,

 

We are in process of moving on-premises VMware environment to VMware on AWS. However there is a problem that customer’s Data center service provider is not allowing to provided us with the authority to install OVA (HCX in this case) on there vSphere.

 

Is there an alternative say – if we copy existing vmdk files and build the VMs on VMware on AWS ? The existing VMs hold SAP systems onto those.

 

Please help with your valuable suggestions.

 

Thank you in advance!

Sujit

ESXi 6.5 U3 Doesn’t Display Locally Attached Storage Devices

This post was originally published on this site

Coming hot off the heels of the previous issue, I now have yet another one to attend to. I have the following drives sitting in the DL580 G7’s front bays:

  • 1x HP 518216-002 146GB HDD
  • 1x Western Digital WD Blue 3D NAND 500GB SATA SSD
  • 4x HP 507127-B21 300GB HDDs
  • 1x 500GB Seagate Video ST500VT003 HDD

 

But only the HP 518216-002 and one of the HP 507127-B21’s seem to have been detected by ESXi. However, if I look in iLO 3 (HP remote management), all of the drives show up. The SSD shows up as faulty, which means that it is possibly incompatible with my server. I can deal with the SSD issue later. My primary concern is that most of my spinning disks aren’t detected in ESXi, even though iLO 3 shows them as being fault-free. Do I simply need to initialise the drives first, or am I missing something here? I apologise if this is a stupid question. Any assistance would be appreciated.

Announcing a second Local Zone in Los Angeles

This post was originally published on this site

In December 2019, Jeff Barr published this post announcing the launch of a new Local Zone in Los Angeles, California. A Local Zone extends existing AWS regions closer to end-users, providing single-digit millisecond latency to a subset of AWS services in the zone. Local Zones are attached to parent regions – in this case US West (Oregon) – and access to services and resources is performed through the parent region’s endpoints. This makes Local Zones transparent to your applications and end-users. Applications running in a Local Zone have access to all AWS services, not just the subset in the zone, via Amazon’s redundant and very high bandwidth private network backbone to the parent region.

At the end of the post, Jeff wrote (and I quote) – “In the fullness of time (as Andy Jassy often says), there could very well be more than one Local Zone in any given geographic area. In 2020, we will open a second one in Los Angeles (us-west-2-lax-1b), and are giving consideration to other locations.”

Well – that time has come! I’m pleased to announce that following customer requests, AWS today launched a second Local Zone in Los Angeles to further help customers in the area (and Southern California generally) to achieve even greater high-availability and fault tolerance for their applications, in conjunction with very low latency. These customers have workloads that require very low latency, such as artist workstations, local rendering, gaming, financial transaction processing, and more.

The new Los Angeles Local Zone contains a subset of services, such as Amazon Elastic Compute Cloud (EC2), Amazon Elastic Block Store (EBS), Amazon FSx for Windows File Server and Amazon FSx for Lustre, Elastic Load Balancing, Amazon Relational Database Service (RDS), and Amazon Virtual Private Cloud, and remember, applications running in the zone can access all AWS services and other resources through the zone’s association with the parent region.

Enabling Local Zones
Once you opt-in to use one or more Local Zones in your account, they appear as additional Availability Zones for you to use when deploying your applications and resources. The original zone, launched last December, was us-west-2-lax-1a. The additional zone, available to all customers now, is us-west-2-lax-1b. Local Zones can be enabled using the new Settings section of the EC2 Management Console, as shown below

As noted in Jeff’s original post, you can also opt-in (or out) of access to Local Zones with the AWS Command Line Interface (CLI) (aws ec2 modify-availability-zone-group command), AWS Tools for PowerShell (Edit-EC2AvailabilityZoneGroup cmdlet), or by calling the ModifyAvailabilityZoneGroup API from one of the AWS SDKs.

Using Local Zones for Highly-Available, Low-Latency Applications
Local Zones can be used to further improve high availability for applications, as well as ultra-low latency. One scenario is for enterprise migrations using a hybrid architecture. These enterprises have workloads that currently run in existing on-premises data centers in the Los Angeles metro area and it can be daunting to migrate these application portfolios, many of them interdependent, to the cloud. By utilizing AWS Direct Connect in conjunction with a Local Zone, these customers can establish a hybrid environment that provides ultra-low latency communication between applications running in the Los Angeles Local Zone and the on-premises installations without needing a potentially expensive revamp of their architecture. As time progresses, the on-premises applications can be migrated to the cloud in an incremental fashion, simplifying the overall migration process. The diagram below illustrates this type of enterprise hybrid architecture.

Anecdotally, we have heard from customers using this type of hybrid architecture, combining Local Zones with AWS Direct Connect, that they are achieving sub-1.5ms latency communication between the applications hosted in the Local Zone and those in the on-premises data center in the LA metro area.

Virtual desktops for rendering and animation workloads is another scenario for Local Zones. For these workloads, latency is critical and the addition of a second Local Zone for Los Angeles gives additional failover capability, without sacrificing latency, should the need arise.

As always, the teams are listening to your feedback – thank you! – and are working on adding Local Zones in other locations, along with the availability of additional services, including Amazon ECS Amazon Elastic Kubernetes Service, Amazon ElastiCache, Amazon Elasticsearch Service, and Amazon Managed Streaming for Apache Kafka. If you’re an AWS customer based in Los Angeles or Southern California, with a requirement for even greater high-availability and very low latency for your workloads, then we invite you to check out the new Local Zone. More details and pricing information can be found at Local Zone.

— Steve

Problem with snapshot, only on one host of the cluster

This post was originally published on this site

I have a cluster of 2 hosts.

 

When i make a snapshot from an host all goes ok. When i make the snapshot from the other host the vm fail and stop and i have an alert that i need to consolidate the disk. Remove snapshot or consolidation is impossible, until i migrate the vm to the other host where i can consolidate disk, and start vm without problem.

 

Where can i search the issue to troubleshoot the problem?

 

The 2 hosts are equals.

 

Thanks.

Iron Castle Systems