Multiple runs of dracut

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Multiple runs of dracut

Ken Schneider - openSUSE
Today when I ran zypper dup to openSUSE Tumbleweed  20171019-0 ->
20171023-0 "dracut" ran no fewer then FOUR times. There is no need for
this to happen with ANY dup.

( 21/462) Installing: plymouth-branding-openSUSE-13.3-8.8.noarch
......................................................[done]
Additional rpm output:
dracut: Executing: /usr/bin/dracut -f

depmod: WARNING:
//lib/modules/4.13.5-1-default/weak-updates/updates/nvidia.ko disagrees
about version of symbol module_layout
Warning: /lib/modules/4.13.5-1-default is inconsistent
Warning: weak-updates symlinks might not be created
Creating initrd: /boot/initrd-4.13.5-1-default
dracut: Executing: /usr/bin/dracut --logf

(145/462) Installing: kernel-default-4.13.8-1.1.x86_64
......................................................[done]
Additional rpm output:
Creating initrd: /boot/initrd-4.13.8-1-default
dracut: Executing: /usr/bin/dracut --logfi

(462/462) Installing: sddm-branding-openSUSE-0.15.0-2.1.x86_64
...........................................................[done]
Output of kernel-firmware-20171009-1.1.noarch.rpm %posttrans script:
     Creating initrd: /boot/initrd-4.13.5-1-default
     dracut: Executing: /usr/bin/dracut --logfil


If something needs "dracut" to be run have it run ONCE at the end of the
dup. Surely a flag can be set for this.

--
Ken Schneider
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Multiple runs of dracut

Neal Gompa
On Wed, Oct 25, 2017 at 12:02 PM, Ken Schneider - Factory
<[hidden email]> wrote:

> Today when I ran zypper dup to openSUSE Tumbleweed  20171019-0 -> 20171023-0
> "dracut" ran no fewer then FOUR times. There is no need for this to happen
> with ANY dup.
>
> ( 21/462) Installing: plymouth-branding-openSUSE-13.3-8.8.noarch
> ......................................................[done]
> Additional rpm output:
> dracut: Executing: /usr/bin/dracut -f
>
> depmod: WARNING:
> //lib/modules/4.13.5-1-default/weak-updates/updates/nvidia.ko disagrees
> about version of symbol module_layout
> Warning: /lib/modules/4.13.5-1-default is inconsistent
> Warning: weak-updates symlinks might not be created
> Creating initrd: /boot/initrd-4.13.5-1-default
> dracut: Executing: /usr/bin/dracut --logf
>
> (145/462) Installing: kernel-default-4.13.8-1.1.x86_64
> ......................................................[done]
> Additional rpm output:
> Creating initrd: /boot/initrd-4.13.8-1-default
> dracut: Executing: /usr/bin/dracut --logfi
>
> (462/462) Installing: sddm-branding-openSUSE-0.15.0-2.1.x86_64
> ...........................................................[done]
> Output of kernel-firmware-20171009-1.1.noarch.rpm %posttrans script:
>     Creating initrd: /boot/initrd-4.13.5-1-default
>     dracut: Executing: /usr/bin/dracut --logfil
>
>
> If something needs "dracut" to be run have it run ONCE at the end of the
> dup. Surely a flag can be set for this.
>

It could be done as a post-transaction trigger, probably as a file trigger.


--
真実はいつも一つ!/ Always, there's only one truth!
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Multiple runs of dracut

Larry Finger
On 10/25/2017 11:04 AM, Neal Gompa wrote:

> On Wed, Oct 25, 2017 at 12:02 PM, Ken Schneider - Factory
> <[hidden email]> wrote:
>> Today when I ran zypper dup to openSUSE Tumbleweed  20171019-0 -> 20171023-0
>> "dracut" ran no fewer then FOUR times. There is no need for this to happen
>> with ANY dup.
>>
>> ( 21/462) Installing: plymouth-branding-openSUSE-13.3-8.8.noarch
>> ......................................................[done]
>> Additional rpm output:
>> dracut: Executing: /usr/bin/dracut -f
>>
>> depmod: WARNING:
>> //lib/modules/4.13.5-1-default/weak-updates/updates/nvidia.ko disagrees
>> about version of symbol module_layout
>> Warning: /lib/modules/4.13.5-1-default is inconsistent
>> Warning: weak-updates symlinks might not be created
>> Creating initrd: /boot/initrd-4.13.5-1-default
>> dracut: Executing: /usr/bin/dracut --logf
>>
>> (145/462) Installing: kernel-default-4.13.8-1.1.x86_64
>> ......................................................[done]
>> Additional rpm output:
>> Creating initrd: /boot/initrd-4.13.8-1-default
>> dracut: Executing: /usr/bin/dracut --logfi
>>
>> (462/462) Installing: sddm-branding-openSUSE-0.15.0-2.1.x86_64
>> ...........................................................[done]
>> Output of kernel-firmware-20171009-1.1.noarch.rpm %posttrans script:
>>      Creating initrd: /boot/initrd-4.13.5-1-default
>>      dracut: Executing: /usr/bin/dracut --logfil
>>
>>
>> If something needs "dracut" to be run have it run ONCE at the end of the
>> dup. Surely a flag can be set for this.
>>
>
> It could be done as a post-transaction trigger, probably as a file trigger.

If a zypper run aborts, and dracut has not been run when it was needed, will the
system still be bootable?

Larry

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Multiple runs of dracut

Ken Schneider - openSUSE
On 10/25/2017 12:24 PM, Larry Finger wrote:

> On 10/25/2017 11:04 AM, Neal Gompa wrote:
>> On Wed, Oct 25, 2017 at 12:02 PM, Ken Schneider - Factory
>> <[hidden email]> wrote:
>>> Today when I ran zypper dup to openSUSE Tumbleweed  20171019-0 ->
>>> 20171023-0
>>> "dracut" ran no fewer then FOUR times. There is no need for this to
>>> happen
>>> with ANY dup.
>>>
>>> ( 21/462) Installing: plymouth-branding-openSUSE-13.3-8.8.noarch
>>> ......................................................[done]
>>> Additional rpm output:
>>> dracut: Executing: /usr/bin/dracut -f
>>>
>>> depmod: WARNING:
>>> //lib/modules/4.13.5-1-default/weak-updates/updates/nvidia.ko disagrees
>>> about version of symbol module_layout
>>> Warning: /lib/modules/4.13.5-1-default is inconsistent
>>> Warning: weak-updates symlinks might not be created
>>> Creating initrd: /boot/initrd-4.13.5-1-default
>>> dracut: Executing: /usr/bin/dracut --logf
>>>
>>> (145/462) Installing: kernel-default-4.13.8-1.1.x86_64
>>> ......................................................[done]
>>> Additional rpm output:
>>> Creating initrd: /boot/initrd-4.13.8-1-default
>>> dracut: Executing: /usr/bin/dracut --logfi
>>>
>>> (462/462) Installing: sddm-branding-openSUSE-0.15.0-2.1.x86_64
>>> ...........................................................[done]
>>> Output of kernel-firmware-20171009-1.1.noarch.rpm %posttrans script:
>>>      Creating initrd: /boot/initrd-4.13.5-1-default
>>>      dracut: Executing: /usr/bin/dracut --logfil
>>>
>>>
>>> If something needs "dracut" to be run have it run ONCE at the end of the
>>> dup. Surely a flag can be set for this.
>>>
>>
>> It could be done as a post-transaction trigger, probably as a file
>> trigger.
>
> If a zypper run aborts, and dracut has not been run when it was needed,
> will the system still be bootable?
>
> Larry
>

I don't see why an older kernel could not be selected. If zypper crashes
half way through it can be rerun (zypper) after booting to CLI and if
not there are more serious problems with the system.

--
Ken Schneider

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Multiple runs of dracut

Olaf Hering-2
In reply to this post by Larry Finger
On Wed, Oct 25, Larry Finger wrote:

> > > ( 21/462) Installing: plymouth-branding-openSUSE-13.3-8.8.noarch
> > > (145/462) Installing: kernel-default-4.13.8-1.1.x86_64
> > > (462/462) Installing: sddm-branding-openSUSE-0.15.0-2.1.x86_64

> If a zypper run aborts, and dracut has not been run when it was needed, will
> the system still be bootable?

Even if it would, none of these packages are essential (beside the
kernel eventually). Since the whole thing is a "transaction" anyway,
aborting in the middle leaves an inconsistent system behind. It may work
by luck, most of the time.

These packages are just broken. They must be converted to %postrans.

Olaf

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Multiple runs of dracut

Andrei Borzenkov
On Thu, Oct 26, 2017 at 9:05 AM, Olaf Hering <[hidden email]> wrote:

> On Wed, Oct 25, Larry Finger wrote:
>
>> > > ( 21/462) Installing: plymouth-branding-openSUSE-13.3-8.8.noarch
>> > > (145/462) Installing: kernel-default-4.13.8-1.1.x86_64
>> > > (462/462) Installing: sddm-branding-openSUSE-0.15.0-2.1.x86_64
>
>> If a zypper run aborts, and dracut has not been run when it was needed, will
>> the system still be bootable?
>
> Even if it would, none of these packages are essential (beside the
> kernel eventually). Since the whole thing is a "transaction" anyway,
> aborting in the middle leaves an inconsistent system behind. It may work
> by luck, most of the time.
>
> These packages are just broken. They must be converted to %postrans.
>

dracut run immediately after kernel installation is intentional
(should be somewhere in archives, I asked this a while ago).
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]