[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-06-20 Thread Scott Moser
This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Fix Committed

[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-19 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 18.2-14-g6d48d265-0ubuntu1 --- cloud-init (18.2-14-g6d48d265-0ubuntu1) bionic; urgency=medium * New upstream snapshot. - net: Depend on iproute2's ip instead of net-tools ifconfig or route - DataSourceSmartOS: fix hang when meta

[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-18 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/343562 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763511 Title: DataSourceSmartOS should de

[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-18 Thread Scott Moser
An upstream commit landed for this bug. To view that commit see the following URL: https://git.launchpad.net/cloud-init/commit/?id=025ddc03 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763511 Title

[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-17 Thread Scott Moser
** Changed in: cloud-init (Ubuntu) Status: New => In Progress ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763511 Title:

[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-17 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343435 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763511 Title: DataSourceSmartOS should defaul

Re: [Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-13 Thread Scott Moser
ah.yeah, you're probably right. On Fri, Apr 13, 2018 at 2:02 AM, Mike Gerdts <1763...@bugs.launchpad.net> wrote: > I think we've been avoiding this issue so far because the file system is > being created without partitioning the disk (layout: False). With "layout: > False", I'm guessing that wh

Re: [Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-12 Thread Mike Gerdts
I think we've been avoiding this issue so far because the file system is being created without partitioning the disk (layout: False). With "layout: False", I'm guessing that whether gpt or mbr is specified makes no difference. Mike On Thu, Apr 12, 2018 at 8:41 PM, Scott Moser wrote: > You prob

[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-12 Thread Scott Moser
You probably need to change table_type mbr to gpt too if the point is big disks. In fact it might just be the mbr table that is limiting you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763511 Tit

[Bug 1763511] Re: DataSourceSmartOS should default to ext4

2018-04-12 Thread Scott Moser
fwiw, I think you could send vendor-data to with cloud-config to set the fs_setup like you wanted (assuming 'you' here are the cloud platform). The point of vendor data is so that the vendor could make changes like this without changing cloud-init. But the 1 byte change is also acceptable. (ext3