Open Stack

So the logs that are needed are actually a tgz file that is uploaded
from the running agent which generated the error to the conductor. The
agent packages the files, and uploads a single file with it's UUID in
the filename to the filesystem. Typically they would be in something
like /var/log/containers/ironic/deploy_logs or something along those
lines.

On Sat, Jan 23, 2021 at 2:55 AM Ruslanas Gžibovskis <ruslanas at lpic.lt> wrote:
>
> hmmmm, I will try to catch it.
>
> I have setup rsyslog to send logs to my undercloud...
> This is what I received from remote side.
>
> it's rebooting after unsuccessful boot, so I cannot get final version in one file...
>
> On Sat, 23 Jan 2021 at 00:46, Julia Kreger <juliaashleykreger at gmail.com> wrote:
>>
>> Umm, wow. That is a new one.
>>
>> Any chance you can post or supply the entire ramdisk log that would
>> have been uploaded to ironic?
>>
>> On Fri, Jan 22, 2021 at 3:02 PM Ruslanas Gžibovskis <ruslanas at lpic.lt> wrote:
>> >
>> > Hi all,
>> >
>> > I am trying to build some cloud again and failing with [1]. I think this is a most critical line. It fails during GRUB2 deployment on overcloud image, I believe main error message is: mount: only root can do that. I used the following steps to create image:
>> >
>> > cp -ar /etc/yum.repos.d repos
>> > # enable: repos/CentOS-HA.repo
>> > sed -i "s/enabled=0/enabled=1/g" repos/CentOS-Linux-HighAvailability.repo
>> > sed -i "s/gpgcheck=1/gpgcheck=0/g" repos/*repo
>> > export DIB_YUM_REPO_CONF="$(ls $(pwd)/repos/*repo)"
>> > export STABLE_RELEASE="ussuri"
>> > source /home/stack/stackrc
>> > mkdir /home/stack/images
>> > cd /home/stack/images
>> > openstack overcloud image build --config-file /home/stack/overcloud-images-python3.yaml
>> > openstack overcloud image upload --update-existing
>> > # openstack overcloud node configure --all-manageable
>> >
>> > overcloud-images-python3.yaml file content can be found here [2], just added additional packages, such as tcpdump, iperf, iptraf and so on...
>> > And steps from link [3] to set root pass to troubleshoot if needed.
>> >
>> > any thoughts? Maybe there were some changes recently (from 22 of December) PRevious images from there. Thank you for your thoughts and attention.
>> >
>> > [1] http://paste.openstack.org/show/GDYriAXxQniZTPQGJGbH/
>> > [2] http://paste.openstack.org/show/2tkVFdwSZ0QMjoJKmOrm/
>> > [3] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/partner_integration/index#qcow_setting_the_root_password
>> >
>> >
>> > --
>> > Ruslanas Gžibovskis
>> > +370 6030 7030
>
>
>
> --
> Ruslanas Gžibovskis
> +370 6030 7030