text:
docker kill SIGWINCH is not forwarded to container

Description of problem
https://github.com/clearcontainers/proxy/blob/master/proxy.go#L451
Expected result
Workload will get the signal if docker kill 28 is used.
Example:
docker run --runtime cc-runtime --name P1GjgyJuoQSVthDf1APV4lnjTauxd9 -dt busybox sh -c 'trap "exit 28" 28 ; while : ; do sleep 1; done'
docker kill -s 28 P1GjgyJuoQSVthDf1APV4lnjTauxd9

The contianer should exit after do kill, but looking at docker ps is still up.
$ docker ps
CONTAINER ID        IMAGE               COMMAND                   CREATED             STATUS              PORTS               NAMES
fed26d7492f6        busybox             "sh -c 'trap "exit..."   8 minutes ago       Up 8 minutes                            P1GjgyJuoQSVthDf1APV4lnjTauxd9
Actual result
The workload get the signal and in the example exits. (this works with runc)
cc-data.txt
Meta details
Running cc-collect-data.sh version 3.0.5 (commit 40047b5) at 2017-10-26.15:04:14.562059613.

Runtime is /bin/cc-runtime.
cc-env
Output of "/bin/cc-runtime cc-env":
[Meta]
  Version = "1.0.4"

[Runtime]
  [Runtime.Version]
    Semver = "3.0.5"
    Commit = "40047b5"
    OCI = "1.0.0-dev"
  [Runtime.Config]
    Path = "/usr/share/defaults/clear-containers/configuration.toml"
    GlobalLogPath = "/var/lib/clear-containers/runtime/runtime.log"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 2.7.0, Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-lite-system-x86_64"

[Image]
  Path = "/usr/share/clear-containers/clear-18400-containers.img"

[Kernel]
  Path = "/usr/share/clear-containers/vmlinuz-4.9.58-79.1.container"
  Parameters = ""

[Proxy]
  Type = "ccProxy"
  Version = "Version: 3.0.5+git.fb22251"
  URL = "unix:///var/run/clear-containers/proxy.sock"

[Shim]
  Type = "ccShim"
  Version = "shim version: 3.0.5 (commit: 86a7c20)"
  Path = "/usr/libexec/clear-containers/cc-shim"

[Agent]
  Type = "hyperstart"
  Version = "<<unknown>>"
  PauseBinPath = "/var/lib/clear-containers/runtime/bundles/pause_bundle/bin/pause"

[Host]
  Kernel = "4.13.5-100.fc25.x86_64"
  CCCapable = true
  [Host.Distro]
    Name = "Fedora"
    Version = "25"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"

Runtime config files
Runtime default config files
/usr/share/defaults/clear-containers/configuration.toml
/usr/share/defaults/clear-containers/configuration.toml

Runtime config file contents
Config file /etc/clear-containers/configuration.toml not found
Output of "cat "/usr/share/defaults/clear-containers/configuration.toml"":
# XXX: Warning: this file is auto-generated from file "config/configuration.toml.in".

[hypervisor.qemu]
path = "/usr/bin/qemu-lite-system-x86_64"
kernel = "/usr/share/clear-containers/vmlinuz.container"
image = "/usr/share/clear-containers/clear-containers.img"
machine_type = "pc"
# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc
kernel_params = ""

# Default number of vCPUs per POD/VM:
# unspecified or 0 --> will be set to 1
# < 0              --> will be set to the actual number of physical cores
# > 0 <= 255       --> will be set to the specified number
# > 255            --> will be set to 255
default_vcpus = -1

# Default memory size in MiB for POD/VM.
# If unspecified then it will be set 2048 MiB.
#default_memory = 2048
disable_block_device_use = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
#enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
#enable_hugepages = true

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# Debug changes the default hypervisor and kernel parameters to
# enable debug output where available.
# Default false
# these logs can be obtained in the cc-proxy logs  when the
# proxy is set to run in debug mode
# /usr/libexec/clear-containers/cc-proxy -log debug
# or by stopping the cc-proxy service and running the cc-proxy
# explicitly using the same command line
#
enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

[proxy.cc]
url = "unix:///var/run/clear-containers/proxy.sock"

[shim.cc]
path = "/usr/libexec/clear-containers/cc-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
enable_debug = true

[agent.hyperstart]
pause_root_path = "/var/lib/clear-containers/runtime/bundles/pause_bundle"

[runtime]
## Uncomment to enable the global logging to the default path.
global_log_path = "/var/lib/clear-containers/runtime/runtime.log"

# If enabled, the runtime will log additional debug messages to the global
# log, assuming that is also enabled.
# (default: disabled)
enable_debug = true

Logfiles
Runtime logs
Recent runtime problems found in global log /var/lib/clear-containers/runtime/runtime.log:
time="2017-10-26T14:34:40.244795313-05:00" pid=19972 name="cc-runtime" level="error" source="runtime" msg="Container ID (28b85bbafe5afa686a7b1a75ccd35e9c76764738efd20651e285fdc931c1917b) does not exist"
time="2017-10-26T14:34:43.552844797-05:00" pid=20037 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db -uuid 36306132-3532-3561-3764-373265363933 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/6afc54161a4e29d6c74e5aaec8edcafd01a9277e3977593eb9c1acbd064e38a1/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db::off::]"
time="2017-10-26T14:34:51.158613266-05:00" pid=20094 name="cc-runtime" level="error" source="runtime" msg="Container 60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db not ready or running, cannot send a signal"
time="2017-10-26T14:34:52.655010411-05:00" pid=20120 name="cc-runtime" level="error" source="runtime" msg="Container ID (60a2525a7d72e6936ee8844653022ddbd914dbef4ef26a98da9aba6133e524db) does not exist"
time="2017-10-26T14:34:58.755128102-05:00" pid=20180 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5 -uuid 34353338-3939-3962-3164-376536323066 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/33d851856706b08e00d277791ec5a2e44b9da0f566232a0982b52839859558f1/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5::off::]"
time="2017-10-26T14:35:05.892807761-05:00" pid=20254 name="cc-runtime" level="error" source="runtime" msg="Container 4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5 not ready or running, cannot send a signal"
time="2017-10-26T14:35:06.132205238-05:00" pid=20266 name="cc-runtime" level="error" source="runtime" msg="Container ID (4538999b1d7e620f5e729c3ca5858aa8f5ff1061149aa685e7b7fb6a8d06d4b5) does not exist"
time="2017-10-26T14:35:10.576431724-05:00" pid=20325 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057 -uuid 31313439-3466-3630-6630-663736656163 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/ecdcbb3a1ea2fbf2a9301d1e11b983bf6f84ef295b94238590dcade408a0ddcd/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057::off::]"
time="2017-10-26T14:35:18.212741274-05:00" pid=20392 name="cc-runtime" level="error" source="runtime" msg="Container 11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057 not ready or running, cannot send a signal"
time="2017-10-26T14:35:19.178801075-05:00" pid=20419 name="cc-runtime" level="error" source="runtime" msg="Container ID (11494f60f0f76eacc72d355d41490eecf2da717f50d05ecebe561cb4633d7057) does not exist"
time="2017-10-26T14:35:23.483815601-05:00" pid=20481 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8 -uuid 61353237-3634-3932-3063-313930356536 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/e3ea1a22a25868a1192767ea37aa72ed68ac647a25ad2504844919f8fc660c12/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8::off::]"
time="2017-10-26T14:35:31.618777618-05:00" pid=20545 name="cc-runtime" level="error" source="runtime" msg="Container a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8 not ready or running, cannot send a signal"
time="2017-10-26T14:35:32.803550239-05:00" pid=20569 name="cc-runtime" level="error" source="runtime" msg="Container ID (a52764920c1905e62eab7d45d973f47d06ccd2ecea6c1e5f071958b83bc23cd8) does not exist"
time="2017-10-26T14:35:35.137388469-05:00" pid=20646 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329 -uuid 62386363-3933-3134-6462-626636346436 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/a89b37a56e3ece4f99b7305b11250fd3383295dd0f6b592e0620bba9c595d070/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329::off::]"
time="2017-10-26T14:35:42.150827091-05:00" pid=20729 name="cc-runtime" level="error" source="runtime" msg="Container b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329 not ready or running, cannot send a signal"
time="2017-10-26T14:35:42.371623955-05:00" pid=20753 name="cc-runtime" level="error" source="runtime" msg="Container ID (b8cc9314dbbf64d67bf332e8d698d247e3850f4d8607f54fa848da29bf953329) does not exist"
time="2017-10-26T14:35:46.959671853-05:00" pid=20841 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e -uuid 66666161-3761-3235-6638-353463363736 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/e594d9eed67eced1c7d66b9d2d34a3870b42cdb21a8a53b0e08afc0f3a99ed2e/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e::off::]"
time="2017-10-26T14:35:54.665665477-05:00" pid=20920 name="cc-runtime" level="error" source="runtime" msg="Container ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e not ready or running, cannot send a signal"
time="2017-10-26T14:35:56.003112556-05:00" pid=20945 name="cc-runtime" level="error" source="runtime" msg="Container ID (ffaa7a25f854c6762395c36fe2fbf43ac0151ad4a42eed50ac5b488bc4dcf73e) does not exist"
time="2017-10-26T14:35:58.09087867-05:00" pid=20999 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1 -uuid 31386337-3530-6139-6132-333166663536 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/8361cd0d5a83a6fe5de82213bd95ae568bb2b1e7c291bb1bb68972a2df981d70/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1::off::]"
time="2017-10-26T14:36:06.09968451-05:00" pid=21055 name="cc-runtime" level="error" source="runtime" msg="Container 18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1 not ready or running, cannot send a signal"
time="2017-10-26T14:36:07.267619927-05:00" pid=21081 name="cc-runtime" level="error" source="runtime" msg="Container ID (18c750a9a231ff565b9a5303b57b9f08629d36a6d0da49a540bd6d347de545d1) does not exist"
time="2017-10-26T14:36:12.554007339-05:00" pid=21138 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce -uuid 63666431-3931-6664-3137-383532373634 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/60c771915e5f2f3c60da55da420ded74b81fb9590d4596c2010d8f427ec29929/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce::off::]"
time="2017-10-26T14:36:23.656541903-05:00" pid=21225 name="cc-runtime" level="error" source="runtime" msg="Container cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce not ready or running, cannot send a signal"
time="2017-10-26T14:36:23.941210036-05:00" pid=21238 name="cc-runtime" level="error" source="runtime" msg="Container ID (cfd191fd1785276419b1c95335acc08ab415828c265a871597f6aa0f164ec2ce) does not exist"
time="2017-10-26T14:36:24.628177505-05:00" pid=21283 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110 -uuid 39613764-3466-3262-6361-333430623437 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/d262fc6b4370a2428cdda4d0e1518069aeceeb48cd16c4eff7e49193764ed5d1/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110::off::]"
time="2017-10-26T14:36:32.405646545-05:00" pid=21343 name="cc-runtime" level="error" source="runtime" msg="Container 9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110 not ready or running, cannot send a signal"
time="2017-10-26T14:36:33.409878125-05:00" pid=21367 name="cc-runtime" level="error" source="runtime" msg="Container ID (9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110) does not exist"
time="2017-10-26T14:36:36.939148594-05:00" pid=21429 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247 -uuid 64666332-3333-3762-3161-396164393765 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/764436c3dd5158267812ba1244bd0343ca0b8a32a01ab243659e671574e8ef41/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247::off::]"
time="2017-10-26T14:36:45.140867103-05:00" pid=21527 name="cc-runtime" level="error" source="runtime" msg="Container dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247 not ready or running, cannot send a signal"
time="2017-10-26T14:36:45.812152044-05:00" pid=21553 name="cc-runtime" level="error" source="runtime" msg="Container ID (dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247) does not exist"
time="2017-10-26T14:36:49.235014349-05:00" pid=21616 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c -uuid 34613335-3966-3563-3437-356235646164 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/a8134748defb84847d542d27b87c51f7fd10cc164e93ccdc51f33bab9b67ca7d/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c::off::]"
time="2017-10-26T14:36:56.149631988-05:00" pid=21697 name="cc-runtime" level="error" source="runtime" msg="Container 4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c not ready or running, cannot send a signal"
time="2017-10-26T14:36:57.531930132-05:00" pid=21721 name="cc-runtime" level="error" source="runtime" msg="Container ID (4a359f5c475b5dad18a64ee46874c6f274e95dcf9bd0075cacad1a666a57de0c) does not exist"
time="2017-10-26T14:40:00.053840765-05:00" pid=21856 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab -uuid 66386436-3231-3738-3735-643636323536 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/1fcad6a1b7aa5561493ec65e2876d8ee7eacf1c0d4df13b47fe9a9f56566938c/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab::off::]"
time="2017-10-26T14:40:01.696592654-05:00" pid=21915 name="cc-runtime" level="error" source="runtime" msg="Container f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab not ready or running, cannot send a signal"
time="2017-10-26T14:40:02.471469505-05:00" pid=21933 name="cc-runtime" level="error" source="runtime" msg="Container ID (f8d6217875d662560ca15de7c31b5c459b2f1e3591739ff3bb8b2f79053fc9ab) does not exist"
time="2017-10-26T14:42:08.717010508-05:00" pid=22533 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870 -uuid 33653962-3435-3638-3732-656466626435 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/4c2e6f703f08121143a5fb35c8593efe7a106be8e91351a4d6efb2458d7f53f5/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870::off::]"
time="2017-10-26T14:49:15.036740411-05:00" pid=23560 name="cc-runtime" level="error" source="runtime" msg="Container 3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870 not ready or running, cannot send a signal"
time="2017-10-26T14:49:15.279488342-05:00" pid=23575 name="cc-runtime" level="error" source="runtime" msg="Container ID (3e9b456872edfbd5008d1cfe86b799b96983135eeb3abe60ab7b5f0408965870) does not exist"
time="2017-10-26T14:50:16.728279878-05:00" pid=23896 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b -uuid 37643363-6266-3266-3630-366535316439 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/1736955ae3469c3d5e0283b7c8296cfcf5abdf7601f871cede31d202211b54ed/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b::off::]"
time="2017-10-26T14:50:42.406689124-05:00" pid=24002 name="cc-runtime" level="error" source="runtime" msg="Container 7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b not ready or running, cannot send a signal"
time="2017-10-26T14:50:43.489850898-05:00" pid=24028 name="cc-runtime" level="error" source="runtime" msg="Container ID (7d3cbf2f606e51d9d273b5a34af43154e540c295c528a51cf7c19ab8161ae22b) does not exist"
time="2017-10-26T14:50:51.251190761-05:00" pid=24136 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691 -uuid 61613330-3837-3237-6138-643139613034 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/b5c6fc2b6d24801c3248459f2c91b8a3b57269e157737836460463133a1c0f63/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 quiet systemd.show_status=false init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691::off::]"
time="2017-10-26T14:52:52.754818256-05:00" pid=24586 name="cc-runtime" level="error" source="runtime" msg="Container aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691 not ready or running, cannot send a signal"
time="2017-10-26T14:52:52.993613744-05:00" pid=24598 name="cc-runtime" level="error" source="runtime" msg="Container ID (aa308727a8d19a046175fe86a117bcb27ba9ec4408ea6c07b145413f1f688691) does not exist"
time="2017-10-26T14:53:03.729032648-05:00" pid=24680 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae -uuid 63363161-3633-3431-6536-333337636134 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/7add7e0fc81bff3795f73e33d1720ecb91fd08a4a482ecfd26e838bfabd305f6/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 debug systemd.show_status=true systemd.log_level=debug init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae::off::]"
time="2017-10-26T14:54:22.189683922-05:00" pid=24883 name="cc-runtime" level="error" source="runtime" msg="Container c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae not ready or running, cannot send a signal"
time="2017-10-26T14:54:22.460205301-05:00" pid=24897 name="cc-runtime" level="error" source="runtime" msg="Container ID (c61a6341e6337ca404669a47c8fff5fe0412a130d250788f75ecae8cf389d4ae) does not exist"
time="2017-10-26T14:54:32.09023956-05:00" pid=24987 name="cc-runtime" level="info" source="virtcontainers" subsystem="qmp" msg="launching qemu with: [-name pod-fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d -uuid 66656432-3664-3734-3932-663630646464 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host -qmp unix:/run/virtcontainers/pods/fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d/monitor.sock,server,nowait -qmp unix:/run/virtcontainers/pods/fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d/ctrl.sock,server,nowait -m 2048M,slots=2,maxmem=16946M -smp 8,cores=8,threads=1,sockets=1 -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/696e2b9326f77e31283f05706000547051cf087da7dcb1cc5f00308d27beb59c/merged,security_model=none -device virtio-serial-pci,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/virtcontainers/pods/fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/clear-containers/clear-18400-containers.img,size=235929600 -device virtserialport,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch0,path=/run/virtcontainers/pods/fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d/hyper.sock,server,nowait -device virtserialport,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -chardev socket,id=charch1,path=/run/virtcontainers/pods/fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d/tty.sock,server,nowait -device virtio-9p-pci,fsdev=extra-9p-hyperShared,mount_tag=hyperShared -fsdev local,id=extra-9p-hyperShared,path=/tmp/hyper/shared/pods/fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d,security_model=none -device driver=virtio-net-pci,netdev=network-0,mac=02:42:ac:11:00:02 -netdev tap,id=network-0,ifname=tap0,downscript=no,script=no,vhost=on -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/clear-containers/vmlinuz-4.9.58-79.1.container -append root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k panic=1 console=hvc0 console=hvc1 initcall_debug iommu=off cryptomgr.notests net.ifnames=0 debug systemd.show_status=true systemd.log_level=debug init=/usr/lib/systemd/systemd systemd.unit=clear-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket ip=::::::fed26d7492f60dddc6adeeb624e7b1f1b89d21afc284e7a6ee0d98f04d8b0a0d::off::]"

Proxy logs
Recent proxy problems found in system journal:
time="2017-10-26T14:36:31.474990364-05:00" level=debug msg="{\\\"container\\\":\\\"9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110\\\",\\\"container-pid\\\":\\\"3\\\",\\\"level\\\":\\\"warning\\\",\\\"msg\\\":\\\"Container process no longer exists\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":190,\\\"time\\\":\\\"2017-10-26T19:36:31.45877852Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110
time="2017-10-26T14:36:31.475103337-05:00" level=debug msg="{\\\"container\\\":\\\"9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110\\\",\\\"container-pid\\\":\\\"3\\\",\\\"level\\\":\\\"warning\\\",\\\"msg\\\":\\\"Container process no longer exists\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":190,\\\"time\\\":\\\"2017-10-26T19:36:31.458949603Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110
time="2017-10-26T14:36:31.475530723-05:00" level=error msg="error serving client: write unix /var/run/clear-containers/proxy.sock->@: use of closed network connection" client=1598 name=cc-proxy pid=29499 source=proxy
time="2017-10-26T14:36:32.475605786-05:00" level=debug msg="{\\\"container-pid\\\":\\\"1\\\",\\\"error\\\":\\\"signal: killed\\\",\\\"level\\\":\\\"error\\\",\\\"msg\\\":\\\"Process wait failed\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":190,\\\"time\\\":\\\"2017-10-26T19:36:32.459355493Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110
time="2017-10-26T14:36:32.475802213-05:00" level=debug msg="{\\\"error\\\":\\\"EOF\\\",\\\"level\\\":\\\"info\\\",\\\"msg\\\":\\\"Sequence has been closed\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":190,\\\"sequence\\\":2,\\\"time\\\":\\\"2017-10-26T19:36:32.459587917Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110
time="2017-10-26T14:36:32.475924383-05:00" level=debug msg="{\\\"error\\\":\\\"EOF\\\",\\\"level\\\":\\\"info\\\",\\\"msg\\\":\\\"Sequence has been closed\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":190,\\\"sequence\\\":1,\\\"time\\\":\\\"2017-10-26T19:36:32.459773639Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110
time="2017-10-26T14:36:32.478377524-05:00" level=debug msg="{\\\"container\\\":\\\"pause-container\\\",\\\"container-pid\\\":\\\"1\\\",\\\"level\\\":\\\"warning\\\",\\\"msg\\\":\\\"Container process no longer exists\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":190,\\\"time\\\":\\\"2017-10-26T19:36:32.462238241Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110
time="2017-10-26T14:36:32.478398528-05:00" level=debug msg="{\\\"container\\\":\\\"pause-container\\\",\\\"container-pid\\\":\\\"1\\\",\\\"level\\\":\\\"warning\\\",\\\"msg\\\":\\\"Container process no longer exists\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":190,\\\"time\\\":\\\"2017-10-26T19:36:32.462286417Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=9a7d4f2bca340b476a6da991e6a93ab403ae3c3cda3431c83a42245a5acab110
time="2017-10-26T14:36:43.189145612-05:00" level=info msg="Signal(power failure,0,0)" client=1605 name=cc-proxy pid=29499 source=proxy
time="2017-10-26T14:36:44.188830482-05:00" level=debug msg="{\\\"error\\\":\\\"read /dev/ptmx: input/output error\\\",\\\"level\\\":\\\"info\\\",\\\"msg\\\":\\\"Sequence has been closed\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":193,\\\"sequence\\\":3,\\\"time\\\":\\\"2017-10-26T19:36:44.172771832Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247
time="2017-10-26T14:36:44.189394556-05:00" level=debug msg="{\\\"container-pid\\\":\\\"3\\\",\\\"error\\\":\\\"exit status 30\\\",\\\"level\\\":\\\"error\\\",\\\"msg\\\":\\\"Process wait failed\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":193,\\\"time\\\":\\\"2017-10-26T19:36:44.173029012Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247
time="2017-10-26T14:36:44.190019477-05:00" level=debug msg="{\\\"container\\\":\\\"dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247\\\",\\\"container-pid\\\":\\\"3\\\",\\\"level\\\":\\\"warning\\\",\\\"msg\\\":\\\"Container process no longer exists\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":193,\\\"time\\\":\\\"2017-10-26T19:36:44.174115065Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247
time="2017-10-26T14:36:44.190490592-05:00" level=debug msg="{\\\"container\\\":\\\"dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247\\\",\\\"container-pid\\\":\\\"3\\\",\\\"level\\\":\\\"warning\\\",\\\"msg\\\":\\\"Container process no longer exists\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":193,\\\"time\\\":\\\"2017-10-26T19:36:44.174379652Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247
time="2017-10-26T14:36:44.19058423-05:00" level=error msg="error serving client: write unix /var/run/clear-containers/proxy.sock->@: use of closed network connection" client=1605 name=cc-proxy pid=29499 source=proxy
time="2017-10-26T14:36:45.223761196-05:00" level=debug msg="{\\\"container-pid\\\":\\\"1\\\",\\\"error\\\":\\\"signal: killed\\\",\\\"level\\\":\\\"error\\\",\\\"msg\\\":\\\"Process wait failed\\\",\\\"name\\\":\\\"cc-agent\\\",\\\"pid\\\":193,\\\"time\\\":\\\"2017-10-26T19:36:45.207902546Z\\\"}" name=cc-proxy pid=29499 source=qemu vm=dfc2337b1a9ad97eab5bd9fdc339738bce978247e0a9cf4cc9aaa4f078a21247
time="2017-10-26T14:36:45.22420

cc shim logs shows that proxy return an error.
time="2017-10-26T14:55:07.392943628-0500" level="debug" pid=25034 function="send_proxy_message" line=300 source="shim" name="cc-shim" msg="Sending frame of type:0, opcode:6, payload:{\"signalNumber\": 28, \"rows\":0, \"columns\":0}"
time="2017-10-26T14:55:07.393403655-0500" level="debug" pid=25034 function="read_frame" line=495 source="shim" name="cc-shim" msg="Frame read - HeaderLength: 3, Version: 2, Payloadlen: 62, Type:1, Opcode: 6, Err:16"
time="2017-10-26T14:55:07.393418323-0500" level="debug" pid=25034 function="handle_proxy_message" line=737 source="shim" name="cc-shim" msg="Received frame with type: 1, opcode: 6"
time="2017-10-26T14:55:07.393442110-0500" level="error" pid=25034 function="handle_proxy_response" line=616 source="shim" name="cc-shim" msg="Error response received from proxy at /var/run/clear-containers/proxy.sock: {\"msg\":\"received SIGWINCH but terminal size is invalid (0,0)\"}"

cc-proxy is not allowing to send that signal because of its values:
https://github.com/clearcontainers/proxy/blob/master/proxy.go#L451

repo: clearcontainers/runtime


text:
"cast increases required alignment" warning

Hi,
This package failed to build for multiple architectures (mips*, armel, armhf, hppa, powerpcspe) with the following error:
result_stream.c: In function 'run_result_field':
result_stream.c:583:37: error: cast increases required alignment of target type [-Werror=cast-align]
const result_record_t *record = (const result_record_t *)self;
^
Bug with proposed solution is reported on Debian: https://bugs.debian.org/833900
Thanks,
Daniel

Hi @Deni90,
This is great! Thanks for finding that and also offering a fix! To merge it in, we just need to fix the checks that are failing the PR - which is just the missing CLA agreement. You can find that here: https://www.clahub.com/agreements/cleishm/libneo4j-client
Thanks again!
Cheers,
Chris

source: gharchive/pull-request

license_type: permissive

license_source: bigquery


text:
add 'extract local variable' feature

Extracts variable inside functions:

Shortcut: ctrl+shift+1

Nice one. You're on fire :)

Closed?

sorry

repo: clemos/haxe-sublime-bundle


text:
chore(nextjs,clerk-js): Detect claimed keys and offer easy way to copy them

Description
Improve the Keyless mode prompt with a button that will move the generated keys from the hidden .clerk/ directory inside .env.development.local or .env.local.

Checklist

[ ] pnpm test runs as expected.
[ ] pnpm build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Closing this as we decided to prompt users to manually move copy the keys from the dashboard.

repo: clerk/javascript

license: MIT

license_source: github-api


text:
integrate check license into mvn verify

for elastic/elasticsearch#11705

that's the last time I try to contribute to your projects man - I don't like this perl stuff anyways :P

haha i didn't even see this :)

repo: clintongormley/elasticsearch


text:
Running Container Mode, How to add the new Cloud Driver Library

What would you like to be enhanced

Spider를 Container Mode로 운영할 경우
built-in으로 제공하는 Cloud Driver 외에 신규 Cloud Driver library 추가 가능하도록 개선 필요

[Plan]

컨테이너 시작시에 ./user-cloud-driver-libs를 volume mount into Container

신규 추가 Cloud Driver Library를 local:.../user-cloud-driver-libs에 복사
Cloud Driver 등록 후 사용

신규 path를 인식하도록 Server 코드 반영 등 필요

컨테이너 시작시에 ./user-cloud-driver-libs를 volume mount into Container

신규 추가 Cloud Driver Library를 local:.../user-cloud-driver-libs에 복사

CB Helm chart 로 실행 시에는 적용하기 어려운 부분입니다.. 😢

컨테이너(를 이용한 CB-Spider) 빌드 환경과
따로 빌드한 드라이버의 빌드 환경이 같지 않은 경우도 있을 수 있어서,
https://github.com/cloud-barista/cb-spider/issues/343#issuecomment-814983514

[CLOUD-BARISTA].[ERROR]: 2021-04-07 08:04:26 CloudDriverHandler.go:251, github.com/cloud-barista/cb-spider/cloud-control-manager.getCloudDriver() - plugin.Open: plugin.Open("/root/go/src/github.com/cloud-barista/cb-spider/cloud-driver-libs/cloudtwin-driver-v1.0"): plugin was built with a different version of package golang.org/x/sys/internal/unsafeheader

추후, 이 현상이 발생하는지 확인이 필요할 것으로 보입니다. 😊

@jihoon-seo

관련 이슈 및 현황을 아래 링크에 매달아 주세요.
함께 고민해보죠.

https://github.com/cloud-barista/cb-spider/issues/468

source: gharchive/issue

authors: jihoon-seo powerkimhub

repo: cloud-barista/cb-spider


text:
fix: coremark-pro flag

Description
Bug where the single character flag was -worker instead of -w for CoreMark-Pro

Can one of the admins verify this patch?

authors: comet-perf-ci ewchong

repo: cloud-bulldozer/benchmark-wrapper


text:
Initialize custom_checks_status

We've recently hit this issue:
2021-03-12 16:32:40,706 [INFO] Exception: local variable 'custom_checks_status' referenced before assignment

The variable custom_checks_status needs to be initialized before so that we don't hang when custom_checks is disabled.

Can one of the admins verify this patch?

repo: cloud-bulldozer/cerberus


text:
App completion

ISSUE #155
Now vela can auto-completion Application names:
# app
$ vela app:delete [tab]
frontend   frontend1  frontend2
$ vela app:status [tab]
frontend   frontend1  frontend2
$ vela app:show [tab]
frontend   frontend1  frontend2
# traits
$ vela manualscaler [tab]
frontend   frontend1  frontend2
$ manualscaler:detach [tab]
frontend   frontend1  frontend2

Signed-off-by: guoxudong sunnydog0826@gmail.com

@sunny0826 As the cli style changes, could you please just command auto-completion? Thanks.

Maybe wait until the feature is stable before adding custom completions

repo: cloud-native-application/RudrX


text:
migration plan for IBM Cloud modules to terraform-ibm-modules

Modules Testing files refer these variables - https://github.com/cloud-native-toolkit/action-module-verify/blob/main/env/ibm_ocp48/terraform.tfvars

Re-grouped the services by category:
Account

[X] https://github.com/cloud-native-toolkit/terraform-ibm-resource-group
[X] https://github.com/cloud-native-toolkit/terraform-ibm-access-group
[X] https://github.com/cloud-native-toolkit/terraform-ibm-account-users
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-add-access-group-users
[X] https://github.com/cloud-native-toolkit/terraform-ibm-account-access-group
[X] https://github.com/cloud-native-toolkit/terraform-ibm-iam-service-authorization
[X] https://github.com/cloud-native-toolkit/terraform-ibm-onboard-fs-account
[X] ~https://github.com/cloud-native-toolkit/terraform-ibm-fs-access-groups~

VPC / VSI

[ ] ~https://github.com/cloud-native-toolkit/terraform-ibm-vpc-vpn~
[X] https://github.com/cloud-native-toolkit/terraform-ibm-ocp-vpc
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vpc-ssh
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vpc
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-vpe-gateway
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vpc-subnets
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vpc-gateways
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-vpn-server
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-iks-vpc [ Need Cluster ]
[ ] ~https://github.com/cloud-native-toolkit/terraform-ibm-vsi-openpages~
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vsi-proxy
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vpc-load-balancer
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vpc-vsi
[X] https://github.com/cloud-native-toolkit/terraform-ibm-flow-log
[X] https://github.com/cloud-native-toolkit/terraform-ibm-vpn-gateway
[ ] https://github.com/cloud-native-toolkit/terraform-vsi-bastion

Gateway

[ ] https://github.com/cloud-native-toolkit/terraform-ibm-transit-gateway

Object Storage

[X] https://github.com/cloud-native-toolkit/terraform-ibm-object-storage
[X] https://github.com/cloud-native-toolkit/terraform-ibm-object-storage-bucket

Event Stream

[X] https://github.com/cloud-native-toolkit/terraform-ibm-event-streams
[X] https://github.com/cloud-native-toolkit/terraform-ibm-event-streams-topic

KMS

[ ] https://github.com/cloud-native-toolkit/terraform-ibm-container-registry
[X] https://github.com/cloud-native-toolkit/terraform-ibm-kms
[X] https://github.com/cloud-native-toolkit/terraform-ibm-kms-key

Deprecated Services from Sep 30th

[X] https://github.com/cloud-native-toolkit/terraform-ibm-cert-manager
[X] https://github.com/cloud-native-toolkit/terraform-ibm-cert-manager-cert

Storage

[  ]~https://github.com/cloud-native-toolkit/terraform-ibm-portworx~ (Moved back and Archived )
[X] https://github.com/cloud-native-toolkit/terraform-ibm-db2-warehouse
[X] https://github.com/cloud-native-toolkit/terraform-ibm-etcd
[X] https://github.com/cloud-native-toolkit/terraform-ibm-mongodb

HPCS

[ ] https://github.com/cloud-native-toolkit/terraform-ibm-hpcs
[X] https://github.com/cloud-native-toolkit/terraform-ibm-hpdbaas-mongodb
[X] https://github.com/cloud-native-toolkit/terraform-ibm-hpcs-initialization
[X] https://github.com/cloud-native-toolkit/terraform-ibm-hpdbaas-postgresql

Cluster config/software

[ ] https://github.com/cloud-native-toolkit/terraform-ibm-log-analysis-bind
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-cloud-monitoring-bind
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-cloud-operator

Cloud Services

[X] https://github.com/cloud-native-toolkit/terraform-ibm-watson-studio
[X] https://github.com/cloud-native-toolkit/terraform-ibm-log-analysis
[X] https://github.com/cloud-native-toolkit/terraform-ibm-cloud-monitoring
[X] https://github.com/cloud-native-toolkit/terraform-ibm-key-protect
[X] https://github.com/cloud-native-toolkit/terraform-ibm-appid
[X] https://github.com/cloud-native-toolkit/terraform-ibm-activity-tracker
[X] https://github.com/cloud-native-toolkit/terraform-ibm-redis
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-image-registry

More Work TBD

[ ] https://github.com/cloud-native-toolkit/terraform-ibm-watson-assistant [ Module is just single main.tf]
[ ] https://github.com/cloud-native-toolkit/terraform-ibm-vpc-hpvsi [ Compile Error in initial version ]

As per discussion,

Sean will do first module and create docs for process.  I am going to follow and repeat/rinse for above list.
Create the TASK if the module takes more than hour(s)

Snippet of process

Move the module from our catalog to IBM target repo via Github Settings
Update the catalog.yaml ID of the module to include the target repo
Make sure the module name have prefix "Toolkit" or "TZ" as well as it does not conflict with target repo since module names already exist
Validate the Github action workflow testing is completed after move to target repo.

Box note from Sean to support this migration

Validated as well as expanded additional information during my 1st journey.
https://ibm.ent.box.com/notes/1001181926527?s=5tmk9s3houumkvl1xyz8bvp765adpxm3

2 modules are migrated as well as validated from BOM

Next Step:

Proposed maintenance window 12-4 pm CST to do this migration activity.
Migration module is On Hold till we get consensus across from consumers to perform this migration activity.

@balasgit can we please progress this work and not limited to 4hr use the whole 8hr CST window but over communicate what is moving and when, the quicker we get this done, the easier it is for us to move onto the next task

Absolutely @mjperrins we can always try to improve to get it done !! will do best :-)

Migration error for IBM cloud monitoring module which requires code fix..

Mongo DB expects the resource group to be present in the Target Cloud Account which i dont have access

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-mongodb/runs/8042605124?check_suite_focus=true

Updates

Re-grouped the services by category which will be easier to come up with strategy such as resources required on the Target Cloud Account which will expedite our migration approach since majority of time spent on.
Our module README needs to be updated with the resources required on target cloud account as Pre-req which is challenging to do reverse engineering and identify.

Released the Mongodb module
Working on the weird issue Cluster not found..

Verified the VPC module build test and here are tickets which am planned to work today. I have just captured issues but didn't had a time to analyze yet.
VPC Build Test
[ ] https://github.com/cloud-native-toolkit/software-everywhere/issues/475
[X] https://github.com/cloud-native-toolkit/software-everywhere/issues/474
[ ] https://github.com/cloud-native-toolkit/software-everywhere/issues/473
[ ] https://github.com/cloud-native-toolkit/software-everywhere/issues/472
[X] https://github.com/cloud-native-toolkit/software-everywhere/issues/471
[X] https://github.com/cloud-native-toolkit/software-everywhere/issues/470
[ ] https://github.com/cloud-native-toolkit/software-everywhere/issues/469
[X] https://github.com/cloud-native-toolkit/software-everywhere/issues/465
[ ] https://github.com/cloud-native-toolkit/software-everywhere/issues/464

End-2-End Testing 4 migrated modules (https://ibm-cloudplatform.slack.com/archives/C039DRPL77U/p1662479225843029)

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-transit-gateway/issues/9
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-container-registry/issues/12
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-object-storage-bucket/issues/34

40 modules are migrated
Migrated Repo
https://github.com/orgs/terraform-ibm-modules/repositories?q=terraform-ibm-toolkit
Catalog Build
https://github.com/cloud-native-toolkit/software-everywhere/blob/main/catalog.yaml
Addressed couple of issues but some pending issues requires more debugging which I will do tomorrow
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-portworx/issues/20
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-kms-key/issues/20
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-cert-manager/issues/9
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-db2-warehouse/issues/5 [ error happens during destroy after merging with main. Test re-running now as I share update in slack )
Ask:
Pls open issue at the module if you face errors as I will check first thing tomorrow morning.

Build Errors

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-hpcs/issues/24
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-hpcs-initialization/issues/9
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-hpdbaas-mongodb/issues/11
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-hpcs-initialization/issues/10
https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-image-registry/issues/36

Remaining Modules

Build Error
-[ ]  https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-iks-vpc/issues/6

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-add-access-group-users/issues/6

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-vpe-gateway/issues/25

https://github.com/cloud-native-toolkit/software-everywhere/issues/472

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-container-registry/issues/12

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-hpcs/issues/24

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-image-registry/issues/36

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-iks-vpc/issues/6

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-log-analysis-bind/issues/40

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-cloud-monitoring-bind/issues/25

https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-cloud-operator/issues/5

@seansund
We need to have cluster for these modules test @ Golden Eye.
Test Cases used are "OCP4_latest" , "OCP_VPC" , ocp44_vpc in the Workflow file as result it returns Cluster not found for these modules.
In Cluster installation
-[ ] https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-log-analysis-bind/issues/40
-[ ] https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-cloud-monitoring-bind/issues/25
-[ ] https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-cloud-operator/issues/5
-[ ] https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-image-registry/issues/37
-[ ] https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-iks-vpc/issues/6

Will discuss cluster pre-req on Thrusday office hours since Tues office hours didn't started.

For the in-cluster installation modules, we need to update the tests to provision a new cluster. I've already made the changes for the log-analysis-bind and cloud-monitoring-bind modules. You can use this commit as a template for the other ones - https://github.com/terraform-ibm-modules/terraform-ibm-toolkit-cloud-monitoring-bind/pull/24/commits/465f6b0e155e738d70740c9177ad8fc4d1889985

authors: balasgit mjperrins seansund triceam


text:
Resource Group deletion failing on IBM Cloud

deletion failing:

https://github.com/IBM/automation-ibmcloud-infra-openshift/actions/runs/3414989859
https://github.com/IBM/ibm-cloud-reference-architectures/actions/runs/3416729407/jobs/5694750893

│   Delete failed. Sleeping for 30 seconds
│     HTTP_STATUS: 500
│     RESULT: {"trace":"e38fcf71c2754fef8bb4a6035a1d90ca","errors":[{"code":"NOT_EMPTY","message":"Resource Group with instances cannot be deleted.","more_info":"n/a"}]}
│ Resource group deletion failed with HTTP Status: 500

Seeing this in both:

https://github.com/IBM/automation-ibmcloud-infra-openshift
https://github.com/IBM/ibm-cloud-reference-architectures

The cli is showing the resource group is empty, but deletion from the CLI fails too:
ic resource service-instances -g fs-800c2-common --type=all
Retrieving instances with all types in resource group fs-800c2-common in all locations under account Cloud-Native Squad 02 as rich_ehrhardt@au1.ibm.com...
OK
No service instance found.
➜  ibm git:(main) ic resource group-delete fs-800c2-common
Really delete the resource group fs-800c2-common? [y/N]> y
Deleting resource group fs-800c2-common under account 9d1cb8e6f75e4e41aab0e8df150e643a as rich_ehrhardt@au1.ibm.com...
FAILED
The following error(s) occurred:
Resource Group with instances cannot be deleted.

Trace ID: 8c12502ba8ed41bd9f8a51115d817299

Started thread in #console-issues slack channel:
https://ibm-cloudplatform.slack.com/archives/C6EA537U3/p1668005486303649

More discussion here:
https://ibm-cloudplatform.slack.com/archives/C2FCRK99V/p1668005806520609
This is happening b/c:

There was a bug patched in the DELETE RG path where it was letting the delete happen even though there were instances that were in reclamation.

I'm pretty sure this was the original issue that caused our ghost resources that had to be cleaned up using support tickets.
As a workaround, we need to force immediate reclamation before we delete the resource group.  (Default reclamation expiration is 7 days).
So:

Get all resource instances using https://cloud.ibm.com/apidocs/resource-controller/resource-controller#list-resource-instances
For all resource instances where state is pending reclamation, force immediate reclamation using https://cloud.ibm.com/apidocs/resource-controller/resource-controller#run-reclamation-action
Poll until no more resources pending reclamation.

I was thinking we could add a flag to the resource group module. By default we would not force immediate reclamation, but for all automated testing, we should.

The changes that caused this issue are being reverted until they "find an option less impactful".
Additional discussion:

Closing.  This was resolved by the Cloud team.


text:
bad link in readme

The ipmi_exporter github repo has moved to https://github.com/prometheus-community/ipmi_exporter.

This role has been deprecated in favor of a the prometheus-community/ansible collection.

authors: SuperQ rstory


text:
Fix role with restrictive UMASK

When a system is configured with a restrictive UMASK (ex 027)  some actions fails because the default permissions prevent the file downloaded to be opened.

This role has been deprecated in favor of a the prometheus-community/ansible collection.

authors: SuperQ bmillemathias

repo: cloudalchemy/ansible-pushgateway


text:
🛑 myrepublic.co.id is down

In 3f24f38, myrepublic.co.id (https://myrepublic.co.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: myrepublic.co.id is back up in 77bcfbc.

repo: cloudbip/upptime


text:
🛑 cbn.id is down

In fe42405, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 669e7bf after 13 minutes.


text:
🛑 flazznetworks.com is down

In 2a71ff6, flazznetworks.com (https://flazznetworks.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: flazznetworks.com is back up in 7547076 after 9 minutes.


text:
🛑 cbn.id is down

In 1f6ec0f, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 164169b.


text:
🛑 member.idwebhost.com is down

In 356ce60, member.idwebhost.com (https://member.idwebhost.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: member.idwebhost.com is back up in e3fab46.


text:
🛑 cbn.id is down

In 0a0e7fb, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in cba5d8d.


text:
Unable to check status of build if inprogress or is stucked using external webpack

Which Cloudflare product(s) does this pertain to?
Workers
Subject Matter
How to check build logs
Content Location
We are integrating  an application with cloud flare but its stucking build may be we are not sure even if build is running.

Additional information
Please check the wrangler.toml file

Hi @VarunTwri, if this is a new project, you may want to look at https://github.com/cloudflare/wrangler2 - a lot of the configuration from wrangler 1 is no longer required, and should be easier to get started.
Closing this issue as unrelated to cloudflare-docs.

authors: VarunTwri rozenmd

repo: cloudflare/cloudflare-docs


text:
Floating menu / sidebar

The current Cloudflar API documentation looks great. I like the sidebar being seperate.
Currenty with doca, when I scorll, I then can't see the menu. A UI thing for sure.

I'll add to this, it would be a bonus to have the sidebar highlight the section you're currently viewing, a la boostrap documentation.

I want to get the default theme and the Cloudflare theme to functional parity.  We obviously don't want the default to carry Cloudflare branding, but I would like for the general UX to be the same.

Right, that makes sense. I actually think that a seperated section with its own scrollbar works better... I sometimes find the bootstrap documentation menu to be annoying on smaller screens, unable to reach the lower parts when a section is expanded.

@Relequestual when you say separated section do you mean like the sidebar for https://api.cloudflare.com/ or something different?

Yes, exactly that. I mean, having its own scrollbar. The Cloudflare API doocs look really neat. My only slight problem is that when scrolling the main docs, if the menu is scrolled to a different section, it is not refocused.

Closing this because the above PR is merged. New theme!

authors: Relequestual handrews

repo: cloudflare/doca


text:
/_oauth is a 403 error screen

after a successful google login I am redirected back to my app where the page throws a 403 error

2019/11/11 05:45:46 [error] 11159#11159: *308 lua entry thread aborted: runtime error: /usr/local/openresty/nginx/access.lua:65: attempt to index upvalue 'domain' (a nil value)
This error is being thrown when I add a resolver 8.8.8.8 to the config

https://github.com/cloudflare/nginx-google-oauth/pull/52 should fix the "upvalue domain" error.

authors: riking samueljim

repo: cloudflare/nginx-google-oauth


text:
resource/cloudflare_record: handle import for data

Fixes the read method to pull from the remote API instead of the local configuration since on Import, the local configuration will be empty.
Fixes #1714

acceptance tests all passing
TF_ACC=1 go test $(go list ./...) -v -run "^TestAccCloudflareRecord_" -count 1 -parallel 1 -timeout 120m -parallel 1
?       github.com/cloudflare/terraform-provider-cloudflare     [no test files]
=== RUN   TestAccCloudflareRecord_ImportBasic
--- PASS: TestAccCloudflareRecord_ImportBasic (11.86s)
=== RUN   TestAccCloudflareRecord_ImportSRV
--- PASS: TestAccCloudflareRecord_ImportSRV (12.70s)
=== RUN   TestAccCloudflareRecord_Basic
=== PAUSE TestAccCloudflareRecord_Basic
=== RUN   TestAccCloudflareRecord_CaseInsensitive
=== PAUSE TestAccCloudflareRecord_CaseInsensitive
=== RUN   TestAccCloudflareRecord_Apex
=== PAUSE TestAccCloudflareRecord_Apex
=== RUN   TestAccCloudflareRecord_LOC
=== PAUSE TestAccCloudflareRecord_LOC
=== RUN   TestAccCloudflareRecord_SRV
=== PAUSE TestAccCloudflareRecord_SRV
=== RUN   TestAccCloudflareRecord_CAA
=== PAUSE TestAccCloudflareRecord_CAA
=== RUN   TestAccCloudflareRecord_Proxied
=== PAUSE TestAccCloudflareRecord_Proxied
=== RUN   TestAccCloudflareRecord_Updated
=== PAUSE TestAccCloudflareRecord_Updated
=== RUN   TestAccCloudflareRecord_typeForceNewRecord
=== PAUSE TestAccCloudflareRecord_typeForceNewRecord
=== RUN   TestAccCloudflareRecord_hostnameForceNewRecord
=== PAUSE TestAccCloudflareRecord_hostnameForceNewRecord
=== RUN   TestAccCloudflareRecord_CreateAfterManualDestroy
=== PAUSE TestAccCloudflareRecord_CreateAfterManualDestroy
=== RUN   TestAccCloudflareRecord_TtlValidation
=== PAUSE TestAccCloudflareRecord_TtlValidation
=== RUN   TestAccCloudflareRecord_ExplicitProxiedFalse
=== PAUSE TestAccCloudflareRecord_ExplicitProxiedFalse
=== RUN   TestAccCloudflareRecord_MXWithPriorityZero
=== PAUSE TestAccCloudflareRecord_MXWithPriorityZero
=== RUN   TestAccCloudflareRecord_TtlValidationUpdate
=== PAUSE TestAccCloudflareRecord_TtlValidationUpdate
=== RUN   TestAccCloudflareRecord_HTTPS
=== PAUSE TestAccCloudflareRecord_HTTPS
=== CONT  TestAccCloudflareRecord_Basic
--- PASS: TestAccCloudflareRecord_Basic (8.89s)
=== CONT  TestAccCloudflareRecord_typeForceNewRecord
--- PASS: TestAccCloudflareRecord_typeForceNewRecord (16.07s)
=== CONT  TestAccCloudflareRecord_HTTPS
--- PASS: TestAccCloudflareRecord_HTTPS (8.90s)
=== CONT  TestAccCloudflareRecord_TtlValidationUpdate
--- PASS: TestAccCloudflareRecord_TtlValidationUpdate (11.73s)
=== CONT  TestAccCloudflareRecord_MXWithPriorityZero
--- PASS: TestAccCloudflareRecord_MXWithPriorityZero (8.40s)
=== CONT  TestAccCloudflareRecord_ExplicitProxiedFalse
--- PASS: TestAccCloudflareRecord_ExplicitProxiedFalse (21.22s)
=== CONT  TestAccCloudflareRecord_TtlValidation
--- PASS: TestAccCloudflareRecord_TtlValidation (3.44s)
=== CONT  TestAccCloudflareRecord_CreateAfterManualDestroy
--- PASS: TestAccCloudflareRecord_CreateAfterManualDestroy (18.55s)
=== CONT  TestAccCloudflareRecord_hostnameForceNewRecord
--- PASS: TestAccCloudflareRecord_hostnameForceNewRecord (21.38s)
=== CONT  TestAccCloudflareRecord_SRV
--- PASS: TestAccCloudflareRecord_SRV (8.79s)
=== CONT  TestAccCloudflareRecord_Updated
--- PASS: TestAccCloudflareRecord_Updated (15.63s)
=== CONT  TestAccCloudflareRecord_Proxied
--- PASS: TestAccCloudflareRecord_Proxied (8.55s)
=== CONT  TestAccCloudflareRecord_CAA
--- PASS: TestAccCloudflareRecord_CAA (15.15s)
=== CONT  TestAccCloudflareRecord_Apex
--- PASS: TestAccCloudflareRecord_Apex (8.72s)
=== CONT  TestAccCloudflareRecord_LOC
--- PASS: TestAccCloudflareRecord_LOC (8.97s)
=== CONT  TestAccCloudflareRecord_CaseInsensitive
--- PASS: TestAccCloudflareRecord_CaseInsensitive (12.11s)
PASS
ok      github.com/cloudflare/terraform-provider-cloudflare/internal/provider   221.751s


text:
🚀 Feature Request: Env var mocking for Pages

Describe the solution
We should really add CF_PAGES and other env vars to pages dev (and if we add a build step)
this allows for a more realistic local dev and also helps for detections (like for SvelteKit'a auto adapter)

Related to https://github.com/cloudflare/workers-sdk/issues/5866

authors: WalshyDev petebacondarwin

repo: cloudflare/workers-sdk


text:
feat(collector-main): apply screen reactivation

To Reviewers

[ ] Skip (style, chore, ci ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[x] Feature improvement
[ ] Refactor
[ ] Others (performance improvement, CI/CD, etc.)

Affects to

[ ] Packages

[ ] core-lib
[ ] mirinae
[ ] etc

[ ] Apps

[ ] storybook
[x] web

Checklist

Did you check the lint and type?
Did you document the changes?

Changes in mirinae should be reflected in storybook.

Did you test the app after the package changes?

Description
SSIA

Desktop

Tablet

Mobile

Things to Talk About

Good. But I have a question. Using isMobile function, does it work responsively on desktop?

It works correctly even on desktop when you switch to mobile view using the device toolbar to confirm!

repo: cloudforet-io/console


text:
Support push to branch for multibranch

This PR adds support for put if multibranches are used (ie if the the branch param is not given). The push happens to the branch that was checked out, it uses the (existing) git config setting to find the correct branch.
I had to change the returned json by out: I needed to add :<branchname> to the version and am not sure what the side-effects of this are.

Thanks!

authors: jhunt msiegenthaler


text:
better error message from filter of API server

[#118614105]

@fraenkel Updated already.(1) Add message to NLS. (2) Format the code.

See tracker item for my comments.

authors: fraenkel qibobo

repo: cloudfoundry-incubator/app-autoscaler


text:
IMP Desired Manifest with resolved variables

Hi, @viovanov
As we talked today, variable generation(Variables are replaced by a Job that runs the operator's image) should be done before variable interpolation. So variable interpolation should replace old placeholders in job properties. And the controller can know what kind of variable it needs to mount.
Please review code and leave comments. I'll update code and relative test cases soon.
Best,
Edward

Hi, @viovanov. I updated code and implemented variable generation part. Please help to review.
Thanks!

repo: cloudfoundry-incubator/cf-operator


text:
cf-warden-diego failing state

Is this correct?
Deployment `cf-warden-diego'
+--------------------+---------+------------------+--------------+
| Job/index          | State   | Resource Pool    | IPs          |
+--------------------+---------+------------------+--------------+
| access_z1/0        | failing | access_z1        | 10.244.16.46 |
| brain_z1/0         | failing | brain_z1         | 10.244.16.6  |
| cc_bridge_z1/0     | failing | cc_bridge_z1     | 10.244.16.14 |
| cell_z1/0          | failing | cell_z1          | 10.244.16.10 |
| etcd_z1/0          | running | etcd_z1          | 10.244.16.2  |
| route_emitter_z1/0 | failing | route_emitter_z1 | 10.244.16.18 |
+--------------------+---------+------------------+--------------+

bosh cck cf-warden now brings it all up
Deployment `cf-warden-diego'
+--------------------+---------+------------------+--------------+
| Job/index          | State   | Resource Pool    | IPs          |
+--------------------+---------+------------------+--------------+
| access_z1/0        | running | access_z1        | 10.244.16.46 |
| brain_z1/0         | running | brain_z1         | 10.244.16.6  |
| cc_bridge_z1/0     | running | cc_bridge_z1     | 10.244.16.14 |
| cell_z1/0          | running | cell_z1          | 10.244.16.10 |
| etcd_z1/0          | running | etcd_z1          | 10.244.16.2  |
| route_emitter_z1/0 | running | route_emitter_z1 | 10.244.16.18 |
+--------------------+---------+------------------+--------------+

What does this mean?

Hi, @charyorde,
Can you provide any more information about the state of your local system before those bosh-lite 'VMs' started failing? Has this happened again since the first time you reported it? If you had other deployments, were they also failing in a similar way?
I've occasionally had problems with Virtualbox on OS X pausing the bosh-lite VM based on the system's energy conservation settings, such that the bosh-lite containers would fail to be reported as running after the system awoke and resumed the VM. A bosh cck would typically bring them back.
Thanks,
Eric

Closing this. This occurred just after I deployed diego. At that moment, I didn't understand how the diego deployment was going to work. So when diego was failing, I didn't realize that diego is dependent on some cf-warden components. Hence, I needed to check the cf-warden VMs first.

authors: charyorde ematpl

repo: cloudfoundry-incubator/diego-release