-
Notifications
You must be signed in to change notification settings - Fork 73
rarely conjure-up will fail at the end with a sudo password issue #1386
Comments
The only reason I can think this might happen would be that sudo had cached auth at the start of the deployment that expired during the deployment. But I would expect the validation on the steps input screen would still require you to enter the password and validate it. Maybe there's an issue with that which lets invalid passwords through when there's cached auth? |
Of course, the better fix would be to remove the requirement for entering the root password entirely, but that would require making |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
sudo passwd - worked for me on this issue in the same env/versions, It was frustrating and really Simple to fix - after allot of effort on a fresh Artful install. This was the 2nd run on this where I received this error on a pretty minimal fresh box. From out of the box ubuntu server and snapd packages with Lxd 1.Insure non root user (ubuntu/set.usr.path.var) member of sudo group - sudo passwd (newpass) I posted this here because very little comes back search wise on sudo failure during conjure. |
Report
Thank you for trying conjure-up! Before reporting a bug please make sure you've gone through this checklist:
sudo snap refresh conjure-up --edge
?Please provide the output of the following commands
What Spell was Selected?
canonical-kubernetes
What provider (aws, maas, localhost, etc)?
aws
Commands ran
conjure-up canonical-kubernetes
Additional Information
The text was updated successfully, but these errors were encountered: