Bug 7039 - Toaster web interface tries to load from address http://0.0.0.0:8000
Summary: Toaster web interface tries to load from address http://0.0.0.0:8000
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.8
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.8 M2
Assignee: Alexandru Damian
QA Contact: Ionut Chisanovici
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-12-08 11:53 UTC by Ionut Chisanovici
Modified: 2015-01-20 14:38 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ionut Chisanovici 2014-12-08 11:53:42 UTC
Hi,

BUILD: 1.8_M1: b813bdebb36501500e86fea5f7e15b4b15ea0902
STEPS TO REPRODUCE: 1. Start toaster in managed mode by issuing the following command in your "poky" directory: 		
			bitbake/bin/toaster
	If prompted, provide path to your "poky" and build directories, respectively.
2. Once browser starts, make sure you are accessing http://localhost:8000

After the bitbake/bin/toaster command, the toaster web interface tries to load from address http://0.0.0.0:8000 which is failing.

If I try to load the toaster web interface using: http://localhost:8000 or http://my.station.ip.address:8000 then the interface is loaded correctly.

Cheers,
Ionut C
Comment 1 Alexandru Damian 2014-12-08 12:36:40 UTC
What user agent / browser shows this problem ?

I've tested Firefox and Chrome, and both can succesfully connect to 0.0.0.0:8000
Comment 2 Ionut Chisanovici 2014-12-08 13:00:42 UTC
I'm using Firefox for Ubuntu 14.10 but I don't think this is related to the browser.

Cheers,
Ionut C
Comment 3 Alexandru Damian 2014-12-16 13:02:43 UTC
Pushed to review on poky-contrib:adamian/20141215-development
Comment 4 Alexandru Damian 2015-01-09 11:32:48 UTC
Fixed in master.
Comment 5 Ionut Chisanovici 2015-01-20 14:38:53 UTC
Hi,

Verified, issue is fixed for 1.8 M2 RC1: d9d5b8b499af3ae01a1e33d0d3969c54c2d4ab1b.

Cheers,
Ionut C