Skip to content

Conversation

@rcmadhankumar
Copy link
Contributor

No description provided.

bci-pushman pushed a commit that referenced this pull request Oct 17, 2025
@github-actions
Copy link

github-actions bot commented Oct 17, 2025

Created a staging project on OBS for 7: home:pushman:BCI:Staging:SLE-15-SP7:7-3054
Changes pushed to branch 7-3054 as commit 763f8c2d14ffb70c5db2357e5eac46604864600f
Build succeeded ✅

Build Results

Repository images in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for x86_64: current state: published
Build results:

package name status build log
389-ds-container ⛔ excluded live log

Repository images in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for aarch64: current state: published
Build results:

package name status build log
389-ds-container ⛔ excluded live log

Repository images in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for s390x: current state: published
Build results:

package name status build log
389-ds-container ⛔ excluded live log

Repository images in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for ppc64le: current state: published
Build results:

package name status build log
389-ds-container ⛔ excluded live log

Repository containerfile in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for x86_64: current state: published
Build results:

package name status build log
389-ds-container ✅ succeeded live log

Repository containerfile in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for aarch64: current state: published
Build results:

package name status build log
389-ds-container ✅ succeeded live log

Repository containerfile in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for s390x: current state: published
Build results:

package name status build log
389-ds-container ✅ succeeded live log

Repository containerfile in home:pushman:BCI:Staging:SLE-15-SP7:7-3054 for ppc64le: current state: published
Build results:

package name status build log
389-ds-container ✅ succeeded live log

Build succeeded ✅

To run BCI-tests against this PR, use the following command:

OS_VERSION=15.7 TARGET=custom BASEURL=registry.opensuse.org/home/pushman/bci/staging/sle-15-sp7/7-3054/ tox -- -n auto
The following images can be pulled from the staging project:
  • registry.opensuse.org/home/pushman/bci/staging/sle-15-sp7/7-3054/containerfile/suse/389-ds:latest

bci-pushman pushed a commit that referenced this pull request Oct 17, 2025
@github-actions
Copy link

github-actions bot commented Oct 17, 2025

Created a staging project on OBS for Tumbleweed: home:pushman:BCI:Staging:Tumbleweed:Tumbleweed-3054
Changes pushed to branch Tumbleweed-3054 as commit a1fcaf4e518cdbc7eb691b8ecfe350b10b1540ef
Build succeeded ✅

Build Results

Repository images in home:pushman:BCI:Staging:Tumbleweed:Tumbleweed-3054 for x86_64: current state: published
Build results:

package name status build log
389-ds-image ⛔ excluded live log

Repository images in home:pushman:BCI:Staging:Tumbleweed:Tumbleweed-3054 for aarch64: current state: published
Build results:

package name status build log
389-ds-image ⛔ excluded live log

Repository containerfile in home:pushman:BCI:Staging:Tumbleweed:Tumbleweed-3054 for x86_64: current state: published
Build results:

package name status build log
389-ds-image ✅ succeeded live log

Repository containerfile in home:pushman:BCI:Staging:Tumbleweed:Tumbleweed-3054 for aarch64: current state: published
Build results:

package name status build log
389-ds-image ✅ succeeded live log

Build succeeded ✅

To run BCI-tests against this PR, use the following command:

OS_VERSION=tumbleweed TARGET=custom BASEURL=registry.opensuse.org/home/pushman/bci/staging/tumbleweed/tumbleweed-3054/ tox -- -n auto
The following images can be pulled from the staging project:
  • registry.opensuse.org/home/pushman/bci/staging/tumbleweed/tumbleweed-3054/containerfile/opensuse/389-ds:latest

bci-pushman pushed a commit that referenced this pull request Oct 17, 2025
@github-actions
Copy link

github-actions bot commented Oct 17, 2025

Created a staging project on OBS for 16.0: home:pushman:BCI:Staging:16.0:16.0-3054
Changes pushed to branch 16.0-3054 as commit 5e6be09481d866d96e09f6f11d94a9b94d591622
Build succeeded ✅

Build Results

Repository containerkiwi in home:pushman:BCI:Staging:16.0:16.0-3054 for x86_64: current state: published
Build results:

package name status build log
389-ds-image ⛔ excluded live log

Repository containerkiwi in home:pushman:BCI:Staging:16.0:16.0-3054 for aarch64: current state: published
Build results:

package name status build log
389-ds-image ⛔ excluded live log

Repository containerkiwi in home:pushman:BCI:Staging:16.0:16.0-3054 for s390x: current state: published
Build results:

package name status build log
389-ds-image ⛔ excluded live log

Repository containerkiwi in home:pushman:BCI:Staging:16.0:16.0-3054 for ppc64le: current state: published
Build results:

package name status build log
389-ds-image ⛔ excluded live log

Repository containerfile in home:pushman:BCI:Staging:16.0:16.0-3054 for x86_64: current state: published
Build results:

package name status build log
389-ds-image ✅ succeeded live log

Repository containerfile in home:pushman:BCI:Staging:16.0:16.0-3054 for aarch64: current state: published
Build results:

package name status build log
389-ds-image ✅ succeeded live log

Repository containerfile in home:pushman:BCI:Staging:16.0:16.0-3054 for s390x: current state: published
Build results:

package name status build log
389-ds-image ✅ succeeded live log

Repository containerfile in home:pushman:BCI:Staging:16.0:16.0-3054 for ppc64le: current state: published
Build results:

package name status build log
389-ds-image ✅ succeeded live log

Build succeeded ✅

To run BCI-tests against this PR, use the following command:

OS_VERSION=16.0 TARGET=custom BASEURL=registry.opensuse.org/home/pushman/bci/staging/16.0/16.0-3054/ tox -- -n auto
The following images can be pulled from the staging project:
  • registry.opensuse.org/home/pushman/bci/staging/16.0/16.0-3054/containerfile/suse/389-ds:3.0

ln -s /data/run /var/run/dirsrv
ln -s /data/run /var/run/dirsrv; \
chown -R dirsrv: /data;\
chown -R dirsrv: /run/dirsrv; \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: can we just set the permissions from start by changing line 135 to install -d -m 0755 -o .. -g .. /path/to/dir

ln -s /data/ssca /etc/dirsrv/ssca; \
ln -s /data/run /var/run/dirsrv
ln -s /data/run /var/run/dirsrv; \
chown -R dirsrv: /data;\
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

update the mkdir -p /data/config to install -d -o dirsrv -g dirsrv /data, install -d -o dirsrv -g dirsv /data/config

overall this only works for podman and cannot work for docker as the directory permissions are not preserved for volumes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can merge all mkdir commands into one install and group the chown commands.

install -d -o dirsrv -g dirsrv /data /data/config /data/ssca /data/run /var/run/dirsrv; \
ln -s /data/config /etc/dirsrv/slapd-localhost; \
ln -s /data/ssca /etc/dirsrv/ssca; \
ln -s /data/run /var/run/dirsrv; \
chown -R dirsrv:dirsrv /data /var/run/dirsrv; \
chgrp -R dirsrv /etc/dirsrv;

bci-pushman pushed a commit that referenced this pull request Nov 3, 2025
bci-pushman pushed a commit that referenced this pull request Nov 3, 2025
bci-pushman pushed a commit that referenced this pull request Nov 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants