rocky-linux / kickstarts Goto Github PK

View Code? Open in Web Editor NEW

24.0 24.0 11.0 815 KB

hacktoberfest

kickstarts's People

Contributors

Stargazers

Watchers

Forkers

tcooper valentin-nasta jwi84 sa0000156ab argo-richh xu001186 psakar svenvd-be sllorente gpanula naioja

kickstarts's Issues

[Rocky-9-Azure-LVM.ks] lot of statements raise errors in %post section

Dear,

Thanks for your works on those kickstart file, after a try; the Rocky-9-Azure-LVM.ks recipe do not works as expected.

Indeed:

dnf install command are not able to reach network and do not know the value of releasever

Unable to detect release version (use '--releasever' to specify release version)
Rocky Linux $releasever - BaseOS                                                                                                                                                                              0.0  B/s |   0  B     00:00    
Errors during downloading metadata for repository 'baseos':
  - Curl error (6): Couldn't resolve host name for https://mirrors.rockylinux.org/mirrorlist?arch=x86_64&repo=BaseOS-$releasever [Could not resolve host: mirrors.rockylinux.org]
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.rockylinux.org/mirrorlist?arch=x86_64&repo=BaseOS-$releasever [Could not resolve host: mirrors.rockylinux.org]

auth is deprecated
missing repo statement
I added these lines

repo           --name=epel                          --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=epel-9&arch=x86_64
repo           --name=epel-next                     --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=epel-next-9&arch=x86_64
repo           --name=packages-microsoft-com-prod   --baseurl=https://packages.microsoft.com/rhel/9.0/prod
repo           --name=rocky-BaseOS-9.4              --mirrorlist=https://mirrors.rockylinux.org/mirrorlist?repo=rocky-BaseOS-9.4&arch=x86_64
repo           --name=rocky-Extra-OS-9.4            --mirrorlist=https://mirrors.rockylinux.org/mirrorlist?repo=plus-9.4&arch=x86_64
repo           --name=rocky-Appstream-9.4           --mirrorlist=https://mirrors.rockylinux.org/mirrorlist?repo=rocky-AppStream-9.4&arch=x86_64
repo           --name=rocky-CRB-9.4                 --mirrorlist=https://mirrors.rockylinux.org/mirrorlist?repo=rocky-CRB-source-9.4&arch=x86_64

dracut have some errors and warning

dracut: WARNING: <key>+=" <values> ": <values> should have surrounding white spaces!
dracut: WARNING: This will lead to unwanted side effects! Please fix the configuration file.

dracut: Cannot find module directory /lib/modules/6.8.9-300.fc40.x86_64/
dracut: and --no-kernel was not specified

sed do not works

sed: can't read /etc/yum/pluginconf.d/product-id.conf: No such file or directory
sed: can't read /etc/yum/pluginconf.d/subscription-manager.conf: No such file or directory

Missing tools

/tmp/ks-script-0v7t0w9h: line 9: grub2-install: command not found
/tmp/ks-script-0v7t0w9h: line 13: parted: command not found

As the command LANG=C sudo livecd-creator --verbose --fslabel=Rocky-9-Azure --config=Rocky-9-Azure-LVM.ks --cache=/var/cache/live is able to generate the .iso file I suspect that those error was not seen

vagrant box v7.0.0 for rocky 8 seems to be broken

I have the following Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.box = "rockylinux/8"
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.define "v5" do |v5|
    v5.vm.box_version = "5.0.0"
  end
  config.vm.define "v7" do |v7|
    v7.vm.box_version = "7.0.0"
  end
end

I have no fancy plugins installed:

$ vagrant plugin list
vagrant-libvirt (0.8.2, system)

And then run vagrant up:

$ vagrant up
Bringing machine 'v5' up with 'virtualbox' provider...
Bringing machine 'v7' up with 'virtualbox' provider...
==> v5: Importing base box 'rockylinux/8'...
==> v5: Matching MAC address for NAT networking...
==> v5: Checking if box 'rockylinux/8' version '5.0.0' is up to date...
==> v5: Setting the name of the VM: test-rocky-8-v7_v5_1670952861960_92069
==> v5: Clearing any previously set network interfaces...
==> v5: Preparing network interfaces based on configuration...
    v5: Adapter 1: nat
==> v5: Forwarding ports...
    v5: 22 (guest) => 2222 (host) (adapter 1)
==> v5: Booting VM...
==> v5: Waiting for machine to boot. This may take a few minutes...
    v5: SSH address: 127.0.0.1:2222
    v5: SSH username: vagrant
    v5: SSH auth method: private key
    v5:
    v5: Vagrant insecure key detected. Vagrant will automatically replace
    v5: this with a newly generated keypair for better security.
    v5:
    v5: Inserting generated public key within guest...
    v5: Removing insecure key from the guest if it's present...
    v5: Key inserted! Disconnecting and reconnecting using new SSH key...
==> v5: Machine booted and ready!
==> v5: Checking for guest additions in VM...
    v5: No guest additions were detected on the base box for this VM! Guest
    v5: additions are required for forwarded ports, shared folders, host only
    v5: networking, and more. If SSH fails on this machine, please install
    v5: the guest additions and repackage the box to continue.
    v5:
    v5: This is not an error message; everything may continue to work properly,
    v5: in which case you may ignore this message.
==> v7: Importing base box 'rockylinux/8'...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "-n", "/home/luc/.vagrant.d/boxes/rockylinux-VAGRANTSLASH-8/7.0.0/virtualbox/box.ovf"]

Stderr: 0%...
Progress state: VBOX_E_OBJECT_NOT_FOUND
VBoxManage: error: Appliance read failed
VBoxManage: error: Failed to open OVF file '/home/luc/.vagrant.d/boxes/rockylinux-VAGRANTSLASH-8/7.0.0/virtualbox/box.ovf' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 471 of file VBoxManageAppliance.cpp

It seems that the v5 box is indeed up but the v7 box not:

$ vagrant ssh v5 --command "echo v5"
v5
$ vagrant ssh v7 --command "echo v7"
VM must be created before running this command. Run `vagrant up` first.

Vagrant Box for Rocky 8 (V5.0.0) has a small hard disk image

I hope that I am reporting this at the right place: the concern are the vagrant boxes published at https://app.vagrantup.com/rockylinux, specifically the v5.0.0 of the Rocky 8 box for the virtualbox provider. If this is not the right place, do you know who creates and publishes these images and where to report bugs? If this is the right place maybe the responsible people can add a link to this repository in the description on the vagrant page.

The default hard disk image for the vagrant box for Rocky Linux 8 is only 5GB in size. For version 4.0.0 of the image it was around 39 GB. It is possible to add extra disks to a vagrant box via the vagrant file but that is some extra manual configuration by the end user.

The images are published via the vagrant cloud (I think, see above). This means they have quite a bit of reach which makes it worthwhile to think about this usability problem.

This has also come up in the Rocky forums: https://forums.rockylinux.org/t/vagrant-vbox-image-only-has-a-5gb-disk/6148/4

Given example for mock shell usage does not work for r9 branch on fedora 36

# livemedia-creator --ks Rocky-9-Workstation.ks   --no-virt   --resultdir /var/lmc   --project="Rocky Linux"   --make-iso   --volid Rocky-Workstation-9   --iso-only   --iso-name Rocky-Workstation-9-x86_64.iso   --releasever=9   --nomacboot
2022-10-17 18:15:07,293: livemedia-creator v34.9.14-1
2022-10-17 18:15:07,293: selinux is Disabled
/usr/lib/python3.9/site-packages/pykickstart/commands/partition.py:448: KickstartParseWarning: A partition with the mountpoint / has already been defined.
  warnings.warn(_("A partition with the mountpoint %s has already been defined.") % pd.mountpoint, KickstartParseWarning)
2022-10-17 18:15:07,334: disk_img = /var/lmc/lmc-disk-bbegxw_d.img
2022-10-17 18:15:07,334: Using disk size of 7752MiB
2022-10-17 18:15:07,472: Running anaconda.
2022-10-17 18:15:09,477: Starting installer, one moment...
2022-10-17 18:15:09,477: terminal size detection failed, using default width
2022-10-17 18:15:09,477: anaconda 34.25.0.29-1.el9_0.rocky.0.3 for Rocky Linux 9 (pre-release) started.
2022-10-17 18:15:09,477: 18:15:09 Service org.fedoraproject.Anaconda.Modules.Storage has failed to start: Process org.fedoraproject.Anaconda.Modules.Storage exited with status 1
2022-10-17 18:15:19,489: Running anaconda failed: process '['unshare', '--pid', '--kill-child', '--mount', '--propagation', 'unchanged', 'anaconda', '--kickstart', '/builddir/kickstarts/Rocky-9-Workstation.ks', '--cmdline', '--dirinstall', '--remotelog', '127.0.0.1:41015']' exited with status 1
2022-10-17 18:16:07,564: Install failed: novirt_install failed
2022-10-17 18:16:07,564: Removing bad disk image
2022-10-17 18:16:07,565: ERROR: Image creation failed: novirt_install failed
2022-10-17 18:16:07,565: Image creation failed: novirt_install failed

My original intention was to use the Rocky-9-GenericCloud-LVM.ks kickstart, which failed with numerous other issues

livemedia-creator complained about package dracut-live not beeing included. I've added this to the kickstart file and that error went away.
livemedia-creator complained text install method must not be specified. So I removed that from the kickstart file.
Next error: Only url, nfs and ostreesetup install methods are currently supported.Please fix your kickstart file. As I don't know enough about the underlying tools I tried to use the kickstart file given in the example (Rocky-9-Workstation.ks)

rocky-linux / kickstarts Goto Github PK

kickstarts's People

Contributors

Stargazers

Watchers

Forkers

kickstarts's Issues

[Rocky-9-Azure-LVM.ks] lot of statements raise errors in %post section

vagrant box v7.0.0 for rocky 8 seems to be broken

Vagrant Box for Rocky 8 (V5.0.0) has a small hard disk image

Given example for mock shell usage does not work for r9 branch on fedora 36

test issue please ignore

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent