Hello All,
So, I have Saltstack Config deployed and a manual installation of a minon works fine. I can then manipulate my Ubuntu target through the minion from the Salt master.
The issue that I am now having however, is when I try to deploy the Salt Minion from the cloud template. vRA and Saltstack are both the latest versions. This is the cloud template.
formatVersion: 1
inputs:
size:
type: string
title: Size
encrypted: false
enum:
- small
- medium
- large
platform:
type: string
title: Platform
enum:
- silver
- gold
resources:
Cloud_vSphere_Machine:
type: Cloud.vSphere.Machine
properties:
image: ubuntu_cloudinit
flavor: ${input.size}
remoteAccess:
authentication: usernamePassword
username: administrator
password: T0pS3cretPassw0rds!!
storage:
constraints:
- tag: storage.profile:${input.platform}
networks:
- network: ${resource.Cloud_vSphere_Network.id}
assignment: static
Cloud_vSphere_Network:
type: Cloud.vSphere.Network
properties:
networkType: existing
constraints:
- tag: network.profile:development
Cloud_SaltStack_1:
type: Cloud.SaltStack
properties:
masterId: saltstack_enterprise_installer
hosts:
- ${resource.Cloud_vSphere_Machine.id}
saltEnvironment: sse
stateFiles:
- /apache/init.sls
When I try to deploy as a Day 0 I get the following error reported:
Resource [/resources/compute/899a63c3-3da1-494b-bab9-adb8f9b35abf]:: Salt resource with job id [769b11e9-ba5a-4de7-9830-f3ae6571cfc9] failed. Error:: 2022-09-20T16:03:45.325292: Minion deployment started. JID - 20220920160345310261 | 2022-09-20T16:07:30.302245: Minion deployment failed. JID - 20220920160345310261 | 2022-09-20T16:07:30.302431: Minion deployment and/or state file run failed.
If I deploy a machine from vRA without any Salt configuration in there, then try and get it going with the built in Day 2 action, I get the following error
Resource [/resources/compute/10e12ee9-c74e-47ff-ae6d-9f1e4e775395]:: Salt resource with job id [54850c1e-8680-4c47-81bd-2a95150b7109] failed. Error:: 2022-09-20T19:14:30.346108: Minion deployment started. JID - 20220920191430330331 | 2022-09-20T19:17:45.329856: Minion deployment failed. JID - 20220920191430330331 | 2022-09-20T19:17:45.330039: Minion deployment and/or state file run failed.
If I follow the 'old' advice on using CloudInit to install the minion and ignore the Salt canvas object, then everything works fine, so as far as I can see, the issue is with the Salt canvas object, not my infrastructure, however, I would love some feedback/assistance to resolve this and move forwards.
To clarify, this process does not work for me, however this one does work.
Am I completely misunderstanding things? Thanks in advance.
### Just to add ###
The following is the contents when attempting to execute the Day2 action to use salt on the Ubuntu 22 server.
administrator@aprodev610:/tmp$ cat bootstrap-salt.log
* INFO: Running version: 2021.09.17
* INFO: Executed by: /bin/sh
* INFO: Command line: '/tmp/.saltcloud-d739b6f5-2afa-4c7c-9be3-cf554c4a7637/de ploy.sh -c /tmp/.saltcloud-d739b6f5-2afa-4c7c-9be3-cf554c4a7637 -x python3 stabl e 3004.2'
* WARN: Running the unstable version of bootstrap-salt.sh
* INFO: System Information:
* INFO: CPU: GenuineIntel
* INFO: CPU Arch: x86_64
* INFO: OS Name: Linux
* INFO: OS Version: 5.15.0-47-generic
* INFO: Distribution: Ubuntu 22.04
* INFO: Installing minion
* INFO: Found function install_ubuntu_stable_deps
* INFO: Found function config_salt
* INFO: Found function preseed_master
* INFO: Found function install_ubuntu_stable
* INFO: Found function install_ubuntu_stable_post
* INFO: Found function install_ubuntu_restart_daemons
* INFO: Found function daemons_running
* INFO: Found function install_ubuntu_check_services
* INFO: Running install_ubuntu_stable_deps()
Hit:1 http://gb.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Get:3 http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Get:4 http://gb.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:5 http://gb.archive.ubuntu.com/ubuntu jammy/main Translation-en_GB [483 kB]
Get:6 http://gb.archive.ubuntu.com/ubuntu jammy/restricted Translation-en_GB [5, 768 B]
Get:7 http://gb.archive.ubuntu.com/ubuntu jammy/universe Translation-en_GB [838 kB]
Get:8 http://gb.archive.ubuntu.com/ubuntu jammy/multiverse Translation-en_GB [10 2 kB]
Get:9 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [584 kB]
Get:10 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [13 7 kB]
Get:11 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 c-n-f Metada ta [8,432 B]
Get:12 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packag es [323 kB]
Get:13 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted Translation- en [50.2 kB]
Get:14 http://gb.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [417 kB]
Get:15 http://gb.archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [104 kB]
Get:16 http://gb.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packag es [7,252 B]
Get:17 http://gb.archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation- en [2,360 B]
Get:18 http://gb.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages [3 32 kB]
Get:19 http://gb.archive.ubuntu.com/ubuntu jammy-security/main Translation-en [7 6.8 kB]
Get:20 http://gb.archive.ubuntu.com/ubuntu jammy-security/restricted amd64 Packa ges [291 kB]
Get:21 http://gb.archive.ubuntu.com/ubuntu jammy-security/restricted Translation -en [45.1 kB]
Get:22 http://gb.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Package s [282 kB]
Get:23 http://gb.archive.ubuntu.com/ubuntu jammy-security/universe Translation-e n [61.2 kB]
Fetched 4,475 kB in 1s (7,966 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
ca-certificates is already the newest version (20211016).
ca-certificates set to manually installed.
wget is already the newest version (1.21.2-2ubuntu1).
wget set to manually installed.
gnupg is already the newest version (2.2.27-3ubuntu2.1).
gnupg set to manually installed.
The following NEW packages will be installed:
apt-transport-https
0 upgraded, 1 newly installed, 0 to remove and 50 not upgraded.
Need to get 1,512 B of archives.
After this operation, 169 kB of additional disk space will be used.
Get:1 http://gb.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 apt-trans port-https all 2.4.7 [1,512 B]
Fetched 1,512 B in 7s (210 B/s)
Selecting previously unselected package apt-transport-https.
(Reading database ... 73343 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_2.4.7_all.deb ...
Unpacking apt-transport-https (2.4.7) ...
Setting up apt-transport-https (2.4.7) ...
NEEDRESTART-VER: 3.5
NEEDRESTART-KCUR: 5.15.0-47-generic
NEEDRESTART-KEXP: 5.15.0-47-generic
NEEDRESTART-KSTA: 1
* ERROR: https://repo.saltproject.io/py3/ubuntu/22.04/amd64/archive/3004.2/salt -archive-keyring.gpg failed to download to /tmp/salt-gpg-5qcBoCTC.pub
* ERROR: Failed to run install_ubuntu_stable_deps()!!!
From the above, the line noted below, seems to have a space between the /salt and -archive-keyring.gpg which doesn't seem right. Internal error requiring a bug fix?
RROR: https://repo.saltproject.io/py3/ubuntu/22.04/amd64/archive/3004.2/salt -archive-keyring.gpg failed to download to /tmp/salt-gpg-5qcBoCTC.pub
If you found this helpful, please consider awarding some points
