[Bug 2069941] Re: sosreport does not collect maas status when using --all-logs
From the latest/edge snap, and some initial debugging Working with "sudo sos report -o sunbeam -a --batch --build" ubuntu@sunbeam:~$ sudo ls -lh /var/tmp/sosreport-sunbeam-2024-06-20-vvzypam/sos_commands/sunbeam total 120K -rw-r--r-- 1 root root 1.2K Jun 20 08:55 juju_controller-config_-c_sunbeam-controller -rw-r--r-- 1 root root 1006 Jun 20 08:55 juju_controller-config_-c_sunbeam-controller_--format_json -rw-r--r-- 1 root root 285 Jun 20 08:54 juju_controllers -rw-r--r-- 1 root root 533 Jun 20 08:55 juju_controllers_--format_json -rw-r--r-- 1 root root 3.1K Jun 20 08:55 juju_model-config_-m_sunbeam-controller_admin.controller -rw-r--r-- 1 root root 3.6K Jun 20 08:55 juju_model-config_-m_sunbeam-controller_admin.controller_--format_json -rw-r--r-- 1 root root 3.5K Jun 20 08:55 juju_model-config_-m_sunbeam-controller_sunbeam.maas.openstack -rw-r--r-- 1 root root 3.8K Jun 20 08:55 juju_model-config_-m_sunbeam-controller_sunbeam.maas.openstack_--format_json -rw-r--r-- 1 root root 184 Jun 20 08:54 juju_model-defaults_-c_sunbeam-controller -rw-r--r-- 1 root root 376 Jun 20 08:54 juju_models_-c_sunbeam-controller -rw-r--r-- 1 root root 1.2K Jun 20 08:54 juju_models_-c_sunbeam-controller_--format_json -rw-r--r-- 1 root root 1.9K Jun 20 08:55 juju_status_-m_sunbeam-controller_admin.controller -rw-r--r-- 1 root root 6.2K Jun 20 08:55 juju_status_-m_sunbeam-controller_admin.controller_--format_json -rw-r--r-- 1 root root 7.3K Jun 20 08:55 juju_status_-m_sunbeam-controller_sunbeam.maas.openstack -rw-r--r-- 1 root root 42K Jun 20 08:55 juju_status_-m_sunbeam-controller_sunbeam.maas.openstack_--format_json -rw-r--r-- 1 root root 634 Jun 20 08:54 sunbeam_cluster_list -rw-r--r-- 1 root root 65 Jun 20 08:54 sunbeam_cluster_list_--format_yaml -rw-r--r-- 1 root root 1.8K Jun 20 08:54 systemctl_status_snap.openstack Non working with "sudo sos report -o sunbeam -a --batch --build --all-logs" ubuntu@sunbeam:~$ sudo ls -lh /var/tmp/sosreport-sunbeam-2024-06-20-uygvuvy/sos_commands/sunbeam total 12K -rw-r--r-- 1 root root0 Jun 20 08:56 juju_controller-config_-c_sunbeam-controller -rw-r--r-- 1 root root0 Jun 20 08:56 juju_controller-config_-c_sunbeam-controller_--format_json -rw-r--r-- 1 root root0 Jun 20 08:56 juju_controllers -rw-r--r-- 1 root root 533 Jun 20 08:56 juju_controllers_--format_json -rw-r--r-- 1 root root0 Jun 20 08:56 juju_model-config_-m_sunbeam-controller_admin.controller -rw-r--r-- 1 root root0 Jun 20 08:56 juju_model-config_-m_sunbeam-controller_admin.controller_--format_json -rw-r--r-- 1 root root0 Jun 20 08:56 juju_model-config_-m_sunbeam-controller_sunbeam.maas.openstack -rw-r--r-- 1 root root0 Jun 20 08:56 juju_model-config_-m_sunbeam-controller_sunbeam.maas.openstack_--format_json -rw-r--r-- 1 root root0 Jun 20 08:56 juju_model-defaults_-c_sunbeam-controller -rw-r--r-- 1 root root0 Jun 20 08:56 juju_models_-c_sunbeam-controller -rw-r--r-- 1 root root 1.2K Jun 20 08:56 juju_models_-c_sunbeam-controller_--format_json -rw-r--r-- 1 root root0 Jun 20 08:56 juju_status_-m_sunbeam-controller_admin.controller -rw-r--r-- 1 root root0 Jun 20 08:56 juju_status_-m_sunbeam-controller_admin.controller_--format_json -rw-r--r-- 1 root root0 Jun 20 08:56 juju_status_-m_sunbeam-controller_sunbeam.maas.openstack -rw-r--r-- 1 root root0 Jun 20 08:56 juju_status_-m_sunbeam-controller_sunbeam.maas.openstack_--format_json -rw-r--r-- 1 root root0 Jun 20 08:56 sunbeam_cluster_list -rw-r--r-- 1 root root0 Jun 20 08:56 sunbeam_cluster_list_--format_yaml -rw-r--r-- 1 root root 2.1K Jun 20 08:56 systemctl_status_snap.openstack Running this directly from the source works without any problems Non working verbose output [plugin:sunbeam] unpacked command: binary=False, changes=False, chroot=True, cmd=juju model-config -m sunbeam-controller:sunbeam.maas/openstack --format json, cmd_as_tag=False, container_cmd=None, env=None, foreground=False, priority=10, root_symlink=None, runas=ubuntu, runat=None, sizelimit=25, stderr=True, subdir=None, suggest_filename=None, tags=[], timeout=None, to_file=True [plugin:sunbeam] collecting output of 'juju model-config -m sunbeam-controller:sunbeam.maas/openstack --format json', as the ubuntu user [plugin:sunbeam] collecting 'juju model-config -m sunbeam-controller:sunbeam.maas/openstack --format json' output directly to disk [plugin:sunbeam] collected output of 'juju' in 0.5286688804626465 (changes=False) Working verbose output [plugin:sunbeam] unpacked command: binary=False, changes=False, chroot=True, cmd=juju model-config -m sunbeam-controller:sunbeam.maas/openstack --format json, cmd_as_tag=False, container_cmd=None, env=None, foreground=False, priority=10, root_symlink=None, runas=ubuntu, runat=None, sizelimit=25, stderr=True, subdir=None, suggest_filename=None, tags=[], timeout=None, to_file=False [plugin:sunbeam] collecting output of 'juju model-config -m
[Bug 2069941] [NEW] sosreport does not collect maas status when using --all-logs
Public bug reported:
I am observing something strange, but maybe there is an explanation to
this?
```
self.add_cmd_output([
'snap info maas',
'maas status'
])
```
When I run sos report -o maas then sos_commands/maas/maas_status
contains expected data, however if I do sos report -o maas --all-logs
then this file is empty.
(I tried changing the order and snap info maas is always there, but not
maas status)
Running with - shows the following:
```
[plugin:maas] collecting output of 'maas status'
[plugin:maas] collecting 'maas status' output directly to disk
[plugin:maas] collected output of 'maas' in 1.8999457359313965 (changes=False)
[plugin:maas] collected plugin 'maas' in 2.686990976333618
```
sos.json
```
{
"name": "maas status",
"return_code": 0,
"href": "../sos_commands/maas/maas_status"
}
```
sosreport: 4.5.6
``
root@maas:/tmp/sos# apt-cache policy sosreport
sosreport:
Installed: 4.5.6-0ubuntu1~22.04.2
Candidate: 4.5.6-0ubuntu1~22.04.2
Version table:
*** 4.5.6-0ubuntu1~22.04.2 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
4.3-1ubuntu2.1 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
4.3-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
```
** Affects: sosreport (Ubuntu)
Importance: Medium
Status: Confirmed
** Changed in: sosreport (Ubuntu)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069941
Title:
sosreport does not collect maas status when using --all-logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2069941/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059386] Re: curtin-install.log and curtin-install-cfg.yaml are not collected
A quick update, the PR has now been merged, we're now awaiting SRU, which is likely next version i.e. 4.7.2 If you would like to try it out, the latest snap in latest/edge channel should have this new plugin and allow you to collect the data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059386 Title: curtin-install.log and curtin-install-cfg.yaml are not collected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2059386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
Hi Mauricio,
I recreated the deb from the original control file as well as with the
new Version option. Both debs now produced have the
/usr/share/locale/*/LC_MESSAGES/sos.mo files. So I suspect this may be
something that ma have been introduced as part of a different package.
Here is a debdiff of 2 packages that I created locally
root@bionic01:~/bionic# debdiff sosreport_4.4-1ubuntu0.18.04.2_amd64.deb
sosreport_4.4-1ubuntu0.18.04.3_amd64.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: python3-pexpect, python3-yaml, python3:any (>= [-3.3.2-2~)-] {+3.6~)+}
Version: [-4.4-1ubuntu0.18.04.2-] {+4.4-1ubuntu0.18.04.3+}
Doing `dpkg-deb --contents ` to both packages now show the locale
files
I think this is unrelated to the change I have made here in my debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
Title:
package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade:
installed sosreport package post-installation script subprocess
returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059386] Re: curtin-install.log and curtin-install-cfg.yaml are not collected
A new PR for this has been created and in progress https://github.com/sosreport/sos/pull/3674 ** Changed in: sosreport (Ubuntu) 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/2059386 Title: curtin-install.log and curtin-install-cfg.yaml are not collected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2059386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
> Why, when this is an upstream release for which Canonical is the upstream, are there local Debian patches included here? Good point, we started the SRU process after 4.7.0 was released, but the time it took us to test the PPA and then the beginning of the patch pilot the noble released a minor version was released. We can do the new release, if that is preferred, but there were still patches that needed to be added for both noble and oracular due to the fact we only started testing dev release recently, and we discovered the issues, and the corresponding fixes. So, we'll see 2 patches for oracular and 1 for noble. If that is ok, then I can re-issue a new debdiff. Alternatively, 4.7.2 is due to be released soon, which will have the relevant fixes included. On the changelog items, I was following the previous maintainers, and didn't add the extra details. But, I am more than happy to change this here moving forward. The "X-Python3-Versiom: >= 3.6" was added, as that is the version of python sos supports, and hence wanted to make that as a soft requirement. This would then change later in the year. But, if you think this is better added for the relevant series that we need to do this, like bionic, then happy to change it in that manner. We do plan to SRU for bionic, as that has caused a corner case of upgrade from xenial to bionic in the corresponding LP Thanks for the "Suggests: python3-boto3" comment, happy to remove that, if it's pointless, was not 100% sure on. On noble, we now going to add that to Depends as this package is in main. I can add that on, and the reasoning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
Hi Athos, sounds good to me; thanks for your detailed notes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
** Description changed: + [impact] + This is what I got when I tried do-release-upgrade from 16.04 to 18.04 Setting up sosreport (4.4-1ubuntu0.18.04.1) ... File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99 f"Failed to communicate with Metadata Server " ^ SyntaxError: invalid syntax dpkg: error processing package sosreport (--configure): installed sosreport package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: sosreport ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sosreport.0.crash' - Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) + Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sosreport 4.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 AptOrdering: NULL: ConfigurePending Architecture: amd64 - Date: Fri Oct 6 11:34:34 2023 + Date: Fri Oct 6 11:34:34 2023 Ec2AMI: ami-1e749f67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: m3.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed sosreport package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 - apt 1.6.17 + apt 1.6.17 SourcePackage: sosreport Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2023-10-06 (0 days ago) + + [ Test Plan ] + + The bug is not easily reproducible, and has been tested by many people within + the team. + + One process that has been a form of testing it so add the bionic repo to a + xenial machine, and try upgrading sosreport. When this is done we see the above + error. This is the only test scenario we have that are able to test. + + Then we can enabled -proposed pocket or the PPA with the change, and do the same + upgrade, and we should not face the same problem. + + [ Where problems could occur ] + + * The package may not install + * The package may not have the right dependencies + * There could be other factors in play that the above that we may not have seen entirely + + [ Other Info ] + + The proposed fix adds "X-Python3-Version: >= 3.6" to the control file, and this + is based on the upstream dependency, and that 3.6 and above are supported. This + would be reflected in all packages for consistency. As per the discussion in + this bug the upstream project is due to move to Python 3.8 later in the year for + releases greater than 4.8.0. This line would follow suite in a future SRU when + we do a release from upstream SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
Thanks for your comments, and the amendments that you have asked for. The relevant Origin + Bugs for DEP3 have all been updated on all the debdiffs. I have also updated mantic changelog, and focal to be consistent. To answer your question on the `X-Python3-Version: >= 3.6`, this is explicitly showing that this sosreport package supports 3.6 and above, and we therefore ensure it as part of the packaging process. This ensures that when upstream decide to move on from 3.6, i.e. 3.8 later in the year, we'll bump this as part of one of the SRUs. This is explained in comment 35 [1]. I hope that makes sense, and let me know if there is anything else. I am hoping we can now get this over the line [1] https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/comments/35 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "focal-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778350/+files/focal-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "jammy-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778348/+files/jammy-sosreport.debdiff ** Patch removed: "focal-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776707/+files/focal-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "mantic-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778347/+files/mantic-sosreport.debdiff ** Patch removed: "jammy-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776706/+files/jammy-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch removed: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776703/+files/noble-sosreport.debdiff ** Patch added: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778346/+files/noble-sosreport.debdiff ** Patch removed: "mantic-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776704/+files/mantic-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch removed: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5777621/+files/oracular-sosreport.debdiff ** Patch added: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778345/+files/oracular-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
Updated debdiff as suggested ** Patch removed: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776702/+files/oracular-sosreport.debdiff ** Patch added: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5777621/+files/oracular-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
The new patch that was added at the end was about the msr module loading and was also present in the CI testing we found upstream and hence added it on. In the original patch that is in noble it was == 24.04 and now it's >=24.04 this will ensure it covers any series that is noble and above, I hope that makes sense. The second patch depends on the change of the first patch based on the git history. In essence the work was combined upstream to fix the issue when I added oracular to the testing. These patches have been directly imported from upstream and no extra modification is done. If you prefer that I remove the CI bits, I can do so. When and if we ship 4.7.3 or 4.8.0 later in the year, these would be already included, including the CI bits -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "focal-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776707/+files/focal-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "jammy-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776706/+files/jammy-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "mantic-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776704/+files/mantic-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776702/+files/oracular-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776703/+files/noble-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch removed: "focal-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775312/+files/focal-sosreport.debdiff ** Patch removed: "jammy-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775311/+files/jammy-sosreport.debdiff ** Patch removed: "mantic-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775310/+files/mantic-sosreport.debdiff ** Patch removed: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775309/+files/noble-sosreport.debdiff ** Patch removed: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775308/+files/oracular-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
@athos-ribeiro @eeickmeyer I created the debdiff by comparing the 2 .dsc files, and indeed it include the file, as well it's symbolic linked file to be changed. I have re-ran the debdiff locally again this morning, and I can see the same thing. I can remove the offending section, and have been able to do a debdiff-apply; I can upload this debdiff if required. The maintainer was originally changed by Julian on version 4.5.6-0ubuntu3 when a rebuild was done, not sure why, and this is for the case for only noble and oracular; the others are still the old maintainer. We are changing the maintainer soon, but we need to change a few things internally for that and hence were going to leave it as is. The upstream project minor releases are created as a requirement for RedHat, and hence the primary maintainer that is RH does those releases. The core release cadence is 6 months, February and August. We plan to stick to that release process and potentially one intermediate. We have an internal testing criteria that can take some time to get our releases out, and hence the SRU was started a month after release, and you can see the release numbers in my PPA https://launchpad.net/~arif- ali/+archive/ubuntu/sosreport-dev. Happy to amend anything that is required and get this moving forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "jammy-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775311/+files/jammy-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775309/+files/noble-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "focal-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775312/+files/focal-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "mantic-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775310/+files/mantic-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch removed: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5773527/+files/oracular-sosreport.debdiff ** Patch removed: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5773526/+files/noble-sosreport.debdiff ** Patch removed: "focal-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757531/+files/focal-sosreport.debdiff ** Patch removed: "jammy-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757530/+files/jammy-sosreport.debdiff ** Patch removed: "mantic-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757529/+files/mantic-sosreport.debdiff ** Patch added: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775308/+files/oracular-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
Sounds good to me, I'll revert the copyright change and upload new debdiffs for all. We can tackle the copyright file in a later SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
Hi Andreas, This was discussed in the PR [1], let me see if I can answer your questions * All the files that need a copyright have the copyright at the top of the files, and hence not therefore require here. If we started to add all the copyright stuff, then this file would be considerably long * The upstream core maintainer changed a few years ago, and Bryn is still one of the old maintainers, and he didn't have any issues with the change. * I can change the debian/* back again, if that needs to change to have Adam the related copyright. One of the main reasons of up-streaming the debian folder was to improve the CI testing, especially with some of the tests we had failed as part of SRU previously. The key thing was to be consistent upstream and downstream. Happy to discuss the best course of action moving forward on this [1] https://github.com/sosreport/sos/pull/3409#discussion_r1387216668 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "oracular-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/oracular/+source/sosreport/+bug/2054395/+attachment/5773527/+files/oracular-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
new debdiff with new oracular being the version, and building on top of the 2 versions that were not there previously ** Patch removed: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/oracular/+source/sosreport/+bug/2054395/+attachment/5772881/+files/noble-sosreport.debdiff ** Patch added: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/oracular/+source/sosreport/+bug/2054395/+attachment/5773526/+files/noble-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Also affects: sosreport (Ubuntu Oracular) Importance: Medium Assignee: Arif Ali (arif-ali) Status: 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/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891296] Re: [plugin][snappy] Collect 'state.json' which may contain sensitive information (macaroons)
** Changed in: sosreport (Ubuntu Jammy)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Mantic)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Noble)
Assignee: Adam Bell (arbell) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Groovy)
Assignee: Adam Bell (arbell) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Groovy)
Assignee: Arif Ali (arif-ali) => (unassigned)
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891296
Title:
[plugin][snappy] Collect 'state.json' which may contain sensitive
information (macaroons)
To manage notifications about this bug go to:
https://bugs.launchpad.net/sosreport/+bug/1891296/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064385] Re: Merge sosreport from Debian unstable for oracular
No merge from debian is required, as we are already using a newer version in Ubuntu, and we are currently in the process of SRU to 4.7.0 in #2054395 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064385 Title: Merge sosreport from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2064385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
Updated noble debdiff with a couple of fixes for py3.12 and `msr` module load on noble ** Patch removed: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5757528/+files/noble-sosreport.debdiff ** Patch added: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5772881/+files/noble-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
** Changed in: sosreport (Ubuntu Bionic) Status: Incomplete => 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/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Changed in: sosreport (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Focal) Assignee: (unassigned) => Arif Ali (arif-ali) ** Changed in: sosreport (Ubuntu Jammy) Assignee: (unassigned) => Arif Ali (arif-ali) ** Changed in: sosreport (Ubuntu Mantic) Assignee: (unassigned) => Arif Ali (arif-ali) ** Changed in: sosreport (Ubuntu Noble) Assignee: (unassigned) => Arif Ali (arif-ali) ** Changed in: sosreport (Ubuntu Focal) Status: New => In Progress ** Changed in: sosreport (Ubuntu Jammy) Status: New => In Progress ** Changed in: sosreport (Ubuntu Mantic) Status: New => In Progress ** Changed in: sosreport (Ubuntu Noble) Status: New => In Progress ** Changed in: ubuntu-pro/18.04 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/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
@Lucas, it is ready. We were planning to resolve that bug as part of the whole SRU of 4.7.0. When n/m/j/f are done, we'll get the bionic one done too, and that will be 4.7.0 as well, I hope that makes sense. Or, would you prefer us to fix the current version there first, and then do the SRU for 4.7.0? EDIT: in-fact I already uploaded a debdiff on that LP, so that is ready for SRU for that fix too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061325] Re: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
We have a planned SRU of sosreport 4.7.0 which would have this fix already which we're still waiting for the sponsors to pick in LP:2054395, that would resolve this bug as well as updating sosreport to the new version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061325 Title: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2061325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059386] Re: curtin-install.log and curtin-install-cfg.yaml are not collected
** Changed in: sosreport (Ubuntu) Status: New => Confirmed ** Changed in: sosreport (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/2059386 Title: curtin-install.log and curtin-install-cfg.yaml are not collected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2059386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
Hi Mauricio, The version that sosreport currently supports is 3.6 and there are plans to potentially move on from 3.6 for the next major release of sosreport. My current idea and plan was, when upstream make that change we would then update the X-Python3-Version based on the upstream python compatibility. So, when 4.8.0 comes out in August, we plan to update that value to 3.8, as th upstream project is planning to move on. This will ensure that the compatibility of this future package will ensure that we have the right version of python, and we are unlikely to be SRU'ing back to bionic, but will ensure that any future upgrades, i.e. bionic to focal would work as the new package will depend on the newer python version when we get there and hence we will not see this particular issue. I hope that makes sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
> One of the requirements is the newer releases (supported & devel) are fixed.
> Can you please provide the debdiffs for them, for us to proceed?
>
> $ for release in noble mantic jammy focal bionic; do git show
> pkg/ubuntu/${release}-devel:debian/control | grep 'X-Python-Version:'; done
> $
The noble, mantic, jammy and focal builds will have the
X-Python3-version sorted in the 4.7.0 SRU which is currently in progress
in LP #2054395. Once that is done, all packages will have this there. I
hope that suffices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
Title:
package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade:
installed sosreport package post-installation script subprocess
returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2028327] Re: [sru] sos upstream 4.5.6
** Changed in: ubuntu-pro Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2028327 Title: [sru] sos upstream 4.5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2028327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941745] Re: [sru] sos upstream 4.2
bionic was never released, so marking it invalid as we had 4.4 ** Changed in: sosreport (Ubuntu Bionic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941745 Title: [sru] sos upstream 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1941745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
So, did the tests again to get more data Below is the diff between the 2 apt-term.log, which shows the ordering of installation of the packages. The main differences are dates, the version of sosreport being installed and loads of data around "Reading database" https://paste.ubuntu.com/p/8wZ5bsXcbh/ history.log was not worth looking at, as it was only 25 lines On another note, I was looking for a corner case where I could re- produce the problem. Installed a xenial machine, changed /etc/apt/sources.ist to point to bionic, and then just install sosreport. This reports the same problem as reported by OP. Now, adding my test PPA with the "X-Python3-version: >= 3.6" doesn't see this problem, and installs python3.6 from the bionic repos. So, on that basis, I think this should work as expected. Hopefully that suffices the tests, and let me know if you need anything further -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
The above debdiffs have been added, and ready for verification We are waiting for the 4.4 main patch for bionic in #2038648 to be uploaded before we crack on with the Pro update for bionic for 4.7.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "focal-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757531/+files/focal-sosreport.debdiff ** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "noble-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757528/+files/noble-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "jammy-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757530/+files/jammy-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Patch added: "mantic-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757529/+files/mantic-sosreport.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
The 4.4 minimal change debdiff attached. tested this in lab, and works as expected ** Patch added: "bionic-4_4-sosreport.debdiff" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5757522/+files/bionic-4_4-sosreport.debdiff ** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756026/+files/apt-term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
** Attachment added: "apt.log" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756025/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
Excerpts from the logs with the upgrade using the PPA apt.log 100 MarkInstall python3 [ amd64 ] < 3.5.1-3 -> 3.6.7-1~18.04 > ( python ) FU=0 101 Installing python3.6 as Depends of python3 102 MarkInstall python3.6 [ amd64 ] < none -> 3.6.9-1~18.04ubuntu1.12 > ( python ) FU=0 103 Installing python3.6-minimal as Depends of python3.6 104 MarkInstall python3.6-minimal [ amd64 ] < none -> 3.6.9-1~18.04ubuntu1.12 > ( python ) FU=0 105 Installing libpython3.6-minimal as Depends of python3.6-minimal 106 MarkInstall libpython3.6-minimal [ amd64 ] < none -> 3.6.9-1~18.04ubuntu1.12 > ( python ) FU=0 107 Installing libpython3.6-stdlib as Recommends of libpython3.6-minimal 108 MarkInstall libpython3.6-stdlib [ amd64 ] < none -> 3.6.9-1~18.04ubuntu1.12 > ( python ) FU=0 548 MarkInstall sosreport [ amd64 ] < 3.9.1-1ubuntu0.16.04.3 -> 4.7.0-0ubuntu1~18.04.7 > ( admin ) FU=0 549 Installing python3-pexpect as Depends of sosreport 550 MarkInstall python3-pexpect [ amd64 ] < none -> 4.2.1-1 > ( python ) FU=0 551 Installing python3-ptyprocess as Depends of python3-pexpect 552 MarkInstall python3-ptyprocess [ amd64 ] < none -> 0.5.2-1 > ( python ) FU=0 apt-term.log 1719 Setting up python3 (3.6.7-1~18.04) ...^M 2019 Setting up sosreport (4.7.0-0ubuntu1~18.04.7) ...^M -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
** Attachment added: "main.log" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756028/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756027/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
ack, no worries. As per our discussions yesterday, I've run 2 different dist-upgrades, and did d dpkg -l in both scenarios. One with my amended PPA [1] with X-Python3-Version: >= 3.6 and one that is default from the bionic repos, and the only difference was the package available in the PPA, as shown below --- xenial01-post-upgrade_comma.txt 2024-03-14 15:14:51.421651041 + +++ xenial02-post-upgrade_comma.txt 2024-03-14 15:14:58.693678265 + @@ -502,7 +502,7 @@ ii,shared-mime-info,1.9-2 ii,snapd,2.58+18.04.1 ii,software-properties-common,0.96.24.32.22 -ii,sosreport,4.7.0-0ubuntu1~18.04.7 +ii,sosreport,4.4-1ubuntu0.18.04.1 ii,squashfs-tools,1:4.3-6ubuntu0.18.04.4 ii,ssh-import-id,5.7-0ubuntu1.1 ii,strace,4.21-1ubuntu1 I hope that this helps and avoids any concerns on the extra package dependancies. [1] https://launchpad.net/~arif-ali/+archive/ubuntu/sosreport-dev -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1
As we have not been able to reproduce the problem, but still conscious of the issue. We have implemented an update with the debian control file for the next SRU where we depend on python 3.6. By default, based on testing the dependency was for python 3.3, and as xenial already had this, we could have gone into a situation where the python3 was then not upgraded for sosreport to be functional. Ref: https://github.com/sosreport/sos/pull/3567 ** Changed in: sosreport (Ubuntu Bionic) Status: Triaged => Fix Committed ** Changed in: sosreport (Ubuntu Bionic) Assignee: (unassigned) => Arif Ali (arif-ali) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038648 Title: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947351] Re: chown not in rootwrap when only installing cinder-backup
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947351 Title: chown not in rootwrap when only installing cinder-backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1947351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947351] [NEW] chown not in rootwrap when only installing cinder-backup
Public bug reported: series: bionic openstack: queens We have an issue with a user, where the cinder-backup and services are installed, and separated from cinder-volume nodes. As part of the cinder-backup, it is required to grab iscsi devices, and hence the likes of /dev/sd* would be there to be consumed. As part of this process we can see that cinder-rootwrap is being run, similar to the command below sudo cinder-rootwrap /etc/cinder/rootwrap.conf chown 64061 /dev/sda By default, this then gives permission denied, and does not move forward We then added the excerpt below following into a new file in /etc/cinder/rootwrap.d/backup.filters, borrowed from /etc/cinder/rootwrap.d/volume.filters (which is typically from cinder- volume package in bionic) [Filters] chown: CommandFilter, chown, root This then moved things along for the user. After further analysis, we found that post bionic, i.e. cosmic and beyond, the volume.filters file is now located in cinder-common package rather than the cinder-volume My request is, can we do the same for queens, such that this file is in cinder-common? ** Affects: cinder (Ubuntu) Importance: Undecided Status: New ** Affects: cinder (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cinder (Ubuntu Bionic) 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/1947351 Title: chown not in rootwrap when only installing cinder-backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1947351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923209] Re: [sos4.1][Policy|Ubuntu] Upload no longer working
[VERIFICATION HIRSUTE] I ran the following command: # sos report -o ubuntu --upload # The important bit here is the --upload option, the rest is just to generate the sos archive. The above command line output: " Attempting upload to Canonical Support File Server Uploaded archive successfully " I also confirmed that the sos archive was present on the Canonical sftp under the right location as it should and as it was before this regression occurs. - Arif ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923209 Title: [sos4.1][Policy|Ubuntu] Upload no longer working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1923209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917894] Re: [FFe][sync][sru] sos upstream 4.1
Tested on bionic, focal, groovy and hirsute, specifically the --clean and --mask options Ran these commands, and all came out sos report --mask --all-logs -a --batch sos report --clean --all-logs -a --batch sosreport --mask --all-logs -a --batch sosreport --mask --all-logs -a --batch sos report --all-logs -a --batch sos clean sosreport-as1-maas-node-01-2021-04-08-xqdpdbp.tar.xz --batch The only thing that sosreport doesn't obfuscate are the journal files, but I think that is expected as these are binary files. I have opened a separate issue on this in the upstream project [1], but I think this was expected [1] https://github.com/sosreport/sos/issues/2478 ** Bug watch added: github.com/sosreport/sos/issues #2478 https://github.com/sosreport/sos/issues/2478 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917894 Title: [FFe][sync][sru] sos upstream 4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1917894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902574] Re: There is no salt package in focal
So based on that debian bug, that was resolved, so I would think that we should be able to move forward, as that comment on the publishing history was dated "2019-11-05 00:10:09 GMT" for version 2018.3. There's no explanation why it was blocked later with version 3000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902574 Title: There is no salt package in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1902574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902574] [NEW] There is no salt package in focal
Public bug reported: noticed that focal did not ship salt in focal, based on the rmadison output below $ rmadison salt-minion salt-minion | 0.17.5+ds-1 | trusty/universe | all salt-minion | 2015.8.8+ds-1 | xenial/universe | all salt-minion | 2015.8.8+ds-1ubuntu0.1| xenial-security/universe | all salt-minion | 2015.8.8+ds-1ubuntu0.1| xenial-updates/universe | all salt-minion | 2017.7.4+dfsg1-1 | bionic/universe | all salt-minion | 2017.7.4+dfsg1-1ubuntu18.04.2 | bionic-security/universe | all salt-minion | 2017.7.4+dfsg1-1ubuntu18.04.2 | bionic-updates/universe | all salt-minion | 3001+dfsg1-2 | groovy/universe | all salt-minion | 3001+dfsg1-2 | hirsute/universe | all salt-minion | 3002+dfsg1-1 | hirsute-proposed/universe | all As I am doing stuff on focal at the moment, I would really appreciate for salt to be integrated back into focal so that we can still use it in focal. Based on a comment from salt slack channel, possibly the reason for not including it originally, may have been because salt didn't support python3.8. But this was resolved in June with salt 3001 in June. ** Affects: salt (Ubuntu) Importance: Undecided Status: New ** Affects: salt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: salt (Ubuntu Focal) 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/1902574 Title: There is no salt package in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1902574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
Initial Test * sos report Ran through the simple.sh as per the document. Had to change all the /var/tmp to /tmp, and then all went through without a problem sos report passed, and didn't have any problems same test using sosreport instead, as that is what customers would be used to Ran all my commands with "-a --batch --case-id=0123456" * sos clean tested sos report with --mask option after extracting, I still have one file, which still shows the hostname sosreport-host0-0123456-2020-09-10-qbfomdn/sos_commands/lvm2/lvmdump_- d_.tmp.sos.csjtzsye.sosreport-focal- test-0123456-2020-09-10-qbfomdn.sos_commands.lvm2.lvmdump:Creating dump directory: /tmp/sos.csjtzsye/sosreport-focal- test-0123456-2020-09-10-qbfomdn/sos_commands/lvm2/lvmdump same issue if you use sos clean on top of the sosreport tarball -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
A suggestion on bringing sos 4.0 to bionic Leave the original sosreport as it is, so that it doesn't break anything for any users Introduce a new package called sosreport4 which packages sos 4.0. This would will then give the opportunity to use the new version of sos so that newer data can be collected as well as being able to support the likes of "sos clean" and "sos collect" Similar how the packaging of python is done, we have python and python3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772556] Re: d-i netinstall fails due to missing apt-transport-https package
Verified the netinstall images i.e. initrd.gz and vmlinuz from https://people.canonical.com/~mruffell/sf289200/ work for me, and I am now able to deploy instance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772556 Title: d-i netinstall fails due to missing apt-transport-https package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1772556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1149269] Re: Dell Precision T1650 - FWTS reports critical errors during Suspend/Resume testing
Hi There, I am getting Dell-Precision-T1650. I want to know if I can go for Xubuntu 12.04 or 13.10. Would I face similar issue. -Arif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1149269 Title: Dell Precision T1650 - FWTS reports critical errors during Suspend/Resume testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1149269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1149269] Re: Dell Precision T1650 - FWTS reports critical errors during Suspend/Resume testing
1) Is there anything i can help you folks with? 2) Let me know the exact use case/workflow and I will test it out and give your details. As i understand issue is only in suspend and resume, it wont cause troble for me as i wont use these features, if there is an issue. As long as shutdown/restart/dual boot works fine , I will be OK. I will install Win 7 64 bit and Xubuntu 12.04 64 bit, i hope dual boot wont have any issue here. 3) Would i need to install this firmware update , but its said for Ubuntu 11.x http://www.dell.com/support/drivers/us/en/04/Product/precision-t1650 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1149269 Title: Dell Precision T1650 - FWTS reports critical errors during Suspend/Resume testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1149269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175072] [NEW] xubuntu software center would become unresponsive
Public bug reported: hi when i am installing softwares using xubuntu software center in 13.04 , it becomes unresponsive. i blieve in xubuntu 12.10 and 1204 it was n't like this , while installatin ois going i could still navigate and search other softwares and add them to installatino queue. But now its not possible , once one all softwares in queue are installed only then it would become responsive you can search new software... painful. CPU usage of software center are 50%-90% all this while ... all other applications are responsive at this time, its only software center who is unresponsive. please make it multi threaded if its already not. reduce the priorityy of installation thread and keeop the main UI thread's priority high, where your can browse for other softwares. I would suggest the best would be that you give an option to add software to basket/cart( isntallatino queue) and how his basket/cart i top right. give an option to start installation manually or when user exits software center, throw a dialog and ask user to install everything he selected. Let user browse and select al lthe softwares that he want to install/uninstall in one go... and later he can execute his changes. as we do in gparted, you do all your partition related operations and then either you say manually that apply all changes or when you exist gparted it would ask you , do you want to apply these changes. please see the attached screenshot. software center is so unresponsive that its not even able to paint itself... sad ** Affects: software-center (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/1175072 Title: xubuntu software center would become unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1175072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175072] Re: xubuntu software center would become unresponsive
** Attachment added: screenshot of software center when unresponsive https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1175072/+attachment/3661195/+files/so9ftware%20center.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175072 Title: xubuntu software center would become unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1175072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175072] Re: xubuntu software center would become unresponsive
hi some more infomation I have 1 GB RAM , Pentium 4 processor with Hyper threading, INtel 915 motherboard. memoty usage of software c enter are as follow VM : 1523 MB , RSS : 680 MB I also see that 80% of computer's entire memory is under use and 35% of swap area is also under use. so that clearly answers that its because of less ram, but still think about my idea of browsing and adding things to basket and executing all queue later, so that user can browse. I loose the context where i was after 45 minutes when it becomes responsive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175072 Title: xubuntu software center would become unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1175072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175072] Re: xubuntu software center would become unresponsive
Now after 20-30 minutes. software cetner - VM 1860 MB , RSS : 650 MB , CPU usage 5-40 % (mostly 5%) , still unresponsive system - Total RAm 1GB, 85% RAM used, total swap space 2 GB, 58% swap space is used. so clearly RAM is bottleneck. I had similar issue while upgrading from xubuntu 12.10 to xubuntu 13.04... it got hung in configuring previously installed packges i had to leave for 10 hours to complete the installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175072 Title: xubuntu software center would become unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1175072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174538] Re: upgrade from 12.10 to 13.04 is hung
ubiquity folder doesn;t exists in my /var/log let me know hwo else i can help you ? another note. i left my cpmuter as it is after waitinf for 4 hours ( 4 hours in restoring previously installed packages ) and slept next day morning i saw it was done. most people on IRC said that it was because of your 1GB RAM, you need to have more RAM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174538 Title: upgrade from 12.10 to 13.04 is hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/1174538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175234] [NEW] submenu of system-menu is not painted correctly
Public bug reported: Please find the screenshot, its happening even after reboot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xfce4-panel 4.10.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Wed May 1 21:41:05 2013 InstallationDate: Installed on 2013-04-30 (0 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130423.1) MarkForUpload: True SourcePackage: xfce4-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: IMAG1719.jpg https://bugs.launchpad.net/bugs/1175234/+attachment/3661578/+files/IMAG1719.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175234 Title: submenu of system-menu is not painted correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1175234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174538] Re: upgrade from 12.10 to 13.04 is hung
** Package changed: ubuntu = apt-clone (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174538 Title: upgrade from 12.10 to 13.04 is hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/1174538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174538] [NEW] upgrade from 12.10 to 13.04 is hung
Public bug reported: I already had xubuntu 12.10 running fine. I decided to upgrade to 13.04 through installation DVD . all stages got over in less than 30 minutes but at the end it got stuck at restoring already installed packages I kept on waiting for more than 3 hours and now also i have left on god , may be after 8 hours when i wake up it will done. I have Pentium 4 processor with 1 GB RAM. I am attaching , screen shots and videos of what was going on. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: IMAG1718.jpg https://bugs.launchpad.net/bugs/1174538/+attachment/3659466/+files/IMAG1718.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174538 Title: upgrade from 12.10 to 13.04 is hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174538] Re: upgrade from 12.10 to 13.04 is hung
I havee also captured HD video of two minutes to show what was going on during installation. I ran 'top' command on the shell as suggested by #xubuntu channel people on IRC. I recorded the video of 'top' output in this. In this video , i am also demonstrating the painting/display issue in ubiquity slide show... when i expand the deails button. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174538 Title: upgrade from 12.10 to 13.04 is hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174538] Re: upgrade from 12.10 to 13.04 is hung
In my 12.10 Xbunutu I had following sofwares installed on top of default installation GCompri ChailPlay Pre-School bundle Primay bundle typing tux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174538 Title: upgrade from 12.10 to 13.04 is hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174538] Re: upgrade from 12.10 to 13.04 is hung
After two hours from now if you check my following Google drive share .. there should be a video ( its uploading righ now ) http://goo.gl/3UH4w -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174538 Title: upgrade from 12.10 to 13.04 is hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174538] Re: upgrade from 12.10 to 13.04 is hung
video is now available in my google drive share. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174538 Title: upgrade from 12.10 to 13.04 is hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588822] Re: r8192se_pci driver occasionally drops connection, refuses to work with some networks
Yeah, I have used rc2 to rc4, and all have given me stable connection using the rtl8192se driver, I am using the natty build with the oneiric kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588822 Title: r8192se_pci driver occasionally drops connection, refuses to work with some networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588822] Re: r8192se_pci driver occasionally drops connection, refuses to work with some networks
The kernel below for me works http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2011-06-02-oneiric/ i.e. 3.0.0-999-generic The driver being used here is rtl8192se, and the stability issues I had are now gone, will test for a few more days and see how it goes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588822 Title: r8192se_pci driver occasionally drops connection, refuses to work with some networks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588822] Re: r8192se_pci driver occasionally drops connection, refuses to work with some networks
I am having the same problem, using the latest drivers from realtek rtl8192se_linux_2.6.0019.1207.2010 My machine is a Thinkpad Edge 15 OS: Ubuntu 11.04 x86_64 Kernel: 2.6.38-8-generic *-network description: Wireless interface product: RTL8191SEvB Wireless LAN Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: wlan0 version: 10 serial: 5c:ac:4c:bc:27:1e width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtl819xSE driverversion=0019.1207.2010 firmware=63 ip=192.168.0.59 latency=0 multicast=yes wireless=802.11bg resources: irq:18 ioport:d000(size=256) memory:d050-d0503fff I will try the latest mainline kernel from ppa, and see if I see the same problems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588822 Title: r8192se_pci driver occasionally drops connection, refuses to work with some networks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588822] Re: r8192se_pci driver occasionally drops connection, refuses to work with some networks
OK, tried the mainline kernel, and no luck at all Tried the following * 2.6.38.7-natty * 2.6.39-rc4-natty neither of these have the r8192se_pci I tried the other drivers such as the rtlwifi and others that were there, but I got no wifi at all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588822 Title: r8192se_pci driver occasionally drops connection, refuses to work with some networks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
