-
Notifications
You must be signed in to change notification settings - Fork 24
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
Functionality #4
Comments
If I recall correctly, this is due to one of two things:
That second case is why I have all Azure images set as user data images, and use Azure custom script extensions to configure the hosts (there are fields during the host build for setting the URI and arguments to a script). I should mention that I'm not completely sure whether Foreman is incapable of handling passing a password to sudo, because I ran into difficulties attempting to persuade it to do so, and just used custom script extensions instead |
Does the SSH session get initiated from the foreman server, or is there logic somewhere to utilize a certain smart-proxy? We have our foreman server in a private datacenter, and a smart-proxy installation in Azure. |
It is initiated from the Foreman server |
Thanks. I'd settle for it to get created at this point, even without a finishing script. Nothing is getting initiated in Azure, it seems, when I submit a request in Foreman. I'm not sure if my data doesn't line up with a valid request in fog so it's getting dropped there, or something else. |
I have the same issue. It will successfully create in Foreman, but no machine is ever created at Azure. |
Can either of you attempt to create a machine, and dump the relevant portion of the logs somewhere I can see them? |
All Azure-related events grepped by event ID (third column of production.log) attached from both of my Foremans. |
Any luck here? I wanted to confirm that you could see the attachment. |
I can indeed see it, I'll go through it later this evening |
No worries.... I just wanted to make sure I attached the file right... upload form was being odd yesterday. |
@Jas612 It looks from your logs like you don't have any finish templates configured, and it's erroring on that. That said, this plugin does not play well with finish templates, because I could not find a way to get Foreman to sudo when attempting to run the finishing script. The way I've been using this is to mark all Azure templates as user data templates, and pass a script to the Azure custom script extension. There are fields for doing this during VM provisioning. |
Similar to @Jas612, I'm trying to figure out what I'm missing. Right now, my scripts are all blank (I'm just trying to get this created), but I defined one of each type - a User data, Finish, iPXE, Provisioning, and PXELinux. When I define a host, if I don't have a "Finishing" template linked for the OS, I get the error jas612 shows above. If I link a template (in my case here a blank one), I get logged immediately upon saving the host: Is my problem that my finishing template is blank? Is there some template you can share to help this deployment succeed? |
I'm now to the same place as @j-pavel is:
|
Any luck? |
Sorry, I just saw your replies. Have you guys used Foreman to provision on another compute provider? The demand for a finish template is built into Foreman, not this plugin. You'll need to set your images as being User data images for Foreman to look for a user data template instead of a finishing script. There is a checkbox in the template for doing this. |
When I do this, the host immediately creates in Foreman, but still does not in Azure. No SSH error this time, though, and no finish template error, this time. Logged create event: 2017-09-16 02:15:38 e37d9d5b [app] [I] Started POST "/hosts" for 172.24.107.78 at 2017-09-16 02:15:38 -0400 |
Can you do a build and provide me with your logs again? Also, are you able to build with other compute providers? |
Done. I log rotated production.log RIGHT BEFORE I hit the Create button in the UI, and copied it shortly after (this is a production system with over 1000 hosts on multiple compute providers). The logs:
|
Any ideas? |
I think I may have found something http://projects.theforeman.org/issues/20098 It looks like, on create, the screen cannot resolve user-data templates, which are the thing you told us to use. So, patching to 1.15.4 apparently fixes. I'll give it a shot and get back to you. |
I'm pegged to 1.14 for other reasons for next few months, and was unaware of that. That said, the user data template does not actually do anything, any post-deployment configuration must be done with the custom script extension. I'm having difficulty figuring out why it's not creating your VM in the first place, I've never encountered such an issue. Not without an error and accompanying stack trace in the logs anyway. |
1.14... that's the key. I setup a green-field instance of 1.14 in Azure and setup this module. It works like a charm. So, I'm guessing your module isn't compatible with 1.15 |
Well damn. I'll have to look into why that's the case. However, in the interest of full disclosure I have moved on to using ManageIQ for provisioning, and now only use Foreman as an ENC; it may be some time before I fix this compatibility issue. I of course welcome PRs |
The issue seems to be related to https://projects.theforeman.org/issues/23859 which is fixed by the PR theforeman/foreman#5675 |
I got this installed in Foreman 1.15.3... when I create a host, it submits successfully, and goes to a "pending installation" state in Foreman. Watching the logs, I see an immediate log message:
Failed to login via SSH to foreman-deployed.dev.mcs.az-eastus2.mob.nuance.com: ERF42-1994 [Foreman::Exception]: Unable to find proper authentication method
| Foreman::Exception: ERF42-1994 [Foreman::Exception]: Unable to find proper authentication method
| /usr/share/foreman/app/models/concerns/orchestration/ssh_provision.rb:53:in `setSSHWaitForResponse'
... is there some other setting necessary before the image can be deployed?
The text was updated successfully, but these errors were encountered: