Anaconda-devel July 2015

anaconda-devel@lists.stg.fedoraproject.org

7 participants
9 discussions

Regarding NFS method of Installation issue in RHEL 6.6
by anant garg 31 Jul '15

31 Jul '15

Hi All, Greeting for the day. I was installation RHEL by using NFS method in a kickstart file My kickstart includes another kickstart Below was a snippet of my kickstart install nfs --server=169.254.1.2 --dir=/export/home/agarg/imag key --skip lang en_US.UTF-8 keyboard us % include /mnt/stage2/kickstart/Additional.inc %packages @base @supp @core %end I found that during Network installation, Installation failed with Error:- The following problem occurred on line 0 of the kickstart file: Unable to open input kickstart file: Could not open/read file:///mnt/stage2/kickstart/Additional.inc I login to tty2 and found that only images directory from ISO has been copied to /mnt/stage2 That is why it is not finding the kickstart. I can not understand this behavior. I tried the same installation by CD and /mnt/stage2 was having kickstart and complete iso tree. Can any one please help me understand this behavior and solution for nfs method of installation of above on RHEL 6.6? Please let me know in case you require more information Thanks and Regards, Anant Garg

2 6

Predictable Network Interface Names
by poma 26 Jul '15

26 Jul '15

It seems the "Anaca" has problemos with "Predictable Network Interface Names", http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac… $ dmesg -t | grep eth ... r8169 0000:01:09.0 enp1s9: renamed from eth1 ... To further confirm this conclusion, if you boot with the 'net.ifnames=0' $ dmesg -t | grep eth ... r8169 0000:01:09.0 eth1: link down r8169 0000:01:09.0 eth1: link down IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready ... problemo does not occur. https://github.com/rhinstaller/anaconda/issues/211

1 1

The EXTLINUX MD RAID1 support
by poma 26 Jul '15

26 Jul '15

The EXTLINUX MD RAID1 support https://bugzilla.redhat.com/show_bug.cgi?id=1246828 https://bugzilla.redhat.com/attachment.cgi?id=1056217 :anaconda The EXTLINUX MD RAID1 metadata 1.0 support https://bugzilla.redhat.com/show_bug.cgi?id=1246829 https://bugzilla.redhat.com/attachment.cgi?id=1056218 :python-blivet Test compilation: - http://goo.gl/Gm4ffO iso/Rawhide-Xfce-Live-725.iso Source RPM: - http://goo.gl/Gm4ffO source/Extra Anaconda/ anaconda-23.17-2.fc24.src.rpm python-blivet-1.10-2.fc24.src.rpm Syslinux/ syslinux-6.04-1.4.8.3.git20150719.src.rpm Screencast: - http://goo.gl/Gm4ffO vids/extlinux-md-raid1.webm For those running the machines on the BIOSes, baremetal and virtual. Super cool, isn't it.

1 0

Anaconda and cloud-init
by Colin Walters 21 Jul '15

21 Jul '15

Fedora right now has three products, and I'm going to ignore Workstation for this post. Server: Download boot.iso, configure via kickstart Cloud: Download qcow2 image, configure via cloud-init Anaconda is used in generating the Cloud image (see my previous post about ImageFactory), with the resulting issues there. But note the kickstart functionality is not accessible to the Cloud user. Instead, cloud-init is the pervasive way to configure cloud images. But if you look at this, cloud-init actually has a lot of great features that *also* make sense on bare metal. A good example is ssh key provisioning. Look at the "ssh-authorized-keys" entry in the YAML here: http://cloudinit.readthedocs.org/en/latest/topics/examples.html#including-u… Kickstart has no declarative syntax to update the ssh keys for a user. And this lack of support is actually reflected in the Anaconda UI/framework logic - it won't let you proceed unless you have a root password or an administrative user (with a password) But ssh keys are *more* secure than passwords, and we should strongly encourage their use. In the RHEL6 era, people of course did it in %post, but there was a common trap around SELinux labeling: https://www.redhat.com/archives/rhelv6-beta-list/2010-November/msg00005.html Basically I'd like to discuss pulling in cloud-init into the installation environment. Ideally, I could chain kickstart -> cloud-config. Say a new toplevel verb like this in %kickstart: %cloud-config users: - name: walters ssh-authorized-keys: ssh-rsa ... %end The simplest way to implement this would be to simply dump the file into /var/tmp on the target system, and then have the cloud-init program execute it on boot. But to fix the issue of anaconda being unaware of ssh keys as a valid way to log in would require parsing it in the install environment and looking at the users stanza. At a high level, I think this is a good architectural match; both programs are Python 2, etc. (cloud-init is GPLv3 though...hmm) cloud-init also has a lot of popularity due to its cross-distribution nature. Finally, the reason I bring this up is because I work on Project Atomic, and as part of that one of the features we're investigating is a PXE-to-Live scenario. For that, cloud-init is a perfect match, because it's designed to configure an already existing system (versus kickstart which is designed to be processed for an installation). Laying the foundation with regular bare metal support for cloud-init would help this as well.

9 21

Testing Hello World addon
by sad man 16 Jul '15

16 Jul '15

Hi I am beginning to write a Cloud addon for Anaconda. I have a question regarding testing and development environment. 1. Hello_world doesn't seem to show up during the install. I cloned the hello_world example <https://github.com/rhinstaller/hello-world-anaconda-addon>and placed it on my install media as specified in the installer. My directory structure <iso>/usr/share/anaconda/addons/org_fedora_hello <iso>images/addon_updates.img What is hello_world addon supposed to do? (is it supposed to show up during install?) how can I test it? 2. Development environment, right now from what I understand I can only test my code by placing it on install media and then running the setup (which is tedious). Is there a better way to setup development environment for anaconda (addons)? -- Cheers, Asad

2 2

Dracut: rd.md=0 & Anaconda/Blivet
by poma 16 Jul '15

16 Jul '15

Mister Harald, could you shed some light on it, why RAID configuration generally occurs when disabled, and creates unnecessary problemos for the Anaca/Blivet? $ man 7 dracut.cmdline $ man 7 dracut.kernel ... MD RAID rd.md=0 disable MD RAID detection # cat /proc/cmdline BOOT_IMAGE=... rd.md=0 ... # dmesg | grep md125 [ 41.473988] md/raid1:md125: active with 2 out of 2 mirrors [ 41.474008] md125: detected capacity change from 0 to 108457419776 [ 298.898394] md125: detected capacity change from 108457419776 to 0 [ 298.898403] md: md125 stopped. # cat /proc/mdstat Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [raid10] unused devices: <none> https://github.com/rhinstaller/anaconda/issues/213

1 0

anaconda-core: liveinst & Extlinux
by poma 14 Jul '15

14 Jul '15

FTR / FYI - "liveinst --extlinux" resulting in: https://bugzilla.redhat.com/show_bug.cgi?id=1243117

1 0

Re: LiveCD/DVDs require dracut-live - dracut-043-40.git20150710.fc23
by poma 14 Jul '15

14 Jul '15

On 10.07.2015 15:00, poma wrote: > > https://github.com/haraldh/dracut/commit/ac13778 > dracut.spec: move dmsquash and livnet to subpackage > > ... > dracut module 'dmsquash-live' cannot be found or installed. > mkinitrd failed > warning: %posttrans(kernel-core-4.2.0-0.rc1.git2.2.fc23.x86_64) scriptlet failed, exit status 1 > ... > > http://koji.fedoraproject.org/koji/buildinfo?buildID=667878 > dracut-live-043-40.git20150710.fc23 > If people who maintain spin-kickstarts do not care for it, whether anaconda should pull this package as requirement? Tested with: Fedora-Live-Xfce-x86_64-rawhide-20150712.iso http://koji.fedoraproject.org/koji/taskinfo?taskID=10336905 Fedora-Live-MATE_Compiz-x86_64-rawhide-20150712.iso http://koji.fedoraproject.org/koji/taskinfo?taskID=10336882 Probably other LiveCD/DVDs are also unbootable due to the lack of 'dracut-live'.

1 2

Packaging Add-on in ISO
by sad man 10 Jul '15

10 Jul '15

Hello I am new to add-on development and have a question on how can I create ISO with my custom add-ons. >From the guide <http://rhinstaller.github.io/anaconda-addon-development-guide/sect-anaconda…>, we can place the .img file in the *images *directory of ISO and the installer will pickup the add-on automatically. But the part on creating RPM is a little vague. Once the RPM is created, how/where should we place it in the ISO? and how can we direct anaconda to use the add-on RPM? -- Cheers, Asadullah Hussain

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel July 2015