Project

General

Profile

Actions
Copy link

Bug #7031

closed

Provisioning to EC2 is not working and not logging

Added by Ashton Davis almost 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Compute resources - EC2
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
1.5.2
Red Hat JIRA:

Description

I've set up an EC2 (VPC) compute resource, and assigned an image, userdata file, etc - but it won't provision.
See this Foreman-Users post for reference
https://groups.google.com/forum/#!searchin/foreman-users/ec2/foreman-users/KeVB6fGaMUk/1N9uD0Ap0Y8J
That's the exact same error I have. The keys I'm using in the resource are full-access keys, the AMI is accessible, they're all in the same region - it's failing on SOMETHING, but not logging what.

I did also follow Lukas' advice and enabled REST debugging - no additional output.

This is a blocker for progress at the moment - any help would be most appreciated. Here are my package versions:

foreman-libvirt-1.5.2-1.el6.noarch
ruby193-rubygem-foreman_bootdisk-2.0.5-1.el6.noarch
ruby193-rubygem-foreman_setup-2.0.3-1.el6.noarch
foreman-release-1.5.0-0.2.RC2.el6.noarch
rubygem-foreman_api-0.1.11-1.el6.noarch
foreman-installer-1.5.0-0.2.RC2.el6.noarch
foreman-1.5.2-1.el6.noarch
foreman-vmware-1.5.2-1.el6.noarch
foreman-postgresql-1.5.2-1.el6.noarch
foreman-proxy-1.5.2-1.el6.noarch
ruby193-rubygem-foreman_xen-0.0.1-1.el6.noarch
foreman-compute-1.5.2-1.el6.noarch
foreman-console-1.5.2-1.el6.noarch
rubygem-hammer_cli_foreman-0.1.1-1.el6.noarch

Actions
Copy link

Also available in: Atom PDF