[BUG] Automator fails when being run on existing BTP subaccount with CF org
AnatolManikalo opened this issue · 5 comments
Is there an existing issue for this?
- I have searched the existing issues
Are you using the latest docker image for BTPSA?
- I'm using the latest docker image for BTPSA.
Which area is mainly impacted
Cloud Foundry setups
Current Behavior
BTPSA fails to login and create Space on the existing subaccounts.
I have a subaccount created earlier, there are a couple of spaces inside. I want to run BTPSA to update some configurations.
BTPSA fails on # Create CF space step. Here's the log output:
####################################################################################################
# Create CF space >sapit-managed<
####################################################################################################
[2023-03-22 13:00:45] INFO : Logging-in to your CF environment in the org >sapit-home-dev-004< for your user >anatol.manikalo@sap.com<
[2023-03-22 13:00:45] RUN COMMAND: cf login -a 'https://api.cf.eu10-004.hana.ondemand.com' -o 'sapit-home-dev-004' -u 'anatol.manikalo@sap.com' -p 'xxxxxxxxxxxxxxxxx
[2023-03-22 13:00:47] ERROR : API endpoint: https://api.cf.eu10-004.hana.ondemand.com
Authenticating...
OK
Targeted org sapit-home-dev-004.
Select a space:
1. abap-home
2. idm_arm
3. launchpad-plugin
4. pranjal-demo-project
5. process-automation
6. sap-copilot-cf
7. service-taskcenter
8. test-project-johannes
9. universal-header
10. work-zone
API endpoint: https://api.cf.eu10-004.hana.ondemand.com
API version: 3.131.0
user: anatol.manikalo@sap.com
org: sapit-home-dev-004
space: No space targeted, use 'cf target -s SPACE'
FAILED
[2023-03-22 13:00:47] ERROR : inappropriate ioctl for device
Looks like script is waiting for an interactive reply from the user on which space too target to and then fails.
There's also ERROR : inappropriate ioctl for device — not sure if this is related
Expected Behavior
BTPSA logs in to CF CLI successfully and continues the setup
Steps To Reproduce
Run BTPSA from the docker container using attached usecase and parameters files on subaccount, which already exists
Logs and configuration files available?
Anything else?
No response
Can you share your parameter file with us? If not, did you use the parameter to define the space you want to use (cfspacename)? If you didn't, the cf cli doesn't know which one to take and ask for the right selection.
It's attached to the zip archive. The space name is mentioned, however, it doesn't exist on the subaccount yet.
Usecase: we are using managed space for central services (such as HANA instance to be shared with other spaces). Other spaces already exist on the subaccount, but space from the parameters file is to be created by running BTPSA.
I also just tested it with the existing space. I updated parameters.json file to contain "cfspacename": "idm_arm" (this space exists on the subaccount) but got the same error:
Fix is available on dev branch and in the dev image
Fix is available in main with release 1.7.0