[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-04 Thread Rafael David Tinoco
All good for a final review and Eoan upload (followed by the SRUs then). ** Description changed: + [Impact] + + * sg3-utils-udev package introduces 55-scsi-sg3_id.rules udev rule that + take places BEFORE rules either finding correct ID_SERIAL for the USB + block device, or calculating it from

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-04 Thread Rafael David Tinoco
This it the upstream pull request: https://github.com/hreinecke/sg3_utils/pull/47 And I have updated Debian pull request as well: https://salsa.debian.org/linux-blocks- team/sg3-utils/merge_requests/2/commits I'm preparing updates for Eoan, Disco and Bionic fixes. -- You received this bug not

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-04 Thread Rafael David Tinoco
Thanks for confirming that! On the other hand, patch seems to be good, even for upstream. >From the merge request comment: """ ACTUALLY, it made little difference because the new rules: Oct 04 09:34:46 macbook systemd-udevd[30592]: Process '/usr/bin/sg_inq --export --inhex=/sys/class/scsi_devic

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-03 Thread dann frazier
A follow-up on comment #47 - I've proven that the reboot loop had nothing to do with your change, I just missed a required section of the preseed. Updated file attached just as an fyi. ** Attachment added: "curtin_userdata_ubuntu_arm64_generic_disco_seidel-FLAKYMEMORY" https://bugs.launchpad.

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-03 Thread Rafael David Tinoco
No no, you are definitely right, I totally missed upstream change, I did "on my own", not sure why I thought upstream didn't have any change/fix (too many bugs in my head perhaps). I'll reply you in the MR, but, we should go with whatever upstream has done, so delta is reduced. I might re-do the MR

Re: [Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-03 Thread dann frazier
On Thu, Oct 3, 2019 at 4:42 AM Rafael David Tinoco wrote: > > Hey Dann, nope, the file changed is Debian related only. hmm.. I see the file in the upstream source, and Debian hasn't patched it. But, perhaps you mean that upstream is not impacted. And yeah, I can see that this may be the case. Ups

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-03 Thread Rafael David Tinoco
Hey Dann, nope, the file changed is Debian related only. I'm glad it worked, I'll ask server team review and merge then! Tks for testing it!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Titl

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-02 Thread dann frazier
@rafaeldtinoco: Also, I wonder if it wouldn't make sense to submit your patch upstream? https://github.com/hreinecke/sg3_utils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Title: failing

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-02 Thread dann frazier
I MAAS deployed an impacted system w/ the attached preseed to include your PPA, and curtin successfully installed. Afterward, the system entered a deploy loop, but there's no sign that this was related to your fix - rather, it may just be a boot order issue. Interrupting the loop and telling it to

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-10-01 Thread Rafael David Tinoco
Disco PPA package (and MR) is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Title: failing to deploy Ubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
Note: I have to re-submit Disco MR and a new PPA package, as the compiler in Disco is likely more recent and treating lots of "new warnings" as errors (-Wimplicit-fallthrough, etc...). I'll do it tomorrow! -- You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
Summary: Merge Requests (to be reviewed): # Debian MR: https://salsa.debian.org/linux-blocks-team/sg3-utils/merge_requests/2 # Eoan https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/sg3-utils/+git/sg3-utils/+merge/373438 # Disco https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/sg3

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
I have asked upstream to consider the following merge: https://salsa.debian.org/linux-blocks-team/sg3-utils/merge_requests/2 ** Changed in: sg3-utils (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: sg3-utils (Ubuntu Disco) Status: Confirmed => In Progress ** Change

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
$ rmadison sg3-utils-udev sg3-utils-udev | 1.40-0ubuntu1 | xenial | all sg3-utils-udev | 1.42-2ubuntu1 | bionic | all sg3-utils-udev | 1.42-2ubuntu1 | disco | all sg3-utils-udev | 1.44-1ubuntu1 | eoan | all And: [ Mauricio Faria de Oliveira ] * sg3-utils-udev (new binary package): pro

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
Alright, I'll change the udev rules from sg3-utils-udev package to ignore USB devices. From the initial ACTION (add) event, I only get simple data from udev: S: disk/by-id/usb-Corsair_Voyager_Mini_3.0_070851D0E490C776-0:0 S: disk/by-path/pci-:00:14.0-usb-0:2:1.0-scsi-0:0:0:0 S: disk/by-label/U

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
Adding: # Ignore USB block devices as they don't contain VPD 0x80 and 0x83 # and their SERIAL is calculated from usb_id in persistent-storage rules DEVPATH=="*usb*", GOTO="sg3_utils_id_end" before #SCSI EVPD page 0x80 values in 55-scsi-sg3_id.rules file fixes the issue. -- You received this

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
I meant "for USB devices and that would be "enough"" in previous comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Title: failing to deploy Ubuntu Disco To manage notifications about t

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
Well, checking udev rules, its exactly what you said. I guess we could change sg3 udev rules not to execute sg_inq --export --inhex to /sys/block/$kernel/device/vpd_pg83 for SCSI devices and that would be "enough" for this issue. --inhex=FN|-I FNread ASCII hex from file FN instead of

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
BTW, you got: 15 the utility is unable to open, close or use the given DEVICE or some other file. The given file name could be incorrect or there may be permission problems. Adding the '-v' option may give more information. And this is likely because USB devices don't have VPD, so sysf

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
This also happens in amd64 (and likely other architectures), only when having "sg3-utils-udev" package installed. Command "udevadm settle" only returns after the initial "sg_inq" command also returns, raising the question: (1) Would call "udevmadm settle" before "udevadm info" be enough to get A

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Ryan Harper
The _real_ concern is: do you get the _same_ ID_SERIAL value with and without the sg3-utils- udev package installed? Can you compare: /dev/disk/by-id/*https://bugs.launchpad.net/bugs/1833618 Title: failing to deploy Ubuntu Disco To manage notifications about this bug go to: https://bugs.launc

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
@Rhyan, thanks for the quick pointers, helped a lot =), I think I found out what is going on. Linux mylab 5.0.0-30-generic #32-Ubuntu SMP Wed Sep 18 00:24:43 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux Using a memstick in an aarch64 server: $ sudo sg_inq -d /dev/sdb standard INQUIRY: PQual=0

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Ryan Harper
@Rafael, the critical path would be to check the output from: udevadm info --query=all --name=/dev/sd[cd] | grep -i serial ID_SERIAL does not get set on Disco where we have sg3-utils package install, which adds the s3g-utils-udev package, and includes the rules file 55-scsi-sg3_id.rules. This u

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
@Patricia, I'll concentrate efforts into the sg3-utils issue with disco for now. For Eoan, based on the console output you attached to the bug, it seems that one of the services listed as "getty@ttyAMA0.service" dependencies did not start before timeout occurred. You can check systemd output after

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-30 Thread Rafael David Tinoco
** Changed in: sg3-utils (Ubuntu) Status: New => Incomplete ** Changed in: sg3-utils (Ubuntu) Status: Incomplete => Confirmed ** Changed in: sg3-utils (Ubuntu) Importance: Undecided => High ** Changed in: sg3-utils (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (raf

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-27 Thread Andrew Cloke
MAAS deployments of disco to Marvell "Sabre" boards (CN99XX SoC) with more than one disk also fails. Internal node: * fails on "starbuck" with 2 disks * passes on "hotdog" and "apollo" server that both only have 1 disk -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-27 Thread Andrew Cloke
@Ryan, do you know who owns sg-utils? Is there any further information or system access that we can provide? Many thanks, Andy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Title: failing

Re: [Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-12 Thread Ryan Harper
On Thu, Sep 12, 2019 at 5:00 PM Patricia Domingues < patricia.doming...@canonical.com> wrote: > Ryan, > Sorry for delay, we had a BMC issue and it required a manual intervention > to fix it. > I've tested Eoan in that machine and it also fails, it doens't show the > same curtin error as Disco show

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-12 Thread Patricia Domingues
Ryan, Sorry for delay, we had a BMC issue and it required a manual intervention to fix it. I've tested Eoan in that machine and it also fails, it doens't show the same curtin error as Disco shows, but Eoan is not deployed. It get stuck and MAAS shows `Marking node failed - Node operation 'Deployi

Re: [Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-03 Thread Ryan Harper
On Tue, Sep 3, 2019 at 9:31 AM Andrew Cloke wrote: > @Ryan, do you know if the Server team looks after sg3-utils-udev, or > should we be chasing the Foundations team to look into this? > Not quite sure, I'll follow up. Also, Patricia, can you try an Eoan install to see if this is maybe fix in n

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-09-03 Thread Andrew Cloke
@Ryan, do you know if the Server team looks after sg3-utils-udev, or should we be chasing the Foundations team to look into this? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Title:

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-08-30 Thread Patricia Domingues
I think it worth mentioning, as the machine above that we are not able to deploy Disco is a Gigabyte(gbt-mt30)Cavium ThunderX 88XX, I've decided to test Disco in other machine, not Gigabyte, but Cavium ThunderX 88XX(CRB-2s) and I've noticed that in one machine Disco is successfully deployed and in

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-08-30 Thread Patricia Domingues
- it fails in a machine where it has more than one disk - in this case an USB stick. (machine nominated as recht) curtin: curtin_recht_failed_disco https://paste.ubuntu.com/p/NVkPnxVDn5/ ** Attachment added: "syslog_recht_failed_disco" https://bugs.launchpad.net/curtin/+bug/1833618/+attachm

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-08-30 Thread Patricia Domingues
- it is deployed in a machine where it has just one disk. (machine nominated as wright) curtin: curtin_wright_success_disco https://paste.ubuntu.com/p/7CmYw57Rn6/ ** Attachment added: "syslog_wright_success_disco" https://bugs.launchpad.net/curtin/+bug/1833618/+attachment/5285881/+files/sysl

[Bug 1833618] Re: failing to deploy Ubuntu Disco

2019-08-30 Thread Ryan Harper
It's actually the sg3-utils-udev package which provides new udev rules to inquery about scsi device's ID_SERIAL. ** Also affects: sg3-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U