[Bug 1543367] Re: nested unprileged container fails to start at mounting /proc
Sorry, I had forgotten my own workaround for this. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1543367 Title: nested unprileged container fails to start at mounting /proc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543367/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1531870] Re: package python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Changed in: samba (Ubuntu) Assignee: (unassigned) => Rwom Samson (rwomcorp) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1531870 Title: package python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1531870/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1531870] Re: package python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1531870 Title: package python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1531870/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1553757] Re: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory
Hi Paul Sorry for not being clear enough. The actual issue/concern I have is: stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory So, I've only been able to reproduce in my system so far, but I have not being able to reproduce it in any cleanly installed system with the latest version of dbconfig-common in Xenial. (2.0.3). At first I thought this was just my system being broken, but I now have not only been the one coming across this issue. See https://bugs.launchpad.net/maas/+bug/1553648. That being said, I must say that I've been using Xenial since very early, and I just started seen this recently, probably the last couple weeks. Obviously, I've been upgrading pretty much daily, but it would match the latest sync from Debian. Now, the way I'm reproducing this issue right now is an install. I have remove/purged all the packages, include dbconfig common packages and made sure that /etc/dbconfig-common doesn't exist : roaksoax@unleashed:~/Desktop/project/packaging-1.10⟫ dpkg -l | grep dbconfig 1 roaksoax@unleashed:~/Desktop/project/packaging-1.10⟫ sudo apt-get install maas Reading package lists... Done [...] The following additional packages will be installed: dbconfig-common dbconfig-pgsql isc-dhcp-server libecap2v5 maas-cli maas-common maas-dhcp maas-dns maas-proxy maas-rack-controller [...] Do you want to continue? [Y/n] y The installation resumes, and It asks me the question to: http://pastebin.ubuntu.com/15319155/ .Right after answering the questions (no matter if I say install the package maintainer's version or keep the local version currently installed) , it is always the same result: Setting up maas-region-controller (2.0.0~alpha1+bzr4736-0ubuntu1~xenial2) ... dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory creating postgres user maas: success. verifying creation of user: success. [] roaksoax@unleashed:~/Desktop/project/packaging-1.10⟫ ls -l /etc/dbconfig-common/ total 4 -rw--- 1 root root 484 Mar 6 23:52 config As you can see, the file doesn't get created. Now, what I'm really wondering if is there is only an issue in systems where dbconfig-common was first upgraded to the latest version (2.0.3), and not on a freshly installed system where dbconfig-common is latest, as I've not been able to reproduce this on a freshly installed system yet. PS: Now, to answer your last question, the question raised by UCF was never there because we preseed the following: set_question maas-region-controller/dbconfig-install true Or maybe, the preseeding doesn't really matter and we just have never gotten into a similar situation, hence it never really has been shown before. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1551311] Re: [MIR] python-sphinx-argparse
Override component to main sphinx-argparse 0.1.15-1 in xenial: universe/misc -> main python-sphinx-argparse 0.1.15-1 in xenial amd64: universe/python/optional/100% -> main python-sphinx-argparse 0.1.15-1 in xenial arm64: universe/python/optional/100% -> main python-sphinx-argparse 0.1.15-1 in xenial armhf: universe/python/optional/100% -> main python-sphinx-argparse 0.1.15-1 in xenial i386: universe/python/optional/100% -> main python-sphinx-argparse 0.1.15-1 in xenial powerpc: universe/python/optional/100% -> main python-sphinx-argparse 0.1.15-1 in xenial ppc64el: universe/python/optional/100% -> main python-sphinx-argparse 0.1.15-1 in xenial s390x: universe/python/optional/100% -> main python3-sphinx-argparse 0.1.15-1 in xenial amd64: universe/python/optional/100% -> main python3-sphinx-argparse 0.1.15-1 in xenial arm64: universe/python/optional/100% -> main python3-sphinx-argparse 0.1.15-1 in xenial armhf: universe/python/optional/100% -> main python3-sphinx-argparse 0.1.15-1 in xenial i386: universe/python/optional/100% -> main python3-sphinx-argparse 0.1.15-1 in xenial powerpc: universe/python/optional/100% -> main python3-sphinx-argparse 0.1.15-1 in xenial ppc64el: universe/python/optional/100% -> main python3-sphinx-argparse 0.1.15-1 in xenial s390x: universe/python/optional/100% -> main 15 publications overridden. ** Changed in: sphinx-argparse (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sphinx-argparse in Ubuntu. https://bugs.launchpad.net/bugs/1551311 Title: [MIR] python-sphinx-argparse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sphinx-argparse/+bug/1551311/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1552384] Re: [MIR] python-positional
Override component to main python-positional 1.0.1-2 in xenial: universe/misc -> main python-positional 1.0.1-2 in xenial amd64: universe/python/optional/100% -> main python-positional 1.0.1-2 in xenial arm64: universe/python/optional/100% -> main python-positional 1.0.1-2 in xenial armhf: universe/python/optional/100% -> main python-positional 1.0.1-2 in xenial i386: universe/python/optional/100% -> main python-positional 1.0.1-2 in xenial powerpc: universe/python/optional/100% -> main python-positional 1.0.1-2 in xenial ppc64el: universe/python/optional/100% -> main python-positional 1.0.1-2 in xenial s390x: universe/python/optional/100% -> main python-positional-doc 1.0.1-2 in xenial amd64: universe/doc/optional/100% -> main python-positional-doc 1.0.1-2 in xenial arm64: universe/doc/optional/100% -> main python-positional-doc 1.0.1-2 in xenial armhf: universe/doc/optional/100% -> main python-positional-doc 1.0.1-2 in xenial i386: universe/doc/optional/100% -> main python-positional-doc 1.0.1-2 in xenial powerpc: universe/doc/optional/100% -> main python-positional-doc 1.0.1-2 in xenial ppc64el: universe/doc/optional/100% -> main python-positional-doc 1.0.1-2 in xenial s390x: universe/doc/optional/100% -> main python3-positional 1.0.1-2 in xenial amd64: universe/python/optional/100% -> main python3-positional 1.0.1-2 in xenial arm64: universe/python/optional/100% -> main python3-positional 1.0.1-2 in xenial armhf: universe/python/optional/100% -> main python3-positional 1.0.1-2 in xenial i386: universe/python/optional/100% -> main python3-positional 1.0.1-2 in xenial powerpc: universe/python/optional/100% -> main python3-positional 1.0.1-2 in xenial ppc64el: universe/python/optional/100% -> main python3-positional 1.0.1-2 in xenial s390x: universe/python/optional/100% -> main 22 publications overridden. ** Changed in: python-positional (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-positional in Ubuntu. https://bugs.launchpad.net/bugs/1552384 Title: [MIR] python-positional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-positional/+bug/1552384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1379065] Re: Ubuntu 14.04.1: irqbalance not working
** Changed in: irqbalance (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1379065 Title: Ubuntu 14.04.1: irqbalance not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1379065/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1483572] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2016-03-06 21:05 EDT--- (In reply to comment #6) > I haven't tried to compile 2.3.2 on s390x, but can do as a data > point. Hi, Did you have the opportunity to try the above? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1483572 Title: 2.4.0: unit test failures on powerpc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1483572/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527882] Re: package pax 1:20120606-2+deb7u1 failed to install/upgrade: package pax is not ready for configuration cannot configure (current status `half-installed')
** Changed in: pax (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pax in Ubuntu. https://bugs.launchpad.net/bugs/1527882 Title: package pax 1:20120606-2+deb7u1 failed to install/upgrade: package pax is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pax/+bug/1527882/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports
Well, I reported the issue because the sarg monthly report was never made in a pristine installation. In the research I found that the access.log file was truncated in a period of time (daily) which is not appropriate for a monthly report, nor even weekly reports. Even though sarg scripts are correctly installed and execute, the problem isn't in them a.f.a I can see, but in the amount of information available in the access.log file. If it is truncated daily, it is not possible for sarg to have enough information to make a monthly report. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1414754 Title: /etc/logrotate.d/squid3 fails to execute sarg-reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1414754/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1401190] Re: curtin makes assumptions about partition names on all devices
ls -la /dev/nvme0* crw--- 1 root root 10, 57 Mar 6 21:10 /dev/nvme0 brw-rw 1 root disk 259, 0 Mar 6 21:44 /dev/nvme0n1 brw-rw 1 root disk 259, 1 Mar 6 21:44 /dev/nvme0n1p1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1401190 Title: curtin makes assumptions about partition names on all devices To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1401190] Re: curtin makes assumptions about partition names on all devices
Hi, thanks for the reply.
Specifying the path doesn't appear to help. I have tried the following:
* Commissioned a new server
* Set disk config in web ui:
Used disks and partitions
Name Model Serial BootDevice typeUsed for
nvme0n1PhysicalGPT partitioned with 1 partition
nvme0n1-part1Partitionext4 formatted filesystem mounted at /
** Without these settings I am unable to deploy due to no disk
configuration. **
* Edited /etc/maas/preseeds/curtin_userdata (After early but before late
commands)
partitioning_commands:
builtin: [curtin, block-meta, custom]
storage:
config:
- {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type:
disk, wipe: superblock}
- {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 1, offset:
4194304B, size: 128026935296B, type: partition, uuid:
e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
- {fstype: ext4, id: nvme0n1p1_format, label: '', type: format, path:
/dev/nvme0n1p1, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877, volume: nvme0n1p1}
version: 1
** Deployment fails **
If I connect to the failed server I can manually run the commands to try
and see what happened.
* ssh node
* /var/lib/cloud/instance/scripts/part-001
* cd curtin
* cat configs/config-002.cfg
partitioning_commands:
builtin: [curtin, block-meta, custom]
storage:
config:
- {grub_device: true, id: sda, model: ST2000DM001-1CH1, name: sda, ptable:
msdos,
serial: Z3409QB2, type: disk, wipe: superblock}
- {id: sdb, model: ST2000DM001-1CH1, name: sdb, serial: Z3409S81, type: disk,
wipe: superblock}
- {id: sdc, model: Samsung SSD 840, name: sdc, serial: S1D9NSAFB19195M, type:
disk,
wipe: superblock}
- {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type: disk,
wipe: superblock}
- {device: nvme0n1, id: nvme0n1-part1, name: nvme0n1-part1, number: 1,
offset: 4194304B,
size: 128026935296B, type: partition, uuid:
e66f2d9d-963a-4cb9-b2b5-472d491e768b,
wipe: superblock}
- {fstype: ext4, id: nvme0n1-part1_format, label: '', type: format, uuid:
6a47f95c-40b6-478a-aefa-ca84a509d877,
volume: nvme0n1-part1}
- {device: nvme0n1-part1_format, id: nvme0n1-part1_mount, path: /, type:
mount}
version: 1
** The above config appears to have ignored my curtin_userdata settings
entirely. **
* cat << EOF > configs/config-002.cfg
> partitioning_commands:
> builtin: [curtin, block-meta, custom]
> storage:
> config:
> - {id: nvme0n1, name: nvme0n1, path: /dev/nvme0n1, ptable: gpt, type: disk,
> wipe: superblock}
> - {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 1, offset:
> 4194304B, size: 128026935296B, type: partition, wipe: superblock}
> - {fstype: ext4, id: nvme0n1p1_format, label: '', type: format, path:
> /dev/nvme0n1p1, volume: nvme0n1p1}
> version: 1
> EOF
* bin/curtin --showtrace --install-deps install --config=configs/config-002.cfg
http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
Creating new GPT entries.
The operation has completed successfully.
The operation has completed successfully.
An error occured handling 'nvme0n1p1_format': ValueError - '/dev/nvme0n11': no
such file or directory
Traceback (most recent call last):
File "/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main
ret = args.func(args)
File "curtin/commands/block_meta.py", line 62, in block_meta
meta_custom(args)
File "curtin/commands/block_meta.py", line 1083, in meta_custom
handler(command, storage_config_dict)
File "curtin/commands/block_meta.py", line 672, in format_handler
mkfs.mkfs_from_config(volume_path, info)
File "curtin/block/mkfs.py", line 207, in mkfs_from_config
label=info.get('label'))
File "curtin/block/mkfs.py", line 145, in mkfs
raise ValueError("'%s': no such file or directory" % path)
ValueError: '/dev/nvme0n11': no such file or directory
'/dev/nvme0n11': no such file or directory
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed
successfully.\nThe operation has completed successfully.\nAn error occured
handling \'nvme0n1p1_format\': ValueError - \'/dev/nvme0n11\': no such file or
directory\nTraceback (most recent call last):\n File
"/home/ubuntu/curtin/curtin/commands/main.py", line 209, in main\nret =
args.func(args)\n File "curtin/commands/block_meta.py", line 62, in
block_meta\nmeta_custom(args)\n File "curtin/commands/block_meta.py", line
1083, in meta_custom\nhandler(command, storage_config_dict)\n File
"curtin/commands/block_meta.py", line 672, in format_handler\n
mkfs.mkfs_from_config(volume_path, info)\n File "curtin/block/mkfs.py", line
207, in mkfs_from_config\nlabel=info.get(\'label\'))\n File
"curtin/block/mkfs.py", line 145, in mkfs\nraise ValueError("\'%s\': no
such file or
[Bug 1551558] Re: vmhgfs-fuse to open-vm-tools package
** Changed in: open-vm-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1551558 Title: vmhgfs-fuse to open-vm-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1551558/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1522936] Re: package libapache2-mod-php5 5.6.11+dfsg-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: php5 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1522936 Title: package libapache2-mod-php5 5.6.11+dfsg-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1522936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513531] Re: Error while installing
** Changed in: open-vm-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1513531 Title: Error while installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1513531/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1553757] [NEW] dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or direct
Hi Andres, On 06-03-16 17:42, Andres Rodriguez wrote: > In MAAS, we make use of dbconfig common. We have been using it exactly > the same way for awhile now and we have just starting seeing the > following on install or upgrade: > > dbconfig-common: writing config to > /etc/dbconfig-common/maas-region-controller.conf dbconfig-common has always done that. So nothing new. > stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory Any idea why this happens? What is special about your setup? How did you configure dbconfig-common? Is the /etc/dbconfig-common directory missing, or is the maas-region-controller.conf file missing? Is this on BOTH install and upgrade or only during install or only during upgrade? > Also, before this it always asks whether to use the local version of the > file or install a new one in case of an upgrade. I am not 100% sure if I understand what you mean. The behavior that you describe seems to be the question raised by ucf. Are you now saying that that is not happening anymore? That would indeed be a serious bug, but nothing on that front has changed. The only thing that I can think of on this front is that I removed the date of installation, such that ucf will not ask the question if the content of the file has not changed. Can you confirm that this is what you mean? Furthermore, there is important information missing: about which version of dbconfig-common are you talking? With which version did you experience the alleged change? Paul -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1553777] Re: named crashed with SIGABRT in isc_assertion_failed()
*** This bug is a duplicate of bug 1552801 *** https://bugs.launchpad.net/bugs/1552801 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1552801, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1553777/+attachment/4590756/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1553777/+attachment/4590758/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1553777/+attachment/4590761/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1553777/+attachment/4590762/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1553777/+attachment/4590763/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1553777/+attachment/4590764/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1553777/+attachment/4590766/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1552801 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1553777 Title: named crashed with SIGABRT in isc_assertion_failed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1553777/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1553757] [NEW] dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory
Public bug reported: In MAAS, we make use of dbconfig common. We have been using it exactly the same way for awhile now and we have just starting seeing the following on install or upgrade: dbconfig-common: writing config to /etc/dbconfig-common/maas-region-controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region-controller.conf': No such file or directory Also, before this it always asks whether to use the local version of the file or install a new one in case of an upgrade. ** Affects: dbconfig-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/1553757 Title: dbconfig-common: writing config to /etc/dbconfig-common/maas-region- controller.conf stat: cannot stat '/etc/dbconfig-common/maas-region- controller.conf': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1553757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports
** Also affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1414754 Title: /etc/logrotate.d/squid3 fails to execute sarg-reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1414754/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1401190] Re: curtin makes assumptions about partition names on all devices
On Sat, Mar 5, 2016 at 3:56 AM, Rob Sanderson <1401...@bugs.launchpad.net> wrote: > Hi, > > I'm still seeing this issue on Xenial. > > root@maas1:~# cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=16.04 > DISTRIB_CODENAME=xenial > DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)" > root@maas1:~# uname -a > Linux maas1 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016 > x86_64 x86_64 x86_64 GNU/Linux > root@maas1:~# dpkg -l|grep curtin > ii curtin-common 0.1.0~bzr359-0ubuntu1 all > Library and tools for curtin installer > ii python3-curtin 0.1.0~bzr359-0ubuntu1 all > Library and tools for curtin installer > > I have tried with the default curtin_userdata and have also tried: > > partitioning_commands: > builtin: curtin block-meta custom > > storage: > version: 1 > config: > - id: nvme0n1 > type: disk > ptable: msdos > If you don't specify a 'serial': or 'path' then curtin will attempt to deduce the path via the id. Can you try adding: path: /dev/nvme0 If that is indeed the path to the device. > - id: nvme0n1p1 > type: partition > number: 1 > size: 128GB > device: nvme0n1 > flag: boot > - id: nvme0n1p1_root > type: format > fstype: ext4 > volume: nvme0n1p1 > - id: nvme0n1p1_mount > type: mount > path: / > device: nvme0n1p1_root > > The error is as follows: > > + exec curtin --install-deps install --config=configs/config-000.cfg > --config=configs/config-001.cfg --config=configs/config-002.cfg > --config=configs/config-003.cfg --config=configs/config-004.cfg > http://10.10.4.221:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz > Error: /dev/sda: unrecognised disk label > Error: /dev/sda: unrecognised disk label > Error: /dev/sdb: unrecognised disk label > Error: /dev/sdb: unrecognised disk label > Error: /dev/sdc: unrecognised disk label > Error: /dev/sdc: unrecognised disk label > An error occured handling 'nvme0n1-part1_format': ValueError - > '/dev/nvme0n11': no such file or directory > '/dev/nvme0n11': no such file or directory > Installation failed with exception: Unexpected error while running command. > Command: ['curtin', 'block-meta', 'custom'] > Exit code: 3 > Reason: - > Stdout: "Error: /dev/sda: unrecognised disk label\nError: /dev/sda: > unrecognised disk label\nError: /dev/sdb: unrecognised disk label\nError: > /dev/sdb: unrecognised disk label\nError: /dev/sdc: unrecognised disk > label\nError: /dev/sdc: unrecognised disk label\nAn error occured handling > 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or > directory\n'/dev/nvme0n11': no such file or directory\n" > Stderr: '' > Unexpected error while running command. > Command: ['curtin', 'block-meta', 'custom'] > Exit code: 3 > Reason: - > Stdout: "Error: /dev/sda: unrecognised disk label\nError: /dev/sda: > unrecognised disk label\nError: /dev/sdb: unrecognised disk label\nError: > /dev/sdb: unrecognised disk label\nError: /dev/sdc: unrecognised disk > label\nError: /dev/sdc: unrecognised disk label\nAn error occured handling > 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or > directory\n'/dev/nvme0n11': no such file or directory\n" > Stderr: '' > > -- > You received this bug notification because you are subscribed to curtin > in Ubuntu. > Matching subscriptions: curtin-bugs, curtin-bugs-all > https://bugs.launchpad.net/bugs/1401190 > > Title: > curtin makes assumptions about partition names on all devices > > To manage notifications about this bug go to: > https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1401190 Title: curtin makes assumptions about partition names on all devices To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 130682] Re: pasv_min_port, pasv_max_port does not work if client uses PASV
Hi, I found a corner case, where it might not work even if you set them: pasv_min_port=1 pasv_max_port=9000 (Notice that min an max was mixed up) In this case the server does start (not yielding a config error) but the configuration is ignored. This is clearly a bug. I could accept both a) work: "I know what you mean" or b) config error: "please be more precise" Cheers, Tamas -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/130682 Title: pasv_min_port,pasv_max_port does not work if client uses PASV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/130682/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1552295] Re: Postfix 3 supports SMTPUTF8 but not enabled
** Also affects: postfix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1552295 Title: Postfix 3 supports SMTPUTF8 but not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/postfix/+bug/1552295/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
