[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-11-27 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671058

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-09-28 Thread Dimitri John Ledkov
Checking in on this stale bug report. Which kernel drivers are missing from the main linux-image package, and have we moved those in later releases and SRUed into xenial? ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-03-13 Thread Po-Hsu Lin
Verified with the older 4.8.0-38 kernel, docker.io version 1.12.1-0ubuntu15 and 1.12.6-0ubuntu1~16.10.1 will both fail without the -extra package as well. So just like xnon mentioned above, we will need to add the missing driver to the main kernel package. -- You received this bug notification

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-03-10 Thread Dimitri John Ledkov
We must support docker on cloud images which by default do not install -extra- package. Thus missing default drivers should be in the main kernel package. ** Changed in: linux (Ubuntu Yakkety) Status: Invalid => Triaged ** Changed in: linux (Ubuntu) Status: Invalid => Triaged --

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-03-09 Thread Po-Hsu Lin
OK the missing driver error message give us a clue, the linux-image-extra-4.8.0-42-generic package was not installed. It work well after that, I will close this bug. Thanks! ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Yakkety) Status:

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-03-09 Thread Po-Hsu Lin
Whoa! It's still failing with the re-spinned 4.8.0-42-generic kernel. But this time I can see more error message from systemctl status output, which is complaining about the driver this time. (Test case: ubuntu_fan_smoke_test) # systemctl status docker.service docker.service - Docker

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-03-08 Thread Po-Hsu Lin
Hi Joseph, I will give it another shot first when the new Yakkety kernel is available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671058 Title: docker service failed to start on s390x (zVM)

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-03-08 Thread Joseph Salisbury
Would you like me to assist with a bisect on this one? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux

[Bug 1671058] Re: docker service failed to start on s390x (zVM) Yakkety

2017-03-08 Thread Po-Hsu Lin
It looks like this is a regression, I switched back to 4.8.0-38, and docker service can be started without any problem. ** Package changed: docker.io (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.