Anaconda-devel August 2017

anaconda-devel@lists.stg.fedoraproject.org

6 participants
7 discussions

Historic and current issues with filesystem tools?
by Jan Tulak 02 Oct '17

02 Oct '17

Hi guys, I'm looking for historic and current issues Anaconda had with filesystem tools which don't have a nice API. For example, some tool getting stuck because it waits for a confirmation which never comes, output that was difficult to parse and led to some errors, that kind of things. I'm trying to get some real data on where (or if) it is worth to put an effort into making those tools more computer-friendly, so if you remember anything, let me know. I tried to find something in bugzilla, but Anaconda has too many issues there to read them all (even historical, already fixed issues are good as examples, or to identify tools which have the most problem). If you remember anything, let me know. Thanks. :-) Cheers, Jan

3 2

Mandatory user spoke
by Cristian Stan 02 Oct '17

02 Oct '17

Hello all, I have an issue I could not fix by myself so far: We have a custom Fedora build. After the base Anaconda install, Initial Setup runs with two spokes, one with a custom add-on, and the user creation spoke. Our issues are with the default user creation spoke; we should both enable by default the 'Make this user administrator' checkbox and make the user creation mandatory, so that the setup may not be exited without creating a user. I've even tried disabling altogether the user creation spoke to be able to run my own user creation add-on. I've had no luck so far. What I've tried until now: To enable by default 'Make this user administrator' I have: * modified the 'c_admin' object in user.glade to enable it by default * tested separately the 'c_admin' user.glade object in Glade Interface Designer (it works, as expected) * tested the 'c_admin' modification on 'c_usepassword' (to isolate the issue; the same setting for one object does not work for the other) To make the original user creation spoke in Initial Setup mandatory I have: * modified the '_checkUsername' method from user.py, class 'UserSpoke' (Anaconda sources) All the modifications were performed after Anaconda's first stage and before running Initial Setup. Do you have any ideas about this and how should I proceed? Thank you, your help is greatly appreciated! Cristian Stan

2 1

logging mount assembly and bootloader install, chroot missing?
by Chris Murphy 15 Sep '17

15 Sep '17

The program.log shows mount commands for assembly, followed by installation itself copying files to a path prefix /mnt/sysimage, and then bootloader setup. Isn't there a chroot happening before the bootloader setup? It's not in the log so I'm having some difficulty exactly replicating an installation environment while troubleshooting this bug: So the questions are: Is there a chroot? Is there a way to discover the command being used? And if there is a chroot, is there a way to log this command in the future? https://bugzilla.redhat.com/show_bug.cgi?id=1289752 Thanks, -- Chris Murphy

4 3

default kickstart configuration (beyond interactive-defaults.ks)
by Colin Walters 15 Sep '17

15 Sep '17

I'd like to fix: https://pagure.io/atomic-wg/issue/226 Right now for Atomic Host, we embed the ostree content inside the squashfs, with the goal that users of the ISO don't have to hit the network. We hook bits into interactive-defaults.ks; see this change for how it works: https://pagure.io/fedora-lorax-templates/c/e34c371501d6eac75925aae86bd737c8… However, if one wants to then extract the ISO to do a kickstart install, the user must repeat the `ostreesetup` bits: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… Specifically from his attachment: ostreesetup --osname="fedora-atomic" --remote="fedora-atomic" --url="file:////run/install/repo/content/repo" --ref="fedora-atomic/25/x86_64/docker-host" --nogpg which is really internal implementation details that I'd like the ability to change without breaking people's kickstarts, and conversely not require them to specify by default. Are there any facilities today for a "default kickstart" like /usr/share/anaconda/interactive-defaults.ks, except not just interactive?

2 4

Historic and current issues with filesystem tools?
by Jan Tulak 30 Aug '17

30 Aug '17

Hi guys, I'm looking for historic and current issues Anaconda had with filesystem tools which don't have a nice API. For example, some tool getting stuck because it waits for a confirmation which never comes, an output that was difficult to parse and led to some errors, that kind of things. I'm trying to get some real data on where (or if) it is worth to put an effort into making those tools more computer-friendly, so if you remember anything, let me know. I tried to find something in bugzilla, but Anaconda has too many issues there to read them all (even historical, already fixed issues are good as examples, or to identify tools which have the most problem). If you remember anything, let me know. Thanks. :-) Cheers, Jan

1 0

Automated rescue mode
by Artem Bityutskiy 25 Aug '17

25 Aug '17

Hi, I am using the stock Fedora 25 OS installer as a "service OS", just because it is convenient and I do not have to build my own. Should something bad happen to a host in my automation system, I just boot the host into the Fedora installer's kernel/initramfs over network and have a decent rescue environment. The Fedora OS installer is based on Anaconda. It can find and mount the "sysroot" to "/mnt/sysimage", which is also very convenient. Now, I wanted my "service OS" to automatically do this - find the sysroot and properly mount it without any questions asked. I could not find the "right" way of doing this, and ended up with a hacky trick. I am sharing the trick in case someone else will be googling for it in the future. And of course I'd appreciate better ideas. First of all, boot anaconda into the rescue mode, by adding 'inst.rescue' to kernel boot parameters. I also have a bunch of 'inst.ks' and 'inst.stage2' and dracut networking parameters. And yes, I have a very small minimal KS file too, which only configures repositories and some network-related stuff. Does not do anything about partitions or packages. Then I put this to my %pre in order to make anaconda proceed with mounting the sysroot: tmux send-keys -t anaconda -- 1 C-m It is hackish, but works. It basically sends key "1" to anaconda, so anaconda selects the "Continue" choice, and proceeds with mounting sysroot. This is not the first time I use anaconda's tmux terminal to achieve my goals with anaconda. E.g., I use it for capturing anaconda's VGA output remotely. So thanks for using tmux in anaconda - very handy!

4 5

Fedora change: reduce initial setup redundancy
by mcatanzaro＠gnome.org 11 Aug '17

11 Aug '17

Hi Anaconda devs, Tomorrow is the system-wide change proposal deadline for F27. I've prepared a draft change page for reducing initial setup redundancy in Fedora Workstation. We discussed this a few years ago, and you all implemented your side of the story already (the user interaction config file), but us Workstation folks dropped the ball and left it unused. Anyway, the proposal: https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy Ideally I would have prepared this earlier and run it by you *before* submitting it... so sorry for the very short notice and for delaying way too long. The Workstation WG has approved the general idea of reducing redundancy between gnome-initial-setup and Anaconda, but has not reviewed this proposal yet either, because I just typed it up an hour ago, so at this point it's just me brainstorming. Everything is subject to change and approval and your feedback and nothing is set in stone. We are (OK, I am) basically planning to hide a bunch of Anaconda spokes (timezone?, networking, user account creation, root password) using the user interaction config file. And then hide some gnome-initial-setup panels (language, keyboard layout, timezone?) using a new g-i-s configuration file. Of course, only when running in Workstation: this would not affect other Fedora products that don't have gnome-initial-setup. (And the networking panel would be needed for netinstall anyway. This proposal is mainly focused on live installs.) Technically, we *could* do this without any further changes in Anaconda, but it turns out that the installation progress screen looks pretty odd with both the account creation and root password spokes removed. So some design changes for this page when no spokes are present would certainly be desirable. So we'd appreciate your feedback on this proposal. Sorry again for the late notice. We can edit or delay it at any time, of course. Thanks, Michael

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel August 2017