stages/systemd.unit.create: fix DefaultDependencies option#608
stages/systemd.unit.create: fix DefaultDependencies option#608say-paul wants to merge 16 commits intoosbuild:mainfrom
Conversation
|
Thanks for spotting this and fixing it. |
4c7f966 to
e0854a5
Compare
|
Something's not right with the change in the systemd service's exec line changes because the boot test is showing that service is failing to start now. |
|
I opened #613 that prints failed unit status outputs in the boot test so cases like these are easier to troubleshoot without reproducing by hand. |
e0854a5 to
81f6e0b
Compare
|
@say-paul https://gitlab.com/redhat/services/products/image-builder/ci/images/-/jobs/6699182166 |
|
hmmh..!! thought -p would take care of it |
|
Yeah it's strange. I wonder if the change in the way the |
|
This will need to be rebased once #632 is merged. |
81f6e0b to
5a74143
Compare
Added a function to pass the bool as pointer. DefaultDependencies in systemd is by default set as true and needs to be exluscively set as false which is oppositeof golangs syntax omitempty. Leaving out omitempty causes the default dependencies to be set as false by default which will cause the service to behave abnormally as its by default set to true in systemd world. Signed-off-by: Sayan Paul <paul.sayan@gmail.com>
bash command refactoring for osbuild-ostree-mountpoints.service for the ExecStartPre,ExecStopPost Signed-off-by: Sayan Paul <paul.sayan@gmail.com>
5a74143 to
f328016
Compare
Currently creating a customization for the root user does not work because `/var/roothome` may not be avaialble in the image. This commit ensures it is created if needed just like we do for `/var/home`. Closes osbuild/bootc-image-builder#143
Bumps the go-deps group with 1 update: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go). Updates `github.com/aws/aws-sdk-go` from 1.51.30 to 1.51.31 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.51.30...v1.51.31) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the go-deps group with 2 updates: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) and [google.golang.org/api](https://github.com/googleapis/google-api-go-client). Updates `github.com/aws/aws-sdk-go` from 1.51.31 to 1.51.32 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Changelog](https://github.com/aws/aws-sdk-go/blob/main/CHANGELOG_PENDING.md) - [Commits](aws/aws-sdk-go@v1.51.31...v1.51.32) Updates `google.golang.org/api` from 0.176.1 to 0.177.0 - [Release notes](https://github.com/googleapis/google-api-go-client/releases) - [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md) - [Commits](googleapis/google-api-go-client@v0.176.1...v0.177.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps - dependency-name: google.golang.org/api dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the go-deps group with 2 updates: [cloud.google.com/go/compute](https://github.com/googleapis/google-cloud-go) and [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go). Updates `cloud.google.com/go/compute` from 1.25.1 to 1.26.0 - [Release notes](https://github.com/googleapis/google-cloud-go/releases) - [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/documentai/CHANGES.md) - [Commits](googleapis/google-cloud-go@pubsub/v1.25.1...pubsub/v1.26.0) Updates `github.com/aws/aws-sdk-go` from 1.51.32 to 1.52.0 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.51.32...v1.52.0) --- updated-dependencies: - dependency-name: cloud.google.com/go/compute dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the go-deps group with 1 update: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go). Updates `github.com/aws/aws-sdk-go` from 1.52.0 to 1.52.1 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.52.0...v1.52.1) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Our RHEL Edge deployments (ISOs and disk images) had inconsistent osnames set. The edge-installer used "rhel" while the simplified installer and disk image used "redhat". For bonus inconsistency, the RHEL Edge ISOs created by the Edge Service modify the kickstart file to set the osname to "rhel-edge". Meanwhile, Fedora IoT images all set the osname to "fedora-iot". To make everything consistent and unify the names, let's set all osnames to "rhel-edge". This aligns better with Fedora (the equivalent to "fedora-iot" in the RHEL world is "rhel-edge") and with what has already been happening in the service. Practically, the osname sets the deployment path: /ostree/deploy/$OSNAME so this will affect new deployments, but will have no effect on existing installations and upgrades.
We need to create a drop-in file that will enable insights-client.service to run on boot for edge systems. Ref: HMS-4031
Insights-client collection must occur at boot time so that the current ostree commit hash can be reflected after upgrade. Otherwise, the upgrade shows as failed in the console UI. Add a drop-in file that enables insights-client.service to run on successful boot. Ref: HMS-4031
- Hold back C9S due to RHEL-29559. - Hold back RHEL 10 because dhcp-client is not included in the newer snapshots (RHEL-26304).
Bumps the go-deps group with 3 updates: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go), [golang.org/x/oauth2](https://github.com/golang/oauth2) and [golang.org/x/sys](https://github.com/golang/sys). Updates `github.com/aws/aws-sdk-go` from 1.52.1 to 1.52.2 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.52.1...v1.52.2) Updates `golang.org/x/oauth2` from 0.19.0 to 0.20.0 - [Commits](golang/oauth2@v0.19.0...v0.20.0) Updates `golang.org/x/sys` from 0.19.0 to 0.20.0 - [Commits](golang/sys@v0.19.0...v0.20.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps - dependency-name: golang.org/x/oauth2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps - dependency-name: golang.org/x/sys dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the go-deps group with 1 update: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go). Updates `github.com/aws/aws-sdk-go` from 1.52.2 to 1.52.3 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.52.2...v1.52.3) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Sayan Paul <paul.sayan@gmail.com>
When testing with "pinned" osbuild commit IDs (defined in the Schutzfile), we set up a repository based on the commit ID that should exist for each commit in osbuild that had a (partially) successful CI run (the RPM jobs should at least run successfully). When a repository doesn't exist for whatever reason (the CI pipeline failed, the commit ID was copied incorrectly, etc), the setup script wouldn't fail and osbuild would be installed from the system repositories. This means that we're not testing what we think we are testing. In the best case our build jobs fail because the osbuild version in the repos isn't new enough to have all the features we're testing, but we might also end up having passing tests that aren't testing what we want, for example a change in osbuild internals that's on an open PR and we want to verify that none or our test image builds are broken. Make the setup-osbuild-repo script check that the repository metadata is reachable and exit with an error if it's not, making any test pipeline that requires it fail when necessary instead of silently skipping the repo configuration.
Bumps the go-deps group with 2 updates: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) and [google.golang.org/api](https://github.com/googleapis/google-api-go-client). Updates `github.com/aws/aws-sdk-go` from 1.52.3 to 1.52.4 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.52.3...v1.52.4) Updates `google.golang.org/api` from 0.177.0 to 0.178.0 - [Release notes](https://github.com/googleapis/google-api-go-client/releases) - [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md) - [Commits](googleapis/google-api-go-client@v0.177.0...v0.178.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: go-deps - dependency-name: google.golang.org/api dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-deps ... Signed-off-by: dependabot[bot] <support@github.com>
|
Replaced by #668 |
Added a function to pass the bool as pointer.
DefaultDependencies in systemd is by default set as true and needs to be exluscively set as false which is oppositeof golangs syntax omitempty. Leaving out omitempty causes the default dependencies to be set as false by default which will cause the service to behave abnormally as its by default set to true in systemd world.
This PR will fix the behavior
Also refactored the bash scripts for osbuild-ostree-mountpoints.service requird for custom-file-system feature