api error: failed to parse query parameter 'since'

[Alex-Izquierdo]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Podman api returns an error when k3d try to get the logs

failed to parse query parameter 'since': "1628092060.000000000": unable to interpret time value 

Steps to reproduce the issue:

1. install k3d

wget -q -O - https://raw.githubusercontent.com/rancher/k3d/main/install.sh | bash

2. try to create a cluster

k3d cluster create mytest --verbose

Describe the results you received:
k3d output:

DEBU[0001] Waiting for node k3d-mytest-server-0 to get ready (Log: 'k3s is up and running') 
ERRO[0001] Failed to get logs from node 'k3d-mytest-server-0' (container '9b869d678eca30914435bb9478e49f6e987c3a806c001a90b78fefe22050306a') 
ERRO[0001] Failed waiting for log message 'k3s is up and running' from node 'k3d-mytest-server-0' 
ERRO[0001] Failed Cluster Start: Failed to start server k3d-mytest-server-0: Node k3d-mytest-server-0 failed to get ready: Error response from daemon: failed to parse query parameter 'since': "1628092060.000000000": unable to interpret time value 
ERRO[0001] Failed to create cluster >>> Rolling Back    

podman logs:

level=info msg="Request Failed(Bad Request): failed to parse query parameter 'since': \"1628086821.000000000\": unable to interpret time value"

Describe the results you expected:
Create a k3s cluster without errors

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:      3.2.3
API Version:  3.2.3
Go Version:   go1.16.6
Built:        Mon Aug  2 21:39:21 2021
OS/Arch:      linux/amd64

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.21.3
  cgroupControllers: []
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.29-2.fc34.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.29, commit: '
  cpus: 12
  distribution:
    distribution: fedora
    version: "34"
  eventLogger: journald
  hostname: alextop
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.13.6-200.fc34.x86_64
  linkmode: dynamic
  memFree: 5032894464
  memTotal: 33377579008
  ociRuntime:
    name: crun
    package: crun-0.20.1-1.fc34.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.20.1
      commit: 0d42f1109fd73548f44b01b3e84d04a279e99d2e
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.9-1.fc34.x86_64
    version: |-
      slirp4netns version 1.1.8+dev
      commit: 6dc0186e020232ae1a6fcc1f7afbc3ea02fd3876
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.0
  swapFree: 8561881088
  swapTotal: 8589930496
  uptime: 9h 3m 11.45s (Approximately 0.38 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /home/alex/.config/containers/storage.conf
  containerStore:
    number: 4
    paused: 0
    running: 1
    stopped: 3
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/alex/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 26
  runRoot: /run/user/1000/containers
  volumePath: /home/alex/.local/share/containers/storage/volumes
version:
  APIVersion: 3.2.3
  Built: 1627933161
  BuiltTime: Mon Aug  2 21:39:21 2021
  GitCommit: ""
  GoVersion: go1.16.6
  OsArch: linux/amd64
  Version: 3.2.3

Package info (e.g. output of rpm -q podman or apt list podman):

podman-3.2.3-2.fc34.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):
Same version of k3d aganist docker works as expected.

[mheon]

@jwhonce PTAL

[cdoern]

I most recently modified the since/until code @mheon let me see if I broke something...

[cdoern]

This isn't explicitly a log issue but a ParseInputTime function issue. I actually do not think anything on our end is "broken" the time that k3d is passing to the api is not one of the supported time values. I guess we can add this format or convert? WDYT @jwhonce

[mheon]

If it works with Docker - and from the fact that K3D is passing it, I imagine it does - it should work with Podman.

[cdoern]

@mheon any idea what time format that is? I can just add that string as an example but for the test I would like to try a genuine time.

[matejvasek]

@cdoern I believe it's unix timestamp with fractional part

[matejvasek]

#11135