VM has reported a failure when processing extension 'install_ansible'.

[ddska]

Deployment fails with this message:

OPERATION ID A91E732E060884E8
TRACKING ID a2847df6-3422-45ce-9585-46cb993c2251
STATUS Conflict
PROVISIONING STATE Failed
TIMESTAMP 6/29/2016, 3:58:42 PM
DURATION PT2M0.9183369S
TYPE Microsoft.Compute/virtualMachines/extensions
RESOURCE ID /subscriptions/0e1db2df-902f-4671-8bfe-c3c9215f6f66/resourceGroups/kuber8grp/providers/Microsoft.Compute/virtualMachines/hckub8ms/extensions/install_ansible
STATUSMESSAGE {
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "VMExtensionProvisioningError",
        "message": "VM has reported a failure when processing extension 'install_ansible'. Error message: \"Enable failed:Not found (The specified container does not exist.)\"."
      }
    ]
  }
}
RESOURCE hckub8ms/install_ansible

[pjshi23]

I got the same error.

[stephgou]

Hi, Sorry about that and about the delay to correct this issue. In fact, the error was due to a change in EPEL. The current active repository is EPEL_REPO="http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-7.noarch.rpm" I updated the deploy.sh file in GitHub. You'll have to publish this new deploy.sh version in your storage vault to have the last template work. Best regards Stéphane

[pjshi23]

sorry @stephgou , issue happened again:

STATUSMESSAGE{ "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'install_ansible'. Error message: "Enable failed:Not found (The specified container does not exist.)"." } ] } }

seems repo is not the root cause

[herveleclerc]

Hello, I think it's because of missing storage for ssh keys

Hervé Leclerc CTO Alter Way 227 Bureaux de la colline 1 rue Royale - Bât. D 92210 Saint-Cloud France +33 141168336 +33 6 83979598

like a halo in reverse

On Mon, Jul 18, 2016 at 9:16 AM, pjshi23 [email protected] wrote:

sorry @stephgou https://github.com/stephgou , issue happened again:

STATUSMESSAGE{ "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'install_ansible'. Error message: "Enable failed:Not found (The specified container does not exist.)"." } ] } }

seems repo is not the root cause

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DXFrance/AzureKubernetes/issues/1#issuecomment-233252450, or mute the thread https://github.com/notifications/unsubscribe-auth/AAO8CaQOVon_m3pNg7LY5HJ94_Mk1K9gks5qWyhegaJpZM4JBg6W .

[pjshi23]

@herveleclerc seems so.

checked the script. seems all the parameters are fixed etc.

log "Create ssh configuration for root" "0"

cat << 'EOF' >> ~/.ssh/config

Host *

user devops

StrictHostKeyChecking no

EOF

error_log "Unable to create ssh config file for root"

cp id_rsa ~/.ssh/id_rsa

error_log "Unable to copy id_rsa key to root .ssh directory"

cp id_rsa.pub ~/.ssh/id_rsa.pub

error_log "Unable to copy id_rsa.pub key to root .ssh directory"