Bug 1526861 - unable to do an installation when a boot option is added
Summary: unable to do an installation when a boot option is added
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1527700 1528215 (view as bug list)
Depends On:
Blocks: F28BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2017-12-18 03:31 UTC by lnie
Modified: 2018-03-12 12:15 UTC (History)
12 users (show)

Fixed In Version: anaconda-28.15-1
Clone Of:
Environment:
Last Closed: 2018-01-08 17:24:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (51.67 KB, image/png)
2017-12-18 03:31 UTC, lnie
no flags Details
anaconda.log (1.77 KB, text/plain)
2017-12-18 11:56 UTC, lnie
no flags Details
journal (260.08 KB, text/x-vhdl)
2017-12-18 11:56 UTC, lnie
no flags Details
syslog (223.94 KB, text/plain)
2017-12-18 11:57 UTC, lnie
no flags Details
storage.log (251 bytes, text/plain)
2017-12-18 11:58 UTC, lnie
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1532451 0 unspecified CLOSED "Fix" for 1526861 prematurely removed unicode-related escape code without properly assessing consequences 2022-04-05 13:43:18 UTC
Red Hat Bugzilla 1554243 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1532451 1554243

Description lnie 2017-12-18 03:31:52 UTC
Created attachment 1369251 [details]
screenshot

Description of problem:
As shown in the attached screenshot,the system just hang there if you add a inst.text boot option.


Version-Release number of selected component (if applicable):
Fedora-Workstation-netinst-x86_64-Rawhide-20171217.n.0.iso

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2017-12-18 03:35:20 UTC
You will see the same hang with inst.vnc or inst.repo added

Comment 2 lnie 2017-12-18 05:06:23 UTC
I lied,inst.repo and inst.ks works,though it will hangs there for a little while.

Comment 3 Vendula Poncova 2017-12-18 10:28:13 UTC
Please, attach the logs or at least the output from journalctl.

Comment 4 lnie 2017-12-18 11:56:27 UTC
Created attachment 1369387 [details]
anaconda.log

Comment 5 lnie 2017-12-18 11:56:56 UTC
Created attachment 1369388 [details]
journal

Comment 6 lnie 2017-12-18 11:57:25 UTC
Created attachment 1369389 [details]
syslog

Comment 7 lnie 2017-12-18 11:58:00 UTC
Created attachment 1369390 [details]
storage.log

Comment 8 lnie 2017-12-19 03:08:42 UTC
Still see this in the latest Fedora-Workstation-netinst-x86_64-Rawhide-20171218.n.0.iso,and console=ttyS0 will also cause the hang,proposing a blocker.

Comment 9 Fedora Blocker Bugs Application 2017-12-19 03:10:24 UTC
Proposed as a Blocker for 28-beta by Fedora user lnie using the blocker tracking app because:

 This bug affects the criteria:
The installer must be able to complete an installation using the serial console interface

Comment 10 Martin Kolman 2017-12-20 14:36:31 UTC
Looks like this was caused by systemd 236 no longer liking an escape sequence in a spurious echo call in the tmux service file. 

A PR fixing this issue (by dropping the echo call) is here:
https://github.com/rhinstaller/anaconda/pull/1283

Comment 11 Adam Williamson 2017-12-20 18:10:10 UTC
*** Bug 1527700 has been marked as a duplicate of this bug. ***

Comment 12 Adam Williamson 2017-12-20 18:16:59 UTC
I don't think the "fix" here is correct. See https://github.com/rhinstaller/anaconda/commit/ab29bdff2e041ec4f354c3334d8aa15ea8366a17#commitcomment-26397639 for details.

Comment 13 Adam Williamson 2017-12-20 18:17:49 UTC
CCing Zbigniew; see above, I don't think this story is over yet, and I don't think the fix is as simple as removing the command. We may still need to be able to do this somehow.

Comment 14 Martin Kolman 2017-12-21 14:50:57 UTC
*** Bug 1528215 has been marked as a duplicate of this bug. ***

Comment 15 Adam Williamson 2018-01-08 17:24:10 UTC
So, the bug reported here definitely is fixed now. I still think the fix was wrong, but probably the best way to handle that is to close this and file a new bug. So I'll do that.


Note You need to log in before you can comment on or make changes to this bug.