ISST-LTE:pVM:pinelp3:ubuntu 16.04: systemctl daemon-reload failed in emergency mode

[bugproxy]

== Comment: #0 - Ping Tian Han <email address hidden> - 2016-03-24 23:19:51 ==
---Problem Description---
After dropping into emergency mode and do some modification to the system's config files, I want to let systemd reload them but failed:

root@pinelp3:~# systemctl daemon-reload
Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
root@pinelp3:~#

This command works in normal mode though.

Contact Information = Ping Tian <email address hidden>, Mikhail <email address hidden>

---uname output---
Linux pinelp3 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:06:23 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = IBM,8408-E8E,lpar
 ---Debugger---
A debugger was configured, however the system did not enter into the debugger

---Steps to Reproduce---
 1. adding a nonexistent partition entry in /etc/fstab:
/dev/mapper/mpathw-part3 /fs_test/mapper/mpathw-part3 xfs defaults 1 2
2. reboot the system
3. drop into emergency mode:

Give root password for maintenance
(or press Control-D to continue):
root@pinelp3:~#

4. removee the nonexistent partition entry from /etc/fstab
5. run 'systemctl daemon-reload'

Userspace tool common name: systemd

Userspace rpm: systemd

The userspace tool has the following bit modes: 64-bit

Userspace tool obtained from project website: na

*Additional Instructions for Ping Tian <email address hidden>, Mikhail <email address hidden>:
-Post a private note with access information to the machine that the bug is occuring on.
-Attach ltrace and strace of userspace application.

== Comment: #3 - Ping Tian Han <email address hidden> - 2016-03-30 21:39:23 ==
Hi,

For how to drop into the emergency mode, I just add a nonexistent partition item, something like

/dev/nonexistent1 /nonexistent1 xfs defaults 1 2

then reboot the system. So systemd won't find the device and will drop into emergency mode.

thanks.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1564220/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-04-05 13:17 EDT-------
Hi, Canonical.

Is `systemctl daemon-reload` a supported command in maintenance mode as described in this bug?

Thanks.

[Martin Pitt (pitti)]

This is just a cosmetical error message, it fails to run polkit as that's not available in emergency mode. But the reload works anyway. This got fixed yesterday in bug 1565617, so I'm marking this a duplicate.

You can enter emergency mode by specifying "emergency" on the kernel command line, BTW.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-05-18 06:45 EDT-------
Hello Canonical,

Do you need more information from us? Can you please let us know if there are any updates on this issue?

Thanks!

[Martin Pitt (pitti)]

@brsriniv: From my point of view this is fixed in 16.04 LTS, the master bug of this (bug 1565617) is closed. What is still missing?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-07-21 23:19 EDT-------
(In reply to comment #12)
> @brsriniv: From my point of view this is fixed in 16.04 LTS, the master bug
> of this (bug 1565617) is closed. What is still missing?

I can comfirm that this bug has been fixed with 16.04.1. Thanks.