Fix notes:
---
Fix commit is a trivial None check, still upstream.
It's in Jammy+. Fix Focal only; asked about Bionic.
$ git log --oneline --patch -1 9fbf9b223dc26
9fbf9b223dc2 When doing xfr, do not compare with expiration if it is
None. [Issue #390]
...
@@
Hi Brett, Tiago,
Thanks for the debdiff!
I reviewed it and fixed a few bits (please check below),
then tested and sponsored it to Focal.
Question: it seems Bionic is affected; shoud it be fixed?
Fixes:
- Reword changelog
- Add DEP-3 headers [1] in .patch (Origin/Bug-Ubuntu)
- Run
The updated debdiff, for reference purposes.
** Patch added: "lp1941988-dnspython-v2.debdiff"
https://bugs.launchpad.net/designate/+bug/1941988/+attachment/5605637/+files/lp1941988-dnspython-v2.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which is
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1941988
Title:
[SRU] Designate DNS – Secondary zone is failed to be created and gets
into the ERROR status
Hey, Fabio!
That looks good; thanks!
I have built/uploaded to ppa:mfo/lp1947099v2 and for SRU,
as the tests on Oracle have `-t` in, thus no code change
from previous tests, effectively.
Per our chat, for completeness/correctness you'll test on
oracle again, and then we can move the SRU upload
it-agent are probably the
> > best
> > low risk way to work around the bug, and fix AWS users.
> >
> > PS, our ec2-hibinit-agent package diverged from upstream long ago, and the
> > foundations team appear to be happy carrying patches not upstreamed.
&
Hey Fabio,
That happens when the package lands in -proposed.
It looks like the SRU vanguards this Wed/Thu are Robie/Lukasz,
which is good as they are familiar with the discussion/changes,
so I'll ask if they have SRU review cycles to for this upload.
Thanks for following up!
** Changed in:
Apparently no changes are needed to the charm; marking its track as Invalid.
Please feel free to correct/note if required.
** Changed in: charm-designate
Status: New => Invalid
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed
Verification done on jammy-proposed.
1) a system/hardware vendor tested and confirmed that:
- systems with SMBIOS 3.5 report the new fields as expected;
- systems with SMBIOS < 3.4 keep the old fields as expected.
2) I tested on several physical and virtual machines, and:
- systems with
ack VM
cheers,
Mauricio
** Changed in: dmidecode (Ubuntu Kinetic)
Status: In Progress => Fix Released
** Changed in: dmidecode (Ubuntu Kinetic)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: dmidecode (Ubuntu Jammy)
Assignee: (unassigned) => Ma
Nicolas and I talked about a brief review of the debdiff,
and he kindly agreed to provide an update/v2 to address:
- changelog version and description line
- patches dep3 headers and lpnumber- prefix
... while patches are reviewed for feedback (not yet done).
Thanks, Nicolas!
--
You received
The autopkgtest regression report for recon-ng/5.0.1-1 (arm64)
was due to a connection timeout and passed with a rerun (thanks, ~teward!)
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
Verification done on focal-proposed with python3-dnspython only.
Setup:
-
$ sudo apt install -y bind9
$ FILE=/tmp/bind-options
$ cat <"$FILE"
listen-on port 12753 { 127.0.0.1/32; };
allow-query { any; };
allow-transfer { any; };
EOF
$ sudo sed -i "/^options {/ r $FILE"
Hey Matthew,
Sure; uploaded to Focal.
I've reviewed the differences between the debdiffs (all good) and that
the security update isn't related to the change content (no
expected/incremental behavior change; all good), and build tested it.
Thanks for the prompt reaction/update on top of the
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1999711
Title:
Snmptrapd cannot reconnect to MySQL server after hitting MySQL
wait_timeout
Status
** Also affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Incomplete => In Progress
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu Bionic)
Status: New => In Progress
**
All archs finished building successfully on ppa:mfo/lp1994002v2.
Just sent the MR for Lunar. If/once it lands, I can do the SRUs.
https://code.launchpad.net/~mfo/ubuntu/+source/qemu/+git/qemu/+merge/434118
--
You received this bug notification because you are a member of SE SRU
("STS")
For documentation purposes,
The qemu package in lunar-proposed has its migration blocked to lunar(-release)
because of autopkgtests failures (sbuild), which have been analyzed/understood.
We're waiting on the autopkgtests queue to run sbuild w/ triggers on qemu _and_
sbuild from lunar-proposed,
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1994002
Title:
[SRU] migration was active, but no RAM info was set
Status in Ubuntu Cloud Archive:
New
Status in Ubuntu Cloud
The sbuild autopkgtests need a fix for lunar-proposed;
reported bug 215 w/ analysis and debdiff attached.
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1994002
Title:
[SRU]
The sbuild autopkgtest failure on the 'unshare' test
is indeed fixed w/ sbuild in lunar-proposed; however,
now the test 'unshare-qemuwrapper' timed out.
autopkgtest [23:36:43]: summary
build-procenvPASS
unshare-qemuwrapper FAIL timed out
unshare PASS
It
** Tags added: se-sponsor-mfo
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1994002
Title:
[SRU] migration was active, but no RAM info was set
Status in Ubuntu Cloud Archive:
Hi Brett,
Thanks for the debdiffs!
I just reviewed them, and there are changes that should be made.
I could do those myself, but that wouldn't be an opportunity to
learn/practice some details for SRUs for you, so I'll add notes.
*However*, if you're too busy and can't do that, do let me know.
Hi Tom,
Thanks for the updated debdiff!
I have reviewed it and adjusted just a couple minor things,
and will upload it to Focal.
1) Deduplicated a bit of the changelog entry.
2) Added back the 'changelog.xml' portion of the patch,
as the (resulting) changelog.html goes in tomcat9-docs,
and it
Brett, per our email conversation, please ignore this:
> - quilt series: missing 'ubuntu/' dir on k/j (not on f)
I missed that focal uses `d/p/ubuntu/` too (it just wasn't present in
`d/p/series` context lines in the debdiff, for CVEs).
Sorry for the confusion, and thanks for checking!
--
You
Thanks, Brett!
Very minor nitpicks left (changelog entry/release for lunar,
and URL for Origin:), I can handle those.
For Lunar/devel release, I'll send a MR for Christian to
review/upload (my upload rights are for stable releases).
This includes a fix to FTBFS per a package change in the
last
Hey Tom,
Thanks for the SRU template, debdiff, and even a synthetic reproducer!
I just sent you some review feedback internally, and next steps.
Setting the bug status to 'Incomplete' to reflect that for now.
** Changed in: tomcat9 (Ubuntu)
Status: Confirmed => Incomplete
--
You
** Tags added: se-sponsor-mfo
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1903851
Title:
Tomcat9: multipart upload fails over https
Status in tomcat9 package in Ubuntu:
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/436051
Your team MAAS Committers is subscribed to branch maas:2.9.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
The proposal to merge ~mfo/maas:2.9 into maas:2.9 has been updated.
Status: Needs review => Rejected
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/436051
--
Your team MAAS Committers is subscribed to branch maas:2.9.
--
Mailing list:
Review: Disapprove
Done.
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/436051
Your team MAAS Committers is subscribed to branch maas:2.9.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe :
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/436051
Your team MAAS Committers is subscribed to branch maas:2.9.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
Test packages:
https://launchpad.net/~mfo/+archive/ubuntu/lp1926139
isc-dhcp 4.4.1-2.1ubuntu5.20.04.4+lp1926139.2
Default behavior: issue fixed.
---
(gdb) break omapip/dispatch.c:333
(gdb) commands
shell sleep 0.2
continue
end
(gdb) run -d -v
Hey Matthew, Chris,
Apparently there's a simpler, less intrusive, and more specific way to
do this.
Apologies that I missed this earlier, but I found more about the
possibilities in bind9-libs functions while checking the previous fix
approach for regressions.
Could you please provide your
** Patch added: "lp1926139_focal_isc-dhcp_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5643626/+files/lp1926139_focal_isc-dhcp_v2.debdiff
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed
** Tags removed: sts-sponsors ubuntu-sponsors
** Tags added: se-sru-sponsor-mfo
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1999816
Title:
Failure to get free disk space
Jammy/22.04:
- test packages in ppa:mfo/lp1926139
- reproduction steps delta (based on comment #9)
...
Reproducer based on GDB and DHCP noise injection.
It uses 3 veth pairs (DHCP server/client/injector,
the latter two under namespaces) on a linux bridge.
...
LXD VM:
lxc launch ubuntu:jammy
Hey Jorge,
Thanks for the bug report, SRU template, and debdiffs!
I just reviewed those; please find the comments below.
I'll keep the points detailed in case they might help
other readers preparing for submitting SRUs in Ubuntu.
Thanks!
Mauricio
...
SRU template:
---
- Added [Impact]
Steps to Reproduce
---
lxc launch ubuntu:focal rmq-focal
lxc exec rmq-focal -- su - ubuntu
sudo apt install --yes rabbitmq-server
$ sudo rabbitmqctl status | grep -i disk
Free Disk Space
Low free disk space watermark: 0.05 gb
Free disk space: 327.7867 gb
DF=$(which df)
SH=/tmp/df.sh
cat <$SH
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1926139
Title:
dhclient: thread concurrency race leads to DHCPOFFER packets not being
received
Reproducer based on GDB and DHCP noise injection.
It uses 3 veth pairs (DHCP server/client/injector,
the latter two under namespaces) on a linux bridge.
LXD VM:
$ lxc launch ubuntu:focal lp1926139-focal --vm
$ lxc shell lp1926139-focal
Network Setup:
# ip link add br0
Hi Matthew,
Thanks for the excellent analysis and considerate fix proposal, as
always!
I looked at this for the last couple of days, for potential sponsorship.
I have attentively gone through the SRU template and Other Info section,
and considered the proposal to switch bind9-libs into
** Patch added: "lp1926139_focal_isc-dhcp.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5642442/+files/lp1926139_focal_isc-dhcp.debdiff
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the
Hi Jorge,
Thanks for the new debdiffs!
They look good; I just adjusted a few things:
- k/j: version: missing .1 suffix per [1] (on me)
- k/j/f: shorter 'd/p/' on changelog (optional)
- k/j/f: origin field pointing to commit vs. PR.
- f: origin keyword of 'backport' vs. 'upstream'
(the backport
Uploaded to k/j/f/b.
** Description changed:
[Impact]
* While live-migrating many instances concurrently, libvirt sometimes
return `internal error: migration was active, but no RAM info was set:`
* Effects of this bug are mostly observed in large scale clusters with
a lot of
Autopkgtests regressions cleared for kinetic.
--
You received this bug notification because you are a member of SE
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1994002
Title:
[SRU] migration was active, but no RAM info was set
Status in Ubuntu
Verification done on kinetic-proposed.
The migration status during the race condition is
not 'active' (which is expected to have RAM info, but didn't)
but 'setup' (which is not, thus no issues).
(qemu) info migrate
-updates:
...
Migration status: active
total time: 0 ms
-proposed:
...
Hi Andreas and Jorge,
I reviewed the focal v4 debdiff (it does address the origin: tag as per
#20 and #9, and adds change description), and also built it in a PPA and
tested/confirmed it now prints 'unknown' (vs. 'undefined' in #9):
...
Free Disk Space
Low free disk space watermark: 0.05 gb
** Tags removed: sts-sponsor-halves
** Tags added: se-sponsor-halves
--
You received this bug notification because you are a member of SE
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1955129
Title:
trace-cmd report buffer overflow detected
Status
** Tags removed: se-sru-sponsor-mfo
** Tags added: se-sponsor-mfo
--
You received this bug notification because you are a member of SE
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1999816
Title:
Failure to get free disk space breaks "rabbitmqctl
Thanks for the detailed steps to reproduce!
Just a copy/paste from pastebin (internal).
> Here are the steps to reproduce the issue.
> https://pastebin.canonical.com/p/MkZ9PR7kmh/
Steps to reproduce:
A. Launch 3 VMs (1 for MySQL Server, 1 Xenial snmptrapd client and 1
Focal snmptrapd client):
These are the steps for a synthetic reproducer with GDB and QEMU.
It's sufficient to validate the change on QEMU and move forward with SRUs.
(We can add libvirt for reaching the error message too, but it's a plus.)
I'll check/coordinate on the QEMU uploads next week.
cheers,
Mauricio
...
Verification done for focal-proposed.
focal-updates: FAIL (status: active)
(qemu) info migrate
...
Migration status: active
total time: 0 milliseconds
focal-proposed: PASS (status: setup)
(qemu) info migrate
...
Migration status: setup
Verification done for bionic-proposed.
bionic-updates: FAIL (status: active)
(qemu) info migrate
info migrate
globals: store-global-state=1, only_migratable=0, send-configuration=1,
send-section-footer=1
capabilities: xbzrle: off rdma-pin-all: off auto-converge:
Hi Igor,
Friendly follow-up, if you have a chance to review the updated changes.
Thanks!
--
https://code.launchpad.net/~jorge-merlino/maas/+git/maas/+merge/437352
Your team MAAS Committers is subscribed to branch maas:master.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to :
Thanks for the review and feedback, Adam!
--
https://code.launchpad.net/~jorge-merlino/maas/+git/maas/+merge/437352
Your team MAAS Committers is subscribed to branch maas:master.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe :
autopkgtests regressions cleared; unrelated to these changes.
--
You received this bug notification because you are a member of SE
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1994002
Title:
[SRU] migration was active, but no RAM info was set
Hi Björn,
Friendly follow-up, if you have a chance to review the tests added.
Thanks!
--
https://code.launchpad.net/~tiago.pasqualini/maas/+git/maas/+merge/439150
Your team MAAS Committers is subscribed to branch maas:master.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to :
Hey Andreas,
Thanks for catching that; I can't recollect why I mentioned the backport
matched the v3.8.x branch:
> (the backport matches the upstream's in v3.8.x).
Let's wait for Jorge's details on that delta.
--
You received this bug notification because you are a member of SE SRU
("STS")
** Tags added: se-sru-sponsor-mfo
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1926139
Title:
dhclient: thread concurrency race leads to DHCPOFFER packets not being
received
>From the 'Where problems could occur' section.
Considerations on regressions and approaches.
[Where problems could occur]
isc-dhcp is a core package, and any change comes with the risk that
users would not be able to receive dhcp leases with dhclient, leaving
their systems with no IP address
Pressing Page Down 17 times to go over the bug description sounds like a
new record! ;-)
Just in case future reviewers don't find that as exciting while going
through reviews, I'll move some text into comments and reference them
from the description.
** Bug watch added:
From the 'Other Info' section.
Detailed analysis of the issue and more.
[Other Info]
Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/
Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/
When you tcpdump dhclient, we see all DHCPDISCOVER packets being replied
to with DHCPOFFER packets,
verification done on jammy
(full steps in comment #9)
The issue is not reproducible with the package in -proposed,
and is reproducible with the 2 switches for the old behavior
(DHCP_FD_FLAGS_POKE=0 or dhcp.fd_flags_poke=0), as expected.
...
# add-apt-repository -yp proposed
# apt policy
verification done on focal
(full steps in comment #9)
The issue is not reproducible with the package in -proposed,
and is reproducible with the 2 switches for the old behavior
(DHCP_FD_FLAGS_POKE=0 or dhcp.fd_flags_poke=0), as expected.
...
# add-apt-repository -y 'deb
The -proposed packages have also been verified by the Microsoft Azure team.
14k+ VM deployments with the fix didn't observe the issue over the weekend.
Marking jammy/focal as verified based on that plus 2 synthetic tests
above.
** Tags removed: verification-needed verification-needed-focal
The proposal to merge ~seyeongkim/maas:lp1979403_to_3_2 into maas:3.2 has been
updated.
Commit message changed to:
Adding Lan_Conf_Channel_1 to 3
BMC with multiple channel can't find ip
so added Lan_Conf_Channel_1 to 3 to support them
(cherry picked from commit
Integration Tests
http://maas-integration-ci.internal:8080/view/MAAS%203.0/job/maas-focal-3.0-git/64/
Fail: 0
Skip: 10
Pass: 74
Total: 84
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443686
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list:
The proposal to merge ~mfo/maas:3.0 into maas:3.0 has been updated.
Status: Needs review => Rejected
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443686
--
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list:
Done.
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443686
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help :
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443686
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
Mauricio Faria de Oliveira has proposed merging ~mfo/maas:3.0 into maas:3.0.
Requested reviews:
Mauricio Faria de Oliveira (mfo)
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443686
Please ignore this. It's just for unit tests.
--
Your team MAAS Committers
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443686
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
** Changed in: ubuntu-pro
Status: New => Invalid
--
You received this bug notification because you are a member of SE
("STS") Sponsors, which is subscribed to Ubuntu Pro.
https://bugs.launchpad.net/bugs/2017760
Title:
pro 不支持ipv6（pro don't support IPv6）
Status in Ubuntu Pro:
Invalid
Hi Seyeong,
If that helps, you can run unit tests locally too; see HACKING.rst
Thanks!
Mauricio
--
https://code.launchpad.net/~seyeongkim/maas/+git/maas/+merge/443937
Your team MAAS Maintainers is requested to review the proposed merge of
~seyeongkim/maas:lp2020397 into maas:master.
--
Mauricio Faria de Oliveira has proposed merging ~mfo/maas:3.1 into maas:3.1.
Requested reviews:
Mauricio Faria de Oliveira (mfo)
Related bugs:
Bug #1807725 in MAAS: "Machine interfaces allow '_' character, results on a
interface based domain breaking bind (as it doesn't allow it for the
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444214
Your team MAAS Committers is subscribed to branch maas:3.1.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
The proposal to merge ~mfo/maas:3.1 into maas:3.1 has been updated.
Status: Rejected => Merged
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444214
--
Your team MAAS Committers is subscribed to branch maas:3.1.
--
Mailing list:
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444214
Your team MAAS Committers is subscribed to branch maas:3.1.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
The proposal to merge ~mfo/maas:2.9 into maas:2.9 has been updated.
Status: Needs review => Rejected
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444216
--
Your team MAAS Committers is subscribed to branch maas:2.9.
--
Mailing list:
The proposal to merge ~mfo/maas:3.1 into maas:3.1 has been updated.
Status: Needs review => Rejected
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444214
--
Your team MAAS Committers is subscribed to branch maas:3.1.
--
Mailing list:
The proposal to merge ~mfo/maas:2.9 into maas:2.9 has been updated.
Status: Rejected => Merged
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444216
--
Your team MAAS Committers is subscribed to branch maas:2.9.
--
Mailing list:
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444127
Your team MAAS Maintainers is requested to review the proposed merge of
~mfo/maas:lp2020397-opt-out into maas:master.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to :
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444127
Your team MAAS Maintainers is requested to review the proposed merge of
~mfo/maas:lp2020397-opt-out into maas:master.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to :
Mauricio Faria de Oliveira has proposed merging ~mfo/maas:lp2020397-opt-out
into maas:master.
Requested reviews:
MAAS Maintainers (maas-maintainers)
Related bugs:
Bug #2020397 in MAAS: "Custom images which worked ok is not working with 3.2"
https://bugs.launchpad.net/maas/+b
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444127
Your team MAAS Maintainers is requested to review the proposed merge of
~mfo/maas:lp2020397-opt-out into maas:master.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to :
http://maas-integration-ci.internal:8080/view/MAAS%203.1/job/maas-focal-3.1-git/20/
Test Result (no failures)
Fail 0
Skip 10
Pass 74
Total 84
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/444214
Your team MAAS Committers is subscribed to branch maas:3.1.
--
Mailing list:
*** This bug is a duplicate of bug 2014975 ***
https://bugs.launchpad.net/bugs/2014975
Private bug reported:
Patch for LP#2014975
** Affects: ubuntu-pro
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 2014975
Test Bug
--
You received this
Mauricio Faria de Oliveira has proposed merging ~mfo/maas:3.0 into maas:3.0.
Requested reviews:
MAAS Maintainers (maas-maintainers)
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Please ignore this. It's just for unit tests.
--
Your team MAAS Committers
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
Integration CI:
Test Result (no failures)
maas-integration
Fail 0
Skip 10
Pass 74
Total 84
http://maas-integration-ci.internal:8080/view/MAAS%203.0/job/maas-focal-3.0-git/62/
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Your team MAAS Committers is subscribed to branch
Apparently unrelated to changes in 3.0.0..origin/3.0.
[2023-05-17T21:57:08.533Z]
==
[2023-05-17T21:57:08.533Z] FAIL:
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
Review: Disapprove
Done.
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe :
The proposal to merge ~mfo/maas:3.0 into maas:3.0 has been updated.
Status: Needs review => Rejected
For more details, see:
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
--
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list:
Reverting VMFS7 feature backport.
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe :
jenkins: !test
--
https://code.launchpad.net/~mfo/maas/+git/maas/+merge/443141
Your team MAAS Committers is subscribed to branch maas:3.0.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More
The 2 failures do not seem related to the reverted changes.
[2023-05-18T18:41:14.660Z]
==
[2023-05-18T18:41:14.660Z] FAIL:
201 - 299 of 299 matches
Mail list logo
