[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
*** This bug is a duplicate of bug 1871154 ***
https://bugs.launchpad.net/bugs/1871154
How would I execute the workaround if I cannot boot? Did anybody else
who couldn't boot solve the issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
*** This bug is a duplicate of bug 1871154 ***
https://bugs.launchpad.net/bugs/1871154
As a workaround in the
/usr/share/initramfs-tools/scripts/functions
replace the line
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
with
n -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
in add_mountroot_fail_hook() dunction as suggested above, then run
# update-initramfs -uk all
as root.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
*** This bug is a duplicate of bug 1871154 ***
https://bugs.launchpad.net/bugs/1871154
The same for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
*** This bug is a duplicate of bug 1871154 ***
https://bugs.launchpad.net/bugs/1871154
** This bug has been marked a duplicate of bug 1871154
Error message displayed during boot (mountroot hook, premount)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Is there any workaround. I can’t boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
I upgraded from 19.10 to 20.04 and happened
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Confirmed, I get the message in #1 every boot. 20.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
** Also affects: initramfs-tools
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
I'm noticing the same behavior. Please fix!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Please fix this, affects me after upgrading to 20.04 from 18.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Forgot to mention, in the current bugged state the following message is
shown during boot:
ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such
file or directory
Presumedly the fail hook will not be invoked either.
** Description changed:
Package lvm2 contains a init-premount script named /usr/share/initramfs-
tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
- mkdir -p /tmp/mountroot-fail-hooks.d
- ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
+ mkdir -p /tmp/mountroot-fail-hooks.d
+ ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does not
exist.
-
- It is clear from lvm2's invocation that it expects the symlink to be named
"20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is the case:
+ It is clear from lvm2's invocation that it expects the symlink to be
+ named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is the
+ case:
add_mountroot_fail_hook()
{
- mkdir -p /tmp/mountroot-fail-hooks.d
- ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
+ mkdir -p /tmp/mountroot-fail-hooks.d
+ ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
-
-
- A simple fix might be to alter focal's version so it supports both
- invocation styles , e.g.
-
- ln -s "$0" /tmp/mountroot-fail-hooks.d/"${1:-$0}"
+ focal's version needs to be updated to either support the "$1" argument
+ or strip the directory from "$0".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873614/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
