Error Deploy - SLES - Debug #689

penguinpages · 2023-09-23T13:59:15Z

penguinpages
Sep 23, 2023

I am trying to deploy SLES 15u4 or u5 via packer.

This workflow is very well documented and very helpful in options but trying to debug an issue.

I have gone through setup three times no on different systems to try to rule out not following all steps /directions and still gettting same failure. I also tried SLES 15u5 (change ISO/md5, versions references etc..) and get same error. So not thinking this is SLES version issue.

vsphere-iso.linux-sles: TASK [users : Adding authorized_keys for the default local user.] **************
    vsphere-iso.linux-sles: changed: [default]
    vsphere-iso.linux-sles:
    vsphere-iso.linux-sles: TASK [users : Adding the default local user to passwordless sudoers.] **********
    vsphere-iso.linux-sles: changed: [default]
    vsphere-iso.linux-sles:
    vsphere-iso.linux-sles: TASK [users : Creating a local user for Ansible.] ******************************
    vsphere-iso.linux-sles: changed: [default]
    vsphere-iso.linux-sles:
    vsphere-iso.linux-sles: TASK [users : Adding authorized_keys to the local user for Ansible.] ***********
    vsphere-iso.linux-sles: fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in <sensitive>.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo /home/<sensitive>/.<sensitive>/tmp `\"&& mkdir \"` echo /home/<sensitive>/.<sensitive>/tmp/<sensitive>-tmp-1695420235.3279278-41817-120283653696923 `\" && echo <sensitive>-tmp-1695420235.3279278-41817-120283653696923=\"` echo /home/<sensitive>/.<sensitive>/tmp/<sensitive>-tmp-1695420235.3279278-41817-120283653696923 `\" ), exited with result 1", "unreachable": true}
    vsphere-iso.linux-sles:
    vsphere-iso.linux-sles: PLAY RECAP *********************************************************************
    vsphere-iso.linux-sles: default                    : ok=7    changed=4    unreachable=1    failed=0    skipped=8    rescued=0    ignored=0
    vsphere-iso.linux-sles:
==> vsphere-iso.linux-sles: Provisioning step had errors: Running the cleanup provisioner, if present...
==> vsphere-iso.linux-sles: Power off VM...
==> vsphere-iso.linux-sles: Destroying VM...
    vsphere-iso.linux-sles: Closing sessions ....
Build 'vsphere-iso.linux-sles' errored after 17 minutes 58 seconds: Error executing Ansible: Non-zero exit status: exit status 4

==> Wait completed after 17 minutes 58 seconds

==> Some builds didn't complete successfully and had errors:
--> vsphere-iso.linux-sles: Error executing Ansible: Non-zero exit status: exit status 4

==> Builds finished but no artifacts were created.

So failure is in post customization before it build it info golden image in vcenter image repo:

packer-examples-for-vsphere\ansible\users/task/linux.yml -->
sudo mkdir -p /home/{{ANSIBLE_USERNAME}}/.ssh

Cannot make the directory.

only variable called in that task are {{ANSIBLE_USERNAME}}

Which is used in previous task and that seems to pass. So trying to debug.

This brings up second question. How can I add a --debug (where packer stops vs destroying deployment ) so I can shell into host and poke around.

when I run .build.sh you can't directly pass --debug

So I tried to stick on end of execution stanza but it does not work.

Start the Build.

echo "Starting the build...."
packer build -force
-var-file="$CONFIG_PATH/vsphere.pkrvars.hcl"
-var-file="$CONFIG_PATH/build.pkrvars.hcl"
-var-file="$CONFIG_PATH/ansible.pkrvars.hcl"
-var-file="$CONFIG_PATH/proxy.pkrvars.hcl"
-var-file="$CONFIG_PATH/common.pkrvars.hcl"
"$INPUT_PATH" --debug # Add in note for debug so vm is not destroyed upon error

#########

Question:

Any ideas on why user can be created but not create .ssh directory within user's home ?
Where can I set --debug for packer where if it has error it halts vs tearing down failed deployment.

Thanks,

Answered by tenthirtyam

Sep 23, 2023

Try adding the following to the ansible.cfg file.

remote_tmp  = /tmp/

View full answer

tenthirtyam · 2023-09-23T19:54:01Z

tenthirtyam
Sep 23, 2023
Maintainer

Try adding the following to the ansible.cfg file.

remote_tmp  = /tmp/

0 replies

penguinpages · 2023-09-24T13:13:39Z

penguinpages
Sep 24, 2023
Author

Thanks. That fixed it for me.

Is this issue unique to Ubuntu ( I use this as my local runner for CI)...

0 replies

tenthirtyam · 2023-09-24T13:35:22Z

tenthirtyam
Sep 24, 2023
Maintainer

Haven't seen it before but seemed logical based on the output.

0 replies

penguinpages · 2023-09-25T14:24:23Z

penguinpages
Sep 25, 2023
Author

Do we have any comment on where / how to add a packer --debug command so VM upon fail does not tear down but waits for input?

Also part of this would be where one could run equivalent of build.sh menu selection via single command: I tried the only example in README.md which is for windows.. but when I try to extrapolate to Linux builds, I get below return like I did not tell it correct path to varables file.

ansible@runner00:~/git/gitlab/rke_poc/acme.local/packer-examples-for-vsphere$ packer build -force -var-file="config/vsphere.pkrvars.hcl" -var-file="config/build.pkrvars.hcl" -var-file="config/common.pkrvars.hcl"  builds/linux/ubuntu/22-04-lts
Warning: Bundled plugins used

This template relies on the use of plugins bundled into the Packer binary.
The practice of bundling external plugins into Packer will be removed in an
upcoming version.

To remove this warning, add the following section to your template:

packer {
  required_plugins {
    vsphere = {
      source  = "github.com/hashicorp/vsphere"
      version = "~> 1"
    }
    ansible = {
      source  = "github.com/hashicorp/ansible"
      version = "~> 1"
    }
  }
}

Then run 'packer init' to manage installation of the plugins

Error: Unset variable "ansible_username"

A used variable must be set or have a default value; see
https://packer.io/docs/templates/hcl_templates/syntax for details.

Error: Unset variable "ansible_key"

A used variable must be set or have a default value; see
https://packer.io/docs/templates/hcl_templates/syntax for details.

I tried to poke around to figure out what it is expecting for variables but figured maybe someone has can just post (and maybe document) single command that would be output from menu option selection.

2 replies

tenthirtyam Sep 25, 2023
Maintainer

I've captured this as a backlog item to add a debug option to the menu.

tenthirtyam Sep 26, 2023
Maintainer

Included in #706 and #705

penguinpages · 2023-09-25T15:30:56Z

penguinpages
Sep 25, 2023
Author

any example of single command Deploy Linux?

Example SLES works fine.. But what is the single line command that I can build into CI process

1 reply

tenthirtyam Sep 25, 2023
Maintainer

It's include in the README.md for Windows builds:

This should work for SLES:

packer build -force -on-error=ask \
     -var-file=config/vsphere.pkrvars.hcl \
     -var-file=config/build.pkrvars.hcl \
     -var-file=config/ansible.pkrvars.hcl \
     -var-file=config/proxy.pkrvars.hcl \ 
     -var-file=config/common.pkrvars.hcl \
     -var-file=config/scc.pkrvars.hcl \
     builds/linux/sles/15

penguinpages · 2023-09-25T18:21:46Z

penguinpages
Sep 25, 2023
Author

Tried that.

Also thought maybe issue was shell context

ansible@runner00:~/git/gitlab/rke_poc/acme.local/packer-examples-for-vsphere$ packer build -force -on-error=ask \
-var-file=config/vsphere.pkrvars.hcl \
-var-file=config/build.pkrvars.hcl \
-var-file=config/ansible.pkrvars.hcl \
-var-file=config/proxy.pkrvars.hcl \ 
-var-file=config/common.pkrvars.hcl \
-var-file=config/scc.pkrvars.hcl \
builds/linux/sles/15
" ": stat  : no such file or directory
-bash: -var-file=config/common.pkrvars.hcl: No such file or directory
ansible@runner00:~/git/gitlab/rke_poc/acme.local/packer-examples-for-vsphere$ pwd
/home/ansible/git/gitlab/rke_poc/acme.local/packer-examples-for-vsphere
ansible@runner00:~/git/gitlab/rke_poc/acme.local/packer-examples-for-vsphere$ ls
ansible  artifacts  builds  build.sh  build.tmpl  build.yaml  CHANGELOG.md  CODE_OF_CONDUCT.md  config  config.sh  CONTRIBUTING.md  LICENSE  MAINTAINERS.md  manifests  NOTICE  README.md  scripts  set-envvars.sh  terraform
ansible@runner00:~/git/gitlab/rke_poc/acme.local/packer-examples-for-vsphere$ packer build -force -on-error=ask \
-var-file=./config/vsphere.pkrvars.hcl \
-var-file=./config/build.pkrvars.hcl \
-var-file=./config/ansible.pkrvars.hcl \
-var-file=./config/proxy.pkrvars.hcl \ 
-var-file=./config/common.pkrvars.hcl \
-var-file=./config/scc.pkrvars.hcl \
builds/linux/sles/15
" ": stat  : no such file or directory
-bash: -var-file=./config/common.pkrvars.hcl: No such file or directory

1 reply

penguinpages Sep 25, 2023
Author

Something with shell and esc characters

This worked

packer build -force -on-error=ask -var-file=./config/vsphere.pkrvars.hcl -var-file=./config/build.pkrvars.hcl -var-file=./config/ansible.pkrvars.hcl -var-file=./config/proxy.pkrvars.hcl -var-file=./config/common.pkrvars.hcl -var-file=./config/scc.pkrvars.hcl builds/linux/sles/15

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error Deploy - SLES - Debug #689

{{title}}

Replies: 6 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Error Deploy - SLES - Debug #689

penguinpages Sep 23, 2023

Start the Build.

Replies: 6 comments · 4 replies

tenthirtyam Sep 23, 2023 Maintainer

penguinpages Sep 24, 2023 Author

tenthirtyam Sep 24, 2023 Maintainer

penguinpages Sep 25, 2023 Author

tenthirtyam Sep 25, 2023 Maintainer

tenthirtyam Sep 26, 2023 Maintainer

penguinpages Sep 25, 2023 Author

tenthirtyam Sep 25, 2023 Maintainer

penguinpages Sep 25, 2023 Author

penguinpages Sep 25, 2023 Author

penguinpages
Sep 23, 2023

Replies: 6 comments 4 replies

tenthirtyam
Sep 23, 2023
Maintainer

penguinpages
Sep 24, 2023
Author

tenthirtyam
Sep 24, 2023
Maintainer

penguinpages
Sep 25, 2023
Author

tenthirtyam Sep 25, 2023
Maintainer

tenthirtyam Sep 26, 2023
Maintainer

penguinpages
Sep 25, 2023
Author

tenthirtyam Sep 25, 2023
Maintainer

penguinpages
Sep 25, 2023
Author

penguinpages Sep 25, 2023
Author