Azure opsman will not allow ssh access until the config is reset about pcf-pipelines

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[calebwashburn]

The latest stable release comes from network.pivotal.io. (https://network.pivotal.io/products/pcf-automation) if you don't have access you need to request this via your sales organization. That being said, I think the problem is you are passing the public key .pub instead of private key. This should match what is in the parameter pcf_ssh_key_priv: (https://github.com/pivotal-cf/pcf-pipelines/blob/master/install-pcf/azure/params.yml#L198)

[gondoi]

I'm passing in both and they work and match. I've tested on other servers. Although, I have come to find out it's not related to this pipeline, but the image for opsman itself. I upgraded the opsman server and after the new image boots up, ssh no longer works, even when attempting to reset the key through Azure. There is a diff and there are a lot of options removed after resetting the configuration (which allows access via the original key).