-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump broker[docker,hussh,podman] from 0.5.7 to 0.6.2 #16691
base: master
Are you sure you want to change the base?
Conversation
trigger: test-robottelo\r |
PRT Result
|
09bfe87
to
f1022d4
Compare
trigger: test-robottelo\r |
PRT Result
|
@omkarkhatavkar @jyejare can you determine why the PRT runs aren't actually installing the updated version of the requirements.txt? Is that an explicit step we need to add to the PRT job setup?
|
@JacobCallahan It is installing the updated requirements but the pytest plugin for mismatch reqs was not updated for the recent changes. The PR is raised in robottelo to handle that and you won't see those warnings again. |
@jyejare The pip freeze output in artifacts still shows broker==0.5.7. Additionally, log lines don't match up with their correct position in Broker 0.6.2. Can we verify that we are actually re-running an install of requirements.txt? |
@JacobCallahan The build artifacts / logs showing 0.6.2. Are they showing for you locally?
Do you mean the name of the broker as a requirement
In CI checks we are not updating the requirements, we are installing all fresh and its working as expected I see. But with req update plugin, we need to mention the option to update all / required reqs then only it updates. Also the update only happens for mismatch requirements and git repositories. All things are now improved in #16692 I may misunderstood something here and open to here from you back. |
@JacobCallahan Do we still have requirements mismatch issues with this PR? Just curious what's pending on this update? |
trigger: test-robottelo |
PRT Result
|
All of the failures here look to be related to the disconnect between the current config and new config. |
@JacobCallahan We have ACKed the CI MR, but the lining is failing in the CI MR blocking it from merging and proceeding further on that MRs / this PRs merge. |
@JacobCallahan Can we rebase the branch? The Jenkins MR's component pipelines are failing due to the missing ipa.group_users config?
|
These changes #16536 must be in this pr. |
@dependabot rebase |
Bumps [broker[docker,hussh,podman]](https://github.com/SatelliteQE/broker) from 0.5.7 to 0.6.2. - [Release notes](https://github.com/SatelliteQE/broker/releases) - [Commits](SatelliteQE/broker@0.5.7...0.6.2) --- updated-dependencies: - dependency-name: broker[docker,hussh,podman] dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
f1022d4
to
1a65b8d
Compare
PRT Result
|
Bumps broker[docker,hussh,podman] from 0.5.7 to 0.6.2.
Release notes
Sourced from broker[docker,hussh,podman]'s releases.
Commits
03456dc
Add checks for bad input for AT provider help paths27a9edb
Remove deprecated method for pulling AnsibleTower host factsecd66d6
More fixes55d312a
Bump pypa/gh-action-pypi-publish from 1.10.1 to 1.10.337ae95b
Quick fix for https config sourcesb8f46f1
Small workaround for container syncingc37ea1c
Update broker/helpers.py54b13f7
Adjust a couple of migrationsf26a40d
Add in the sad ability to lessen color output for richc1d0c7d
Rework inventory cliYou can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)