I also received the same error, though there are some differences with my scenario, I think the information and my workaround may help provide some useful context:
- Ubuntu Server 22.04.3 LTS (Minimal Install) on bare metal (ubuntu-22.04.3-live-server-amd64.iso)
- Installing MicroStack/Sunbeam (uses JuJu)
I was running the bootstrap command:
```bash
sunbeam cluster bootstrap
```
and I received the error:
```
chown: invalid user: ‘syslog:adm’
ERROR failed to bootstrap model: subprocess encountered error code 1
Error: Command '['/snap/openstack/247/juju/bin/juju', 'bootstrap', 'sunbeam', 'sunbeam-controller', '--agent-version=3.2.0']' returned non-zero exit status 1.
```
I checked and there was no syslog user on my system:
```bash
cat /etc/passwd | grep syslog
```
I then checked for a syslog file at `/var/log/syslog` and also found no syslog file there.
I found other Ubuntu servers I manage with the `rsyslog` package installed where I did have a `syslog` user in `/etc/passwd` and a `/var/log/syslog` file exists.
As a workaround I was able to install the `rsyslog` package on my server, re-run the same bootstrap command and continue my installation.
I also received the same error, though there are some differences with my scenario, I think the information and my workaround may help provide some useful context: 22.04.3- live-server- amd64.iso)
- Ubuntu Server 22.04.3 LTS (Minimal Install) on bare metal (ubuntu-
- Installing MicroStack/Sunbeam (uses JuJu)
I was running the bootstrap command:
```bash
sunbeam cluster bootstrap
```
and I received the error:
```
chown: invalid user: ‘syslog:adm’
ERROR failed to bootstrap model: subprocess encountered error code 1
Error: Command '['/snap/ openstack/ 247/juju/ bin/juju' , 'bootstrap', 'sunbeam', 'sunbeam- controller' , '--agent- version= 3.2.0'] ' returned non-zero exit status 1.
```
I checked and there was no syslog user on my system:
```bash
cat /etc/passwd | grep syslog
```
I then checked for a syslog file at `/var/log/syslog` and also found no syslog file there.
I found other Ubuntu servers I manage with the `rsyslog` package installed where I did have a `syslog` user in `/etc/passwd` and a `/var/log/syslog` file exists.
As a workaround I was able to install the `rsyslog` package on my server, re-run the same bootstrap command and continue my installation.