fluentd stock image in 2023.2 will not start

[Noel Ashford]

logs show this as the error:

++ [[ fluentd:kolla != \f\l\u\e\n\t\d\:\k\o\l\l\a ]]
Running command: 'td-agent -c /etc/td-agent/td-agent.conf -o /var/log/kolla/fluentd/fluentd.log'
+ echo 'Running command: '\''td-agent -c /etc/td-agent/td-agent.conf -o /var/log/kolla/fluentd/fluentd.log'\'''
+ exec td-agent -c /etc/td-agent/td-agent.conf -o /var/log/kolla/fluentd/fluentd.log
/usr/local/bin/kolla_start: line 24: exec: td-agent: not found <--

root@5net:~# docker container ls -a | grep fluentd
b5b06e49c278 quay.io/openstack.kolla/fluentd:2023.2-ubuntu-jammy "dumb-init --single-…" 2 minutes ago Exited (127) 9 seconds ago fluentd

This is stop out of the box, un-changed. I have tried with images from 17.1-17.3, consistent issue. How can this be fixed? I saw in another thread someone saying that td-agent was renamed to fluentd perhaps but that it was never fixed to reflect this elsewhere.

Can it be fixed on the fly? If so, exactly how (full instructions as the container will not start) & also, how can we get this fixed in 2023.2. Side note, when is 2024.1 coming out for kolla and is this fixed in it ?

[Russell Tweed (russell-tweed)]

Guessing it was something missed in https://review.opendev.org/c/openstack/kolla/+/894948

Interestingly, going back to the 2023.1 image (and thus td-agent v4) appears to work, provided you link /usr/sbin/td-agent to /usr/sbin/fluentd - otherwise you have the exact opposite problem of td-agent then not being found. :)

[Travis Best (tb2097)]

I believe this bug was introduced somewhat more recently then that review. I have a test deploy that was working from ~March, however I had wiped the dev environment and I don't have the image ID. I was utilizing 2023.2-rocky-9.

This also seems to be affecting the master branch as well. Any documentation on how to manually update the config to get 2023.2 or master working until a proper fix is in place would be appreciated.

[Noel Ashford (nashford77)]

+1 - please advise how to manually fix this for now

On Tue, Apr 30, 2024, 9:25 PM Travis Best <email address hidden>
wrote:

> I believe this bug was introduced somewhat more recently then that
> review. I have a test deploy that was working from ~March, however I had
> wiped the dev environment and I don't have the image ID. I was
> utilizing 2023.2-rocky-9.
>
> This also seems to be affecting the master branch as well. Any
> documentation on how to manually update the config to get 2023.2 or
> master working until a proper fix is in place would be appreciated.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2061265
>
> Title:
> fluentd stock image in 2023.2 will not start
>
> Status in kolla-ansible:
> New
>
> Bug description:
> logs show this as the error:
>
> ++ [[ fluentd:kolla != \f\l\u\e\n\t\d\:\k\o\l\l\a ]]
> Running command: 'td-agent -c /etc/td-agent/td-agent.conf -o
> /var/log/kolla/fluentd/fluentd.log'
> + echo 'Running command: '\''td-agent -c /etc/td-agent/td-agent.conf -o
> /var/log/kolla/fluentd/fluentd.log'\'''
> + exec td-agent -c /etc/td-agent/td-agent.conf -o
> /var/log/kolla/fluentd/fluentd.log
> /usr/local/bin/kolla_start: line 24: exec: td-agent: not found <--
>
>
> root@5net:~# docker container ls -a | grep fluentd
> b5b06e49c278 quay.io/openstack.kolla/fluentd:2023.2-ubuntu-jammy
> "dumb-init --single-…" 2 minutes ago Exited
> (127) 9 seconds ago fluentd
>
>
> This is stop out of the box, un-changed. I have tried with images from
> 17.1-17.3, consistent issue. How can this be fixed? I saw in another thread
> someone saying that td-agent was renamed to fluentd perhaps but that it
> was never fixed to reflect this elsewhere.
>
> Can it be fixed on the fly? If so, exactly how (full instructions as
> the container will not start) & also, how can we get this fixed in
> 2023.2. Side note, when is 2024.1 coming out for kolla and is this
> fixed in it ?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kolla-ansible/+bug/2061265/+subscriptions
>
>

[kyle (kyle233)]

One action that is currently available is to replace the image tag, for example, if version 2023.1 is available, replace 2023.1 with your own target version.

docker tag xxx/openstack.kolla/fluentd:2023.1-rocky-9 xxx/quay/openstack.kolla/fluentd:master-rocky-9

[Noel Ashford (nashford77)]

I had considered that but I meant to fix the 2023.2 image.

On Thu, May 2, 2024, 9:01 PM kyle <email address hidden> wrote:

> One action that is currently available is to replace the image tag, for
> example, if version 2023.1 is available, replace 2023.1 with your own
> target version.
>
>
> docker tag xxx/openstack.kolla/fluentd:2023.1-rocky-9
> xxx/quay/openstack.kolla/fluentd:master-rocky-9
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2061265
>
> Title:
> fluentd stock image in 2023.2 will not start
>
> Status in kolla-ansible:
> New
>
> Bug description:
> logs show this as the error:
>
> ++ [[ fluentd:kolla != \f\l\u\e\n\t\d\:\k\o\l\l\a ]]
> Running command: 'td-agent -c /etc/td-agent/td-agent.conf -o
> /var/log/kolla/fluentd/fluentd.log'
> + echo 'Running command: '\''td-agent -c /etc/td-agent/td-agent.conf -o
> /var/log/kolla/fluentd/fluentd.log'\'''
> + exec td-agent -c /etc/td-agent/td-agent.conf -o
> /var/log/kolla/fluentd/fluentd.log
> /usr/local/bin/kolla_start: line 24: exec: td-agent: not found <--
>
>
> root@5net:~# docker container ls -a | grep fluentd
> b5b06e49c278 quay.io/openstack.kolla/fluentd:2023.2-ubuntu-jammy
> "dumb-init --single-…" 2 minutes ago Exited
> (127) 9 seconds ago fluentd
>
>
> This is stop out of the box, un-changed. I have tried with images from
> 17.1-17.3, consistent issue. How can this be fixed? I saw in another thread
> someone saying that td-agent was renamed to fluentd perhaps but that it
> was never fixed to reflect this elsewhere.
>
> Can it be fixed on the fly? If so, exactly how (full instructions as
> the container will not start) & also, how can we get this fixed in
> 2023.2. Side note, when is 2024.1 coming out for kolla and is this
> fixed in it ?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kolla-ansible/+bug/2061265/+subscriptions
>
>