This bug is believed to be fixed in curtin in version 18.2. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/360217
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when
This bug is fixed with commit ea939ee7 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=ea939ee7
** Changed in: curtin
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
** Merge proposal unlinked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/358104
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when
My theory on different versions of GRUB causing the issue didn't pan
out. After wiping the PReP partition I was able to go between 14.04,
16.04, and 18.04 with no problems. The only way I've been able to
reproduce the issue after fixing it is by filling the PReP partition
with garbage using
$ dd
** No longer affects: maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when partition table is GPT
To manage notifications about this bug go to:
** Changed in: curtin
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when partition table is GPT
To manage
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/358104
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when
On Wed, Oct 31, 2018 at 9:20 AM Scott Moser wrote:
>
> With regard to wiping all prep partitions...
> We do have code that does this in helpers/pt_prep. Ie, the non-storage
> config path does this.
> However, this is kind of a grey line here. If maas wants a partition wiped,
> then MAAS
With regard to wiping all prep partitions...
We do have code that does this in helpers/pt_prep. Ie, the non-storage config
path does this.
However, this is kind of a grey line here. If maas wants a partition wiped,
then MAAS should send config that says it should be wiped.
If we bake in
On Tue, Oct 30, 2018 at 7:35 PM Lee Trager wrote:
>
> Every time I commission the PPC host we have in our CI I always get a
> GPT partitioning table using MAAS 2.4.2+. Looking through the source
> code it appears GPT is always set when creating a new partitioning
> table[1] and when generating
Every time I commission the PPC host we have in our CI I always get a
GPT partitioning table using MAAS 2.4.2+. Looking through the source
code it appears GPT is always set when creating a new partitioning
table[1] and when generating the preseed[2] due to the bios_boot_method
being powernv. I'm
@Andres can you attatch the full config when you run this under beta3
with the MBR config?
>From what I can tell, the prep partition (/dev/sda1) is created fine,
but our wipe clears out the first and last 1M , it's an 8M partition.
This is a curtin bug as you've specified 'wipe: zero' which
@Ryan, with curtin verbose: https://pastebin.ubuntu.com/p/nzvHvStyKb/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el when partition table is GPT
To
Can you do a curtin verbose install with GPT and capture the logs from
that? I don't think mbr should matter, but we do use 'parted' for msdos
partition creation and 'sgdisk' for gpt so there could be some issue
going on here.
--
You received this bug notification because you are a member of
>From the MAAS perspective, I can confirm that MAAS is setting to GPT,
and it is failing. When setting it to MBR, it succeeds.
That said... the other question is whether curtin needs to support using
GPT instead?
** Changed in: maas
Status: Triaged => Incomplete
--
You received this bug
The difference in behavior is between 2.5.0-beta3 and
418bd67af816b4a99747eb7a1ca8cb966b58ed84
The only storage related change is a UI change:
https://git.launchpad.net/maas/commit/?id=32e3d12485456e07fbf5deb82ba6ab455eeefcb5
, which wouldn't seem related.
** Changed in: maas
Assignee:
After further investigation, it seems that commissioning is setting
different partition tables:
MAAS 2.5.0beta3 sets partition table to MBR
MAAS 2.5.0beta4 sets partition table to GPT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I deployed using MAAS 2.5.0beta3, and the result is successful. This is
the config from get-curtin-config: http://paste.ubuntu.com/p/bg4JZ4bVb7/
It seems that 2.5.0beta3 has:
- id: sda
model: IPR-0 6DC90500
name: sda
ptable: msdos
serial: IBM_IPR-0_6DC90580
type:
The failed installation log for the above config:
https://pastebin.ubuntu.com/p/FSMCXRMzXt/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage
** Attachment added: "storage-ppc64.png"
https://bugs.launchpad.net/maas/+bug/1800153/+attachment/5206915/+files/storage-ppc64.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
The curtin configuration can be found here:
http://paste.ubuntu.com/p/89DwnJGzc2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage
** Changed in: curtin
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage notifications about this bug go to:
Can you attach the curtin logs?
And do you have logs from the last previous successful run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800153
Title:
[2.5] Failed to deploy ppc64el
To manage notifications
25 matches
Mail list logo
