OL 7.7 fails to create a user

Bug #1841816 reported by Chad Smith
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init
Expired
Undecided
Unassigned

Bug Description

Provider: Oracle
Distro: Oracle Linux 7.7

Upon boot the user directory can't be created.

Revision history for this message
gcstang (gcstang) wrote :
gcstang (gcstang)
description: updated
Revision history for this message
Dan Watkins (oddbloke) wrote :

Hi gcstang, thanks for the bug report! The cloud.cfg you've pasted has the default_user name as "clouduser", whereas the traceback shows "/home/cloud-user" being the problem. Can you paste matching files, please, and set this back to New?

Thanks!

Changed in cloud-init:
status: New → Incomplete
Revision history for this message
gcstang (gcstang) wrote :
Changed in cloud-init:
status: Incomplete → New
Revision history for this message
Paride Legovini (paride) wrote :

Hi gcstang, thanks for providing the configuration file, however it seems that it's still not enough to describe the complete context which made your system run into the problem you are describing. The cloud-init.log file shows that cloud-init tried to add *both* the 'clouduser' and 'cloud-user' users, encountering an error on both cases:

  useradd: cannot create directory /home/cloud-user
  [...]
  useradd: cannot create directory /home/clouduser

and from journal.txt:

  OSError: [Errno 13] Permission denied: '/home/clouduser'

moreover cloud-init tries to setup the 'opc' user, but fails:

__init__.py[INFO]: User opc already exists, skipping
  util.py[DEBUG]: Running command ['passwd', '-l', 'opc']
  util.py[WARNING]: Failed to disable password for user opc

  Command: ['passwd', '-l', 'opc']
  Exit code: 1
  Stdout: Locking password for user opc.
          passwd: Error (password not set?)

My impression here is that cloud-init is trying to configure a dirty system. What would help is a more complete picture with some more context; in other words: can you describe which steps are needed to reproduce this issue from scratch?

Again, please set the bug status back to New after providing additional information. Thanks!

Changed in cloud-init:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cloud-init because there has been no activity for 60 days.]

Changed in cloud-init:
status: Incomplete → Expired
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.