-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
Axiom-init not working with Azure #262
Comments
@ResistanceIsUseless Thank you for letting us know. Would you mind adding |
Hi, I can confirm it wont deploy instances, and I've noticed there's a mismatch between the values provided during account setup and the ones used during image building, (region and something else I cant remeber) I think it could be related to the bug.
|
I can confirm the bug is related to the image building script, but I dont know how o where to fix it. |
Image creation worked for me in azure but not deploying. Manually creating
the VM worked i just haven't had the time to update the script and retry
building the VM. I'll try and get to that today or tomorrowand paste some
output as well as my review of the script. I think one of the switches
might be unneeded or a wrong value.
…On Mon, Mar 22, 2021 at 5:18 PM Francisco Díaz ***@***.***> wrote:
I can confirm the bug is related to the image building script, but I dont
know how o where to fix it.
-> when provisioning the image it is always built at "eastus", so when
creating an instance it is wrongly referenced.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#262 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKCJ2N6RITYLZZZPM7WLQLTE7M5LANCNFSM4ZPKIOIA>
.
|
just tested it out and i get the following error with the command axiom is sending to ARM CLI.
Running it again manually and adding "--admin-username axiom" resolves the issue. I'm not sure if that got changed away from the azure default someplace or it's now required. The az vm create -h doesn't say it's required. |
@ResistanceIsUseless @cthulhu897 I updated the azure builder https://github.com/pry0cc/axiom/blob/master/images/builders/azure.json to include region. Can you run axiom-update and axiom-build, axiom-init to see if that fixes it? If not i'll make time later tonight and recreate. thanks guy for bringing this issue forward! To debug, I would also add |
I had to run |
@ResistanceIsUseless let us know if youre still having issues. If everything is copacetic, feel free to close. |
Did axiom-update, axioom-account-setup, axiom-init right now and the build from image to vm still fails. Looks like it's still not liking the missing username. I then did the following(below) and re-ran everything and it fixed it. This could just be something wrong with me if @cthulhu897 wasn't having any issues. I added "--admin-username op" to the following line https://github.com/pry0cc/axiom/blob/master/providers/azure-functions.sh#L58
Once I did that and reran axiom-init it successfully built the VM from the image. Feel free to close this out if it's just me having this issue or leave it open to see if other azure users have issues. I'm not sure if hardcoding the username would break building for people not running into this issue. Weird that this fixes it for me if it's still a region issue.
|
@ResistanceIsUseless after provisioning an instance like that, can you ssh into it and axiom is set up? That is an odd issue, and I havent read anything to suggest the username is required. Can you try to run axiom-build again and see if that makes a difference? If that doesnt work, I would suggest setting up axiom on a fresh VPS or VM to test. I still havent had time to attempt an azure fleet, I hope to have some time tonight. Reach out to us on Discord as well if you are still experiencing issues. Thanks you! |
I'd suggest removing ~/.axiom and also all the resources in your azure panel, and then try it again. |
Everything works as expected when provisioning like this. So I'm guessing its just me. If it causes any issues I'll delete everything and start over. |
WARNING: Command group 'vm' is experimental and under development. Reference and support levels: https://aka.ms/CLI_refstatus
ssh: Could not resolve hostname moser15: nodename nor servname provided, or not known
Looks like whatever az commands axiom is using have been changed. :-/
The text was updated successfully, but these errors were encountered: