sts-sponsors team mailing list archive

1. sts-sponsors team
2. Mailing list archive
3. Messages by date

Messages by date

Messages sent to the sts-sponsors mailing list, ordered by date from the newest to oldest.

• [Bug 1746630] Re: virsh api is stuck when vm is down with NFS borken
  From: ChristianEhrhardt, 2018-02-02
• [Bug 1746630] Re: virsh api is stuck when vm is down with NFS borken
  From: ChristianEhrhardt, 2018-02-02
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Hua Zhang, 2018-02-02
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Seyeong Kim, 2018-02-02
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Seyeong Kim, 2018-02-02
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Brian Murray, 2018-02-01
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-02-01
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Brian Murray, 2018-02-01
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Brian Murray, 2018-02-01
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-02-01
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: David Coronel, 2018-02-01
• [Bug 1743787] Re: FTBFS in Trusty
  From: Eric Desrochers, 2018-02-01
• [Bug 1743787] [NEW] FTBFS in Trusty
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1717714] Please test proposed package
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1734983] Please test proposed package
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1742531] Update Released
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1743232] Update Released
  From: Łukasz Zemczak, 2018-02-01
• [Bug 1746630] Re: virsh api is stuck when vm is down with NFS borken
  From: Ubuntu Foundations Team Bug Bot, 2018-02-01
• [Bug 1746630] Re: virsh api is stuck when vm is down with NFS borken
  From: Bug Watch Updater, 2018-02-01
• [Bug 1746630] Re: virsh api is stuck when vm is down with NFS borken
  From: Seyeong Kim, 2018-02-01
• [Bug 1746630] Re: virsh api is stuck when vm is down with NFS borken
  From: Seyeong Kim, 2018-02-01
• [Bug 1746630] [NEW] virsh api is stuck when vm is down with NFS borken
  From: Launchpad Bug Tracker, 2018-02-01
• [Bug 1733276] Re: Cannot resize partitions on NVME devices due to bad device name parsing
  From: Eric Desrochers, 2018-01-31
• [Bug 1733276] [NEW] Cannot resize partitions on NVME devices due to bad device name parsing
  From: Launchpad Bug Tracker, 2018-01-31
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-31
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-31
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-31
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-31
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-31
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-30
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-29
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Launchpad Bug Tracker, 2018-01-29
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-29
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-29
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Launchpad Bug Tracker, 2018-01-29
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-29
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-29
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-29
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-29
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-29
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-29
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Hua Zhang, 2018-01-29
• [Bug 1745531] Re: [SRU] Reinforce hostname preseed regex
  From: Hua Zhang, 2018-01-29
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Hua Zhang, 2018-01-29
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Hua Zhang, 2018-01-29
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Hua Zhang, 2018-01-29
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Hua Zhang, 2018-01-29
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Hua Zhang, 2018-01-29
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-26
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Ubuntu Foundations Team Bug Bot, 2018-01-26
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-26
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-26
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-26
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Eric Desrochers, 2018-01-26
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: David Coronel, 2018-01-26
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: David Coronel, 2018-01-26
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: David Coronel, 2018-01-26
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: David Coronel, 2018-01-26
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: David Coronel, 2018-01-26
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: David Coronel, 2018-01-26
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: David Coronel, 2018-01-26
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: David Coronel, 2018-01-26
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-26
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-26
• [Bug 1745531] Re: Reinforce hostname preseed regex
  From: Eric Desrochers, 2018-01-26
• [Bug 1745531] [NEW] Reinforce hostname preseed regex
  From: Launchpad Bug Tracker, 2018-01-26
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-25
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-25
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-25
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Łukasz Zemczak, 2018-01-25
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Łukasz Zemczak, 2018-01-25
• [Bug 1742531] Please test proposed package
  From: Łukasz Zemczak, 2018-01-25
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Łukasz Zemczak, 2018-01-25
• [Bug 1743232] Please test proposed package
  From: Łukasz Zemczak, 2018-01-25
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Łukasz Zemczak, 2018-01-25
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-24
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-23
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-23
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Eric Desrochers, 2018-01-23
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Launchpad Bug Tracker, 2018-01-23
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Launchpad Bug Tracker, 2018-01-23
• [Bug 1693574] Re: Docker plugin uses the wrong command for Ubuntu
  From: Eric Desrochers, 2018-01-23
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-22
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Eric Desrochers, 2018-01-22
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-22
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-22
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Eric Desrochers, 2018-01-22
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-20
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Eric Desrochers, 2018-01-20
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-20
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-20
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-20
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-19
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Bryan Quigley, 2018-01-19
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-19
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-19
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-18
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-18
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-18
• [Bug 1316970] Re: g_dbus memory leak in lrmd
  From: Dan Streetman, 2018-01-18
• [Bug 1316970] Re: g_dbus memory leak in lrmd
  From: Seyeong Kim, 2018-01-18
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Bug Watch Updater, 2018-01-18
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-17
• [Bug 1743787] [NEW] FTBFS in Trusty
  From: Launchpad Bug Tracker, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-17
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Nish Aravamudan, 2018-01-17
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Chris Newcomer, 2018-01-16
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Doug Parrish, 2018-01-16
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Alex Moldovan, 2018-01-16
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: Alex Moldovan, 2018-01-16
• [Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade
  From: Eric Desrochers, 2018-01-16
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-16
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Eric Desrochers, 2018-01-16
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-16
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Eric Desrochers, 2018-01-16
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Eric Desrochers, 2018-01-16
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Andreas Hasenack, 2018-01-16
• [Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade
  From: Andreas Hasenack, 2018-01-16
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Andreas Hasenack, 2018-01-16
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Andreas Hasenack, 2018-01-16
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Victor Tapia, 2018-01-16
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-16
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-16
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Eric Desrochers, 2018-01-16
• [Bug 1734983] Re: Request to backport sosreport v3.5
  From: David Coronel, 2018-01-15
• [Bug 1693574] Re: Docker plugin uses the wrong command for Ubuntu
  From: David Coronel, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-15
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Eric Desrochers, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Simon Poirier, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Simon Poirier, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Simon Poirier, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Simon Poirier, 2018-01-15
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Andreas Hasenack, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Launchpad Bug Tracker, 2018-01-15
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: Launchpad Bug Tracker, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Ubuntu Foundations Team Bug Bot, 2018-01-15
• [Bug 1743232] Re: set vm_info to kvm for digitalocean instances
  From: David Coronel, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: David Coronel, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-15
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-15
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Bug Watch Updater, 2018-01-14
• Re: [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: intrigeri, 2018-01-14
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-14
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-14
• [Bug 1743232] [NEW] set vm_info to kvm for digitalocean instances
  From: Eric Desrochers, 2018-01-14
• [Bug 1743232] [NEW] set vm_info to kvm for digitalocean instances
  From: Launchpad Bug Tracker, 2018-01-14
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-13
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-13
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-13
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-13
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Simon Poirier, 2018-01-13
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Simon Poirier, 2018-01-13
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Chris Gregan, 2018-01-12
• [Bug 1742531] Re: New Amazon AWS C5 instances are not recognised as a VM
  From: Eric Desrochers, 2018-01-12
• [Bug 1316970] Re: g_dbus memory leak in lrmd
  From: Dan Streetman, 2018-01-12
• [Bug 1742531] [NEW] New Amazon AWS C5 instances are not recognised as a VM
  From: Launchpad Bug Tracker, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Bug Watch Updater, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-12
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Seyeong Kim, 2018-01-12
• [Bug 1657444] [NEW] Can't failover when rabbit_hosts is configured as 3 hosts
  From: Launchpad Bug Tracker, 2018-01-11
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Victor Tapia, 2018-01-11
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Victor Tapia, 2018-01-11
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Victor Tapia, 2018-01-10
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Dimitri John Ledkov, 2018-01-10
• [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Dimitri John Ledkov, 2018-01-10
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Christian Boltz, 2018-01-10
• [Bug 1316970] Re: g_dbus memory leak in lrmd
  From: Dan Streetman, 2018-01-09
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-09
• [Bug 1740892] [NEW] corosync upgrade on 2018-01-02 caused pacemaker to fail
  From: Launchpad Bug Tracker, 2018-01-09
• [Bug 1316970] Re: g_dbus memory leak in lrmd
  From: Dan Streetman, 2018-01-09
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-09
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Eric Desrochers, 2018-01-09
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Seyeong Kim, 2018-01-09
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Seyeong Kim, 2018-01-09
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Seyeong Kim, 2018-01-09
• [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
  From: Seyeong Kim, 2018-01-09

 •  Take the tour  •  Read the guide  •  Help for mailing lists  

© 2004-2021 Canonical Ltd.  •  Terms of use  •  Data privacy  •  Contact Launchpad Support  •  Blog  •  Careers  •  System status