Configuring non root sudoer for molecule tests #96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SequeI
force-pushed
the
asiek/moleculeUser
branch
3 times, most recently
from
a1d33d1
to
91f814f
Compare
bkabrda
requested changes
Nov 14, 2024
SequeI
force-pushed
the
asiek/moleculeUser
branch
16 times, most recently
from
29448be
to
d5baf9f
Compare
bkabrda
requested changes
Nov 18, 2024
|
It seems that something is wrong with the way password is provided/used. From the failed task: |
SequeI
force-pushed
the
asiek/moleculeUser
branch
5 times, most recently
from
dbad4da
to
19f6222
Compare
|
OIDC instance down so CI won't pass + createtree container fails to spin up on centOS but is fine on RHEL. Will test again once identity instance is back to remove an outside factor in failure but all works as it should on a RHEL machine. |
SequeI
force-pushed
the
asiek/moleculeUser
branch
from
19f6222
to
b666c4a
Compare
SequeI
force-pushed
the
asiek/moleculeUser
branch
from
cae303f
to
b1850e3
Compare
SequeI
commented
Dec 2, 2024
molecule/testing_user_setup.yaml
Outdated
| create_home: yes | ||
|
|
||
| - name: Set password for testingUser | ||
| ansible.builtin.shell: echo {{ item.password }} | passwd --stdin {{ item.user }} |
There was a problem hiding this comment.
Manually setting the password, using user.password previously resulted in constant password errors for some reason
|
I constantly ran into the createtree issue before today, but after rebasing with the new Dex OIDC config + changing a small discrepancy it seems to work fine? Still not sure what the underlying issue was |
SequeI
force-pushed
the
asiek/moleculeUser
branch
from
1627670
to
c2fca54
Compare
bkabrda
approved these changes
Dec 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding Redis config which I forgot in initial scenario PR for user_provided
Adding non-root sudoer configuration for our scenario tests to emulate a real user environment
Changed shell commands to ansible collections, such as lineinfile
(Waiting for tf access so I can personally snoop around our molecule scenarios on a tf vm before merge)