Can't have multiple sessions to one physical host.
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 737
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Lets say I have one physical host:
skeletor.dupa.net
this host contains two lxc containers one listens on 1111 and other one on 2222, if my ini file looks like:
[foo]
skeletor.dupa.net port=11111
skeletor.dupa.net port=22222
rex connects only to one of them.
$ rex -G foo uptime
[2015-05-11 17:08:12] INFO - Running task uptime on skeletor.dupa.net
[2015-05-11 17:08:12] INFO - Connecting to skeletor.dupa.net:22222 (root)
[2015-05-11 17:08:14] INFO - Connecting to skeletor.dupa.net:22222 (root)
[2015-05-11 17:08:16] INFO - Connecting to skeletor.dupa.net:22222 (root)
[2015-05-11 17:08:17] WARN - Can't connect to skeletor.dupa.net
[2015-05-11 17:08:17] WARN - Error running task/batch: Couldn't connect to skeletor.dupa.net. at /usr/share/perl5/Rex/TaskList/Base.pm line 295.
[2015-05-11 17:08:17] INFO - Exiting Rex...
[2015-05-11 17:08:17] INFO - Cleaning up...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using the shown ini entries and rex -G foo uptime, then trace how Rex identifies and stores sessions for the two host entries. Done means both configured ports are treated as distinct targets and the task reaches both containers rather than repeatedly using one port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100