Bug 988575

The above /tmp/ovirt.log is on IDE, below on VirtIO (both doesn't show pvs or vgs)

/sbin/restorecon:  Warning no default label for /var/tmp/systemd-private-9jlW6J
/sbin/restorecon:  Warning no default label for /var/tmp/systemd-private-9jlW6J/tmp
/sbin/restorecon:  Warning no default label for /tmp/ovirt.log
/sbin/restorecon:  Warning no default label for /tmp/systemd-private-6Oc9Iy
/sbin/restorecon:  Warning no default label for /tmp/systemd-private-6Oc9Iy/tmp
/sbin/restorecon:  Warning no default label for /tmp/.Test-unix
/sbin/restorecon:  Warning no default label for /tmp/.XIM-unix
/sbin/restorecon:  Warning no default label for /dev/mqueue
/sbin/restorecon:  Warning no default label for /dev/pts/ptmx
/sbin/restorecon set context /usr/lib/modules->unconfined_u:object_r:modules_object_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/systemd-vdsmd->unconfined_u:object_r:init_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/system/sshd.socket->unconfined_u:object_r:sshd_unit_file_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/system/firewalld.service->unconfined_u:object_r:firewalld_unit_file_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/system/auditd.service->unconfined_u:object_r:auditd_unit_file_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/system/sshd.service->unconfined_u:object_r:sshd_unit_file_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/system/kdump.service->unconfined_u:object_r:kdump_unit_file_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/system/sshd-keygen.service->unconfined_u:object_r:sshd_unit_file_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/system/sshd@.service->unconfined_u:object_r:sshd_unit_file_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib/systemd/systemd-vdsm-reg->unconfined_u:object_r:init_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib64/sa/sa1->unconfined_u:object_r:sysstat_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib64/sa/sa2->unconfined_u:object_r:sysstat_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/lib64/sa/sadc->unconfined_u:object_r:sysstat_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/bin/qemu-system-unicore32->unconfined_u:object_r:qemu_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/bin/kdumpctl->unconfined_u:object_r:kdumpctl_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/bin/qemu-kvm->unconfined_u:object_r:qemu_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/bin/passwd->unconfined_u:object_r:passwd_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon reset /dev/.initramfs context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/rwtab context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/state context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/state/var context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/state/var/lib context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/state/var/lib/dhclient context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/state/etc context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/state/etc/sysconfig context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/state/etc/sysconfig/network-scripts context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/.need_shutdown context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/live-baseloop context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/squashfs context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/squashfs.osmin context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /dev/.initramfs/livedev context system_u:object_r:tmpfs_t:s0->system_u:object_r:device_t:s0
/sbin/restorecon reset /usr/lib/modules context unconfined_u:object_r:lib_t:s0->unconfined_u:object_r:modules_object_t:s0
/sbin/restorecon reset /usr/lib/systemd/systemd-vdsmd context unconfined_u:object_r:lib_t:s0->unconfined_u:object_r:init_exec_t:s0
/sbin/restorecon reset /usr/lib/systemd/system/sshd.socket context unconfined_u:object_r:systemd_unit_file_t:s0->unconfined_u:object_r:sshd_unit_file_t:s0
/sbin/restorecon reset /usr/lib/systemd/system/firewalld.service context unconfined_u:object_r:systemd_unit_file_t:s0->unconfined_u:object_r:firewalld_unit_file_t:s0
/sbin/restorecon reset /usr/lib/systemd/system/auditd.service context unconfined_u:object_r:systemd_unit_file_t:s0->unconfined_u:object_r:auditd_unit_file_t:s0
/sbin/restorecon reset /usr/lib/systemd/system/sshd.service context unconfined_u:object_r:systemd_unit_file_t:s0->unconfined_u:object_r:sshd_unit_file_t:s0
/sbin/restorecon reset /usr/lib/systemd/system/kdump.service context unconfined_u:object_r:systemd_unit_file_t:s0->unconfined_u:object_r:kdump_unit_file_t:s0
/sbin/restorecon reset /usr/lib/systemd/system/sshd-keygen.service context unconfined_u:object_r:systemd_unit_file_t:s0->unconfined_u:object_r:sshd_unit_file_t:s0
/sbin/restorecon reset /usr/lib/systemd/system/sshd@.service context unconfined_u:object_r:systemd_unit_file_t:s0->unconfined_u:object_r:sshd_unit_file_t:s0
/sbin/restorecon reset /usr/lib/systemd/systemd-vdsm-reg context unconfined_u:object_r:lib_t:s0->unconfined_u:object_r:init_exec_t:s0
/sbin/restorecon reset /usr/lib64/sa/sa1 context unconfined_u:object_r:lib_t:s0->unconfined_u:object_r:sysstat_exec_t:s0
/sbin/restorecon reset /usr/lib64/sa/sa2 context unconfined_u:object_r:lib_t:s0->unconfined_u:object_r:sysstat_exec_t:s0
/sbin/restorecon reset /usr/lib64/sa/sadc context unconfined_u:object_r:lib_t:s0->unconfined_u:object_r:sysstat_exec_t:s0
/sbin/restorecon reset /usr/bin/qemu-system-unicore32 context unconfined_u:object_r:bin_t:s0->unconfined_u:object_r:qemu_exec_t:s0
/sbin/restorecon reset /usr/bin/kdumpctl context unconfined_u:object_r:bin_t:s0->unconfined_u:object_r:kdumpctl_exec_t:s0
/sbin/restorecon reset /usr/bin/qemu-kvm context unconfined_u:object_r:bin_t:s0->unconfined_u:object_r:qemu_exec_t:s0
/sbin/restorecon reset /usr/bin/passwd context unconfined_u:object_r:bin_t:s0->unconfined_u:object_r:passwd_exec_t:s0
/sbin/restorecon reset /usr/bin/qemu-system-x86_64 contex/sbin/restorecon set context /usr/bin/qemu-system-x86_64->unconfined_u:object_r:qemu_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/bin/qemu-system-i386->unconfined_u:object_r:qemu_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /usr/bin/qemu-system-moxie->unconfined_u:object_r:qemu_exec_t:s0 failed:'Read-only file system'
/sbin/restorecon set context /data2->unconfined_u:object_r:default_t:s0 failed:'Read-only file system'
/sbin/restorecon:  Warning no default label for /run/anytermd.pid
/sbin/restorecon:  Warning no default label for /run/multipathd.pid
/sbin/restorecon:  Warning no default label for /run/lvmetad.pid
/sbin/restorecon:  Warning no default label for /run/lock/subsys
/sbin/restorecon:  Warning no default label for /run/lock/subsys/ovirt-firstboot
/sbin/restorecon:  Warning no default label for /run/initramfs
/sbin/restorecon:  Warning no default label for /run/initramfs/rwtab
/sbin/restorecon:  Warning no default label for /run/initramfs/state
/sbin/restorecon:  Warning no default label for /run/initramfs/state/var
/sbin/restorecon:  Warning no default label for /run/initramfs/state/var/lib
/sbin/restorecon:  Warning no default label for /run/initramfs/state/var/lib/dhclient
/sbin/restorecon:  Warning no default label for /run/initramfs/state/etc
/sbin/restorecon:  Warning no default label for /run/initramfs/state/etc/sysconfig
/sbin/restorecon:  Warning no default label for /run/initramfs/state/etc/sysconfig/network-scripts
/sbin/restorecon:  Warning no default label for /run/initramfs/.need_shutdown
/sbin/restorecon:  Warning no default label for /run/initramfs/live-baseloop
/sbin/restorecon:  Warning no default label for /run/initramfs/squashfs
/sbin/restorecon:  Warning no default label for /run/initramfs/squashfs.osmin
/sbin/restorecon:  Warning no default label for /run/initramfs/livedev
t unconfined_u:object_r:bin_t:s0->unconfined_u:object_r:qemu_exec_t:s0
/sbin/restorecon reset /usr/bin/qemu-system-i386 context unconfined_u:object_r:bin_t:s0->unconfined_u:object_r:qemu_exec_t:s0
/sbin/restorecon reset /usr/bin/qemu-system-moxie context unconfined_u:object_r:bin_t:s0->unconfined_u:object_r:qemu_exec_t:s0
/sbin/restorecon reset /boot-kdump context system_u:object_r:boot_t:s0->system_u:object_r:default_t:s0
/sbin/restorecon reset /data2 context unconfined_u:object_r:root_t:s0->unconfined_u:object_r:default_t:s0
2013-07-25 21:25:29,591 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:25:29,601 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:25:29,657 - DEBUG - ovirtfunctions - Translating: /dev/vda
2013-07-25 21:25:34,887 - DEBUG - ovirtfunctions - Translating: /dev/sr0
2013-07-25 21:25:34,897 - DEBUG - ovirtfunctions - Translating: /dev/vda
2013-07-25 21:25:35,061 - DEBUG - ovirtfunctions - Translating: vda
2013-07-25 21:25:35,087 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:25:35,105 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:25:35,135 - DEBUG - ovirtfunctions - Translating: /dev/vda
2013-07-25 21:25:40,898 - DEBUG - ovirtfunctions - Translating: /dev/sr0
2013-07-25 21:25:40,912 - DEBUG - ovirtfunctions - Translating: /dev/vda
2013-07-25 21:25:41,060 - DEBUG - ovirtfunctions - Translating: vda
2013-07-25 21:26:00,512 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:26:00,522 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:26:03,415 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:26:03,433 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:26:03,452 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:26:03,463 - DEBUG - ovirtfunctions - Translating:
2013-07-25 21:26:07,642 - DEBUG - ovirtfunctions - Translating: /dev/vda
2013-07-25 21:26:07,657 - DEBUG - ovirtfunctions - Translating: /dev/vda
2013-07-25 21:26:07,665 - DEBUG - ovirtfunctions - Translating: /dev/vda
2013-07-25 21:32:34,721 - ERROR - ovirtfunctions - /config is not mounted

Same happened with http://resources.ovirt.org/releases/3.3/iso/ovirt-node-iso-3.0.0-5.1.5.vdsm.el6.iso

Please let me know if you need any additional log.

Thanks!

Mike, I was trying to install node on 8G space. I have increased the size and it doesn't show the error. On 2.6.x series we had  a check before proceed with installation and shows a message that the size of disk is not accurate for installation. Looks like we just need it to avoid this error.

Thanks!

Ok, so it's working as it's supposed to.  I'm guessing you had a relatively large swap size.

humm, I am not sure if it's NOTABUG status. We should show to users a message (At least, in 2.6.x series we had.) that the space available to install the node is not enough instead of to show a message: "RunTimeError('Failed to partition/format')" and stop the installation in the middle. Is it possible?

(In reply to Douglas Schilling Landgraf from comment #5)
> humm, I am not sure if it's NOTABUG status. We should show to users a
> message (At least, in 2.6.x series we had.) that the space available to
> install the node is not enough instead of to show a message:
> "RunTimeError('Failed to partition/format')" and stop the installation in
> the middle. Is it possible?

agreed, but this won't be fixed for 2.6.x

In 3.0.0, it's a different installer and we catch that issue earlier in the installer.  We don't let you get to the install if you have bad partition sizes

(In reply to Mike Burns from comment #6)
> (In reply to Douglas Schilling Landgraf from comment #5)
> > humm, I am not sure if it's NOTABUG status. We should show to users a
> > message (At least, in 2.6.x series we had.) that the space available to
> > install the node is not enough instead of to show a message:
> > "RunTimeError('Failed to partition/format')" and stop the installation in
> > the middle. Is it possible?
> 
> agreed, but this won't be fixed for 2.6.x

On 2.6.x it works.

> 
> In 3.0.0, it's a different installer and we catch that issue earlier in the
> installer.  We don't let you get to the install if you have bad partition
> sizes

Looks like it's not working, the bug is about  ovirt-node-iso-3.0.0-5.0.5.vdsm.fc19.iso.

OK, maybe it broke.  I thought you were using 2.6.x

Douglas,

could you explain a bit more what you did to trigger this error?

I'm also installing node oin a VM with 8GB of storage.

(In reply to Fabian Deutsch from comment #9)
> Douglas,
> 
> could you explain a bit more what you did to trigger this error?
> 
> I'm also installing node oin a VM with 8GB of storage.

In the time, just tried to install the node on 8GB of storage and triggered this report.

Not sure if this should be an update or a new bug.

Just tried booting ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso on a HP BL460C server with 20GB of RAM and a 136GB RAID1 disk array and had the same problem.

Should we be ok accepting the default storage layouts presented or customising?

(In reply to Darren Paxton from comment #11)
> Not sure if this should be an update or a new bug.
> 
> Just tried booting ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso on a HP BL460C
> server with 20GB of RAM and a 136GB RAID1 disk array and had the same
> problem.
> 
> Should we be ok accepting the default storage layouts presented or
> customising?

Hey,

thanks for your report. It could be the same bug.

Could please provide a screenshot of the volume page containing the szes for the different partitions?
I need to find out what the ratios are between the sizes to be able to reproduce it here.

(Or just write down the numbers, instead of making a screenshot, which can be hard in the tui.)

Hi

Screenshot easy enough with an ILO card.

I did try adjusting swap to something like 12GB and adding Data with remaining space but no joy.

I dont appear to be able to add attachments so here's a link to the screenshot.

http://i.imgur.com/QmZg1v7.png

Thanks

Darren

We need some additional informations for further debugging, could you please do the following to get more debugging informations:

1. Boot the ISO as usual
2. When the installer TUI comes up, press F" and drop to a shell
3. Set a password for root
4. Now run: ovirt-node-installer --debug
   This will run the installer in debug mode (writing tons of infos
to /var/log/ovirt-node.debug.log).
5. Continue the installation as usual until you reach a problem, then:

6. Switch to a second console and login (the setup tui should come up)
7. Drop to shell by pressing F2
8. Please send the files
* /var/log/ovirt-node.debug.log
* /var/log/ovirt.log
* /tmp/ovirt.log (if available)

And - did you use the "Custom Device" item to enter a custom disk on any page?

(In reply to Fabian Deutsch from comment #15)
> We need some additional informations for further debugging, could you please
> do the following to get more debugging informations:
> 
> 1. Boot the ISO as usual
> 2. When the installer TUI comes up, press F" and drop to a shell

Should be "Press F2" ^^

> 3. Set a password for root
> 4. Now run: ovirt-node-installer --debug
>    This will run the installer in debug mode (writing tons of infos
> to /var/log/ovirt-node.debug.log).
> 5. Continue the installation as usual until you reach a problem, then:
> 
> 6. Switch to a second console and login (the setup tui should come up)
> 7. Drop to shell by pressing F2
> 8. Please send the files
> * /var/log/ovirt-node.debug.log
> * /var/log/ovirt.log
> * /tmp/ovirt.log (if available)
> 
> And - did you use the "Custom Device" item to enter a custom disk on any
> page?

Created attachment 800451 [details]
ovirt-debuglog

Created attachment 800453 [details]
/var/log/ovirt.log

Created attachment 800454 [details]
/tmp/ovirt.log

Attachments added as requested and for info, i tried both selecting the device and choosing from other, both ended up with the same behaviour.

I encountered this same issue many times while installing to a Supermicro box with 2 x 250GB SATA disks.

The solution for me was wiping the GPT partition table.  I used dd to overwrite the last few hundred MB of each disk and then tried again.  Worked perfectly.

This was with 3.0.1-1.0.2.el6.

Allen

Hey Haiyang,

have you possibly seen this bug?

Created attachment 827712 [details]
Nov22 2013 ovirt-node.log

Created attachment 827713 [details]
Nov22 2013 ovirt.log

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

(In reply to Fabian Deutsch from comment #22)
> Hey Haiyang,
> 
> have you possibly seen this bug?

Hey Fabian,
I didn't meet the similar issue before.

This is possibly fixed in 3.0.4

Please reopen if necessary