-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Openstack builder connects to wrong endpoint #5201
Comments
If you can post the info required to reproduce this, we might be able to take a look. However, I suspect the mailing list might be a better place to ask for help.
hard to say what this connection is without seeing your scripts, but I'm certain this is a node that's launched as part of the build |
I don't know what I can post that would allow you to reproduce, as you do not have access to our cloud provider and it would not be prudent to share that information. What would be great is some way of getting better output from Packer about why the call failed. If you know of a way to do that, that could make a huge difference. As far as I can tell, that's the only way we can get to something of a repro out of this. I am not using any Amazon cloud services, but rather an entirely different provider. And as I said in the original message, tcpdump running while using the nova client does not show connections to the Amazon addresses. It could be spurious, but it's concerning. |
oh, I see, I think that's https://checkpoint.hashicorp.com/
you can disable by setting `CHECKPOINT_DISABLE=1`
…On Tue, Aug 1, 2017 at 12:44 PM JoelFeiner ***@***.***> wrote:
I don't know what I can post that would allow you to reproduce, as you do
not have access to our cloud provider and it would not be prudent to share
that information. What would be great is some way of getting better output
from Packer about why the call failed. If you know of a way to do that,
that could make a huge difference. As far as I can tell, that's the only
way we can get to something of a repro out of this.
I am not using any Amazon cloud services, but rather an entirely different
provider. And as I said in the original message, tcpdump running while
using the nova client does *not* show connections to the Amazon
addresses. It could be spurious, but it's concerning.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5201 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA9Agg7tYxP5XiqMsl__bJYY8IKRiNJks5sT4A0gaJpZM4Op-8R>
.
|
What is the output of:
|
openstack catalog list: https://gist.github.com/JoelFeiner/5857f90ce727606ccd3017fa30eae688
openstack flavor show A1.1
openstack network show XXX
|
Just a minor thing, in your OpenStack you use flavor
|
I switched to using A1.1 so that the image can be used for A1.1 instances, as well as the higher level ones. The only difference is that A1.1 has half as many CPUs, half as much RAM and half as much hard-drive space as A1.2. It's not relevant to this issue. |
This issue has been automatically migrated to hashicorp/packer-plugin-openstack#21 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-openstack#21. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I am attempting to build an image using the OpenStack provider. It ultimately fails at launching the server with the following message: "Error launching source server: Invalid request due to incorrect syntax or missing required parameters".
It is able to connect to the identity service, verify the flavor and set up the keypair (which might be a local thing).
One thing I am noticing is that tcpdump shows a lot of connections to ec2-54-235-77-197.compute-1.amazonaws.com, whereas when I launch the server with the nova client, there are none. I'm wondering if there's a hardcoded URL in Packer somewhere.
I'm unable to further debug this because Packer or the underlying library does not provide the response from the OpenStack server. From Googling, I see that this is simply not supported at the current juncture.
Packer 1.0.3
Ubuntu 17.04 64-bit
Build output: https://gist.github.com/JoelFeiner/7f7102e3324e4efc00980600217a07aa
Builder config in JSON file:
Environment variables set:
OS_AUTH_URL
OS_REGION_NAME
OS_IDENTITY_API_VERSION
OS_TENANT_NAME
OS_PASSWORD
OS_USERNAME
The text was updated successfully, but these errors were encountered: