Bug 481785
| Summary: | ovirt-config-boot fails to update boot files | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | David Huff <dhuff> |
| Component: | ovirt-node | Assignee: | Perry Myers <pmyers> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | ovirt-bugs, ovirt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-27 21:24:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
looks like the device label is getting set wrong: e2label on /dev/sda1 = "BOOT" needs to be "/BOOT" changing fixes the problem -D I get kernel dump when I run this command, however its not dumping core to the serial console......
# parted /dev/sda1 "print all" > /dev/ttyS0 2>&1
Model: Unknown (unknown)
Disk /dev/sda1: 52.0MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00kB 52.0MB 52.0MB ext3
Model: ATA WDC WD1600ADFS-7 (scsi)
Disk /dev/sda: 160GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 0.51kB 52.0MB 52.0MB primary ext3 boot
2 52.0MB 160GB 160GB primary lvm
Model: SanDisk Cruzer (scsi)
Disk /dev/sdb: 4016MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 31.7kB 4015MB 4015MB primary fat32 boot
Error: Unable to open /dev/md0 - unrecognised disk label.
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
has been opened read-only.
Ok I think this was a problem on the image I was trying to update from: ovirt-node-image-0.97-0.1.el5ovirt.x86_64.rpm. On this image when the above command was run parted segfaulted and caused ovirt-config-boot, causing the image not to be installed. So rebuilt a new image and forced it onto the box, now when the above command is run parted catches the error and prints out a nice error message: something like can not partition outside the disk. I can now run an upgrade form the new image to the new image. The only issue is that you have to run ovirt-config-storage first (I think this is working as designed). |
Description of problem: ovirt-config-boot fails to update boot info Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: - copy new iso file to node - source . /etc/init.d/ovirt-functions - run mount_boot - run ovirt-config-boot /boot /mnt/img Actual results: Does not update files Expected results: update files Additional info: Looks like what is happening is that when you run mount_boot it mounts the /boot partition however does not update fstab. It looks like parted looks at fstab so in the script always fails: if [ 0 -eq $? ]; then ovirt_boot_setup "$disk" "$live" "$bootparams"