Skip to content
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

Unable to run Update all (looks like some issue this time stamp) #1

Open
vushikamalla opened this issue Feb 2, 2024 · 0 comments
Open

Comments

@vushikamalla
Copy link

from cryptography.hazmat.backends import default_backend # noqa: F401
Scheduling job UPDATEALL
/root/lib/oracle-cli/lib64/python3.6/site-packages/oci/_vendor/httpsig_cffi/sign.py:10: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography will remove support for Python 3.6.
from cryptography.hazmat.backends import default_backend # noqa: F401
Usage: oci os-management scheduled-job create [OPTIONS]

Error: Missing option(s) --schedule-type, --time-next-execution.
date: invalid option -- 'v'
Try 'date --help' for more information.
./update_install_group.sh: line 29: --schedule-type: command not found
Scheduling job INSTALL
date: invalid option -- 'v'
Try 'date --help' for more information.
/root/lib/oracle-cli/lib64/python3.6/site-packages/oci/_vendor/httpsig_cffi/sign.py:10: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography will remove support for Python 3.6.
from cryptography.hazmat.backends import default_backend # noqa: F401
Usage: oci os-management scheduled-job create [OPTIONS]

Error: Invalid value for '--time-next-execution': Value --managed-instance-groups is not in a supported datetime format. The following datetime formats are supported:

YYYY-MM-DDTHH:mm:ss.ssssssTZD (UTC) with microseconds, e.g. 2017-09-15T20:30:00.123456Z
YYYY-MM-DDTHH:mm:ss.sssTZD (UTC) with milliseconds, e.g. 2017-09-15T20:30:00.123Z
YYYY-MM-DDTHH:mm:ssTZD (UTC) without milliseconds, e.g. 2017-09-15T20:30:00Z
YYYY-MM-DDTHH:mmTZD (UTC) with minute precision, e.g. 2017-09-15T20:30Z
YYYY-MM-DDTHH:mm:ssTZD (timzone with offset) with microseconds, e.g. 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
YYYY-MM-DDTHH:mm:ssTZD (timzone with offset) with milliseconds, e.g. 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
YYYY-MM-DDTHH:mm:ssTZD (timezone with offset) without milliseconds, e.g. 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
YYYY-MM-DDTHH:mmTZD (timezone with offset) with minute precision, e.g. 2017-09-15T12:35-08:00, 2017-09-15T12:35-0800
YYYY-MM-DD HH:mm, e.g. 2017-09-15 17:25. The timezone for this date will be taken as UTC. (Needs to be surrounded by single or double quotes)
YYYY-MM-DD, e.g. 2017-09-15. This date will be taken as midnight UTC of that day
Unix time in seconds, e.g. 1412195400

For OCI CLI commands and parameters suggestion, auto completion and other useful features, try the Interactive mode by typing oci -i.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant