6:32 p.m.
[ 23.607625] rhino.road.example.org ignition[907]: INFO : files: createUsers:
checking if user "core" exists: [Attention] exit status 1: Cmd:
"chroot" "/sysroot" "id" "core" Stdout: id:
‘core’: no such user
[ 23.624949] rhino.road.example.org ignition[907]: INFO : files: createUsers: op(1):
[started] creating or modifying user "core"
[ 23.624949] rhino.road.example.org ignition[907]: DEBUG : files: createUsers: op(1):
executing: "useradd" "--root" "/sysroot"
"--home-dir" "/home/core" "--create-home"
"--password" "*" "--comment" "CoreOS Admin"
"--gid" "core" "--groups"
"adm,sudo,systemd-journal,wheel,docker,rkt,portage" "--shell"
"/bin/bash" "core"
[ 23.624949] rhino.road.example.org ignition[907]: CRITICAL : files: createUsers: op(1):
[failed] creating or modifying user "core": exit status 6: Cmd:
"useradd" "--root" "/sysroot" "--home-dir"
"/home/core" "--create-home" "--password" "*"
"--comment" "CoreOS Admin" "--gid" "core"
"--groups" "adm,sudo,systemd-journal,wheel,docker,rkt,portage"
"--shell" "/bin/bash" "core" Stdout: "" Stderr:
"useradd: group 'core' does not exist\n"
CRITICAL : Ignition failed: failed to create users/groups: failed to create users: failed
to create user "core": exit status 6: Cmd: "useradd"
"--root" "/sysroot" "--home-dir" "/home/core"
"--create-home" "--password" "*" "--comment"
"CoreOS Admin" "--gid" "core" "--groups"
"adm,sudo,systemd-journal,wheel,docker,rkt,portage" "--shell"
"/bin/bash" "core" Stdout: "" Stderr: "useradd: group
'core' does not exist\n"
I would be happy to provide detailed logs
CoreOS was PXE installed with options:
KERNEL fedora-coreos-30.20190801.0-installer-kernel
APPEND ip=dhcp rd.neednet=1 initrd=fedora-coreos-30.20190801.0-installer-initramfs.img
console=tty0 console=ttyS0,115200n8 coreos.inst=yes coreos.inst.text=yes
coreos.inst.install_dev=mmcblk0 coreos.autologin=tty1 coreos.autologin=ttyS0
coreos.inst.image_url=http://10.20.30.2:8000/fedora-coreos-30.20190801.0-metal.raw.xz
coreos.inst.ignition_url=http://10.20.30.2:8000/bare_metal_ignition.json
IPAPPEND 2
$ ~/bin/fcct -version
Fedora CoreOS Config Transpiler v0.2.0
bare_metal_ignition.json was generated with fcct with the below YAML file
variant: fcos
version: 1.0.0
passwd:
users:
- name: core
ssh_authorized_keys:
- ssh-rsa AAAAB1LR7 coreos_metal
home_dir: /home/core
no_create_home: false
primary_group: core
groups:
- wheel
- sudo
- docker
- rkt
- systemd-journal
- portage
shell: /bin/bash
storage:
files:
- path: /etc/hosts
user:
name: root
group:
name: root
contents:
source: http://10.20.30.2:8000/hosts
compression: null
mode: 0644
12:42 p.m.
New subject: CoreOS does not process ignition files on a system that has MMC as the only storage device
On 8/21/19 7:32 PM, Shivaram Mysore wrote:
variant: fcos
version: 1.0.0
passwd:
users:
- name: core
ssh_authorized_keys:
- ssh-rsa AAAAB1LR7 coreos_metal
home_dir: /home/core
no_create_home: false
primary_group: core
groups:
- wheel
- sudo
- docker
- rkt
- systemd-journal
- portage
Some of these groups don't exist on FCOS. Here is the default group list we use
for the `core` user (i.e. if you don't specify your own core user):
https://github.com/coreos/fedora-coreos-config/blob/testing-devel/overlay...
Note that the `core` group gets created when the `core` user is created so you don't
need to specify that group.
> shell: /bin/bash
> storage:
> files:
> - path: /etc/hosts
> user:
> name: root
> group:
> name: root
> contents:
> source: http://10.20.30.2:8000/hosts
> compression: null
> mode: 0644
> _______________________________________________
> CoreOS mailing list -- coreos(a)lists.fedoraproject.org
> To unsubscribe send an email to coreos-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org
>
6:33 p.m.
New subject: CoreOS does not process ignition files on a system that has MMC as the only storage device
Hi Dusty,
Thanks for the hints. They were very helpful. I did the following things
to get it to work correctly:
1. I renamed my user account to "core2" - this fixed first part of the
problem. This also included the updated group info.
2. I removed the /etc/hosts file creation as it was useless and
conflicting with the actual generation.
3. modifying just /usr/lib/ignition/user.ign and rerunning coreos-installer
did not work. I started with PXE boot and reinstalled the image with
the updated ignition files.
4. *fcct* tool *-o *option does not overwrite the file. It tries to
incorrectly update the JSON file and messes it up. So, forcefully removing
the JSON/ign file and recreating it from YAML file works. - maybe I will
file a bug against this.
Thanks again for your help
/Shivaram
On Thu, Aug 22, 2019 at 10:42 AM Dusty Mabe <dusty(a)dustymabe.com> wrote:
On 8/21/19 7:32 PM, Shivaram Mysore wrote:
>
> variant: fcos
> version: 1.0.0
> passwd:
> users:
> - name: core
> ssh_authorized_keys:
> - ssh-rsa AAAAB1LR7 coreos_metal
> home_dir: /home/core
> no_create_home: false
> primary_group: core
> groups:
> - wheel
> - sudo
> - docker
> - rkt
> - systemd-journal
> - portage
Some of these groups don't exist on FCOS. Here is the default group list
we use
for the `core` user (i.e. if you don't specify your own core user):
https://github.com/coreos/fedora-coreos-config/blob/testing-devel/overlay...
Note that the `core` group gets created when the `core` user is created so
you don't
need to specify that group.
> shell: /bin/bash
> storage:
> files:
> - path: /etc/hosts
> user:
> name: root
> group:
> name: root
> contents:
> source: http://10.20.30.2:8000/hosts
> compression: null
> mode: 0644
> _______________________________________________
> CoreOS mailing list -- coreos(a)lists.fedoraproject.org
> To unsubscribe send an email to coreos-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org
>
6:27 a.m.
New subject: CoreOS does not process ignition files on a system that has MMC as the only storage device
On 8/22/19 7:33 PM, Shivaram Mysore wrote:
Hi Dusty,
Thanks for the hints. They were very helpful. I did the following things to get it to
work correctly:
1. I renamed my user account to "core2" - this fixed first part of the
problem. This also included the updated group info.
2. I removed the /etc/hosts file creation as it was useless and conflicting with the
actual generation.
3. modifying just /usr/lib/ignition/user.ign and rerunning coreos-installer did not
work. I started with PXE boot and reinstalled the image with the updated ignition files.
4. *fcct* tool *-o *option does not overwrite the file. It tries to incorrectly update
the JSON file and messes it up. So, forcefully removing the JSON/ign file and recreating
it from YAML file works. - maybe I will file a bug against this.
Sounds good. Yes please file a bug.
Thanks again for your help\
No problem. Are you unblocked now?
Dusty
1:26 p.m.
New subject: CoreOS does not process ignition files on a system that has MMC as the only storage device
Yes - unblocked for now.
Bug was filed - https://github.com/coreos/fcct/issues/42 and also fixed a
few minutes ago - https://github.com/coreos/fcct/pull/43
/Shivaram
On Fri, Aug 23, 2019 at 4:27 AM Dusty Mabe <dusty(a)dustymabe.com> wrote:
On 8/22/19 7:33 PM, Shivaram Mysore wrote:
> Hi Dusty,
> Thanks for the hints. They were very helpful. I did the following
things to get it to work correctly:
>
> 1. I renamed my user account to "core2" - this fixed first part of the
problem. This also included the updated group info.
> 2. I removed the /etc/hosts file creation as it was useless and
conflicting with the actual generation.
> 3. modifying just /usr/lib/ignition/user.ign and rerunning
coreos-installer did not work. I started with PXE boot and reinstalled the
image with the updated ignition files.
> 4. *fcct* tool *-o *option does not overwrite the file. It tries to
incorrectly update the JSON file and messes it up. So, forcefully removing
the JSON/ign file and recreating it from YAML file works. - maybe I will
file a bug against this.
Sounds good. Yes please file a bug.
>
> Thanks again for your help\
No problem. Are you unblocked now?
Dusty
1708
days inactive
1710
days old
coreos@lists.fedoraproject.org
4 comments
2 participants
participants (2)
-
Dusty Mabe -
Shivaram Mysore