SQA is happy to give a +1 for Bionic and Focal
we have no Juju workloads which currently run on Jammy, and only do Juju
workloads on LTS's
Bionic:
https://solutions.qa.canonical.com/testplans/testplaninstance/7792f440-db83-452a-adbe-
edbb0bbd2b62
Focal:
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907250
Title:
[focal] charm becomes blocked with workload-status "Failed to connect
to MySQL"
To manage
Hello,
Solutions QA has observed successful deployments of openstack using the
proposed cloud-init on bionic and focal and are happy to give a +1
https://solutions.qa.staging.canonical.com/testplans/testplaninstance/bacea2e4-8842-44a3-941f-febeb529f6ae
--
You received this bug notification
I'm going to re-open this bug after working through Openstack networking
migration for OVS to OVN.
I ran into an issue where the MTU set in netplan caused all my instances
to be lost after the migration. While this can, and should, be
documented, I also think that reducing places where instances
We had this issue using the maas 3.0 snap in the new SQA lab
curling the address came back with a long delayed "connection refused"
and nothing else.
I was able to get everything back in working order by restarting maas.
Another odd symptom was that I could loop calls where i would connect
via
Hello
SQA has had successful test runs against this version of cloud-init and are
happy to bless this release.
results against bionic and focal can be found below:
Bionic:
https://solutions.qa.canonical.com/testplans/testplaninstance/6cc457fe-125b-4ef0-b77c-b11da2022fbb
Focal:
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
Focal/Groovy deploy creates a 'node1' node
To manage notifications about this bug go to:
+1 from SQA running deploys against openstack/ceph on both focal and bionic
openstack results can be seen at:
https://solutions.qa.canonical.com/testplans/testplaninstance/3a227faa-70b0-4fb6-be4d-0ea79dfe1845
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm that this fixes the issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go to:
Thanks for the work on that, very nice turn around time;
lowering to field-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage
Because of the blocking for charmed kubernetes on focal; we're raising
this bug to field critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
subbing to field high,
the workaround for a new snapped install MaaS seems to be to install Maas into
a container, but existing installs upgrading to Focal will run into this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This workaround doesnt seem to work for snapped maas applying the fix to
/var/snap/maas/current/bind/named.conf.options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start
** Tags added: cdo-qa
** Tags added: foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792978
Title:
initscript avahi-daemon, action "start" failed
To manage notifications about
Public bug reported:
When installing maas-region-controller, avahi-deamon failed to install
because it was it seemed to already be running.
$ apt-get -q install -y maas-region-controller
[1invoke-rc.d: initscript avahi-daemon, action "start" failed.
[0;1;31m●[0m avahi-daemon.service -
15 matches
Mail list logo
