[Bug 1924588] Re: P2P mode doesn't work in qla2xxx
The bug with P2P is now fixed in stable v5.4.114. Please update GA kernel of 20.04 to v5.4.114 at your earliest convenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924588 Title: P2P mode doesn't work in qla2xxx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924588] Re: P2P mode doesn't work in qla2xxx
** Description changed: + Link to a patch series to the stable: + https://www.spinics.net/lists/stable/msg458515.html + QLogic FC adapters don't work in direct mode on focal (at least QLE2692, and QLE2694, QLE2742 are affected): [ 266.821659] qla2xxx [:05:00.0]-3874:3: ELS_DCMD PLOGI sent, hdl=1a, loopid=0, to port_id 02 from port_id 01 [ 266.822926] qla2xxx [:05:00.0]-583f:3: ELS IOCB Done -Driver ELS logo error hdl=1a comp_status=0x0 error subcode 1=0x0 error subcode 2=0x0 total_byte=0x74 [ 266.822933] qla2xxx [:05:00.0]-3872:3: ELS_DCMD ELS done rc 0 hdl=1a, portid=02 21:00:34:80:0d:74:14:d2 [ 266.822937] qla2xxx [:05:00.0]-2918:3: qla_handle_els_plogi_done 1764 21:00:34:80:0d:74:14:d2 post PRLI [ 266.822965] qla2xxx [:05:00.0]-291b:3: Async-prli - 21:00:34:80:0d:74:14:d2 hdl=0, loopid=0 portid=02 retries=29 nvme. [ 266.823008] qla2xxx [:05:00.0]-5837:3: Async-prli failed - 21:00:34:80:0d:74:14:d2 hdl=1b portid=02 comp=31 iop0=18 iop1=b. [ 266.823011] qla2xxx [:05:00.0]-2929:3: qla2x00_async_prli_sp_done 21:00:34:80:0d:74:14:d2 res 0 [ 266.823014] qla2xxx [:05:00.0]-2918:3: qla24xx_handle_prli_done_event 1934 21:00:34:80:0d:74:14:d2 post NVMe prli [ 266.823019] qla2xxx [:05:00.0]-e801:3: Scheduling sess a438982b for deletion 21:00:34:80:0d:74:14:d2 [ 266.823031] qla2xxx [:05:00.0]-290a:3: qlt_unreg_sess sess a438982b for deletion 21:00:34:80:0d:74:14:d2 [ 266.823039] qla2xxx [:05:00.0]-f884:3: qlt_free_session_done: se_sess / sess a438982b from port 21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 logout 1 keep 0 els_logo 0 [ 266.823043] qla2xxx [:05:00.0]-f886:3: qlt_free_session_done: waiting for sess a438982b logout [ 266.823066] qla2xxx [:05:00.0]-2870:3: Async-logout - hdl=0 loop-id=0 portid=02 21:00:34:80:0d:74:14:d2. [ 266.823087] qla2xxx [:05:00.0]-5836:3: Async-logout complete - 21:00:34:80:0d:74:14:d2 hdl=1c portid=02 iop0=0. [ 266.823093] qla2xxx [:05:00.0]-f893:3: qlt_logo_completion_handler: se_sess / sess a438982b from port 21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 LOGO failed: 0x0 [ 266.928413] qla2xxx [:05:00.0]-f887:3: qlt_free_session_done: sess a438982b logout completed [ 266.931754] qla2xxx [:05:00.0]-f89a:3: se_sess / sess a438982b port 21:00:34:80:0d:74:14:d2 is gone, no own PLOGI pending (ref=-1) The snippet above shows that qla2xxx is trying to send NVMe PRLI instead of FCP PRLI to FCP target and link connection doesn't succeed. The same bug exists in linux-stable since 5.4.69. P2P worked until 5.4.69 but issue_lip was broken and link was not recovered after issue_lip. We have triaged the issue and found a way to fix it by backporting and properly merging upstream patches and will send a series to linux-stable - shortly. + shortly. (https://www.spinics.net/lists/stable/msg458515.html) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-71-generic 5.4.0-71.79 ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 Uname: Linux 5.4.0-71-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-71-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Thu Apr 15 15:43:55 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: - /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - /: Bus 01.Port 1:
[Bug 1924588] [NEW] P2P mode doesn't work in qla2xxx
Public bug reported: QLogic FC adapters don't work in direct mode on focal (at least QLE2692, and QLE2694, QLE2742 are affected): [ 266.821659] qla2xxx [:05:00.0]-3874:3: ELS_DCMD PLOGI sent, hdl=1a, loopid=0, to port_id 02 from port_id 01 [ 266.822926] qla2xxx [:05:00.0]-583f:3: ELS IOCB Done -Driver ELS logo error hdl=1a comp_status=0x0 error subcode 1=0x0 error subcode 2=0x0 total_byte=0x74 [ 266.822933] qla2xxx [:05:00.0]-3872:3: ELS_DCMD ELS done rc 0 hdl=1a, portid=02 21:00:34:80:0d:74:14:d2 [ 266.822937] qla2xxx [:05:00.0]-2918:3: qla_handle_els_plogi_done 1764 21:00:34:80:0d:74:14:d2 post PRLI [ 266.822965] qla2xxx [:05:00.0]-291b:3: Async-prli - 21:00:34:80:0d:74:14:d2 hdl=0, loopid=0 portid=02 retries=29 nvme. [ 266.823008] qla2xxx [:05:00.0]-5837:3: Async-prli failed - 21:00:34:80:0d:74:14:d2 hdl=1b portid=02 comp=31 iop0=18 iop1=b. [ 266.823011] qla2xxx [:05:00.0]-2929:3: qla2x00_async_prli_sp_done 21:00:34:80:0d:74:14:d2 res 0 [ 266.823014] qla2xxx [:05:00.0]-2918:3: qla24xx_handle_prli_done_event 1934 21:00:34:80:0d:74:14:d2 post NVMe prli [ 266.823019] qla2xxx [:05:00.0]-e801:3: Scheduling sess a438982b for deletion 21:00:34:80:0d:74:14:d2 [ 266.823031] qla2xxx [:05:00.0]-290a:3: qlt_unreg_sess sess a438982b for deletion 21:00:34:80:0d:74:14:d2 [ 266.823039] qla2xxx [:05:00.0]-f884:3: qlt_free_session_done: se_sess / sess a438982b from port 21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 logout 1 keep 0 els_logo 0 [ 266.823043] qla2xxx [:05:00.0]-f886:3: qlt_free_session_done: waiting for sess a438982b logout [ 266.823066] qla2xxx [:05:00.0]-2870:3: Async-logout - hdl=0 loop-id=0 portid=02 21:00:34:80:0d:74:14:d2. [ 266.823087] qla2xxx [:05:00.0]-5836:3: Async-logout complete - 21:00:34:80:0d:74:14:d2 hdl=1c portid=02 iop0=0. [ 266.823093] qla2xxx [:05:00.0]-f893:3: qlt_logo_completion_handler: se_sess / sess a438982b from port 21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 LOGO failed: 0x0 [ 266.928413] qla2xxx [:05:00.0]-f887:3: qlt_free_session_done: sess a438982b logout completed [ 266.931754] qla2xxx [:05:00.0]-f89a:3: se_sess / sess a438982b port 21:00:34:80:0d:74:14:d2 is gone, no own PLOGI pending (ref=-1) The snippet above shows that qla2xxx is trying to send NVMe PRLI instead of FCP PRLI to FCP target and link connection doesn't succeed. The same bug exists in linux-stable since 5.4.69. P2P worked until 5.4.69 but issue_lip was broken and link was not recovered after issue_lip. We have triaged the issue and found a way to fix it by backporting and properly merging upstream patches and will send a series to linux-stable shortly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-71-generic 5.4.0-71.79 ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 Uname: Linux 5.4.0-71-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-71-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Thu Apr 15 15:43:55 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-71-generic root=UUID=fed00282-cd6d-405e-ba8d-3f1d5cd7bcff ro net.ifnames=0 biosdevname=0 quiet console=ttyS0 console=tty1 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux
[Bug 1865878] [NEW] Ubuntu 18.04 won't install
Public bug reported: This error occurs while installing Ubuntu 18.04. I created a partition with 550MB for EFI booting and the rest (about 250Gb) left for Ext4 with mount point / ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.14 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:12:00 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865878 Title: Ubuntu 18.04 won't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1865878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764264] Re: bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza
** Changed in: juju Status: Incomplete => Invalid ** Changed in: juju/2.3 Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764264 Title: bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1764264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
** Changed in: juju Status: Fix Committed => Fix Released ** Changed in: juju-core (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764264] Re: bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza
Removing form milestone to let the report expire. ** Changed in: juju/2.3 Milestone: 2.3.10 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764264 Title: bionic cloud-init 18.2 WARNING Juju's 'runcmd' stanza To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1764264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756040] Re: bionic: LXD containers don't get fan network IP addresses
Removing from a milestone as this work will not be done in 2.3 series. ** Changed in: juju/2.3 Status: Triaged => Won't Fix ** Changed in: juju/2.3 Milestone: 2.3.10 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756040 Title: bionic: LXD containers don't get fan network IP addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1756040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
This failure has not been due to Juju but rather the setup of the CI environment. We have not seen any consecutive failures of this nature, so the issue has been resolved. I am closing this report. ** Changed in: juju Status: Incomplete => Fix Released ** Changed in: dbus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
** Changed in: juju Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
Merge PR brining this change into develop among other things: https://github.com/juju/juju/pull/10390 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
** Also affects: juju/2.6 Importance: Undecided Status: New ** Changed in: juju/2.6 Status: New => Fix Committed ** Changed in: juju/2.6 Importance: Undecided => Medium ** Changed in: juju/2.6 Assignee: (unassigned) => Anastasia (anastasia-macmood) ** Changed in: juju/2.6 Milestone: None => 2.6.5 ** Changed in: juju-core (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: juju-core (Ubuntu) Assignee: (unassigned) => Anastasia (anastasia-macmood) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
PR for 2.6: https://github.com/juju/juju/pull/10377 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
Actually, both json and yaml formats display secrets when asked. I'll update option and command help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564168] Re: juju list-credentials --show-secrets does not display passwords
** Changed in: juju Status: Triaged => In Progress ** Changed in: juju Assignee: (unassigned) => Anastasia (anastasia-macmood) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377169] Re: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure:addFailure:addFa
I am pretty sure that veebers is not working on this bug. ** Changed in: autopilot (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377169 Title: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure:addFailure:addFailure:addError:_convert:status:status:_gather_test:_fail:_details_to_str:as_text:_iter_text:decode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1377169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238662] Re: [autopilot] needs tests for deployment features
I am pretty sure that veebers is not working on this bug. ** Changed in: qtcreator-plugin-ubuntu (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238662 Title: [autopilot] needs tests for deployment features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1238662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237846] Re: OSK autopilot emulator isn't able to shift into CAPSLOCK state successfully.
I am pretty sure that veebers is not working on this bug. ** Changed in: ubuntu-keyboard (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237846 Title: OSK autopilot emulator isn't able to shift into CAPSLOCK state successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1237846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1204982] Re: refactored autopilot tests are fail prone for wrong environment setup
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204982 Title: refactored autopilot tests are fail prone for wrong environment setup To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1204982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229561] Re: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes)
I am pretty sure that veebers is not working on this bug. ** Changed in: ubuntu-keyboard (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229561 Title: Automated regression test for Bug #1227714 (OSK doesn't close after the application closes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1229561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1202511] Re: Clean up unity8 indicator client test suite
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1202511 Title: Clean up unity8 indicator client test suite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1202511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1260013] Re: [ap test] need to test click package app launching from dash
I am pretty sure that veebers is not working on this bug. ** Changed in: unity8 (Ubuntu) Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1260013 Title: [ap test] need to test click package app launching from dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1260013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174928] Re: unity 3D needs to support autopilot 1.3 dbus wire protocol
I am pretty sure that veebers is not working on this bug. ** Changed in: unity Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174928 Title: unity 3D needs to support autopilot 1.3 dbus wire protocol To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1174928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322199] Re: autopilot cannot fully introspect Qt applications
I am pretty sure that veebers is not working on this bug. ** Changed in: autopilot-qt Assignee: Christopher Lee (veebers) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322199 Title: autopilot cannot fully introspect Qt applications To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-qt/+bug/1322199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1281688] Re: autopilot vis fails with: autopilot.introspection.dbus.StateNotFoundError
I am pretty sure that veebers is not working on this bug. ** Changed in: xpathselect Assignee: Christopher Lee (veebers) => (unassigned) ** Changed in: xpathselect Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281688 Title: autopilot vis fails with: autopilot.introspection.dbus.StateNotFoundError To manage notifications about this bug go to: https://bugs.launchpad.net/xpathselect/+bug/1281688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798117] Re: juju sends "network" top level key to user.network-config in lxd containers
** Changed in: juju Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798117 Title: juju sends "network" top level key to user.network-config in lxd containers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1798117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804018] Re: Autogenerated interface name prevents creating a bridge over a VLAN
Or maybe Witold is since the last update was less than 2 weeks ago :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804018 Title: Autogenerated interface name prevents creating a bridge over a VLAN To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1804018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804018] Re: Autogenerated interface name prevents creating a bridge over a VLAN
I am pretty sure that Witold is not working on this for Juju 2.5. However, since John has addressed the issue on 2.4.7, we would have merged the solution forward. I am re-assigning this to John and updating the status to Fix Committed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804018 Title: Autogenerated interface name prevents creating a bridge over a VLAN To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1804018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600766] Re: initial dhcp has default hostname of ubuntu
>From Scott's comments and John's comments in the linked bug, this does not seem to be a Juju but cloud-init issue only. ** Changed in: juju Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600766 Title: initial dhcp has default hostname of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1600766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600766] Re: initial dhcp has default hostname of ubuntu
Potentially, a solution here might also address the bug # 1746358. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600766 Title: initial dhcp has default hostname of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1600766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600766] Re: initial dhcp has default hostname of ubuntu
** Changed in: juju Status: New => Triaged ** Changed in: juju 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/1600766 Title: initial dhcp has default hostname of ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1600766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613864] Re: Missing "juju-2"/"juju2" command.
I am pretty sure that @pangkit's status changes were invalid. I'll revert them back to what they were prior to these changes. ** Changed in: juju Status: In Progress => Invalid ** Changed in: juju-core (Ubuntu) Status: In Progress => Invalid ** Changed in: juju-release-tools Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613864 Title: Missing "juju-2"/"juju2" command. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1613864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing
Marking as Incomplete Wishlist as per 'maas' ** Changed in: juju Status: New => Incomplete ** Changed in: juju Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737428 Title: VRF support to solve routing problems associated with multi-homing To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570651] Re: Manpages for juju aliases drop version
going forward, we are not likely to make this change. ** Changed in: juju Status: Triaged => 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/1570651 Title: Manpages for juju aliases drop version To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1570651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570660] Re: Plugins not included in juju manpages
** Tags added: helptext -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570660 Title: Plugins not included in juju manpages To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1570660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705988] Re: snap install --classic juju fails
** Also affects: snap (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/1705988 Title: snap install --classic juju fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1705988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692866] Re: /snap/bin not in path for juju run/juju ssh
This seems to be related to, if not duplicate of, bug # 1660273. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692866 Title: /snap/bin not in path for juju run/juju ssh To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1692866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju Milestone: 2.2-beta3 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573681] Re: conflict when managing LXD storage with Juju 2.0
** Changed in: juju Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573681 Title: conflict when managing LXD storage with Juju 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-lxd/+bug/1573681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673652] Re: SRU juju-mongodb 3.2.12-0ubuntu1 to yakkety and xenial
** Tags removed: verification-needed ** Tags added: verification-done-xenial verification-done-yakkety ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673652 Title: SRU juju-mongodb 3.2.12-0ubuntu1 to yakkety and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1673652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536525] Re: juju-local: Don't depend on rsyslog
We are unlikely to address this on 1.25x. ** Changed in: juju-core/1.25 Status: Triaged => Won't Fix ** Changed in: juju-core/1.25 Importance: Critical => Undecided ** Changed in: juju-core-1 (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536525 Title: juju-local: Don't depend on rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1536525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju Milestone: 2.2-beta2 => 2.2-beta3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670891] Re: MongoDB used by Juju has replication bug
Since the package is now in Zesty, I am marking this as Fix Committed. SRU bug linked in comment # 3 will be used to track backports. ** Changed in: juju Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670891 Title: MongoDB used by Juju has replication bug To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1670891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637230] Re: [2.0] Error calling 'lxd forkstart
@Larry, 2.1-rc2 might not be the best release to recreate this - either 2.1.2 or 2.2-alpha1 or daily snaps would be best. Could you please re-try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637230 Title: [2.0] Error calling 'lxd forkstart To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1637230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670891] Re: MongoDB used by Juju has replication bug
SRU bug for Xenial and Yakkety: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1673652 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670891 Title: MongoDB used by Juju has replication bug To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1670891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673652] [NEW] SRU juju-mongodb 3.2.12-0ubuntu1 to yakkety and xenial
Public bug reported: juju-mongodb 3.2.12-0ubuntu1 is in zesty. It provides several performance and stability fixes. It also allows us to drop patches to support rare architectures. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This will affect juju only, juju controllers specifically. Biggest impact bug that requires new microversion: https://bugs.launchpad.net/juju/+bug/1670891 [QA/Testing] Juju QA will verify that new controllers work with the new mongo on all archs for both yakkety and xenial. Existing controller will be upgraded to the new version and verified. This will be tested both in Juju CI and manually. ** Affects: juju-mongodb3.2 (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/1673652 Title: SRU juju-mongodb 3.2.12-0ubuntu1 to yakkety and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb3.2/+bug/1673652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573681] Re: conflict when managing LXD storage with Juju 2.0
Looping in LXD project for comment on support of multiple storage backends as per comment # 4. ** Also affects: lxd (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/1573681 Title: conflict when managing LXD storage with Juju 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-lxd/+bug/1573681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
Great idea, John \o/ Marked as hidden now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju Milestone: 2.2-alpha1 => 2.2-rc1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657305] Re: percona cluster getting wrong private ip
Based on Ryan's assessment and marking of this as 'Invalid' for juju (ubuntu), I am marking this as 'Invalid' for "juju" project too. ** Changed in: juju Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657305 Title: percona cluster getting wrong private ip To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1657305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668264] Re: pending message needs more information
Renaming the bug as this is not necessarily LXD specific. We want to expose more information to the user when trying/re-trying provisioning. Pending status by itself is not helpful. ** Summary changed: - lxc provisioning hangs with no feedback due to lack of network + pending message needs more information ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668264 Title: pending message needs more information To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1668264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668264] Re: lxc provisioning hangs with no feedback due to lack of network
** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Changed in: juju Status: New => Triaged ** Changed in: juju Importance: Undecided => Medium ** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668264 Title: lxc provisioning hangs with no feedback due to lack of network To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1668264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
Marking this as Invalid for Juju. The problem occurs under heavy load and as per comment # 17, there is nothing Juju can do about it. It behaves as expected. You may find comment # 21 very helpful. ** Changed in: juju Status: New => Invalid ** Changed in: juju/2.1 Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665648] Re: Juju 2.0.3 fails to deploy LXC container lxdbr0 overlapping subnets
@Mateusz, I believe you mean "LXD" containers both in bug title and description, right? :D It also looks like a duplicate of bug # 1569106. ** Changed in: juju (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665648 Title: Juju 2.0.3 fails to deploy LXC container lxdbr0 overlapping subnets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1665648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
** Changed in: juju/2.1 Milestone: 2.1.0 => None ** Changed in: juju Milestone: 2.2.0-alpha1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599886] Re: apt-mirror does not override security.ubuntu.com for containers on trusty
@Seyeong Kim (xtrusia), You have previously tested against 2.0.2 and 2.1 beta (I am guessing both on xenial). Have you had a chance to test your fix with Juju on trusty? Latest equivalent versions are 2.0.3 and 2.1-rc1. ** Changed in: juju Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599886 Title: apt-mirror does not override security.ubuntu.com for containers on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1599886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574076] Re: juju package should suggest juju-1.25 not juju-core
As this issue will be addressed through packaging and juju-release-tools project, I am marking it as Invalid for "juju" itself. ** Changed in: juju Status: Triaged => Invalid ** Changed in: juju Milestone: 2.1.0 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574076 Title: juju package should suggest juju-1.25 not juju-core To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1574076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613864] Re: Missing "juju-2"/"juju2" command.
Removing 2.1 milestone as we will not be addressing this issue in 2.1. ** Changed in: juju Milestone: 2.1.0 => None ** Tags added: usability ** Also affects: juju-release-tools 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/1613864 Title: Missing "juju-2"/"juju2" command. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1613864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543660] Re: juju needs to fix the yaml parser
Linked yaml issues was merged into go-yaml 18 days ago. Juju needs to update library dependency to a newer revision to take advantage of the merge. ** Changed in: juju Importance: High => Medium ** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543660 Title: juju needs to fix the yaml parser To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1543660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570660] Re: Plugins not included in juju manpages
Removing 2.1 milestone as we will not be addressing this issue in 2.1. ** Changed in: juju Milestone: 2.1.0 => None ** Changed in: juju Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570660 Title: Plugins not included in juju manpages To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1570660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364037] Re: Juju expects a public address for all machines maybe insecure
Removing 2.1 milestone as we will not addressing this issue in 2.1. ** Changed in: juju Milestone: 2.1.0 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364037 Title: Juju expects a public address for all machines maybe insecure To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1364037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
** Changed in: juju Importance: Critical => High ** Also affects: juju/2.1 Importance: Undecided Status: New ** Changed in: juju/2.1 Status: New => Incomplete ** Changed in: juju/2.1 Importance: Undecided => High ** Changed in: juju/2.1 Milestone: None => 2.1.0 ** Changed in: juju Milestone: 2.1.0 => 2.2.0-alpha1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
** Changed in: juju Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637230] Re: [2.0] Error calling 'lxd forkstart
** Changed in: juju Milestone: 2.1-rc1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637230 Title: [2.0] Error calling 'lxd forkstart To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1637230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640079] Re: LXDs doesn't start after a reboot
*** This bug is a duplicate of bug 1631254 *** https://bugs.launchpad.net/bugs/1631254 ** This bug has been marked a duplicate of bug 1631254 [2.0rc3] lxd containers do not autostart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640079 Title: LXDs doesn't start after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1640079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
>From internal discussion, for Juju, in clouds, there is no guarantee that the images can support particular kernel parameters. For us, it is best not to try and guess and better surface the error in the status. ** Changed in: juju Importance: Critical => High ** Changed in: juju Milestone: 2.1-rc1 => 2.2.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
** Changed in: juju Milestone: 2.1.0 => 2.1-rc1 ** Changed in: juju Assignee: Richard Harding (rharding) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660542] Re: container mac addresses should use 'locally assigned' section
We track Juju 2.x issues in "juju" project. Re-targeting :D ** Also affects: juju Importance: Undecided Status: New ** Changed in: juju Status: New => Triaged ** Changed in: juju Importance: Undecided => Medium ** No longer affects: juju-core -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660542 Title: container mac addresses should use 'locally assigned' section To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1660542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
** Changed in: juju Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637230] Re: [2.0] Error calling 'lxd forkstart
We suspect this is more LXD related than Juju. Marking the bug as Incomplete for Juju until Stephane's and Tycho's questions are answered. ** Changed in: juju Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637230 Title: [2.0] Error calling 'lxd forkstart To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1637230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: None => 2.1.0 ** Changed in: juju Status: In Progress => Triaged ** Changed in: juju Assignee: Christian Muirhead (2-xtian) => (unassigned) ** Changed in: juju Milestone: 2.1.0 => 2.2.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647299] Re: maas container networking broken: Internet connection for 0/lxd/1 failed
** Changed in: juju Milestone: 2.1-rc1 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647299 Title: maas container networking broken: Internet connection for 0/lxd/1 failed To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1647299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640079] Re: LXDs doesn't start after a reboot
Re-targeting to "juju" launchpad project which tracks Juju 2.x issues. ** Also affects: juju Importance: Undecided Status: New ** No longer affects: juju-core ** Changed in: juju Status: New => Triaged ** Changed in: juju Importance: Undecided => High ** Changed in: juju Milestone: None => 2.1.0-beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640079 Title: LXDs doesn't start after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1640079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560487] Re: local provider fails to create lxc container from template
@Benedikt Troester (btroester) The final resolution is summarized in comment # 15, extract here: ... install both juju-local and lxc from trusty-backports: sudo apt-get install juju-local -t trusty-backports lxc ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560487 Title: local provider fails to create lxc container from template To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1560487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471237] Re: Mongo causes juju to fail: bad record MAC
** Also affects: juju-core/1.25 Importance: Undecided Status: New ** Changed in: juju-core/1.25 Status: New => 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/1471237 Title: Mongo causes juju to fail: bad record MAC To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1471237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560487] Re: local provider fails to create lxc container from template
** Changed in: juju-core (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560487 Title: local provider fails to create lxc container from template To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1560487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560487] Re: local provider fails to create lxc container from template
** Changed in: juju-core Status: Triaged => Invalid ** Changed in: juju-core Milestone: 1.25.7 => None ** Changed in: juju-core Importance: Critical => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560487 Title: local provider fails to create lxc container from template To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1560487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208430] Re: mongodb runs as root user
Last comments and concerns on this discussion were raised more than 2 years ago. ** Changed in: juju-core Status: Triaged => 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/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536525] Re: juju-local: Don't depend on rsyslog
** Changed in: juju-core/1.25 Milestone: 1.25.7 => 1.25.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536525 Title: juju-local: Don't depend on rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1536525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403955] Re: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0
** Changed in: juju-core Status: Triaged => 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/1403955 Title: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1402763] Re: Multicast traffic not propating correctly over linux bridge
** Changed in: juju-core Status: Triaged => 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/1402763 Title: Multicast traffic not propating correctly over linux bridge To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423626] Re: Inconsistent device naming depending on install method - biosdevname/no biosdevname
** Changed in: juju-core Status: Triaged => 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/1423626 Title: Inconsistent device naming depending on install method - biosdevname/no biosdevname To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1423626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471237] Re: Mongo causes juju to fail: bad record MAC
** Changed in: juju-core Status: Triaged => 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/1471237 Title: Mongo causes juju to fail: bad record MAC To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1471237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242237] Re: Mongodb server ignores --smallfiles if other paramethers are set in the command line
** Changed in: juju-core Status: Triaged => 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/1242237 Title: Mongodb server ignores --smallfiles if other paramethers are set in the command line To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1242237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340836] Re: error: error executing "lxc-start" when juju client runs inside kvm
** Changed in: juju-core Status: Triaged => 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/1340836 Title: error: error executing "lxc-start" when juju client runs inside kvm To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1340836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318378] Re: rsyslog starts dropping connections in large environments
** Changed in: juju-core Milestone: 1.25.7 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318378 Title: rsyslog starts dropping connections in large environments To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318378] Re: rsyslog starts dropping connections in large environments
** Changed in: juju-core Status: Triaged => 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/1318378 Title: rsyslog starts dropping connections in large environments To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1318378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: 2.0.0 => 2.0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
** Changed in: juju Milestone: None => 2.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** Changed in: juju Importance: Medium => High ** Changed in: juju Milestone: None => 2.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183129] Re: 'juju status' difficult to read and provides unneccessary information
** Changed in: juju-core (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183129 Title: 'juju status' difficult to read and provides unneccessary information To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1183129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576318] Re: juju register not clear that you're creating a new password
** Changed in: juju-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576318 Title: juju register not clear that you're creating a new password To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1576318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604988] Re: Inconsistent licence in github.com/juju/utils/series
** Changed in: juju-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604988 Title: Inconsistent licence in github.com/juju/utils/series To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1604988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427257] Re: Juju backup doesn't contain .juju files
** Changed in: juju-core (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427257 Title: Juju backup doesn't contain .juju files To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1427257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290920] Re: non-default lxc-dir breaks local provider
** Changed in: juju-core (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** Changed in: juju-core (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331019] Re: allow setting fixed MAC addresses for juju created LXC containers
>From Dimiter: We have other plans for HA/VIPs. ** Changed in: juju-core (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331019 Title: allow setting fixed MAC addresses for juju created LXC containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1331019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364037] Re: Juju expects a public address for all machines maybe insecure
>From Dimiter: We still assume to have public IPs in most providers and have no way of not using them if the user doesn't want to (except for the use-floating-ips setting for openstack) ** Also affects: juju Importance: Undecided Status: New ** Changed in: juju Status: New => Triaged ** Changed in: juju Importance: Undecided => High ** Changed in: juju Milestone: None => 2.1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364037 Title: Juju expects a public address for all machines maybe insecure To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1364037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536525] Re: juju-local: Don't depend on rsyslog
** No longer affects: juju -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536525 Title: juju-local: Don't depend on rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1536525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
