Incorrect sudo password when running [singleplatform-eng.users : Per-user group creation] on the seed VM #65
Comments
|
Hi @Banshee1221. The Can you ssh to centos@192.168.33.5? |
|
Hi @markgoddard, yes I seem to be able to connect. It does, however, take around 3 minutes to get to prompt. |
|
Often long timeouts with SSH indicates a problem with DNS resolution inside the server you are connecting to. Can you check that? |
|
I had a look at the DNS and it wouldn't appear to be an issue there.. I can eventually get to the prompt, though. The timeout extension does help me get past that anyway. Any other suggestions there? |
|
Hi @Banshee1221 the pattern of taking ages to connect, but eventually getting there really does sound like you have If it is not that we'll need to think of other ways the machine is working, but extremely slowly. Can you check if hardware virtualisation support is enabled in your bare metal host (eg, use |
|
Hi @oneswig thanks for the response. I had a brain-fart and didn't think to actually check the seed vm. I only verified that the DNS settings on the host were correct (not sshd). I went ahead and looked through the Ansible and found that the seed vm root volume is at I've also verified that the vmx flag is on for hardware virtualisation and VT-x is set in BIOS. |
|
If you SSH to the seed |
|
No, I'm prompted for a password. I assumed that this was normal.
|
|
This is the cause of your issues. Kayobe is trying to use Normally the |
|
There is no file called Do the Ansible scripts copy EDIT: Manually setting I wonder if there's some cloud-init step that's not running correctly? |
|
So this may be off topic and please let me know if I should open a new ticket around this, but the reason I'm posting it here is because it's possible that it's all related to the seed VM. After manual adding the centos user This kind of leads me to believe that perhaps there's some issue with the creation of the seed VM? This could also be a totally unrelated bug, though, and I haven't gotten past it yet. Perhaps I'm missing something here, but I haven't had the time to dig through all of the Ansible. EDIT: This doesn't seem to be network related, as I can reach https://pypi.python.org via |
|
It does sound like something has gone wrong during the creation of the VM. I would expect cloud-init to create the |
|
Hi @markgoddard. Sorry for the delay in response. I poked around and found this: As for DNS, I'm not 100% sure yet. |
Hello,
This seems to apply to stable/train and stable/rocky.
I have a bare-metal server that I'm trying to run UFN on. I have a stock CentOS 7.8 install and have created a
centosuser withNOPASSWDset for sudo access and thecentosuser does have a password set.Everything seems to run fine up to the point where the seed VM is accessed in
./dev/seed-deploy.sh. I originally struggled with "Timeout (12s) waiting for privilege escalation prompt:", but after adjusting the timeout I'm now faced with "Incorrect sudo password." I can't access the VM viasshfrom thecentosuser either. I've also tried this withANSIBLE_BECOME_ASK_PASS=1.Any ideas?
Here's a dump of that last action with
ANSIBLE_DEBUG=1:The text was updated successfully, but these errors were encountered: