[oracle] chown: invalid user: 'syslog:adm'

[Peter Jose De Sousa]

Hi,

[Problem]

When bootstrapping onto Oracle Cloud Infrastructure boostrap fails:

update-alternatives: warning: skip creation of /usr/share/man/man1/nc.1.gz because associated file /usr/share/[4/1616]/nc.traditional.1.gz (of link group nc) doesn't exist
update-alternatives: warning: skip creation of /usr/share/man/man1/netcat.1.gz because associated file /usr/share/man/man1/nc.traditional.1.gz (of link group nc) doesn't exist
Setting up ubuntu-fan (0.12.10) ...
Created symlink /etc/systemd/system/multi-user.target.wants/ubuntu-fan.service → /lib/systemd/system/ubuntu-fan.servic
e.
Setting up netcat (1.10-41.1) ...
Processing triggers for systemd (237-3ubuntu10.42) ...
chown: invalid user: 'syslog:adm'
18:38:08 ERROR juju.cmd.juju.commands bootstrap.go:796 failed to bootstrap model: subprocess encountered error code 1
18:38:08 DEBUG juju.cmd.juju.commands bootstrap.go:797 (error details: [{github.com/juju/juju/cmd/juju/commands/bootst
rap.go:890: failed to bootstrap model} {github.com/juju/juju/environs/bootstrap/bootstrap.go:633: } {github.com/juju/j
uju/environs/bootstrap/bootstrap.go:599: } {subprocess encountered error code 1}])
18:38:08 DEBUG juju.cmd.juju.commands bootstrap.go:1511 cleaning up after failed bootstrap
18:38:08 INFO juju.provider.common destroy.go:21 destroying model "controller"
18:38:08 INFO juju.provider.common destroy.go:32 destroying instances

[Workaround]

None at the time of writing

Peter

[Ian Booth (wallyworld)]

Can you provide extra details on how bootstrap was done? What cloud image was used? Is it standard Ubuntu? A custom image? What series?

[Peter Jose De Sousa (pjds)]

Hey Ian,

The bootstrap was performed from the juju docs with no modifications, the
bootstrap command was:

juju bootstrap --config compartment-id=$OCID_COMPARTMENT oracle
oracle-controller

Where COMPARTMENT_ID was the root compartment,

Cheers,

On Tue, Sep 15, 2020 at 9:20 AM Ian Booth <email address hidden>
wrote:

> Can you provide extra details on how bootstrap was done? What cloud
> image was used? Is it standard Ubuntu? A custom image? What series?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1895407
>
> Title:
> [oracle] chown: invalid user: 'syslog:adm'
>
> Status in juju:
> Triaged
>
> Bug description:
> Hi,
>
> [Problem]
>
> When bootstrapping onto Oracle Cloud Infrastructure boostrap fails:
>
> update-alternatives: warning: skip creation of
> /usr/share/man/man1/nc.1.gz because associated file
> /usr/share/[4/1616]/nc.traditional.1.gz (of link group nc) doesn't exist
> update-alternatives: warning: skip creation of
> /usr/share/man/man1/netcat.1.gz because associated file
> /usr/share/man/man1/nc.traditional.1.gz (of link group nc) doesn't exist
> Setting up ubuntu-fan (0.12.10) ...
> Created symlink
> /etc/systemd/system/multi-user.target.wants/ubuntu-fan.service →
> /lib/systemd/system/ubuntu-fan.servic
> e.
> Setting up netcat (1.10-41.1) ...
> Processing triggers for systemd (237-3ubuntu10.42) ...
> chown: invalid user: 'syslog:adm'
> 18:38:08 ERROR juju.cmd.juju.commands bootstrap.go:796 failed to
> bootstrap model: subprocess encountered error code 1
> 18:38:08 DEBUG juju.cmd.juju.commands bootstrap.go:797 (error details: [{
> github.com/juju/juju/cmd/juju/commands/bootst
> rap.go:890: failed to bootstrap model} {
> github.com/juju/juju/environs/bootstrap/bootstrap.go:633: } {
> github.com/juju/j
> uju/environs/bootstrap/bootstrap.go:599: } {subprocess encountered error
> code 1}])
> 18:38:08 DEBUG juju.cmd.juju.commands bootstrap.go:1511 cleaning up
> after failed bootstrap
> 18:38:08 INFO juju.provider.common destroy.go:21 destroying model
> "controller"
> 18:38:08 INFO juju.provider.common destroy.go:32 destroying instances
>
> [Workaround]
>
> None at the time of writing
>
> Peter
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1895407/+subscriptions
>

--

[image: Description: Description: Description:
cid:image001.gif@01CA09E6.C3B72C10]
------------------------------

Peter De Sousa

Associate Field Software Engineer | Canonical Ltd.

*Mobile:* [phone] | *Email: **<email address hidden>
<email address hidden>*

[John A Meinel (jameinel)]

Are you able to confirm that there isn't a syslog user and/or adm group?

That feels very much like a standard user and group for Ubuntu, so not having it feels like these are nonstandard images

/etc/passwd:
syslog:x:102:106::/home/syslog:/usr/sbin/nologin
/etc/group:
adm:x:4:syslog,ubuntu

These are both very much system users, not arbitrary users that Juju would create.

[Peter Jose De Sousa (pjds)]

Hi John,

I ran again today, and now I am not seeing this error despite seeing it the three times I ran this. Not sure what's changed here.

I guess we can mark this as invalid.

[Rahul Bourai (rahulbourai)]

Hi,

I am facing the same issue while ​adding cloud and bootstrapping Manual cloud as only 4 regions are supported of oracle cloud.

I am running Instance of Canonical Ubuntu 20.04 Image build 2021.04.15-0 and
Canonical Ubuntu 20.04 Minimal Image build 2021.04.19-0 also tried with other versions

tried with Regions us-phoenix-1 and ap-mumbai-1

Every Time Getting the same error

chown: invalid user: ‘syslog:adm’
ERROR failed to bootstrap model: subprocess encountered error code 1

[Matt Johnson (mttjohnson)]

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.

[Heather Lanigan (hmlanigan)]

https://bugs.launchpad.net/juju/+bug/2031590 has the same issue with a different cloud.

[Nicolas Vinuesa (nvinuesa)]

This should be fixed by https://github.com/juju/juju/pull/16859 on 3.3.2+